I agree, once you know the patterns and the foundation of the web new tech is not that hard to adapt to. I agree as a new dev it can feel like a bottomless pit, in the same way low level programming feels for most new devs.
That said web frontend has had a wild ride the past years. But its really starting to stabilize now, around a few core frameworks (react and angular for example). Sure there is still forks and revamps but its not the big world changing differences (like going from jQuery to react was).
I have not lost a file in 10years. I have a NAS with backup to the cloud, nothing fancy just a single drive NAS with automatic rolling backups. Important files go to multiple clouds.
There does seem to be an increasing interest in physical mediums. Or perhaps that fad has faded already.
I know some of the younger guys at work have started collecting vinyl. For a short period, it seemed like cassettes were hip too. I have no idea if that ever got going.
A hack is to use a regular chromecast and a hdmi to rca/spdif adapter/splitter. Works pretty well and you can get them pretty cheap (in the ballpark of $20). But it will be more expensive than the chromecast audio unfortunatley
The Right Thing™ for a project that actually has multiple contributors is that the CI pipeline rejects code that based on the compiler diagnostics is either definitely wrong or, if it was correct, should be annotated in a way the compiler can understand and stop emitting the diagnostic. It doesn't matter whether one or another contributor has this switched off or ignored it.
That is, committing this code should have had the same impact as if it was missing the semi-colon, the library doesn't build, tree is on fire, fix before you do new work.
Of course if your code is in sufficiently bad state, you might find it's frustrating to have say 500 bugs to solve before you can get the CI pipeline to output artefacts. I think that means you didn't have good software and you must fix those bugs first, but if you're convinced the software is good it can be tempting to instead disable the diagnostics telling you otherwise and press on.
The big thing is that nuclear is more predictable. Downtime is scheduled most of the time. Wind is weather dependant and can be producing noting even if demand is high. This can be mitigated with storage like the 2 dam systems where you pump water uphill when there is a surplus (but that cost efficiency).
Well that's illegal in almost all (western) countries. A device need to have an declaration of all radio equipment inside in some form (depending on locale).
It also would be a lot harder to profit from ads when you have to pay for lte bandwidth especially with the prices in the US.
> Well that's illegal in almost all (western) countries. A device need to have an declaration of all radio equipment inside in some form (depending on locale).
I agree, but I'm pretty sure that it will be buried on the declarations page.
> It also would be a lot harder to profit from ads when you have to pay for lte bandwidth especially with the prices in the US.
You vastly overestimated the costs of wholesale network access, which is surprisingly cheap, that's why Kindles (for the most part) do have Amazon-provided SIM cards. Bad news is that you can't get it: basically you need commit to a minimum bandwidth (in hundreds of terabytes range) with a minimum subscription count (in hundreds of thousands range) to get these cheap prices, which would be more expensive than individual plans.
Depends? Amazon's SIMs are locked to the specific Kindles, so you need to clone at least the radio identification codes (like IMEI) that is used, and you need to relay that to a specific proxy operated by Amazon because the network-in-question would block (on behalf of Amazon) other servers.
I imagine that in case someone has implemented this, it would be locked in a similar way to ensure that it can only access those ad servers and nothing else.
Personally I didn't want passive collection phoning home if, at any point, anyone connected it to anything, and there is also the possibility of connecting to open access points.
And, well, saw no reason for leaving around untrusted unreliable crud I couldn't remove. It was worth a modest markup to get rid of it.
I usually just connect the "smart tv" to the internet once a year and update the firmware (after checking the change log for useful fixes). Then I disconnect it again and use my chromecast to stream.
Good idea, but before I'd update I'd doubly check the net to see there are no new/hidden gotchas as some have reported (like the way some manufacturers have coded around Pi-hole, etc.).
That said web frontend has had a wild ride the past years. But its really starting to stabilize now, around a few core frameworks (react and angular for example). Sure there is still forks and revamps but its not the big world changing differences (like going from jQuery to react was).