Re:Ruby Still isn't dead
by jack9 on Friday January 12, 2018 @10:33PM
(#16138145)
I had to write Ruby (with no prior experience) as part of an interview exercise, about 10 years ago. Never encountered it or used it since. Not sure it has a purposeful niche or enough of a differentiation to grow in use.
Re:Ruby Still isn't dead
by ParamModule on Friday January 12, 2018 @10:39PM
(#16138171)
Perl isn't dead so much as it's primarily only used in production by older sys admins but it still has a community that loves it, VB.NET is alive and well in Microsoft shops and among noob malware authors.
My definition of fucking dead is smalltalk.
But this is coming from a guy who's favorite pls are erlang, SML/NJ, and Ocaml lol.
Re:Ruby Still isn't dead
by overloadrix on Saturday January 13, 2018 @05:17AM
(#16139001)
> My definition of fucking dead is smalltalk
A curious definition. Not only Smalltalk is still used (e.g. in fintech), but it's intelectual virtues are always revisited and rediscovered by new generations who, invariably, try to come up with a "modern" version of it, or something inspired by it.
Re:Ruby Still isn't dead
by rurban on Tuesday January 16, 2018 @06:35AM
(#16157433)
Like ruby? AFAIK nothing new ever came out of ruby. It was just a nice pure implementation of smalltalk on top of Perl. Of course the everything is a method strategy and unoptimized MOP burned them.
Just look at their new jit. Can anybody think of a worse strategy to implement a jit? There are serious technical and management problems. V Makarov at least wrote the register machine before the naive cc -> so jit, but then the Japanese came and even ripped that out.
Go is fine but yeah those other two are, uh, well.
My definition of fucking dead is smalltalk. But this is coming from a guy who's favorite pls are erlang, SML/NJ, and Ocaml lol.
A curious definition. Not only Smalltalk is still used (e.g. in fintech), but it's intelectual virtues are always revisited and rediscovered by new generations who, invariably, try to come up with a "modern" version of it, or something inspired by it.
Just look at their new jit. Can anybody think of a worse strategy to implement a jit? There are serious technical and management problems. V Makarov at least wrote the register machine before the naive cc -> so jit, but then the Japanese came and even ripped that out.