hapless

I doubt it

I really, truly suspect Wayland is the future

We have had like one hundred X11 replacements between 1990 and now, and at least half a dozen have caught on with the open source community

What makes Wayland different is that it has attracted multiple vendors supporting it. Most notably IBM/Redhat, Intel, AMD, and, to a lesser extent, nVidia.

I am posting this message from an X11 environment, because I need X11 for a lot of things, home and work both, but, I can at least imagine a world where Wayland is the new default. That is not something I could say about the last hundred attempts to replace X11.

Edit: Again, this is just a suspicion. A notion. I neither hope for Wayland's success nor failure. I just keep my finger to the wind.

I can't hardly blame them, I imagine they want all their paying customers to get off ia64 and alpha, too.

Microsoft used to sell Windows as a runtime. Like, you would ship Windows on floppy disks as part of your software product for end-users.

16 bit Windows was consciously designed, intentionally made modular, to accomplish things like this. Albeit the author was surely not the intended customer!

I mean, they ARE putting their money where their mouth is

They pay existing employees less, and new employees, more. If a whole team quits, a replacement will be more expensive. That's the state of the game!

It is a fact of life. You don't have to like it, or embrace it, but it remains true.

It is generally easier to get a raise than to get promoted. It is generally easier to get a new job than to get a raise.

On balance, if you want to maximise earnings as an IC, you are gonna change jobs more often than you get an above-inflation raise.

This whole thing is bad advice

* New hires get paid more because they are worth more to the employer. Point blank. You don't have to pay existing employees more to keep them working there. "A bird in hand is worth two in the bush" was meant to be a parable but it turns out to be rather more literal

* Never accept the counter-offer. If you have gone as far as interviewing outside, you are already checked out, and you are already branded as disloyal. It's time to make your exit! If you ask for a counter-offer, it should be a move to squeeze more out of your offers, not a real attempt to "stay" where you have already decided to leave

* Arguing about a raise is almost always a waste of time. If you are not happy with your 3% COLA, will 5% really mollify you? LOOK FOR NEW WORK

SGI was already moribund in 1997. Executives made a conscious choice to pivot. It didn't work out, but it is real hard for me to believe they could have done better with a redoubled focus on MIPS development they could not afford.

Sun's last successful SPARC project was the UltraSPARC II, in 1997. Their subsequent projects, like "Rock" and "Niagara," were disasters. (USIII and USIV were little more than core shrinks of USII)

If Sun had given up the day Itanium was announced, they mighta come out ahead!

Context is important.

All of those competing architectures were becoming prohibitively expensive to enhance.

Alpha never paid for itself, ever, the market share was too small. POWER and SPARC had multiple failed projects with enormous capital costs. MIPS hit a performance dead-end with such low market share SGI saw no way to rebuild. HPPA was bleeding HP dry.

Itanium may have hastened their demise but all of these archs had the same core problems with investment returns. The writing was on the wall, and Intel was offering something people desperately wanted. (Unfortunately for everyone involved, it did not pan out.)

Everyone uses the FAANG loop + system design + leetcode design now

I don't know when that change happened but it is practically universal

Police exist to enforce a notion of "order" based on extremely specific notions of property and class relations

That said, I am not seeing the relevance to the originally posted article. This is an example of the law actually working against the structures police forces were created to enforce

That is an important political question that has relatively little to do with intentional, spiteful "payment"

There are a number of reasons rents paid to landlords are treated somewhat differently from wages paid to workers! Those are deeply political and important, and not super relevant here

In the narrowly relevant question: No one would ever accept a spite-filled "rent" paid to a landlord in the form of oil-covered pennies, provided only as a means of spiting the creditor

1. that fact is not disputed in the article

2. hours worked, and "working," have legal meaning, which, again, is not disputed by either party

in america, if you contract with a fellow to work, and you find the work unsuitable, you can discharge him quite easily. but you still owe him his wages!

No, of course not. You are tilting at windmills. No one has suggested non-payment followed by spiteful "payment" would be suitable for a dispute with a landlord.

You have invented a villain who does not exist.

The story comes from the Macon paper. Georgia has very clear guidelines around oil disposal!

https://epd.georgia.gov/document/document/used-oil-guidance-...

A "bad" worker who you are happy to see go is still entitled to all of his pay.

In the article, the business owners keep suggesting that it was bad performance, or a bad attitude, or something like that, that justifies this behavior. But, factually, both as a matter of law and custom, nothing justifies this.

If a fellow works for you on an agreed rate, you are obliged to pay him. If you are not, ultimately, happy with an employee, that doesn't mean you get to keep his last paycheck.

I love how this thread goes completely off the rails almost immediately.

In the grim darkness of the internet, there is only eternal flamewar

The interview snippets make it clear that SimCity 2013 was hopelessly compromised from minute one

If nothing else, consider the mandates from EA:

  1. Make it "unpirateable" even if it compromises gameplay
  2. Make it depend on EA's online service, b/c we need to sell that even more than we need the game to succeed
  3. Make sure it can handle a steady trickle of "expansions" like The Sims

If you are going to implement those mandates, you are gonna end up with something bad. Even if SimCity 2013 had not been otherwise brain-damaged or screwed up, just EA's goals for the product were damning.

(Of course, it is not JUST the mandates -- the game was screwed up in many other ways as well. But the mandates alone would have been bad.)

Here's a marketing rule of thumb: don't use "post hog" or "post hole" as your core marketing identity

(Unless you are primarily targeting "adult" firms, of course)

It doesn't fool anyone.

SBF is doing his best work in witness tampering, and federal courts are failing to stop him.

I know a few places. The answer is, 100% of the time, "legacy code."

One of my former employers has millions of lines of code that just assume a bigendian architecture and play fast and loose with byte order as a result. They are probably not gonna port that code off SPARC any time soon. Eventually. But not soon.

In the 80s and 90s, they were significantly faster and more capable than their PC / Mac analogues. Double or triple the speeds and feeds, ten times the price ;)

By the 2000s the advantages had more or less vanished and the workstation SKUs were discontinued one by one.

Sun licensed SunOS and Solaris source to pretty much anyone who asked (and wanted to pay for it)

All of the proprietary unix vendors would sell source licenses to a greater or lesser extent. There's IRIX and AIX source trees out there if you go looking, licensed for university use back in the day.

Cross-compiling for AIX+IA64+COFF is going to be tricky.

I rather doubt binutils supports that particular combination of items

RS/6000 was the fourth AIX platform after x86 (AIX 1.x), IBM RT/ROMP (AIX 2.x), and the mainframe (AIX/370, AIX/390)

That statement was worded carefully

They are saying they dont store or forward your message text, not that your phone doesnt send them topics of interest

Canon devices usually support PCL and Postscript.

The proprietary drivers are just faster/fancier.

Printer drivers are user space.

Microsoft historically funded OpenBSD because they drew on OpenBSD source for their UNIX userland in products like MS SFU. They were all too happy to fund the development of /bin/sh and /bin/ls.

They absolutely do not have any interest in any "security" matters in OpenBSD -- Microsoft Windows and Microsoft .NET are decades ahead of OpenBSD in terms of security.