Recent searches
Search options
Haskell. Its tool chain and version management pose significant hurdles, admittedly.
While the language itself inspires wonder, I must confess that the tooling falls short when measured against the high standards set by contemporary languages like Go and Rust.
In all fairness, we should recognize its historical context, where Haskell competed with C. From that perspective, its advancements were indeed commendable, and it's miles ahead of the rather "horrible" tooling in C.
#Haskell
@Amirography
Man, when in history Haskell ever actually competed with C? Also can you cite some of the shortfalls of the tooling? The GPTish lack of reference in your claims leaves me wonder.
@exa the competition I meant was of course of paradigm, where C being a champion of imparitive approach and and haskell the opposite.
This I find to be a rather common comparison.
@Amirography hm "neumann legacy" is kinda weird even with C. Is it actually a competition though? There are literally things that you can do with one approach but are literally unthinkable in the other one (but that's ok because no one would sanely choose to do so anyway). Imagine implementing `pandoc` imperatively versus say `pv` functionally... :D
@exa honestly I was just emphasizing that probably haskell's tooling only had to satisfy the standards of the time that the major players at the time were C.
@Amirography ok depends "which time" though...back then before usable cabal (mid 2000’s) there's been perl, PHP, java, few remaining prologs, veeery good lisps, plenty of magical closedsource C++libs, and a few other things with pretty good packaging systems (relative to the standards back then). C packages kinda exist as the "autoconf" ones, these are in use to date with no significant change in sight, but that's hardly a C language-related effort, more like unix/gnu distro related.