The cure for this is 1.2 million copies of Malwarebytes, cleaning this shit off.

Sadly, I am dreaming if 1.2 million people would visit malwarebytes.com, download their stuff, and run it regularly. :(

Some people still life in the free world.

In IT, development, there are often a lot of different ways to achieve a thing. Version control is one of them, for most basic needs most version control systems offer the same features. Subsversion, mercurial and git? I can use any of them and have all common needs met. So why demand specific knowledge of a specific solution?

Because of shit for brains developers. They are ALWAYS on the lookout for the magic tool that means they don't have to do their job anymore and insist solution X is the only solution until a new flavor of the day comes along.

Here is a warning sign, if your a web developer and the job/project uses more then two programming languages, RUN! It means the developers are hammering in their flavors of the day creating a mass of code in different languages, 9 times out of 10 completely depended on a specific config and version that nobody wants to bother with anymore because their experiment failed and now they want to experiment some more.

I recently did an interview where more and more requirements kept cropping up and more and more languages with the backend being written in javascript, php and python. Ooh yes, I would LOVE to become responsible for fixing that mess. NOT!

Interviewing is like dating, its main goal is NOT to find true love but to ditch the crazies before they found out where you life (but I will get you my pretty oh, yes and then we will be happy FOREVER) anyway, if a job seems to suck during the recruitment process consider yourself warned and move on (but I will never let you escape!)

This was the whole fucking point of computer languages in the first place.

So that, not only would programmers NOT need to specialize. . . .
But also, so that a company that works in a niche technology would have a wider supply of workers who can easily adapt to that niche technology.

So that brings us back, AGAIN, to the main point of this discussion: HR and recruiters DO NOT UNDERSTAND TECHNOLOGY, or the workers, or the skills. Therefore, their job requirements suck.

You got a good dental plan?

'Truly private money is an inferior alternative to the money that comes with the backing of a political authority.

Authority to govern comes from the consent of the governed.

So anything that's true about "government money" is also true for private money.

we don't know for sure, but I don't want to find out the hard way, better to play it safe and not burn it all

There is no doubt in my mind that we WILL find out the hard way.
I think we may have had a chance had we acted on this in the 1970's. When we DID have the technology, and the understanding.

A billion people in the world are going to get access to AC and clean water over the next 50 years.

With growing loss of biodiversity, and ecological degradation, I would ask: what the fuck are these people going to eat? Who's going to employ them so they can afford AC and clean water? Where's this magical water going to come from - the exhaust pipe of a leaky nuclear reactor cooling condenser?

They DO have a thing called "winter" in Phoenix.

While, I do think that they could benefit from a lot more PV and solar thermal use (they're using incredibly scarce fresh water to cool that nuclear power plant in the desert), I can see why they still need clothes dryers.

The AC, IMO, is more a function of culture than necessity. Folks in these warmer climates DO tend to overcompensate. When I was in Illinois, people would crank them up full-blast in the summer, because it was so damn humid outside, and it felt so damn good to come inside from being out in it. But not so good to sit in the chill all day long, freezing your ass off.

My data plan is only $240 per year (on top of a plan for just voice data that I'd be paying with a dumb phone anyway). If I really didn't want to pay it, I could rely on wi-fi networks or just use apps that didn't require the internet.

However, always having the internet with me is a far greater killer app than being able to be called everywhere as far as I'm concerned.

Stick transmissions are less convenient and don't really get much more than marginal benefits compared to modern automatics and CVTs in terms of fuel efficiency or power, especially since most drivers don't shift as efficiently as an automatic system can. Most drivers over-rev, and learning to drive efficiently is a skill that takes time and effort. A stick shift is more or less just the illusion of control.

Manual transmission is to car drivers what vacuum tube amplifiers are to guitar players. The only real advantage is cheaper maintenance.

Funny, for someone who supposedly doesn't accept high levels of data collection, you seem to mock anyone else who actually cares.

And ineffectual.

We have whistleblowing protections, but in both of their cases, those protections do not apply. Government protection for government whistleblowers really only extends to financial fraud and waste and to workplace safety and other regulations non-compliance. It doesn't apply to officially sanctioned policies that are in legal gray areas, and it does not provide any exceptions (that I am aware of) for the release of classified data to the parties you are blowing the whistle to. Telling Congress or their superiors about acts they had no business knowing would have simply landed them in jail without any positive effect.

So what options do you speak of?

To call them "collaborators" is somewhere between spin doctoring and malicious slander. They provided information to the public without any specific intent to collaborate with enemies. If such people also picked up on the information, then that's the breaks, but it should not make it illegal to tell the rest of us what is going on when the government is acting without accountability and in ways hostile to the public's interest.

Your bog-standard disposable plastic shopping bag, (which DOES get re-used, at least they did in my household, before they were banned in my county), will degrade in about 2-3 years, when exposed to direct sunlight, (UV). When buried, it's a different story.

One of the really damaging plastics out there is large-scale plastic sheeting used for trapping moisture in farming. It's polyethelene, and it stands up to more UV abuse, and they come in sheets hundreds of yards long. When they get blown away or washed out to sea - they definitely cause harm to wildlife. Several beached whales have been found with this crap bunched up and blocking their digestive tracts. The thing is: for shorelines not managed by humans, that whale carcass will rot away, and that plastic sheeting will wash back out into the ocean, and threaten more marine life.

Tried it.

"error loading firmwares" - - - having to go back and locate 1, 2, 3, (how many more) proprietary firmwares made installation a bit more painful than I had patience for. (after dealing with Legacy/UEFI boot issues).

Also: latest Debian kernel seems pretty old compared to what ships in the latest ubuntu release.

But I really feel the community drop-off in ubuntu, compared to a couple of years ago. And that's pretty important. They're going the way of Red Hat.

At some point in their careers, all programmers, after spending a month hunting down a heap corruption, or a race condition, or some other bug nasty like that, come to the realisation that they are spending more time fixing mistakes than writing code. At this moment, most, but not all programmers follow a very logical path of reasoning. They think to themselves, "well, if this code took me 1 week to write, then 4 to fix, that is five weeks, what if I spent 3 weeks writing it carefully, then it would be done right away and I wouldn't have to fix it, I could have been done two weeks earlier!".

From that moment on, this programmer becomes all but useless to their current and future employers.

"Why?" Seasoned veterans may ask. "It saves time in the long run! You are just focussing on the short term results, being distracted by smoke and mirrors and building upon pillars of sand!"

Well, that is occasionally the case, but not usually. What is more often the case is when something is implemented it is either not what we needed or not implemented how it should have been implemented. When something is more or less built, nomatter how badly it is built, it is so clear and obvious what we needed instead and how it should have been made. If you had done that useless feature badly in 1 week, it could have been thrown out and we could have moved on. Sure, your experience might have told you that this was a waste of time, great, could you have told everyone what we really need? Are you going to take the reigns and pull the project in the right direction, or are you just going to be content in doing nothing in preference to doing some useless task?

The thing is, sure, you might do the right thing, in the right way the first time and the twenty year old across the room probably will do the wrong thing, in the wrong way the first and maybe even the second time. However, are you so positive that you will be finished before that twenty year old has finished his third and correct solution? Are you sure that what you build will be better than what the twenty year old builds after two attempts? Is your stable and clean version so much more useful to your team than the twenty year old's buggy first attempt that they will be happy to go without even seeing it for another few weeks, when they could have continued using it as a prototype or placeholder for a less buggy version.

Anyway, a few general maxims to stay relevant as you get older: 1) bad code is not so hard to rewrite 2) useless code is even easier to delete 3) if you're stumped on a problem, just try something, if it's wrong, you'll find out very soon. 4) no amount of experience, no amount of guile, no amount of planning or foresight can compare to a little intuition, a flurry of activity and being willing to make mistakes.