Modern airliners do away with most dedicated instrumentation (a few critical ones such as airspeed, compass heading, and altitude might still have analog backups) and use a few screens to display all of this. Computers monitor most of the parameters and issue alerts when anything is out of normal.
The liability limits on most renters insurance policies are low $100Ks, because most renters don't have many assets they need to protect. This would be pretty inconsequential in the scenario of "burning down the apartment complex."
Landlords/owners have their own fire and liability insurance (ultimately paid for by the tenants as part of their rent); it's unnecessary to demand that the tenants provide their own. Renter's insurance is for the tenant's protection, not the landlord's.
My leases always point out that the landlord's insurance does not cover the tenant's personal property or liability, and recommend renter's insurance. But it's not required.
Modern installation is direct bury. There are no trenches, no way to run new cables without new directional drilling. In any already built areas, these projects are constantly hitting gas, water, sewer, cable, electric, and other already buried infrastructure. Maybe (probably) it's still cheaper than launching satellites but it can be quite disruptive.
Perhaps there will be communications nodes in LEO with high bandwidth directional links to heavy compute nodes in higher orbits? At some point I would assume that the jurisdiction of the FCC no longer applies? Or maybe you use laser links?
I still cannot believe it's economical to have "data centers in orbit" but I guess the truth will be seen in whether or not it actually happens.
You can see it all over the USA, there are many localities and routes that have banned outdoor advertising, and when you're traveling on a parkway with nothing but trees on either side and then you come to the end and there are billboards every 100 yards it's really noticable.
Same here. This has only been a thing recently when landlords figured out they could make money selling the insurance. When I was a renter, insurance was never required from me.
The U.S. Federal minimum wage is $7.25/hr. Some states or localities might have higher minimums, but it's been a long time since I've seen any jobs paying that little. McDonald's here is about $15/hr to start and jobs go begging. CoL here is not the lowest but it's not like a major urban center either.
It's been a number of years, and all I really remember is coming to the conclusion that "emacsclient only works with a local server." It uses a domain socket for this, but forwarding that from a remote server doesn't seem to be enough.
Simply editing a remote file over an ssh connection is easy enough using TRAMP, but that isn't the same as accessing existing buffers in a remote server.
Used to work with a guy who would frequently say "a comment is an apology" i.e. the comment is there because the code itself is not clear. That can be the case, but I generally find more comments better than fewer, especially if they relate the code to actual business or functional requirements and don't just restate what the code is doing.
Years ago I would often write comments first. I.e. start with describing the overall goals. Then break it down into routines and order of operations, all still in plain english. Once I was happy with that, I'd break up the comments with blocks of code. I guess this is sort of like "literate programming" though I was doing it long before I ever heard that term and I still have never read much about it. It's almost more like I was prompting myself towards the end goal. The downside of this approach is that the comments do end up more or less just explaining in english what the code is doing, so maybe aren't quite as useful to future maintainers.
Emacs itself can run as a client and server. To start the server:
emacs --daemon
Then use `emacsclient` to connect to it. All `emacsclient` instances whether in terminals or GUI are using the same server and can access the same open files and buffers.
Unfortunately it only works locally. I've tried to forward the emacs server socket over ssh to a remote client and it doesn't work.