France has a pretty low-carbon grid (relatively) already, this doesn't fix the water consumption issue though, which is getting more problematic as climate change cause droughts all over the country.
If you're interested in leveraging web workers easily for repetitive compute-heavy tasks in a webapp, i've built a little library that takes care of launching and managing worker threads for you: https://github.com/GitSquared/rinzler
Netflix joined the Motion Picture Association not so long ago. I'd recon they are well into the transition from startup mentality to dominant bureaucracy-driven business mentality.
It's not just "some out of date bits", 90% of this post is ridiculously outdated.
Making an end-to-end encrypted web app with WebAssembly, WebCrypto, Service Workers and free TLS by Let's Encrypt is totally viable nowadays. Also, the Web userbase is largely using evergreen browsers like Firefox and Chrome.
Running side-projects at a loss prevents you from keeping a lot of them around, and might make it harder to decide to create a new one - "I want to do this cool project, but i already spend $X a month in hosting and I don't want to spend more".
> It's a link in the SF Bay Area, and the server is in Texas, so it has to get out there and back. That's at least 50 milliseconds right there when measured by a boring old ping.
Am I the only one surprised by this 50ms ping? I can reach cloud servers in the SF Bay Area from Paris in 50ms - and I'm on wifi. Surely SFO-TX should take much less time..?
Also, "I couldn't see any reason why it wouldn't work" seems to me like a very dangerous assumption.
I personally try my hardest not to declare that X works on/with Y until I've seen it with my own eyes. Not 2 computing environments are the same, and everything receives updates all the time.
As an open-source maintainer, helpful error/debug messages is the key to reduce the number of GitHub issues, mails and all the other way people will track you down to ask for your help.
Ultimately spending an hour writing helpful errors can save you hundred of hours in support.
Of course you can just ignore everybody asking for help, but then if people aren't going to be able to use your project why make it open-source in the first place?
Mainstream OSs are slow to evolve. While I agree that embedded DNS resolvers in browsers and the like should have an off switch, I think embedding in widely adopted software is the only solution to push adoption of these new privacy-focused protocols.
Pushing updates to ever-green browsers is the key to change how millions of people use their computer - since browsing the web is almost all they do!
I use viewport units (vh, vw) in my CSS to ensure everything scales to different screens/resolutions; so far augmented-ui seems to handle that very well.