261 private links
Programming with HTML, CSS and JS :)
The website has a neon title with pixellised icons and multiple themes are available for the website.
The blog: https://localghost.dev/blog
Writing recently about Hotwire, SPA, and Dev stuff
because it does not fit long-term.
I was lucky to learn this lesson very early in my career: there is no silver bullet, any single tool, no matter how good it is, must be evaluated from the engineering point of view of pros and cons. Everything has a cost, and implies compromises. It's a matter of ROI. Which is hard to evaluate without experience.
JS technologies are reinventing the wheel and breaks compatibility often. More examples are provided.
So it is coming back to reason:
- YAGNI is popular again
- Vue, HTMX and unpoly, alpine.js or just vanilla are getting traction.
- There is talk of coming back to using Postgres for most things.
You do need the cloud, containers, nosql, go, rust and js build systems. Modern software requirements, customers’ expectations and incredible new features are not to be ignored.
Just not for everything.
It follows the slow pace of the software. The one's that evolves slowly are here to stay.
Following the same ideas: "my product is my garden" https://herman.bearblog.dev/my-product-is-my-garden/
Because it can leads to (better) answers with less time needed.
In a nutshell:
- I think we are overly focused on learning programming languages instead of programming models,
- We should try to make the coding models learnable in the programming languages people use.
All of these sound good to me. The thoughts are in contradiction with some terms of the current IT developments and programming.
About the current state of the software:
- it is getting slower as demonstrated by the latency. A computer from 2015 is 2-5 times slower than an Apple 2e from 1986 just at reading a keystroke and displaying it on screen. https://danluu.com/input-lag/
- putting all-in-one software increase complexity, and maintenance costs. They become untrustworthy.
- they are more a liability than an asset
I take some quotes out of it.
Humanity didn't get good at building houses by building the same house a million times. We built lots of different houses and learned from each other's failures.
As a programmer, I've tried multiple times in the past decade to create services just for myself and a few friends. Each of them has fallen away after a year or two. And a big reason for that was the burden of keeping up with updates for all the tools they depend on.
My initial plan had been to create clones of apps for myself and take out lots of features. [...] I didn't expect to find myself wondering what a web browser for memory palaces might look like.
Solutions
- making forks instead of all-in-one software. It keeps them lighter.
- we can have a huge amount of softwares. It is ok. Prefer software with thousands rather than millions of users, that seldom requires updates, that spawns lots of forks, that is easy to modify, that you can modify.
Another personal blog :)
Des avantages d'être un développeur ennuyeux.
- le pragmatisme
- la stabilité
- l'économie
- la simplicité
It depends on the type of discussion:
- Soil is the property of running code in that language.
- Surface is how the programming language
- atmosphere represents things that aren't the language or its code, but the broader community.
I agree :) I am dead after work, so it is useless to "have to be productive" again.
Instead doing something we love is great!
Shit, it's programming for me.
A great OSS developer in the Vue ecosystem