Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-31 Thread Bienlein via Digitalmars-d-announce
Java programmers are having to come to terms with this. Python programmers sort of have, except that BDFL has failed to accept the correct end point and still likes loops. Scala has done it all wrong. (Further opinions available on request :-) Could you provide some sample Scala code to

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-31 Thread Paolo Invernizzi via Digitalmars-d-announce
On Monday, 30 March 2015 at 18:20:39 UTC, Walter Bright wrote: Well put. My brain still thinks in terms of loops. Sadly, mine also... ;-P

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-31 Thread Laeeth Isharc via Digitalmars-d-announce
On Tuesday, 31 March 2015 at 02:05:05 UTC, Andrei Alexandrescu wrote: On 3/30/15 12:29 AM, Jonathan M Davis via Digitalmars-d-announce wrote: On Saturday, March 28, 2015 14:19:46 Walter Bright via Digitalmars-d-announce wrote: Thank you. I need to learn std.algorithm better. Don't we all.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-31 Thread Andrei Alexandrescu via Digitalmars-d-announce
On 3/31/15 1:19 AM, Laeeth Isharc wrote: On Tuesday, 31 March 2015 at 02:05:05 UTC, Andrei Alexandrescu wrote: On 3/30/15 12:29 AM, Jonathan M Davis via Digitalmars-d-announce wrote: On Saturday, March 28, 2015 14:19:46 Walter Bright via Digitalmars-d-announce wrote: Thank you. I need to

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-31 Thread via Digitalmars-d-announce
On Tuesday, 31 March 2015 at 08:35:47 UTC, Andrei Alexandrescu wrote: I've offered a number of times to write a slides-like tutorial if anyone wants to do the slides logic. Nobody came about. Probably nobody will, so I'll have to do it myself. What do you mean by slides logic? What are you

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-31 Thread Laeeth Isharc via Digitalmars-d-announce
Then we need more examples and tutorials. -- Andrei how are these to appear? I've offered a number of times to write a slides-like tutorial if anyone wants to do the slides logic. Nobody came about. Probably nobody will, so I'll have to do it myself. Sorry for my denseness, but what is

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-31 Thread ketmar via Digitalmars-d-announce
On Tue, 31 Mar 2015 01:35:47 -0700, Andrei Alexandrescu wrote: We need to do better at empowering people. it's fairly easy: just pay them for the tasks. most people using D to solve *their* task at hand, and if they see something wrong, they report it as an issue (sometimes) and go on with

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-31 Thread Panke via Digitalmars-d-announce
Umm that was me... I don't feel confident enough to write at a Phobos standard yet and might be a little while before I am experienced enough. But I see your point. Fastest way to get better is to submit PRs and get reviewed.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-31 Thread Andrei Alexandrescu via Digitalmars-d-announce
On 3/31/15 3:40 AM, Laeeth Isharc wrote: Then we need more examples and tutorials. -- Andrei how are these to appear? I've offered a number of times to write a slides-like tutorial if anyone wants to do the slides logic. Nobody came about. Probably nobody will, so I'll have to do it myself.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Jonathan M Davis via Digitalmars-d-announce
On Saturday, March 28, 2015 14:19:46 Walter Bright via Digitalmars-d-announce wrote: Thank you. I need to learn std.algorithm better. Don't we all. Part of the problem with std.algorithm is its power. It's frequently the case that you think that something isn't there when it's either there

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Paulo Pinto via Digitalmars-d-announce
On Sunday, 29 March 2015 at 22:07:40 UTC, Laeeth Isharc wrote: should we add a link to the wiki and ask author if we could mirror there ? This section on wiki looks like it could with a bit of fleshing out! http://wiki.dlang.org/Coming_From/Python I just seen what you did in the wiki,

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Gary Willoughby via Digitalmars-d-announce
On Monday, 30 March 2015 at 00:20:11 UTC, Laeeth Isharc wrote: https://www.quora.com/Why-didnt-D-language-become-mainstream-comparing-to-Golang Post this on reddit.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Paulo Pinto via Digitalmars-d-announce
On Monday, 30 March 2015 at 03:26:14 UTC, deadalnix wrote: On Sunday, 29 March 2015 at 16:32:32 UTC, Idan Arye wrote: Computer science is all about tradeoffs. I used to love Ruby, but then a Rails project got out of hand... Nowadays I use it mainly as a bash replacement - Hundredfolds more

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread via Digitalmars-d-announce
On Sunday, 29 March 2015 at 19:03:06 UTC, Laeeth Isharc wrote: On Sunday, 29 March 2015 at 15:34:35 UTC, Ola Fosheim Grøstad wrote: Actually, there is quite a large overlap if you look beyond the syntax. Dart is completely unexciting, but I also find it very productive when used with the IDE.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread ketmar via Digitalmars-d-announce
On Mon, 30 Mar 2015 00:29:46 -0700, Jonathan M Davis via Digitalmars-d-announce wrote: On Saturday, March 28, 2015 14:19:46 Walter Bright via Digitalmars-d-announce wrote: Thank you. I need to learn std.algorithm better. Don't we all. Part of the problem with std.algorithm is its power.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Paulo Pinto via Digitalmars-d-announce
On Monday, 30 March 2015 at 08:53:15 UTC, Ola Fosheim Grøstad wrote: On Sunday, 29 March 2015 at 19:03:06 UTC, Laeeth Isharc wrote: On Sunday, 29 March 2015 at 15:34:35 UTC, Ola Fosheim Grøstad wrote: Actually, there is quite a large overlap if you look beyond the syntax. Dart is completely

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Idan Arye via Digitalmars-d-announce
On Monday, 30 March 2015 at 07:45:50 UTC, Paulo Pinto wrote: On Monday, 30 March 2015 at 03:26:14 UTC, deadalnix wrote: On Sunday, 29 March 2015 at 16:32:32 UTC, Idan Arye wrote: Computer science is all about tradeoffs. I used to love Ruby, but then a Rails project got out of hand... Nowadays

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Laeeth Isharc via Digitalmars-d-announce
On Monday, 30 March 2015 at 07:29:56 UTC, Jonathan M Davis wrote: On Saturday, March 28, 2015 14:19:46 Walter Bright via Digitalmars-d-announce wrote: Thank you. I need to learn std.algorithm better. Don't we all. Part of the problem with std.algorithm is its power. It's frequently the case

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Laeeth Isharc via Digitalmars-d-announce
On Monday, 30 March 2015 at 08:53:15 UTC, Ola Fosheim Grøstad wrote: same theme. I pick them based on what they+ecosystem is good at, not the language by itself. So basically, you have to be best at one particular application area to do well. Go is aiming to have a good runtime for building

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread bearophile via Digitalmars-d-announce
Ola Fosheim Grøstad: So, it will just fade way in the sea of JavaScript wannabe replacements. Maybe, but Google is using it for Google Ads. Which is their primary business? Still, a bit early to say what happens next. Perhaps next some kind of blend of Typescript and Dart will become part

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread via Digitalmars-d-announce
On Monday, 30 March 2015 at 10:04:11 UTC, Paulo Pinto wrote: Very dark as Angular team decided to look for Typescript instead[0]. It isn't very dark though, they cooperate with MS to build atscript features into Typescript instead. The two dialect were always meant to be merged at some

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread via Digitalmars-d-announce
On Monday, 30 March 2015 at 10:45:50 UTC, bearophile wrote: Ola Fosheim Grøstad: So, it will just fade way in the sea of JavaScript wannabe replacements. Maybe, but Google is using it for Google Ads. Which is their primary business? Still, a bit early to say what happens next. Perhaps

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Walter Bright via Digitalmars-d-announce
On 3/30/2015 12:29 AM, Jonathan M Davis via Digitalmars-d-announce wrote: On Saturday, March 28, 2015 14:19:46 Walter Bright via Digitalmars-d-announce wrote: Thank you. I need to learn std.algorithm better. Don't we all. Part of the problem with std.algorithm is its power. It's frequently

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread weaselcat via Digitalmars-d-announce
On Monday, 30 March 2015 at 12:04:22 UTC, Laeeth Isharc wrote: On Monday, 30 March 2015 at 07:29:56 UTC, Jonathan M Davis wrote: On Saturday, March 28, 2015 14:19:46 Walter Bright via Digitalmars-d-announce wrote: Thank you. I need to learn std.algorithm better. Don't we all. Part of the

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Walter Bright via Digitalmars-d-announce
On 3/30/2015 11:53 AM, weaselcat wrote: speaking of optimization, are there any guarantees(documented?) on the kind of optimizations you should expect from range programming in D(i.e, function chaining) similar to Haskell's stream fusion? No. It's a QoI issue.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Walter Bright via Digitalmars-d-announce
On 3/30/2015 11:41 AM, Russel Winder via Digitalmars-d-announce wrote: Java programmers are having to come to terms with this. Python programmers sort of have, except that BDFL has failed to accept the correct end point and still likes loops. Scala has done it all wrong. (Further opinions

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Russel Winder via Digitalmars-d-announce
On Mon, 2015-03-30 at 11:20 -0700, Walter Bright via Digitalmars-d-announce wrote: […] Even Andrei, who wrote most of std.algorithm, posted here recently how he was surprised at how powerful it was. An indicator of plagiarism? ;-) -- Russel.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread weaselcat via Digitalmars-d-announce
On Monday, 30 March 2015 at 18:41:17 UTC, Russel Winder wrote: On Mon, 2015-03-30 at 11:19 -0700, Walter Bright via Digitalmars-d-announce wrote: […] My brain still thinks in terms of loops. The excellent influence of functional programming on imperative programming is implicit iteration and

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Russel Winder via Digitalmars-d-announce
On Mon, 2015-03-30 at 11:19 -0700, Walter Bright via Digitalmars-d-announce wrote: […] My brain still thinks in terms of loops. The excellent influence of functional programming on imperative programming is implicit iteration and higher-order functions. Any explicit for/while loop in a

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-30 Thread Andrei Alexandrescu via Digitalmars-d-announce
On 3/30/15 12:29 AM, Jonathan M Davis via Digitalmars-d-announce wrote: On Saturday, March 28, 2015 14:19:46 Walter Bright via Digitalmars-d-announce wrote: Thank you. I need to learn std.algorithm better. Don't we all. Part of the problem with std.algorithm is its power. It's frequently the

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread deadalnix via Digitalmars-d-announce
On Sunday, 29 March 2015 at 16:32:32 UTC, Idan Arye wrote: Computer science is all about tradeoffs. I used to love Ruby, but then a Rails project got out of hand... Nowadays I use it mainly as a bash replacement - Hundredfolds more expressive, only a tiny tiny bit syntax overhead, and for

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread deadalnix via Digitalmars-d-announce
On Sunday, 29 March 2015 at 21:43:21 UTC, Walter Bright wrote: On 3/28/2015 5:34 PM, ketmar wrote: on the other side of the spectrum was Chuck Moore, for example, who imagines modern computers filled with many cheap and average RISC processors, and using parallel multiprocessor execution to

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Laeeth Isharc via Digitalmars-d-announce
On Thursday, 26 March 2015 at 08:44:20 UTC, Gary Willoughby wrote: I wrote the article in a rush last night (girlfriend calling me to bed) and as a result it has a few spelling/grammar errors which I've hopefully corrected. The article is a total rant about Go after using it over the last

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread deadalnix via Digitalmars-d-announce
On Sunday, 29 March 2015 at 08:37:54 UTC, Idan Arye wrote: On Saturday, 28 March 2015 at 18:47:04 UTC, Walter Bright wrote: On 3/28/2015 3:20 AM, Jonathan M Davis via Digitalmars-d-announce wrote: Personally, I'm not sure that much is gained in pitting Go against D precisely because they're so

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Joakim via Digitalmars-d-announce
On Monday, 30 March 2015 at 00:20:11 UTC, Laeeth Isharc wrote: https://www.quora.com/Why-didnt-D-language-become-mainstream-comparing-to-Golang fwiw Nice, well-written answer, enjoyed reading it.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread deadalnix via Digitalmars-d-announce
On Saturday, 28 March 2015 at 14:33:14 UTC, Russel Winder wrote: On Sat, 2015-03-28 at 12:52 +0100, Sönke Ludwig via Digitalmars-d-announce wrote: […] You can access TLS from an event callback just as easy as from a fiber. […] TLS is the evil here. Anyone working with TLS is either writing

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Laeeth Isharc via Digitalmars-d-announce
On Monday, 30 March 2015 at 03:47:45 UTC, Joakim wrote: On Monday, 30 March 2015 at 00:20:11 UTC, Laeeth Isharc wrote: https://www.quora.com/Why-didnt-D-language-become-mainstream-comparing-to-Golang fwiw Nice, well-written answer, enjoyed reading it. Thank you.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread ketmar via Digitalmars-d-announce
On Sun, 29 Mar 2015 14:43:14 -0700, Walter Bright wrote: On 3/28/2015 5:34 PM, ketmar wrote: on the other side of the spectrum was Chuck Moore, for example, who imagines modern computers filled with many cheap and average RISC processors, and using parallel multiprocessor execution to achieve

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Andrei Alexandrescu via Digitalmars-d-announce
On 3/29/15 4:43 AM, Marc =?UTF-8?B?U2Now7x0eiI=?= schue...@gmx.net wrote: On Sunday, 29 March 2015 at 08:37:54 UTC, Idan Arye wrote: On Saturday, 28 March 2015 at 18:47:04 UTC, Walter Bright wrote: On 3/28/2015 3:20 AM, Jonathan M Davis via Digitalmars-d-announce wrote: Personally, I'm not

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread cym13 via Digitalmars-d-announce
On Sunday, 29 March 2015 at 12:21:01 UTC, Ola Fosheim Grøstad wrote: On Sunday, 29 March 2015 at 02:15:38 UTC, cym13 wrote: Moreover, it is possible to reach a good expressiveness (maybe not as good as python, but that's the whole goal of python so there's no shame in not matching it). There

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread via Digitalmars-d-announce
On Sunday, 29 March 2015 at 02:15:38 UTC, cym13 wrote: Moreover, it is possible to reach a good expressiveness (maybe not as good as python, but that's the whole goal of python so there's no shame in not matching it). There are many alternatives to Python. Like Nim or Dart:

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Idan Arye via Digitalmars-d-announce
On Sunday, 29 March 2015 at 15:57:18 UTC, Andrei Alexandrescu wrote: On 3/29/15 4:43 AM, Marc =?UTF-8?B?U2Now7x0eiI=?= schue...@gmx.net wrote: On Sunday, 29 March 2015 at 08:37:54 UTC, Idan Arye wrote: On Saturday, 28 March 2015 at 18:47:04 UTC, Walter Bright wrote: On 3/28/2015 3:20 AM,

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Idan Arye via Digitalmars-d-announce
On Saturday, 28 March 2015 at 18:47:04 UTC, Walter Bright wrote: On 3/28/2015 3:20 AM, Jonathan M Davis via Digitalmars-d-announce wrote: Personally, I'm not sure that much is gained in pitting Go against D precisely because they're so different that they're likely to appeal to completely

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Laeeth Isharc via Digitalmars-d-announce
On Sunday, 29 March 2015 at 02:15:38 UTC, cym13 wrote: Urr As an active Python developer, I find that one pretty harsh. It's not that we need to enforce good style, it's that we take good style as granted and choose to lighten it consequently. On the contrary I think that D has

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread weaselcat via Digitalmars-d-announce
On Sunday, 29 March 2015 at 19:09:52 UTC, Laeeth Isharc wrote: On Sunday, 29 March 2015 at 02:15:38 UTC, cym13 wrote: Urr As an active Python developer, I find that one pretty harsh. It's not that we need to enforce good style, it's that we take good style as granted and choose to lighten

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Laeeth Isharc via Digitalmars-d-announce
On Sunday, 29 March 2015 at 15:34:35 UTC, Ola Fosheim Grøstad wrote: Actually, there is quite a large overlap if you look beyond the syntax. Dart is completely unexciting, but I also find it very productive when used with the IDE. Glad to hear this - I haven't yet got very far with Dart, but

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread cym13 via Digitalmars-d-announce
On Sunday, 29 March 2015 at 19:09:52 UTC, Laeeth Isharc wrote: As an active Python developer, what would you add to or change about the following: http://bitbashing.io/2015/01/26/d-is-like-native-python.html I like this article very much. IMO python's generators and list comprehensions are

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Laeeth Isharc via Digitalmars-d-announce
On Sunday, 29 March 2015 at 19:44:01 UTC, cym13 wrote: On Sunday, 29 March 2015 at 19:09:52 UTC, Laeeth Isharc wrote: As an active Python developer, what would you add to or change about the following: http://bitbashing.io/2015/01/26/d-is-like-native-python.html I like this article very

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Walter Bright via Digitalmars-d-announce
On 3/29/2015 12:09 PM, Laeeth Isharc wrote: As an active Python developer, what would you add to or change about the following: http://bitbashing.io/2015/01/26/d-is-like-native-python.html Has someone reddit-ized it?

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread cym13 via Digitalmars-d-announce
On Sunday, 29 March 2015 at 21:45:23 UTC, Walter Bright wrote: On 3/29/2015 12:09 PM, Laeeth Isharc wrote: As an active Python developer, what would you add to or change about the following: http://bitbashing.io/2015/01/26/d-is-like-native-python.html Has someone reddit-ized it? It seems

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Walter Bright via Digitalmars-d-announce
On 3/29/2015 2:46 PM, cym13 wrote: On Sunday, 29 March 2015 at 21:45:23 UTC, Walter Bright wrote: On 3/29/2015 12:09 PM, Laeeth Isharc wrote: As an active Python developer, what would you add to or change about the following: http://bitbashing.io/2015/01/26/d-is-like-native-python.html Has

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread cym13 via Digitalmars-d-announce
On Sunday, 29 March 2015 at 21:06:28 UTC, Laeeth Isharc wrote: On Sunday, 29 March 2015 at 19:44:01 UTC, cym13 wrote: On Sunday, 29 March 2015 at 19:09:52 UTC, Laeeth Isharc wrote: As an active Python developer, what would you add to or change about the following:

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-29 Thread Laeeth Isharc via Digitalmars-d-announce
should we add a link to the wiki and ask author if we could mirror there ? This section on wiki looks like it could with a bit of fleshing out! http://wiki.dlang.org/Coming_From/Python I just seen what you did in the wiki, that's great! I don't have much time to invest tonight but I'll

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Walter Bright via Digitalmars-d-announce
On 3/27/2015 12:34 PM, w0rp wrote: Sean Parent's advice for no raw loops comes to mind. https://channel9.msdn.com/Events/GoingNative/2013/Cpp-Seasoning With that rule, basically a one-line body for foreach becomes acceptable. This really is a great video. Which leads me to wonder why

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread ketmar via Digitalmars-d-announce
On Sat, 28 Mar 2015 18:39:34 +, Russel Winder via Digitalmars-d-announce wrote: yet current CPUs are still the same as 50 years before, that is the problem. ;-) I'd suggest that a Intel x86_64 of 2015 bears only a passing relationship to an IBM 360 of the 1960s. but core principles are

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Dicebot via Digitalmars-d-announce
On Saturday, 28 March 2015 at 19:16:32 UTC, Russel Winder wrote: If you write your software to fit a particular platform, including hardware features, then you are writing an operating system dedicated to that one specific platform and no other. Yes and I believe writing dedicated

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread ketmar via Digitalmars-d-announce
On Sat, 28 Mar 2015 19:17:23 +, Russel Winder via Digitalmars-d-announce wrote: It is a pity that D is not pitching as a Python replacement. D can't: it doesn't dumb enough to attract people that requires compiler enforcements on whitespace to correctly format their code. signature.asc

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Sönke Ludwig via Digitalmars-d-announce
Am 28.03.2015 um 19:51 schrieb Walter Bright: On 3/28/2015 8:41 AM, Sönke Ludwig wrote: Am 28.03.2015 um 15:33 schrieb Russel Winder via Digitalmars-d-announce: TLS is the evil here. Anyone working with TLS is either writing an operating system or doing it wrong. As long as we are talking

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Walter Bright via Digitalmars-d-announce
On 3/28/2015 3:20 AM, Jonathan M Davis via Digitalmars-d-announce wrote: Personally, I'm not sure that much is gained in pitting Go against D precisely because they're so different that they're likely to appeal to completely different sets of people. I also do not regard Go as a competitor to

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread weaselcat via Digitalmars-d-announce
On Saturday, 28 March 2015 at 18:47:04 UTC, Walter Bright wrote: On 3/28/2015 3:20 AM, Jonathan M Davis via Digitalmars-d-announce wrote: Personally, I'm not sure that much is gained in pitting Go against D precisely because they're so different that they're likely to appeal to completely

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Walter Bright via Digitalmars-d-announce
On 3/28/2015 8:41 AM, Sönke Ludwig wrote: Am 28.03.2015 um 15:33 schrieb Russel Winder via Digitalmars-d-announce: TLS is the evil here. Anyone working with TLS is either writing an operating system or doing it wrong. As long as we are talking about a closed system that works exclusively on

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Russel Winder via Digitalmars-d-announce
On Sat, 2015-03-28 at 18:55 +, Dicebot via Digitalmars-d-announce wrote: […] I don't think it is that simple. From the purist academical parallelism POV - most likely. In practice it often can be quite the contrary, TLS is your best friend (depending on how efficient platfrom

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Russel Winder via Digitalmars-d-announce
On Sat, 2015-03-28 at 18:51 +, weaselcat via Digitalmars-d-announce wrote: On Saturday, 28 March 2015 at 18:47:04 UTC, Walter Bright wrote: On 3/28/2015 3:20 AM, Jonathan M Davis via Digitalmars-d-announce wrote: Personally, I'm not sure that much is gained in pitting Go against D

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Peter Alexander via Digitalmars-d-announce
On Saturday, 28 March 2015 at 20:35:07 UTC, Walter Bright wrote: On 3/27/2015 12:34 PM, w0rp wrote: Sean Parent's advice for no raw loops comes to mind. https://channel9.msdn.com/Events/GoingNative/2013/Cpp-Seasoning With that rule, basically a one-line body for foreach becomes acceptable.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Sönke Ludwig via Digitalmars-d-announce
Am 28.03.2015 um 21:51 schrieb Walter Bright: On 3/28/2015 1:32 PM, Sönke Ludwig wrote: I/O is crucial of course, but there are also a lot of other important and inherently impure things such as message passing. If the message channel is passed as a parameter to the droutine, then the

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Walter Bright via Digitalmars-d-announce
On 3/28/2015 3:24 PM, Sönke Ludwig wrote: If you ask me, they are very practical as they are - in fact much more practical than if they could move between threads, not just because of purity or not. I'm for example heavily using vibe.d's tasks for all kinds of UI, 3D graphics, sound and physics

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Dicebot via Digitalmars-d-announce
On Saturday, 28 March 2015 at 14:33:14 UTC, Russel Winder wrote: On Sat, 2015-03-28 at 12:52 +0100, Sönke Ludwig via Digitalmars-d-announce wrote: […] You can access TLS from an event callback just as easy as from a fiber. […] TLS is the evil here. Anyone working with TLS is either writing

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Walter Bright via Digitalmars-d-announce
On 3/28/2015 2:01 PM, Peter Alexander wrote: On Saturday, 28 March 2015 at 20:35:07 UTC, Walter Bright wrote: On 3/27/2015 12:34 PM, w0rp wrote: Sean Parent's advice for no raw loops comes to mind. https://channel9.msdn.com/Events/GoingNative/2013/Cpp-Seasoning With that rule, basically a

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread ketmar via Digitalmars-d-announce
On Sat, 28 Mar 2015 18:41:04 +, weaselcat wrote: On Saturday, 28 March 2015 at 17:57:35 UTC, ketmar wrote: On Sat, 28 Mar 2015 14:28:00 +, Russel Winder via Digitalmars-d-announce wrote: It could be argued that it is all just co-routines underneath, but I think that would be missing

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread ketmar via Digitalmars-d-announce
On Sun, 29 Mar 2015 02:15:38 +, cym13 wrote: On Sunday, 29 March 2015 at 00:24:36 UTC, ketmar wrote: On Sat, 28 Mar 2015 19:17:23 +, Russel Winder via Digitalmars-d-announce wrote: It is a pity that D is not pitching as a Python replacement. D can't: it doesn't dumb enough to

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Walter Bright via Digitalmars-d-announce
On 3/28/2015 1:32 PM, Sönke Ludwig wrote: I/O is crucial of course, but there are also a lot of other important and inherently impure things such as message passing. If the message channel is passed as a parameter to the droutine, then the droutine can still be pure. I think such a

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Paolo Invernizzi via Digitalmars-d-announce
On Saturday, 28 March 2015 at 02:31:37 UTC, Laeeth Isharc wrote: The data points we have suggest that the scarcity of D programmers is an imaginary problem, because enterprises just hire good people and they pick it up (ask Don at Sociomantic or Dicebot for example). Modern business has a

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Sönke Ludwig via Digitalmars-d-announce
Am 28.03.2015 um 10:17 schrieb Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= ola.fosheim.grostad+dl...@gmail.com: On Friday, 27 March 2015 at 16:48:26 UTC, Sönke Ludwig wrote: 1. No stack. That reduces the memory footprint, but doesn't reduce latency. It removes hard to spot dependencies on thread

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread ketmar via Digitalmars-d-announce
On Sat, 28 Mar 2015 13:27:55 +, Ola Fosheim Grøstad wrote: In essence, you should ideally be able to break a task into all it's independent parts and run them in parallel (i.e.. futures, events etc). Preferably batch them to get better performance, and sort them based on when they have

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Russel Winder via Digitalmars-d-announce
On Sat, 2015-03-28 at 11:16 +, ketmar via Digitalmars-d-announce wrote: […] hm. yes, that was coroutines on steroids. But that's the point isn't it: 1. Processes are too heavyweight, invent threads. 2. We have masses of cores, let's map threads to cores via the kernel. 3. Processes and

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Russel Winder via Digitalmars-d-announce
On Fri, 2015-03-27 at 22:48 +, ketmar via Digitalmars-d-announce wrote: […] the whole userspace threads concept is a reimplementation of kernel threads and sheduling. ;-) And kernel threads are a reimplementation of user space threads. -- Russel.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread ketmar via Digitalmars-d-announce
On Sat, 28 Mar 2015 11:02:23 +, Russel Winder via Digitalmars-d-announce wrote: On Fri, 2015-03-27 at 22:48 +, ketmar via Digitalmars-d-announce wrote: […] the whole userspace threads concept is a reimplementation of kernel threads and sheduling. ;-) And kernel threads are a

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread via Digitalmars-d-announce
On Saturday, 28 March 2015 at 13:27:56 UTC, Ola Fosheim Grøstad wrote: On Friday, 27 March 2015 at 22:32:32 UTC, ketmar wrote: but it is broken! the whole point of async i/o servers is that Note: I presume that you meant servers and no OS-level async i/o (the limitations of unix select() is

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Russel Winder via Digitalmars-d-announce
On Sat, 2015-03-28 at 13:27 +, via Digitalmars-d-announce wrote: […] Nah. Cooperative multitasking is a sorry excuse that belongs to the 80s. This should be as transparent as possible. You cannot insert yield into an external library. 1960s. Software developers have spent 50+ years

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread via Digitalmars-d-announce
On Saturday, 28 March 2015 at 11:52:34 UTC, Sönke Ludwig wrote: You can access TLS from an event callback just as easy as from a fiber. Yes, but it is much easier to verify that you don't hold onto references to TLS if get rid of arbitrary call stacks when moving to a new thread. And why

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Russel Winder via Digitalmars-d-announce
On Sat, 2015-03-28 at 12:58 +, Atila Neves via Digitalmars-d-announce wrote: […] It does, and it should. In fact, I'd consider it massive selling point for D if it were; you want easy Go-like concurrency? D has that too. Right now, it's available easily for writing servers: just use

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Russel Winder via Digitalmars-d-announce
On Sat, 2015-03-28 at 12:52 +0100, Sönke Ludwig via Digitalmars-d-announce wrote: […] You can access TLS from an event callback just as easy as from a fiber. […] TLS is the evil here. Anyone working with TLS is either writing an operating system or doing it wrong. -- Russel.

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Atila Neves via Digitalmars-d-announce
On Friday, 27 March 2015 at 04:24:52 UTC, Walter Bright wrote: On 3/26/2015 7:06 PM, weaselcat wrote: vibe has (experimental?) green threads, doesn't it? I don't keep up with vibe, so I may be wrong. I don't know, but if it does have good 'uns they should be moved into Phobos! It does, and

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread via Digitalmars-d-announce
On Saturday, 28 March 2015 at 13:52:54 UTC, ketmar wrote: then you have to switch to some functional language, preferably one that does cps transformations in the compiler. as you told somewhere else, D is too broad to be restricted to this. Fibers is really not a system level thing. So I

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Sönke Ludwig via Digitalmars-d-announce
Am 28.03.2015 um 13:32 schrieb Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= ola.fosheim.grostad+dl...@gmail.com: On Saturday, 28 March 2015 at 11:52:34 UTC, Sönke Ludwig wrote: You can access TLS from an event callback just as easy as from a fiber. Yes, but it is much easier to verify that you don't

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Sönke Ludwig via Digitalmars-d-announce
Am 28.03.2015 um 15:33 schrieb Russel Winder via Digitalmars-d-announce: On Sat, 2015-03-28 at 12:52 +0100, Sönke Ludwig via Digitalmars-d-announce wrote: […] You can access TLS from an event callback just as easy as from a fiber. […] TLS is the evil here. Anyone working with TLS is either

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread ketmar via Digitalmars-d-announce
On Sat, 28 Mar 2015 14:28:00 +, Russel Winder via Digitalmars-d-announce wrote: It could be argued that it is all just co-routines underneath, but I think that would be missing the point that we have 55 years more experience of doing these things since that single processor operating

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Russel Winder via Digitalmars-d-announce
On Sat, 2015-03-28 at 17:57 +, ketmar via Digitalmars-d-announce wrote: On Sat, 28 Mar 2015 14:28:00 +, Russel Winder via Digitalmars-d-announce wrote: It could be argued that it is all just co-routines underneath, but I think that would be missing the point that we have 55

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread weaselcat via Digitalmars-d-announce
On Saturday, 28 March 2015 at 17:57:35 UTC, ketmar wrote: On Sat, 28 Mar 2015 14:28:00 +, Russel Winder via Digitalmars-d-announce wrote: It could be argued that it is all just co-routines underneath, but I think that would be missing the point that we have 55 years more experience of

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread weaselcat via Digitalmars-d-announce
On Saturday, 28 March 2015 at 18:39:47 UTC, Russel Winder wrote: On Sat, 2015-03-28 at 17:57 +, ketmar via Digitalmars-d-announce wrote: On Sat, 28 Mar 2015 14:28:00 +, Russel Winder via Digitalmars-d-announce wrote: It could be argued that it is all just co-routines underneath, but

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread via Digitalmars-d-announce
On Friday, 27 March 2015 at 16:48:26 UTC, Sönke Ludwig wrote: 1. No stack. That reduces the memory footprint, but doesn't reduce latency. It removes hard to spot dependencies on thread local storage. 2. Batching. Can you elaborate? Using fibers you deal with a single unit. Using events

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread Jonathan M Davis via Digitalmars-d-announce
On Friday, March 27, 2015 16:03:01 Walter Bright via Digitalmars-d-announce wrote: On 3/27/2015 2:47 PM, weaselcat wrote: On Friday, 27 March 2015 at 20:58:44 UTC, Walter Bright wrote: On 3/27/2015 1:35 PM, weaselcat wrote: there's a difference between minimalism and blatantly not adopting

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread via Digitalmars-d-announce
On Saturday, 28 March 2015 at 02:31:37 UTC, Laeeth Isharc wrote: Fair points that I wouldn't argue with (although I think predicting when one will finish something entirely new is a mugs game - another reason to favour prototyping and rapid iteration when possible). Yet you have to if you

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-28 Thread via Digitalmars-d-announce
On Friday, 27 March 2015 at 16:44:50 UTC, Chris wrote: I'd say Go fans are worse in this respect (yes, I know, probably not all of them). People in the D community are here, But that is just because there is more Go fans... ;)

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-27 Thread via Digitalmars-d-announce
On Friday, 27 March 2015 at 01:47:57 UTC, Walter Bright wrote: The one difference was Go's support for green threads. There's no technical reason why D can't have green threads, it's just that nobody has written the library code to do it. Go can move stacks and extend them. Go is closer to

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-27 Thread via Digitalmars-d-announce
On Friday, 27 March 2015 at 04:05:30 UTC, Laeeth Isharc wrote: Programming is - for now - still a human activity, and what is important in human activities may not always be measured, and what may be easily measured is not always important. That doesn't mean one should throw away the profiler

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-27 Thread Walter Bright via Digitalmars-d-announce
On 3/26/2015 11:40 PM, Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= ola.fosheim.grostad+dl...@gmail.com wrote: Go can move stacks and extend them. That has no value on 64 bit systems, and is not a language issue (it's an implementation issue). Go is closer to having a low latency GC. I.e. it

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-27 Thread Walter Bright via Digitalmars-d-announce
On 3/27/2015 2:57 AM, Russel Winder via Digitalmars-d-announce wrote: I think the way go handles interfaces and their composition would require a few tricks in D and C++, but I am sure it can be done. Interfaces can be done with D templates. It'll be compile time polymorphism rather than run

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-27 Thread via Digitalmars-d-announce
On Friday, 27 March 2015 at 09:44:27 UTC, Walter Bright wrote: On 3/27/2015 1:41 AM, Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= ola.fosheim.grostad+dl...@gmail.com wrote: On Friday, 27 March 2015 at 08:25:26 UTC, Walter Bright wrote: The MMU makes it pointless. The virtual address space allows for 4

Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers

2015-03-27 Thread Russel Winder via Digitalmars-d-announce
On Fri, 2015-03-27 at 03:11 -0700, Walter Bright via Digitalmars-d-announce wrote: On 3/27/2015 2:57 AM, Russel Winder via Digitalmars-d-announce wrote: […] However, I cannot see this happening purely on volunteer, hobbyist resource. We need to find an organization or three willing to

  1   2   >