81–90 of 166 posts
>Node was created by software developer Ryan Dahl as a way of building and running entire online applications with JavaScript—the standard programming language for writing code that runs in your browser. Really? I thought that they intentionally choose javascript because it doesn't have any features like threading. > The massively popular programming framework Ruby on Rails, for instance, is still sponsored by its cr…
>Node was created by software developer Ryan Dahl as a way of building and running entire online applications with JavaScript—the standard programming language for writing code that runs in your browser. Really? I thought that they intentionally choose javascript because it doesn't have any features like threading. > The massively popular programming framework Ruby on Rails, for instance, is still sponsored by its cr…
Earlier quoted context omitted.
But it's true that Node is losing traction.
By what, hacker news discussions? It seems here only "new" things are discussed, but not as much about platforms growing and stabilizing. Its almost like Rust and Golang have taken over the world if you measure by this community.
Rust on the other hand also has a bit of hype, but that hype actually has a base. It is due to a features that are quite significant, not because it comes from Mozilla. The ability to do memory safety checks at compile time is quite a big deal (maybe Rust is not first here to offer that, but it is first that it build the entire language around it).
I believe that Rust actually really has a huge chance to replace C and C++ (languages that were developed in 70s and 80s respectively) and influence future languages.
Earlier quoted context omitted.
I can think of MySQL. While I wouldn't call it dead by any measure it certainly suffered when the spit happened.
Yeah, but how much of that was due to forking and how much of that was folks realising that PostgreSQL is much better than MySQL for most metrics of better?
I think the intersection of politics and internet is interesting. I write about it quite a bit on my blog, as well as here: http://qbix.com/blog/index.php/2013/04/a-new-kind-of-platfor... In this case, we see sort of an "arab spring" of open source projects lately. Consider MySQL after it was bought by Oracle, and then the MariaDB fork was born. Now we have Node.js and Docker being forked. Until now, most successful…
I think the most interesting aspect of this is the cross-disciplinary nature, when analyzing something like the Internet and information technology through the lens of a different field, politics. The way politics presents itself and interacts in this field (much like other fields) is a whole area of study itself.
>Node was created by software developer Ryan Dahl as a way of building and running entire online applications with JavaScript—the standard programming language for writing code that runs in your browser. Really? I thought that they intentionally choose javascript because it doesn't have any features like threading. > The massively popular programming framework Ruby on Rails, for instance, is still sponsored by its cr…
I believe given the nature of those that forked it, we'll be replacing Node.JS with IO.JS (that is awkward to write) soon in http://Clara.io . I think that the confusion around Node.JS versus IO.JS will persist for some time though. If I wasn't a regular HN reader, I would have missed this completely.
Earlier quoted context omitted.
By what, hacker news discussions? It seems here only "new" things are discussed, but not as much about platforms growing and stabilizing. Its almost like Rust and Golang have taken over the world if you measure by this community.
My prediction is that Go will disappear in same way as it happen to Ruby, Perl and others. It currently rides on the fame that it comes from Google "so it hast to be good". It doesn't really provide anything revolutionary, it just is more friendly toward writing specific type of applications. Just by seeing that majority of people who are using Go are the ones who always explore new languages, and you see majority of…
> My prediction is that Go will disappear in same way as it
> happen to Ruby, Perl and others.
> Rust on the other hand also has a bit of hype, but that
> hype actually has a base. It is due to a features that
> are quite significant, not because it comes from Mozilla.
> I believe that Rust actually really has a huge chance
> to replace C and C++ (languages that were developed in
> 70s and 80s respectively) and influence future languages.
Finally, I agree that Rust will be an influence on future languages. Just yesterday D proposed something akin to Rust's borrowed references (http://wiki.dlang.org/DIP69), and I'm curious to see if something similar emerges in future editions of C++. There's also Microsoft's secretive M# language, which I suspect will use a similar mechanism.
Earlier quoted context omitted.
But it's true that Node is losing traction.
I see this more as a return to reality from Node.js's astronomical levels of hype. The use cases for a single-threaded web server are specific and limited in the real world. Node.js will continue to solve those use cases (simple web server for static content or I/O bound apps) but the resultant decline will lead some to believe that the framework is dying.
You can always run multiple process instances, and communication between processes isn't really so different in practice than inter-server communication... Which just means you are scaling horizontally by design earlier in development.
Earlier quoted context omitted.
This is more about how, for many companies, the OSS doctrine that they espouse doesn't really jive with their need for profitability. In the long run, they need to make decisions for the company that are not in the best interest of the project, and either the project dies or is forked or abandoned. Sun did really well by the OSS community for a very long time, but they had nothing to show for it and Oracle has since…
> I honestly think we're going to see a Firefox fork in the next 2-3 years. There are already semi-forks (downstream distributions that continue to pull from upstream and are mostly synced, but also maintain distinct and divergent feature sets) -- both GNU IceCat is an example (Debian Iceweasel I think is less so, because IIRC it is synced but for branding with upstream.)