By far no. Now I don't know if I even should read beyond that.
By far no. Now I don't know if I even should read beyond that.
If a company chose brainfuck as a main programming language, it's doubtful they'd come back from that choice.
Based on what? Economics define where you go, not language. If company using Perl or VB has steady cash flow and their bottleneck is language - they’ll just rewrite when it makes sense. No amount of writing in C# or Python from scratch will save you if your product is garbage.
Same thing with the fundamental architecture of programs, and especially the data model & database solution.
Still I don't entirely agree with the article. He makes it sound like there isn't any difference between programming languages and any preference is purely about developer identity. But that identity doesn't come from nowhere. Rust is popular because a load of C++ developers finally found something technically better. Not because they all woke up one morning and decided to be "a Rust developer".
Where the story falls apart is that Perl is arguably even worse than PHP. One deluded Perl programmer does not prove a principle.
On Rust vs Go, he's absolutely right that Go is has a slightly better "build & deploy" story (though not by a much). But reading between the lines I think he's misrepresenting that - it sounds like a) that was just one point for choosing Rust, and b) that was a point when comparing to typical alternatives, e.g. C++ or Java. It's not untrue that Rust is easy to build & deploy simply because Go is slightly easier.
What about them?
Extremely costly choice would be choosing .Net or Java and never releasing at all. Creating Hack advanced whole PHP ecosystem and cost nothing in the grand scheme of things.
> Dropbox had to rewrite their sync engine in Rust, and I think they also have rewritten backend stuff in Go.
Bah, idiots, should've just waited 4 years until Go and Rust came into existence.