All of these bring me a sense of dread, each in a unique way.
Java I have a special loathing for, but the ecosystem isn’t too wild, just verbose and so XML heavy.
JS is its own hell because of the sheer number of permutations of technologies a given project will use. There’s always at least one nonstandard framework or tool lingering around from an old trend.
Python reimplemented the same dep management wheels 5x each, and I have no idea what common stacks look like anymore, but every time I encounter Python projects, something is always broken.
C is nice and easy from what I’ve used (just GCC & make), but idk what complexity arises in bigger projects.
Just so glad I’m not a webdev anymore and work with mostly just Rust, cargo, and containers.
Honestly I think the main thing that the JS ecosystem does well is dependency / package management (npm). The standard library is very small so everything has to be added as a dependency in package.json, but it mostly works without any of the issues you often see in other languages.
Yeah, it’s not perfect, but it’s better than anything else I’ve tried:
Python’s approach is pretty terrible (pip, easy_install, etc.) and global vs local packages
Ruby has its own hell with bundler and where stuff goes
PHP has had a few phases like python (composer and whatnot) and left everyone confused
Java needs things somewhere in its $PATH but it’s never clear where (altough it’s better with Gradle and Maven)
C needs root access because the only form of dependency management is apt-get
In contrast, NPM is pretty simple: it creates a node_modules and puts everything there. No conflicts because project A uses left-pad 1.5 and project B uses left-pad 2.1. They can both have their own versions, thank you very much.
The only people who managed to mess this up are Linux distributions, who insist on putting things in folders owned by root.
Python reimplemented the same dep management wheels 5x each, and I have no idea what common stacks look like anymore, but every time I encounter Python projects, something is always broken.
We need just one more complete re-engineering of the packaging standard. We promise to get it right, this time. No take-backs.
PHP is crazy. While you are learning Laravel or Drupal you are learning the deep seated desire to shoot yourself over the lack of consistent use of type hinting, regardless of consent. :skull:
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
JavaScript is crazy. While you are learning React.js or Vue.js you are learning Webpack, Rollup or Vite.js even without your consent :skull:
C is crazy. While you are learning it you are learning Make and gcc without your consent.
Java is crazy. While you are learning Spring you are learning Maven or Gradle even without your consent.
All of these bring me a sense of dread, each in a unique way.
Java I have a special loathing for, but the ecosystem isn’t too wild, just verbose and so XML heavy.
JS is its own hell because of the sheer number of permutations of technologies a given project will use. There’s always at least one nonstandard framework or tool lingering around from an old trend.
Python reimplemented the same dep management wheels 5x each, and I have no idea what common stacks look like anymore, but every time I encounter Python projects, something is always broken.
C is nice and easy from what I’ve used (just GCC & make), but idk what complexity arises in bigger projects.
Just so glad I’m not a webdev anymore and work with mostly just Rust, cargo, and containers.
Honestly I think the main thing that the JS ecosystem does well is dependency / package management (npm). The standard library is very small so everything has to be added as a dependency in package.json, but it mostly works without any of the issues you often see in other languages.
Yeah, it’s not perfect, but it’s better than anything else I’ve tried:
In contrast, NPM is pretty simple: it creates a node_modules and puts everything there. No conflicts because project A uses left-pad 1.5 and project B uses left-pad 2.1. They can both have their own versions, thank you very much.
The only people who managed to mess this up are Linux distributions, who insist on putting things in folders owned by root.
You can use
~/.local/libandLD_LIBRARY_PATHfor shared libs.Or better yet just give in and use the
nixpackage manager, it is basically a virtual environment for your C programs.C dependency management is the worst. I thoroughly dislike how it works over there.
What dependency management lol
Pretending that the distro package manager is a suitable tool is not enough? Kids these days smh
We need just one more complete re-engineering of the packaging standard. We promise to get it right, this time. No take-backs.
PHP is crazy. While you are learning Laravel or Drupal you are learning the deep seated desire to shoot yourself over the lack of consistent use of type hinting, regardless of consent. :skull:
Preact is actually usable without build tools. It can be loaded like the good ol’ jQuery in modern browsers.
Good ol’ jQuery - never thought I’d hear that
Also missing SASS/SCSS/Tailwind, bootstrap, and Babel
I like Tailwind. It makes me not write CSS or any preprocessor DSL. It’s nice.