Except when a bug pops up somewhere. Ownership/Responsibility changes in sub-Planck-second time when assigning blame.

Sveltekit is the fullstack/SSR version of svelte (like next is for react or nuxt is for vue). I reckon learning one of them might be helpful to learn component-based SSR and its benefits, personally I do think they have a firm place in the future of webapps.

Vite I can highly recommend, it's the best, fastest and least fussy bundler/builder I have ever used hands down (having used webpack briefly and packer for a while). Has some great features and is less of a pain to configure and get to work in my experience.

The CLI is scriptable/automatable and unambiguous when sharing instructions with coworkers. Both of these things make it very useful to know the commands. I do agree that it helps in some situations to visualize what is going on with a GUI/TUI though (neogit for nvim or magit for emacs are great if anyone is wondering), it can make things clearer at a glance.

Thanks for the summary and edits 🫶

Logging in to Kagi is a great way to deanonymize yourself on Tor.

You are correct, I don't care about cookies was acquired by avast. It is still GPL3 licensed and, according to the privacy policy, does not capture user data. But for those who don't trust avast (which includes me), there is an independent fork called I still don't care about cookies. The builtin Firefox cookie deletion settings are not granular enough for my usecase (with container tabs) and a hassle to configure for imo, which is why I still recommend the forked extension if it suits your usecase.

And how does that work? How do you unmount the root directory of a live system and invoke a script?

In Firefox, you can use the cookie autodelete extension (it's open source) which deletes all cookies for sites you haven't explicitly whitelisted. Same thing, integrates well with other privacy features on Firefox (like container tabs and I still don't care about cookies, and is probably better maintained than the feature in DDG.

IMO starting with a more minimalistic base, and adding whatever features you need is a better approach that suits more use cases. Just reduce your extensions to what you really need, and deactivate or uninstall those you don't need. Make sure what you are installing is open source, well-maintained and trustworthy (look at the github page: when was the most recent commit or release? how many contributors and stars are there? It's not foolproof, but a good start and definitely beats closed source extensions). Having access to more extensions is not a bad thing.

EDIT: don't use I don't care about cookies as it was acquired by some shady companies. Use the independent fork called I still don't care about cookies instead.

But... But :x is superior because it doesn't overwrite unchanged files with a new modified date :(

Yeah this has been my experience too, I graduated a year too late >.< I've already invested so much time learning web dev, I can't give up now. But I wonder how long it will take to find anyone who'll hire me.

Man I needed to hear this. Thank you! I feel you're right but there is so much doom and gloom reprting floating around in the headlines, YouTube and the internet. Trying not to get disheartened looking for my first employment as a dev.

Nextcloud is a FOSS fork of OwnCloud. Both projects are great in their own way, hugely successful and serve a lot of people very well. They just moved in different directions.

This is just one example of many. Ability to fork is super important to ensure that projects stay open source, like in this example.