3 ms·
I am an amateur developer (my own stuff and open source) and I always pick the same stack when writing something. This is because I found the optimal, third-bes
by BrandoElFollito 2y ago
I am an amateur developer (my own stuff and open source) and I always pick the same stack when writing something. This is because I found the optimal, third-best stack that pretty much fits everywhere with minimal friction.
It is not optimized. It is not the fastest. But it works everytime.
This is akin to using the arrow library in Python whenever I have to do the slightest date whatever. Display a date? arrow. Manipulate a date? arrow. Store a date? ISO. Yes this is a dependency, yes, there are edge cases but it mostly works - certainly better if I had to understand dumb vs full dates etc.
Unfortunately I am a curious and excited person and I keep changing this "ideal stack" twice a year but still.