... That even *IF* we could, however hypothetically, completely trust the government to not abuse the ability to eavesdrop on private conversations, and that the government had absolutely no security leaks whatsoever....

Again, I stress that *EVEN IF* absolutely everything was working exactly as such a government intended...

... it is unavoidably true that if the government has the ability to break your encryption, however altruistic they may claim their intentions to be, then so can the bad guys... people with less benevolent intentions, who will abuse that information, and cause harm to completely innocent parties.

This is because laws don't actually *stop* people from breaking them, they only ensure that something that is considered appropriate punishment will follow when people do. Unfortunately, such punishment cannot always negate the effects of the harm that was done while someone broke the law in the first place.

And again, this is even *IF* their system for eavesdropping on encrypted communications was function as best as they can possibly intend.

So hey, Mr. Cameron.... I can sincerly appreciate that you might have the very best of intentions, but your goals will deprive entirely innocent people of the ability to even have the most rudimentary protections from people that will use the same abilities that the government has, however illegally, to cause very harm to people who have done nothing wrong except to follow a law that says they are not allowed to take precautions against such means.

This. We got 7 billion people - probably closer to 10 before it peaks, and as a minimum I should have one IP address at home, at work and for my cell phone. So 3*10 billion is 30 billion, IPv4 can offer 4 billion. And that's not counting every other odd thing I might want, like remote-controlled alarm/heating/whatever at my cabin or my car, servers of various kind and maybe IoT will become good for something.

Of course they probably could have just done it much, much simpler by making a dotted quad a dotted quint:

1.2.3.4.5

For compatibility each host under 1.2.3.4.x is granted 256 ports IPv4 ports mapped from x*256 to (x+1)*256-1 to a designated "IPv4 compatibility ports" like say the last ports from 65279 to 65535. So 1.2.3.4.1 can either be fully addressed by quint-capable equipment or 1.2.3.4:256-511 that'll be mapped to 1.2.3.4.1:65279-65535. And 1.2.3.4.2 will have 1.2.3.4:512-767 mapped to 1.2.3.4.2:65279-65535 and so on. You could use the same technique to provide a virtual IPv4 interface for legacy software, it thinks it is listening to 1.2.3.4:256 but it's really listening at 1.2.3.4.1:65279 - and any application it tells to connect to 1.2.3.4:256 would work.

That would have led to a gradual 256-times expansion of the address space without any hard switch-offs. But instead they decided to solve everything and now 19 years after the IPv6 standard we're still only barely in motion.

If you're working on the equipment, and it shouldn't move, you put a padlock, with a nametag, on the switch and physically lock the power out. You take the key with you into the workcell, and only you are allowed to remove that lock.

If the robot must be moving (typically, when you're teaching the robot the path it should follow), then every single person in the workcell must have an active deadman switch (anyone lets go, the robot emergency-stops). And you run the program at 10% speed so that you have time to trip the deadman or get out of the way. The workcell itself is fenced off, usually with either a tripwire or electric-eye switch that will e-stop the robot if triggered.

I used to work for a robot company, and we enforced these rules religiously. When I went to visit plants and work on the robots, they issued me my own padlock and tags for lockout/tagout. Someone had to have skipped some safety procedures in this case.

Indeed, in most places, a bug where the system crashes is the most severe possible bug. When dealing with robots, that's only the second most severe. The most severe were "unexpected motion" bugs, where the robot didn't follow the path in the correct way or otherwise didn't behave predictably. Those got everybody's attention.

I meant password, of course. Sorry, not fully awake.

Also, don't give your SSID to anyone who does or might in the future use Windows 10, or have a Windows phone.

The very page you link to says:

What's ICU?

Not sure exactly how much Qt functionality you'd lose, but it's an optional dependency.

The difference makes itself up quite quickly only *AFTER* the car is finished being paid for.... The point of getting a loan to buy a car in the first place is to get some immediate benefit for some longer term sacrifice (you pay more money overall)... but paying more money every month for a car that costs more than what you'd pay for a similarly sized conventional vehicle even *after* you factor in the cost of gasoline doesn't offer any immediate benefit at all..

The alternative is to just buy a new car in cash... but not everyone has that kind of money lying around.... even if they haven't bought a vehicle in many years.

FTA:

it shares Wi-Fi passwords with the user's contacts.... Those contacts include their Outlook.com (nee Hotmail) contacts, Skype contacts and, with an opt-in, their Facebook friends

So it seems that it *DOES* send out your wifi password... and I see this as less of a problem for myself, since I am neither a windows user nor do I have a large online social network, than it is for me to let specific people use my wifi while they are visiting my place, since if they have not set their own security settings appropriately, something which I cannot administrate, my wifi password would end up getting propagated to everyone on *THEIR* contacts lists. While they may only be able to use it if they are nearby, that is entirely beside the point.... these would still be people that I did *NOT* authorize to use my network.

Chernobyl didn't explode and contaminate Northern Ukraine, Belarus and parts of Western Europe because it is a state run enterprise and immune to market forces that cut corners.

Oh. Wait.

There's kind of a difference between storing passwords in clear text on a device that you still need to have physical access to in order to learn what those passwords are and actually broadcasting such passwords to absolutely everyone who happens to have a particular social network connection to you

Or maybe it's okay if systemd fucks up all the servers running RHEL 7. After all, nothing important runs on that. So let's check, is Red Hat Inc. tanking and considering backtracking? Hell no, they're growing strong both in revenue and profits in the year that's passed since. So if a $14 billion dollar company can make systemd work for them, it probably can't be that bad. Or if it's bad, well then rip out the bad parts like write a non-binary log because how hard could it be to take the binary messages, printf and log the text in addition to/instead of a blob? Sometimes it sounds like the only two options is to drink the kool-aid or nuke it from orbit.

Not sure if you're stoned or trolling or dropped out of a time vortex from the 90s, but

1) GUI installers have been the norm for desktop oriented distros for years, mostly through live CDs.
2) For most of Linux history there's been zero credible competitors to X
3) Wayland is mainly driven by ex-X developers
4) Wayland will still need drivers to have accelerated graphics

