News for hackers. Stuff that matters.
Re:Analyzing GitHub, how developers change programming langu... by joekrill on Wednesday July 12, 2017 @04:33PM (#14756391)
Unfortunate they had to exclude Javascript. I understand why they chose to do that, but that's a HUGE chunk of data that's been pretty much randomly ignored. So can this really be considered a fair analysis given that?
Re:Analyzing GitHub, how developers change programming langu... by haburka on Wednesday July 12, 2017 @06:00PM (#14757059)
No one has a choice with JavaScript. Theoretically you could go native or transpile but it's very rare.

Therefore, if you included it, the data wouldn't lead to meaningful conclusions. I feel like this was pretty obvious from the article and that the explanation was enough. For example, substituting node for js seemed to work well enough.

Re:Analyzing GitHub, how developers change programming langu... by remline on Wednesday July 12, 2017 @06:22PM (#14757194)
No one really has a choice with C, but its tally was very interesting..

I think there is a lot more vertical movement and the horizontal stuff might be a sideshow without considering overlap or experience with C or JavaScript as significant in how one transitions between purely competing languages.

But JavaScript's real problem for the analysis might be that its competition is largely excluded since the walled garden apps rarely have related code on GitHub, even if their language is present.

Re:Analyzing GitHub, how developers change programming langu... by freehunter on Wednesday July 12, 2017 @08:24PM (#14757838)
There's a huge choice for C. For a lot of uses, you can use C++, Go, Java, Rust, or a few other systems languages. The only thing that needs C is some very niche embedded stuff, or the Linux kernel (also niche).
Re:Analyzing GitHub, how developers change programming langu... by bluejekyll on Wednesday July 12, 2017 @10:25PM (#14758309)
All the major Unix kernels are in C. If it continues this trend, it seems clear that new kernels in new languages will be needed, or existing kernels will need to be ported to other languages. A memory safe one would be cool...
Re:Analyzing GitHub, how developers change programming langu... by thehardsphere on Thursday July 13, 2017 @10:26AM (#14761498)
Well, if you think that C is going to go the way of conversational Latin, that would probably be accurate. I doubt that's accurate, because:

1. The fact that fewer people are choosing C for other projects doesn't mean they can't or won't learn it for kernels.

2. Nobody has yet to produce a language that is clearly superior to C for systems programming. Otherwise, we would be seeing movement towards that language instead of Java and Python.

The other thing to remember is that these are GitHub projects; the vast majority of them are not going to be kernels but application software or libraries. That would explain the moves from C to Java and Python; it's easier to write applications in those languages.

Re:Analyzing GitHub, how developers change programming langu... by bluejekyll on Thursday July 13, 2017 @11:44AM (#14762250)
> clearly superior to C for systems programming.

I would argue Rust already has.

Re:Analyzing GitHub, how developers change programming langu... by tomsmeding on Friday July 14, 2017 @06:53AM (#14768843)
I think Rust doesn't have the speed props for that yet. It might in the future, but that's probably one of the reasons.
Re:Analyzing GitHub, how developers change programming langu... by bluejekyll on Friday July 14, 2017 @10:45AM (#14770148)
Rust has been shown to outperform C in some cases and in most be on par.

This isn't scientific: http://benchmarksgame.alioth.debian.org/u64q/rust.html

Re:Analyzing GitHub, how developers change programming langu... by igouy on Friday July 21, 2017 @01:46PM (#14822414)
What isn't scientific?

tomsmeding's comment?

Your statement "Rust has been shown to…"?

The website you point to?

(What is "This isn't scientific" even supposed to mean?)

Re:Analyzing GitHub, how developers change programming langu... by thehardsphere on Thursday July 13, 2017 @02:34PM (#14763899)
When someone writes a system based on Rust, that claim will be much stronger.
Re:Analyzing GitHub, how developers change programming langu... by bluejekyll on Thursday July 13, 2017 @09:42PM (#14766801)
Some of my favorite examples:

https://os.phil-opp.com

https://github.com/helena-project/tock

https://www.redox-os.org

https://github.com/redox-os/tfs

https://github.com/intermezzOS/kernel

The biggest application example:

https://github.com/servo/servo

And some self promotion:

https://github.com/bluejekyll/trust-dns

----

I encourage all programmers to check it out. You may discover like me, that Rust is a compiler and language which guards against all the hard learned lessons I've had over my career. It's an amazing language to program in.

Re:Analyzing GitHub, how developers change programming langu... by steveklabnik on Thursday July 13, 2017 @04:30PM (#14764889)
What kind of "system" are you looking for?
Re:Analyzing GitHub, how developers change programming langu... by muricula on Thursday July 13, 2017 @12:59AM (#14758844)
Or maybe C is uniquely suited to the task of writing a kernel, after all that's what it was designed for.
Re:Analyzing GitHub, how developers change programming langu... by pjmlp on Thursday July 13, 2017 @02:30AM (#14759175)
Not really, kernels were being written in HLL 10 years before C existed, and at strange places like IBM research.

The only good thing about it is that the language is easier to write a compiler for, as it is basically a portable macro assembler, specially the K&R C variant.

Re:Analyzing GitHub, how developers change programming langu... by Inityx on Thursday July 13, 2017 @01:50AM (#14759008)
Re:Analyzing GitHub, how developers change programming langu... by blattimwind on Thursday July 13, 2017 @08:51AM (#14760807)
Operating systems were written in high(er) level languages a number of years before C, or UNIX, were invented.
Re:Analyzing GitHub, how developers change programming langu... by remline on Thursday July 13, 2017 @03:15AM (#14759346)
Right, so the restrictions on at the bottom seem pretty meaningless, and that matches the migration off of C.

So how do we justify this JavaScript as forced labor argument?

The programmer can decide to do webapps that run atop C and get assistance from a backend that ultimately runs on C. The programmer can use backend frameworks that deliver incantations in JavaScript much like their downcalls to C.

If the migration were toward metal we would be hearing that C has to be excluded. Really how the Buffalo herd is moving does matter in a discussion of what ditches they are stuck in in the middle Savannah.

Re:Analyzing GitHub, how developers change programming langu... by Sir_Substance on Thursday July 13, 2017 @04:46AM (#14759736)
>The programmer can decide to do webapps that run atop C

Please explain how to make a slippymap[1] in C.

For srs, I'm making a hobby project at the moment that needs a dynamic, interactable map on a webpage, and as a long time noscript user it galls me a little to use JS. The only compromise I can come up with is re-hosting the JS libraries I use and ensuring they don't have their own dependencies so that users only need to enable my domain for the site to work.

If you can tell me how to do the same thing in C, I'll swap to it immediately.

[1] http://wiki.openstreetmap.org/wiki/Slippy_Map

Re:Analyzing GitHub, how developers change programming langu... by homarp on Thursday July 13, 2017 @06:26AM (#14760128)
>Please explain how to make a slippymap[1] in C.

The same way Doom has been compiled and run in the browser.

https://github.com/kripken/emscripten/wiki/Porting-Examples-...

Re:Analyzing GitHub, how developers change programming langu... by Sir_Substance on Thursday July 13, 2017 @06:44AM (#14760186)
But emscripten compiles...to javascript.

I guess that meets the criteria of "programming for the web but not making github commits in javascript", but it doesn't really solve my problem. Oh well.

Re:Analyzing GitHub, how developers change programming langu... by pjmlp on Thursday July 13, 2017 @08:08AM (#14760591)
No, it also compiles to WebAssembly.
Re:Analyzing GitHub, how developers change programming langu... by microcolonel on Thursday July 13, 2017 @12:45AM (#14758790)
I think you could make the argument that because the C ABI is available in most compiled languages, you do have a choice. Whereas on the web, JavaScript is the ABI.
Re:Analyzing GitHub, how developers change programming langu... by pjmlp on Thursday July 13, 2017 @02:28AM (#14759165)
Not really when doing code on UNIX or aiming for portability.

There are still systems that lack full C++98 compliant compilers, for example (mostly embedded stuff).

Re:Analyzing GitHub, how developers change programming langu... by kwhitefoot on Friday July 14, 2017 @04:30AM (#14768394)
Most working developers don't have a choice at all for most of the coding they do because the company or team that they join has already chosen a language. Ditto for frameworks.
Re:Analyzing GitHub, how developers change programming langu... by kevinb7 on Thursday July 13, 2017 @12:00AM (#14758591)
There's a lot of compile to JS languages. It'd be interesting to see how many frontend devs are migrating to these languages for at least some of their projects.
Re:Analyzing GitHub, how developers change programming langu... by collyw on Thursday July 13, 2017 @05:26AM (#14759896)
They have a choice on the backend, and for some reason people do choose it there.
Re:Analyzing GitHub, how developers change programming langu... by lloeki on Thursday July 13, 2017 @05:53AM (#14759992)
> Our data retrieval pipeline could not distinguish regular JS from Node and thus we had to exclude it completely.
Re:Analyzing GitHub, how developers change programming langu... by __s on Thursday July 13, 2017 @05:57AM (#14760009)
I chose node because it meant I could share logic between server & client
Re:Analyzing GitHub, how developers change programming langu... by pacala on Thursday July 13, 2017 @03:42PM (#14764494)
ObjC, Swift, Java, Kotlin
Re:Analyzing GitHub, how developers change programming langu... by dirkc on Wednesday July 12, 2017 @05:06PM (#14756679)
If you see JavaScript as the clear leader, then this is probably a fair evaluation of what's left over.

According to the stack overflow survey this year, JavaScript is at the top of the list of programming languages

https://insights.stackoverflow.com/survey/2017#technology-pr...

Re:Analyzing GitHub, how developers change programming langu... by bluejekyll on Wednesday July 12, 2017 @10:28PM (#14758315)
Not by choice... and I think that's the intended point of this analysis, what languages are people moving to from.

When WebAssembly stabilizes, it would be interesting to redo this analysis and see if JS will remain king.

Re:Analyzing GitHub, how developers change programming langu... by thehardsphere on Wednesday July 12, 2017 @04:46PM (#14756525)
I think so. I mean, aside from Node based projects, how many people are really doing pure-javascript apps? The pattern is typically JS on the front and something else on the back.

I guess if you can split out Node, React Native, and whatever other thing people are doing with Javascript that is pure Javascript, that would be a little bit more fair.

Re:Analyzing GitHub, how developers change programming langu... by ricardobeat on Wednesday July 12, 2017 @05:04PM (#14756666)
Why would exclude nodejs based projects? It's becoming the most common server type across the top 500 sites, and has an estimated 4+ million users.

Don't forget Electron desktop apps, also pure js - the framework itself has 100-200k monthly downloads.

Re:Analyzing GitHub, how developers change programming langu... by thehardsphere on Thursday July 13, 2017 @11:33AM (#14762136)
I am not saying that I would exclude Node projects; I am saying I would exclude all Javascript projects that are not Node. Or React Native. Or Electron. Or whatever is used to create a purely Javascript app instead of one that only uses Javascript because a portion of the app's user interface exists at runtime in the context of a web browser.
Re:Analyzing GitHub, how developers change programming langu... by Zyst on Wednesday July 12, 2017 @05:08PM (#14756702)
If you read the article: It's because they couldn't tell apart Node and JavaScript projects.

However, I do disagree about not including JS.

Re:Analyzing GitHub, how developers change programming langu... by ricardobeat on Wednesday July 12, 2017 @07:05PM (#14757441)
If you read the parent comment, you'll find the question "how many people are really doing pure-javascript apps?"