2 ms·
The common thread I see in this is people pouring their heart and soul into a super awesome tool, and then moving on with their lives. The tool was made for on
by klyrs 6y ago
The common thread I see in this is people pouring their heart and soul into a super awesome tool, and then moving on with their lives. The tool was made for one version of one language, and the world moves on, too. But then I think about the tools that I do use.
Package distributions. Good word, I am not happy here. Still an unsolved problem in general, some languages tackle it better than others.
Testing frameworks. It's getting better. Big props to zig, for including tests for free with comptime. But in general, it's piles of code that somebody maintains for each language. Often, there are multiple tools because the language devs don't pull them into first-class components.
Debuggers. There's pretty good tools out there. They're clunky to use, but there are multiple front ends that can handle multiple languages, thanks to a common data format.
Code formatters. Props to zig, go, and rust for building these in. But for most languages, it's DIY.
Common theme here: all of this stuff is fairly generic, but each language tends to do its own thing. Tools aren't officially part of the languages, neither are they generic. Except debuggers! There's a common interface, DWARF support becomes a part of the language, and (another key point) language devs use it -- so they don't rot.
Developer tools can be magic, but unless they're generic, I expect them all to rot.
Edit: Oh, I forgot documentation generation -- like debugging, there's been some convergence around some generic tools and it's pretty easy to build support into / on top of a language. And newer languages use these tools internally to build their docs. Great!
And how could I forget compilers! LLVM might save the day for all of this stuff (except versioning and distribution... ick). Build a tool that can grok LLVM-IR, and you've solved the problem for most languages out there.
- astrange 6y ago> And how could I forget compilers! LLVM might save the day for all of this stuff (except versioning and distribution... ick). Build a tool that can grok LLVM-IR, and you've solved the problem for most languages out there. You do still have to maintain it. LLVM is just a compiler IR and reserves the right to change at any time. (same goes for other compiler IRs of course) I suppose you could use SPIR-V or PNACL which are based on fixed versions of LLVM.