Really, sink a completely full oil tanker? Who's gonna clean that up?

Board and confiscate, yea that might work if anyone has the courage to try it. Sink? Um. Nope. Too much environmental damage doing it that way.

The idea is to pick a time zone and stick with it. Nobody gives 2 craps whether it is DST or standard, just stick with it. For me personally, DST year-round "feels" more normal, so I'd be happy sticking with DST instead of just changing time zones completely.

Either way, we ought to pick one and stick with it. The changing back and forth is stupid.

In California, DST actually seems more "normal" a lot of the time. It's the switch away from DST that always seems stupid.

Agreed. They've hidden everything useful, wrecked a completely useable UI trying to imitate the stylistic cues of a river rock.

Microsoft can't and won't force me to use any version of skype. After MS bought skype and made some UI changes that made it harder to use, I just switched to facetime. "Problem" solved. Even my Mom is getting an iphone, in part so she can use facetime with everyone else who has ditched skype after MS ruined the UI.

Skype circa 2011 was pretty useable. It's been destroyed since then by UI mismanagement. I still prefer windows over apple OS and I use a windows computer instead of a mac, but for video chat and conferencing I've gone completely to facetime for no reason other than the skype UI has been wrecked since MS bought it.

Forcing users to "upgrade" to their latest crummy version is just one more push to switch services. There are plenty of alternatives.

Hostile management, 99% of the reason I left. Union contract had been up for renegotiation for 2 years. Company fouled up the schedule then blamed the union for an illegal work slowdown, a completely fabricated charge, and sued us. The judge ruled while the union lawyer was still en-route to the courtroom, more proof it was a setup.

3 months later the company realized how horrible a mistake they had made when they lost 40 million dollars (or more) and had to report to the shareholders that they couldn't follow company growth plans because guess what - they didn't have a contract after 2 years. Almost immediately the company agreed to the union proposed payscale but by that time it was far too little too late, the company had already proven itself utterly untrustworthy and hostile.

My new job required an initial pay cut, has nearly identical long-term income potential, and is harder work. But my new company isn't suing me over a pretend "illegal work action" so it's much better.

The money isn't everything.

Drop the thing on Mars. Sure sure sure, make it as *slow* of a drop as possible, but still. Kersplash!

I'll even give a sample business model.

Rockets
Tesla car in outer space
David Bowie song
Rogue "dwarf planet" with lots of water
Mars
Profit!

Lenovo (IBM) thinkpad keyboards have been water and crumb resistant for ages. Maybe Apple should just license the applicable patents and be done with it instead of re-inventing a perfectly good wheel.

In the last 50 years, it's gone from being 20 yrs away to now being only 15 years away. Assuming it's not on a log curve, we'll see practical fusion power generation in another 150 years.

Fusion has been just 15 years away ever since man first noticed that the sun was actually on fire. Just ask any true sci-fi author or science/technology magazine editor.

Yes but. I used to declare variables overly large as a kludge to help out when error-trapping was consuming too much time and I knew that the compiler wasn't good with overflows. So I'd do input error checking up to the point where it started to take too much time, then declare a variable larger than reasonable input would be, and then attempt to trap and reject input at a length between reasonable input values and the declared variable size. Declaring a variable just larger than the input buffer was one specific way to address attempts to force overflows through buffer overruns. Yes it was a horrible kludge and can't survive any sort of dedicated attack, but it served to deter casual probes looking for exploitable boundary condition errors.

Of course the better answer is to not use an OS and compiler that sucks so bad that the basic io buffers and basic overflows are exploitable, but sometimes you gotta use what you have.

This is just another way to vandalize stuff. I owned a far cheaper version of this 30 years ago. Its called a baseball bat. Before that, I had a tack-hammer. My ancestors had a version too, but they called it a "brick". Even earlier versions were called "rocks".

If we're lucky, cities will start passing ordinances to make mere possession of these a crime, since there is no legal purpose for these.