hairyballs

Genuine question: what's wrong with templating engines?

My coworkers do document the code:

/// Returns a list of foos, given a bar. 
fn get_foos_from_bar(bar: Bar)

Htmx is a godsend for that. You actually write HTML while having AJAX easily.

The desktop website is so bad... I ask for a light theme in my settings, they don't care (it's white on black) because it's HARD to add a few CSS rules. Then there is a flash of light which could give a seizure to someone with a condition. It's shitty design at its peak. That doesn't really inspire confidence...

Firefox is really badly integrated in MacOS. The fn + arrow shortcut doesn't work, for example, it's not integrated in the menu system (the menu shortcuts don't work) etc. But there is Sideberry, so...

Nope, my webpages are not just nested divs. I use nav, main, form, select, etc to name a few. I actually use very few JS. It's mainly for communication with the server when I need AJAX to retrieve data.

It's much easier to work with streams of untyped data in a weakly typed language.

Funny, I think C++ is literally the worst language to learn programming. I would go with JS or OCaml at first, then Rust if they need manual memory management.

This is especially true for steam... what a crappy app

I have a degree in philosophy (and no other diploma) and I make $200k/year as a senior developer. The degree does not really matter.

I really like this instance, so of course I'm 100% for the move

What is "funny" is that I had the maximum password size thing on several bank websites (and a low one, at that). Fortunately, with 2FA, it doesn't really matter I guess.