I have to admit, not working at a startup or FAANG-scale company, I'm amazed to see the place I work mentioned, even just as a note, on here. Fun little double-take!
I absolutely agree that plaintext email should be kept alive, but is it really "many" for 99% of companies? I'd be shocked if anyone I know told me they disable html emails, even when I do it myself most of the time.
In my experience with recent thinkpads, my battery life never really beats the w10 install it comes with. Not sure if there are some very clever windows-only optimizations or what, but that's what I've noticed.
Complaining about the communication and response time of a company is different from yelling in the direction of some stressed engineer that they are useless and incompetent at everything they do. Sadly you get too much of the latter around the Internet.
Interesting, over here I would say et Dukkehjem (a doll's house), Vildanden (the wild duck), and Peer Gynt are his most known works, probably not-very-closely followed by en folkefiende (Enemy of the people). Fascinating.
As in Norwegian, I have to ask... is Vildanden (the wild duck) not one of his most known/iconic plays outside of Norway? I would say it's easily one of the three defining plays people would know about over here, so it confuses me to see it mentioned like this.
I'm pretty sure there isn't a ton of background fetching asides from marking servers as unread, it can take a bit to actually load the messages when you click an inactive server, and it won't have any new messages if you don't have a connection (even if it had a connection when it was sent)
I honestly don't think I would want to keep working with webdev if I had to go back to relying on server side rendering for everything, the workflow is just _so_ much worse (to me).
There was a straight up jailbreak app that got through the process with a single button and all it did was apply the exploit to your phone. So I guess I wouldn't put too much faith in their reviews.
I've seen a lot of people talk about having a separate table for ids that should be removed when you restore a backup. It seems like a plan pretty viable solution, at least from what I've seen.