froztbyte

just stop posting

When I first read it I almost replied with the well guy meme :)

(your comment didn’t really say anything to make its tone or intent clear)

that’s…extremely off the beaten path, and incredibly very not how most people use / experience email

for the viewers at home: treat this as extremely niche through outright bad advice to follow if you ever want to try set up your own mail

(e: there are more than a few parts of it that are also laughably insufficient for what it aims to do, but this isn’t the place and it’s saturday on top; free tech support comes on other days)

I go have one rare afternoon nap and the (un)professional services posters come out on stage, smdh

disclosures for ants

also the other one, where this feature gets lacklustre uptake but not enough to kill it, and then it just gets sorta shoved into a side panel, and then every so often it's turned on by default again because someone updated the config/prefs code or some other banal-but-instantly-effective reason (presuming it's not even intentionally turned on again by adding new default-on settings for "different" uses-that-to-build features)

also I believe you'll greatly enjoy reading https://lemming-articlestash.blogspot.com/2011/12/institutional-memory-and-reverse.html

I think that sequence of events happens sometimes but not all the times. the generational-departed programmer thing happens more in bigger orgs or teams with a bit of a more established presence/footprint. and I don't really get the impression proton is that big yet

this one smells more like the other kind of ratfuckery I've seen in shartups: some particular bugbear/feature-idea "driven" by a C-level/owner/teamlead (where "driven", n.: "someone said go do it"), enabled by complicit PM/POs doing some goalwashing, with devs either just keeping their head down, or actively participating in creation

older-era computers aren't all great on power. the different between something like a c2d and i3 was immense. it's still absolutely fucking mental how little power the apple arm shit draws (for what it does). something like a kill-a-watt or so would be the easiest to do some measurement

I'll hit you up elsewhere a bit later and share some ideas for backup :)

bit of a whoopsie walkback after caught pants down

totes normal. everyone has this all the time, amirite?!

yeah, you can get quite damn far with something like that. best other advice I can give you is to make sure your provisioning and backups are solid (because something will break sometime), and to keep an eye on power draw

not everything needs to be 902834098234 cores and distributed systems shit

Question for the experts: do you all suppose this will drive a new cycle of hype around thin clients and network booting?

I don't think this alone would push towards that (any more than the last few years of "everything is a webapp!!!!!!" have done), but I would love to see people try to hypewave this purely so we get rid of so much fucking fat js garbage