Your analogy is very incomplete. No one is saying that Intel's products or technology is "moving backwards", but rather that their market share and performance as a company are declining.

Take your person "standing still" and imagine they were previously in the lead during a marathon and suddenly stopped before the finish line. They're not moving backwards, but their position in the race is dropping from first, to second, to third, and they will eventually be last if they don't start moving again.

I sometimes name booleans after the action that will be taken rather than the condition they represent For example, I might have booleans called "doQuickInit" or "invertResult". I find this very useful when the value of a boolean is determined by a complex series of conditions that are not actually true or false.

Command & Conquer Generals did it first.

Why hello there, Mr. 0352.

At least your MOS still exists. I was one of them SMAW guys, and now both my job and old unit have been deactivated. It makes me feel like even more of a dinosaur than I otherwise would when I talk to people about my time enlisted.

It's only a matter of time before it's not an option anymore. Every shitty new behavior they put in is an easy-to-use option at first, then a registry setting or policy, then even that goes away and it gets baked in.

Embedded software developer here.

Oh damn, I thought I was going to be the only one here!

I don't know how you get by with only one. Between source code, simulators/emulators, datasheets, requirement specs, log files, e-mails from senior devs with tribal knowledge not written down anywhere else, and a bunch of other bullshit, I sometimes find 3 24" monitors to be lacking.

Distractions aren't a problem because I can easily use up all that screen real estate for a single task.

From the hovertext: "I wrote 20 short programs in Python yesterday. It was wonderful. Perl, I'm leaving you."

After years of a dozen other languages, I finally tried Perl the other day.

Never again, if I can help it.

Depending on the beam's weight, where it impacts, and what kind of tank it is, here are some possible effects:

1. Absolutely nothing
2. Cause the crew to button up, reducing their visibility
3. Draw the crew out to assess or repair damage, expsoing them to small arms fire
4. Remind the crew that their enemy is active in the area and slow the advance
5. Distract the crew long enough for infantry to employ a more effective weapon, possibly including approach the tank on foot without being seen
6. Main gun barrel impact - deform the barrel enough to disable it
7. Turret impact - disable turret rotation, reducing aiming capability
8. Track impact - mobility kill by damaging roadwheels and/or track, or just getting stuck there
9. Direct side impact - probably nothing
10. Random gear impact - even old tanks have external mounted machine guns, optics, radio antennae, and shit that could be disabled
11. Exposed crew impact - squishy squishy

Of all these possibilities, I think just trying to get the damn thing stuck in the wheels/tracks is the most likely to actually work, even on relatively modern tanks.

If you read the fine print, many "lifetime" warranties are like this too. They mean the "lifetime of the product" which is usually defined in the same fine print as like, 5 years or some other bullshit timespan.

Using multiple desktops may help you keep all those open programs more organized. :)

I use only use them at work. One desktop is for e-mail, chats, and my music player, the other has all the stuff I need for whatever I'm actually working on at the moment. If I'm switching back and forth between two unrelated tasks, I might use a third to keep everything for the two tasks separate.

Is "multiple desktops" different from virtual desktops? Because i've been using virtual desktops in Windows 10 for a while now.

Everyone at Mentor Graphics did before it got gobbled up by Siemens in 2017. I don't know if they still do.