5) Neither application developers nor users usually see X, you write against for example Qt and the toolkit takes care of talking to X. They might hate X, but they hide its quirks pretty well.

It was refuted in the 1970s, not the 200's. It was never a popular theory. No one should doubt Global Warming on the basis that the scientific community switched its stance. It never did: the majority of scientists were saying it was warming all along.

It has been called "climate change" since before 1988, when the Intergovernmental Panel on Climate Change (IPCC) was formed. Today, people act like the name is some kind of knee-jerk defense against the switch between "global cooling" and "global warming" when in fact, there was no name change at all, nor was there ever a switch.

I think those wanna-be generals aren't really the community, but those who want to exploit the community to achieve their pet goals. To steal an expression from 4chan: The FOSS community is not your personal army. The opposite is less intuitive, but it also means the community isn't going to stand still just because your pet needs have been met while many others feel theirs haven't. For example I haven't heard much shit about PulseAudio in recent years, though initially it was rather crappy but it did add features that didn't exist before. Maybe in ten years time we'll feel the same about systemd.

+1

Not to be sexist, but most women prefer jobs that include more interaction with people and less time spent in solo problem solving, so it's not terribly surprising that she does't love coding. This isn't to say there aren't women who really like coding, or even introverted women who find working with people all day to be unpleasant. There are all kinds... but on average my observation is that women prefer more human interaction.

So, assuming that your wife falls into that category, there are lots of roles in and around software development that are more people-focused. Project management requires an additional set of skills, both people skills and management skills, but it's eminently learnable, and having a technical background is very valuable -- as long as it doesn't cause her to second-guess what the developers are telling her (always a risk with PMs, and even more with those whose technical background is shallower than they think it is. There's a tendency to assume that everything they don't know how to do is easy.)

Business Analyst is another good one. It, again, requires some additional skills she probably doesn't have but can learn. Industry knowledge tends to be important, but most companies are okay with analysts learning that context on the job. She also needs to learn how to gather and document requirements. A technical background is useful there because good requirements need quite a bit more precision than most non-technical people are used to. There's also a risk; formerly-technical BAs have a tendency to overspecify. An important skill for this role which isn't so easy to learn is writing. Good BAs are excellent writers, able to concisely and accurately boil complex issues down to simple statements.

Another option that might be excellent if she can swing it is Systems or Application Architect. Companies generally want experienced, senior developers to move into these roles, but smart but less-experienced people can do it as well. Architects take the business requirements and convert them into high-level technical plans/architectures. Architects tend to spend less time interacting with people than PMs or BAs, but still quite a bit since they provide the primary interface between the technical and business teams. Architects need to have good technical skills and good "taste", meaning a good feel for what sorts of structures are easy to build, easy to maintain and flexible, and for how to intelligently trade those issues off. They also need to be good at translating technical issues into language the business people can understand. Honestly I expect that your wife probably doesn't have the depth of experience needed to make a good architect, but I thought I'd throw it out.

Another that might be good if she's a good writer and enjoys writing is technical writing. Good tech writers have greater need for writing skill than they do technical skill, but the latter is very valuable because it enables them to more quickly and accurately understand the information that needs to be documented.

In smaller companies a lot of these roles get mixed and combined with other business roles, so another good option is to look for a position that isn't necessarily directly related to software development, but could benefit from having a deeply IT-literate person.

Finally, the option that I've long thought I'd take if I ever got tired of writing code is the law. It's a lot of additional training, but I think there is a deep and growing need for attorneys who understand technology. This is especially true in the areas of patent and copyright law, but I think it applies in many areas. Of course, the law may not have any attraction whatsoever for your wife.

Whatever, I'd really encourage her to take the time to figure out what she wants to do, and do that, rather than settling for something she doesn't really like. We so much of our lives working that it's really a waste to spend it doing something we don't like.