Live data from Hacker News

D for the Win

tomerfiliba.com

1–10 of 105 posts

Re: D for the Win

#2
I know this is an inevitable comment on any article that calls any software slow, but: "~500 requests/sec" using ten servers? Python may be slow, but I would be very suprised if it can't do 50req/second.

Re: D for the Win

#3
> go (Google must be joking if they actually consider it for system programming)

I am curious what led the author to be dismissive of Go in such a strongly negative manner. Lack of generics? Disagree with certain language design choices? Too many cuddly caricatures of gophers?

Re: D for the Win

#5
post #3

> go (Google must be joking if they actually consider it for system programming) I am curious what led the author to be dismissive of Go in such a strongly negative manner. Lack of generics? Disagree with certain language design choices? Too many cuddly caricatures of gophers?

Go hasn't been intended for "systems programming" for quite a while. It is a general purpose language.

Re: D for the Win

#6
post #3

> go (Google must be joking if they actually consider it for system programming) I am curious what led the author to be dismissive of Go in such a strongly negative manner. Lack of generics? Disagree with certain language design choices? Too many cuddly caricatures of gophers?

I need some clarifications. I think there are two definitions of systems being used here :

  - low-level hardware control (c,D,...) implicitely concurrent
  - explicitely concurrent higher level components (go, erlang maybe)

Re: D for the Win

#7
post #3

> go (Google must be joking if they actually consider it for system programming) I am curious what led the author to be dismissive of Go in such a strongly negative manner. Lack of generics? Disagree with certain language design choices? Too many cuddly caricatures of gophers?

Go hasn't been intended for "systems programming" for quite a while. It is a general purpose language.

Those properties are not mutually exclusive.

Re: D for the Win

#8
post #3

> go (Google must be joking if they actually consider it for system programming) I am curious what led the author to be dismissive of Go in such a strongly negative manner. Lack of generics? Disagree with certain language design choices? Too many cuddly caricatures of gophers?

I need some clarifications. I think there are two definitions of systems being used here : - low-level hardware control (c,D,...) implicitely concurrent - explicitely concurrent higher level components (go, erlang maybe)

Hail Wikipedia for it is the source of all truth.

http://en.wikipedia.org/wiki/System_programming_language

Re: D for the Win

#9

I know this is an inevitable comment on any article that calls any software slow, but: "~500 requests/sec" using ten servers? Python may be slow, but I would be very suprised if it can't do 50req/second.

This doesn't pass the smell test for me either. I'm running a Python Django server with a primarily write load on an EC2 small instance, and easily exceeding 50 requests per second, with very low load on the box.

Re: D for the Win

#10

I know this is an inevitable comment on any article that calls any software slow, but: "~500 requests/sec" using ten servers? Python may be slow, but I would be very suprised if it can't do 50req/second.

As I read it that's one AWS server of unknown size serving ~500rps of an application of unknown complexity. Tripled when using PyPy (whatever that is).

Maybe a very small instance serving something fairly complex?

Post reply on HN