SoylentNews is people
SoylentNews
from the java-is-in-the-lead-because-of-the-caffine dept.
Think of it as a map of the rapidly changing world of computer software.
On Wednesday, GitHub published a graph tracking the popularity of various programming languages on its eponymous Internet service, a tool that lets anyone store, edit, and collaborate on software code. In recent years, GitHub.com has become the primary means of housing open source software—code that's freely available to the world at large; an increasing number of businesses are using the service for private code, as well. A look at how the languages that predominate on GitHub have changed over time is a look at how the software game is evolving.
In particular, the graph reveals just how much open source has grown in recent years. It shows that even technologies that grew up in the years before the recent open source boom are thriving in this new world order—that open source has spread well beyond the tools and the companies typically associated with the movement. Providing a quicker, cheaper, and more comprehensive way of building software, open source is now mainstream. And the mainstream is now open source.
Hmm, Perl has been declining...
(Score: 2) by Nerdfest on Saturday August 22 2015, @07:12PM
I remember reading about one of the creators of JavaScript saying that it was not intended for large scripts. They considered something like 1000 lines of code more than it was intended for. I'm not trolling here, I actually do a lot of JavaScript and don't *mind* it if it's written properly, that being with lots of unit tests (QUnit), and use of Require.js for dependency and namespace management. TypeScript is probably worth a look as well, or will be when a bit better tool support is in place.
I really can't imaging people doing anything more than tiny projects without that. Dynamically typed languages require unit testing but I'm the only one I know that actually does it. Without something like Require.js *everything* pollutes the global namespace leading quickly to unmaintainable code.
With those caveats it's not a bad language if you avoid some of the stupid inconsistencies.