NPM
When I was a kid, making websites, you'd find some library that you wanted to use, then you'd either copy the .js file to your website or use a cdn host and add the .js to a <script src>on your webpage and you'd be using it.
It seems like now you find a library that you want to use and the expectation is that you're using npm.
Now let me just say, I get the point of npm. I get that at a certain point you want to make all your javascript one big bundle to minimize the amount of files that the client downloads etc.. I get that having a package manager makes sense.
But something about it surprises me.. Is everyone using this? Are normal web developers typing command-lines to add packages? Are normal web developers running a command to build the javascript every time? Are they setting up an intricate system to auto re-compile on change? Are normal web developers dealing with multi-second compiles every save?
Is this why no-one makes their own websites anymore?
The thing I noticed for myself was how I slowly switched from handwriting over to frameworks. These days I tend to use SvelteKit and I'm pretty happy with it. I honestly don't know if I'd currently have fun in web development if it weren't for Svelte. I used Gatsby / React before and it became a dependency hell. (The big reason on why I've not updated my main website in a while, still building up courage for the big rewrite in Svelte.)
It really is a big shame how monotonous the modern web has become. Everythings on a few big platforms, and websites which are actually standalone are either some Wordpress template, a Linktree, or a barely customized website builder project. It's really a bummer, because each web developer really has their own handwriting. A good friend of mine and I can recognize each others designs just by the way we handle our fonts and colors. It's a bummer so much of that is lost in the modern web.
I should add I'm in my early 20s, so I sadly only caught the tail end of "the old web", but I've always had a facination in the kinds of websites you find 10 links deep on some old forum.
-- Kevin
Nowadays, you can find a package for basically any action you want to accomplish to the point where its getting silly. I personally keep it limited to only a couple of packages and have base templates to accomplish the task at hand.
When it comes to rebuilding each change, that's usually not the case and there's multiple solutions out there which allows you to just auto hot-reload your solution as you're working on it. I only really build and compile at the moment of pushing to production.
It sounds silly but I think it's true for most programmers who choose web as their starting point. Unlike application programmers, they usually have some exposure to the command line interface, at least "Hello, world!".
Obviously, for web programmers, there is almost no CLI here, only a few Linux users really need CLI to install IDE and running environment. Otherwise, your job will mostly be: go to htdocs, create an index.htm file, type "Hello, World!", and open localhost in the browser.
Before 2016, no web programmer I know can use CLI as part of his job, even if he needs to touch other parts of the job like GIT or HostServer, what he does is use any GUI application instead of typing the command line. And, who fucking cares?
I quite like the idea of โโnpm and js-frameworks that aim to pre-compile resources. But the issue of reducing the overall page load size or bundling dependencies into one file is not interesting to me. I am more interested in the idea of โโ"reducing dependency on CDN". But obviously doing so will make us dependent on the package manager. Is the idea of โโredirecting dependencies from A to B - in this case from CDN to NPM, a good idea?
In more than ten years of working with the web from school, amateur work, to professional work. I have witnessed the development of web browsing technology. With my limited access to WAP browsers at that time, until working on computers using IE, and then Opera, FireFox, Chrome, ... loading a web page with resource components is constantly improving from protocol to rendering program.
Not only that, even the Javascript interpreter is getting more modern - with ES Module support directly in the browser.
So what NPM is doing, I see it as fighting against this development. Silly, right?
Anyway, NPM or JS-Frameworks are still doing a good job of simplifying many complex things in the process of developing web products, at least reducing a lot of copy-paste effort. Otherwise, why are there so many people using it - including me *LMFAO.
Although the number of products I do using NPM is the majority., but I spend more time with Javascript-Vanilla (or Web-Vanilla). And I believe that many other older web developers will always find Vanilla something attractive.
I am a programmer born in the 90s of the last century, currently have good experience in developing web, server, protocol, desktop, mobile, IoT (arduino, avr) applications and an emerging player in reverse engineering. I am doing R&D work on technology products. I often prefer original things, experimenting without being bound by dependencies, this helps me easily find new inspiration in research as well as find ways to help products become better and better.
Add a Comment