Live data from Hacker News

The Next Big Language

steve-yegge.blogspot.com

41–50 of 75 posts

Re: The Next Big Language

#41

I keep thinking that the Next Big Language will be a thing of re -evolution, e.g. someone going back to C and retracing steps of C++ but in a more sensible way. Also, on a tangential note -- the garbage collection is a huge deal if an adoption of the NBL among C/++ programmers is considered. The only way is to have the garbage collection optional. Similarly to how D has it, but much much simpler. Something like addin…

just curious, do you allow malloc_gc'ed items to reference malloc'd ones?

Re: The Next Big Language

#42
post #6

I didn't realize how old this was, which tells you something about how prescient Yegge's writing can be. I would have added "pattern matching", though. At a minimum, keyword arguments or syntactic sugar for them.

He mentions "Perl 5 compatible regular expression literals" under "kitchen sink"

Re: The Next Big Language

#43

Earlier quoted context omitted.

While I'm not sure Scala is the Language of the Future™, it's relevant to this discussion to point out that the method_missing hacks that make ruby's dynamic typing so attractive are being actively prototyped in Scala. An example snippet: https://gist.github.com/783394 The implementation: http://lampsvn.epfl.ch/trac/scala/changeset/23993

For what it's worth, and a bit OT, I find method_missing to be the least appealing part of Ruby's runtime dynamism. What _is_ helpful is to be able to add methods on the fly (e.g., through define_method); on the other hand, being able to handle arbitrary messages (which is what method_missing does) is occasionally interesting (as with Rails' dynamic finders) but generally considered bad form given that there are clea…

I only mention the method_missing because most modern languages have fairly good answers to the "safely extend a type" problem, without succumbing to the problems that languages like Ruby suffer.

Re: The Next Big Language

#44
post #6

I didn't realize how old this was, which tells you something about how prescient Yegge's writing can be. I would have added "pattern matching", though. At a minimum, keyword arguments or syntactic sugar for them.

He mentions "Perl 5 compatible regular expression literals" under "kitchen sink"

Pretty sure the GP is referring to pattern matching as it exists in ML or Scala. Or, somewhat less elegantly (given the constraints of the language) something like what https://github.com/jfd/match-js does.

Re: The Next Big Language

#45

Earlier quoted context omitted.

Scala would be a fucking awesome mainstream language.

And it actually has a chance of achieving that, unlike Haskell/Erlang/Ocaml/whatever, because Blub developers can just use it as a better Java.

I think you would see JRuby used as an industry de facto before you would see Scala.

Re: The Next Big Language

#46
post #44

Earlier quoted context omitted.

He mentions "Perl 5 compatible regular expression literals" under "kitchen sink"

Pretty sure the GP is referring to pattern matching as it exists in ML or Scala. Or, somewhat less elegantly (given the constraints of the language) something like what https://github.com/jfd/match-js does.

Yup. IIRC the R language includes really cool features of both pattern matching and keyword arguments in its function signatures.

Re: The Next Big Language

#48
post #20

Earlier quoted context omitted.

How was that a great guess? Certainly things could change, but very very very few people are doing server side JS right now. That could change, but I'm still pretty skeptical. Node.js (if that's what you're thinking of) is still very much in the experimental stage.

He doesn't say it will be ubiquitous in that timeframe. You'd have to be pretty crazy to think that. He means it will arrive. Which is correct. The thing is, javascript is what's available in all devices. And it's a pretty nice language.

it's also showing up in other things. I believe KDE is using it as the primary scripting language for their stuff. Apple has dipped it's toe in that water with the dashboard widgets. etc

Re: The Next Big Language

#49
post #20
post #2

Ahh... I think we all miss Big Stevey. He role was never replaced and it's a shame for our entire community. I'm glad this was posted. It was written four years ago (Feb. 2007), and his quote is, "[The NBL] is going to arrive very soon (timeline: 18-24 months ...)" He later gave away that he was thinking the NBL was to be server-side Javascript. You have to hand it to him; that was a great guess, even if the timeline…

How was that a great guess? Certainly things could change, but very very very few people are doing server side JS right now. That could change, but I'm still pretty skeptical. Node.js (if that's what you're thinking of) is still very much in the experimental stage.

LOL. I guess landing in every Palm phone currently in production with the full backing and weight of HP is considered "still very much in the experimental phase." Somebody probably isn't a very good Javascript programmer. =P Wait till they make their Feb 9th announcement too.

http://developer.palm.com/index.php?id=2109 http://www.google.com/search?q=palm+feb+9

Post reply on HN