klausa

>You’re not neurodivergent

I have paperwork from three different countries disagreeing with you, but thanks for your concern :)

Reading posts like this makes me painfully aware just how neurodivergent I am.

It took me until... late twenties? to understand that most people _aren't_ feeling physically uncomfortable in anything long sleeved (or with long pant legs), and that they're just more... patient? tolerant than I am?

It just straight up isn't an inconvenience to other people!

I am very, very, very glad I have a career (and live in a climate) that lets me get away with shorts and short sleeves on 99,9% of days.

Good thing we're not talking about GDP then!

I'll bite, even though I really shouldn't.

How do you define "average living standard", so that it would take a colossal disaster to have US reduced to that of Poland?

You hear about them _because_ they launched in a poor state; not because _every_ game launches like this.

Yes; there have been some pretty high profile cases of games launching in terrible state, and Day 0 patches have become an industry standard, but acting like all (or even most) of big games launch like this is just sampling bias.

I mean this in the kindest possible way: Xbox 360 launched over twenty years ago; modchips on Xbox/Playstations haven't been a thing for... a good while now.

GTA6 will not have a disk release, which is why this is important for some people.

There's understanding and there's understanding.

Have you never "fixed a bug", only to realize that you just papered over a single symptom, while the underlying bug is still intact?

People you're disagreeing with (I think!), would say that during your first attempt, you didn't _really_ understand the part you're modifying.

It is _very easy_ to do this in large codebases, and even more so when working on anything touching UI.

This presupposes the information/calculation was incorrect.

I disagree with this being a foregone conclusion

There are documents linked in the footnotes that spell this explicitly, you don’t have to infer this:

The offer letter, which spells out “which vests over 4 years”: https://colo.to/invitation.pdf

The option grant which has the accelerated schedule: https://colo.to/grant.pdf

I feel like I'm going crazy reading the comments, and I guess, big props to the author for writing this in a way that pulls it off.

The issue here is, IMHO, not "Nvidia owes me stock in an ironclad way and gets away with it because of statue of limitations", but "I accepted an offer from Nvidia but the paperwork between the offer and the options grant differed in a way that both benefits me, and nobody noticed or cared about until now".

The original offer was for 25k shares, vesting over 4 years.

The options paperwork says 25k shares, vesting over 4 _quarters_.

Now, I'm not a lawyer, and certainly not a securities lawyer, but that seems like it could be reasonably chalked down to a clerical error on the options paperwork? "You made a mistake and now I can get a billion dollars more than we agreed to originally" doesn't feel like a great lawsuit!

I think that's an overly charitable reading.

Whether they "earned" them is disputable — the offer letter specifies one vesting schedule (25% every year), the "cover sheet" from the options agreement specifies other (25% every _quarter_).

So — the OP got the shares he was promised in the original offer letter; but later discovered that some of the documents he later got implied that the vesting schedule should be accelerated compared to what he agreed to.

I think that is probably the funniest way possible to earn a billion dollars; but whether he's "owed" that money/shares, is... up for a debate.

There’s bugs, and there’s also just a ton of bizarre choices that no human would ever make.

CC (the desktop version) has a built-in terminal. It’s great idea when working with worktrees!

But the terminal is _in the sidebar_. Not as a panel that pops up from the bottom like in… every IDE ever that has this feature, but in the sidebar.

You can drag it to the bottom using tiny drag targets if you want, but if course this only persists for a duration of a single conversation.

And there’s a built-in keyboard shortcut to toggle it being shown/hidden. Again, great idea!

But using this resets the panel to its original position, again, making it appear in the sidebar.

Bonus points: when I tried to submit this via the GUI version of /feedback, it told me that it was disabled by workspace policy _after_ I filled out the form and hit submit. Brother, just hide the button that makes the form appear in the first place!

Because their job stopped, to a large degree, involving programming.

This might have been true in the past (I’m not going to verify their old T&Cs), but it’s not true anymore - you can send back engraved items back to Apple with no issues.

You can’t _exchange_ them for a different item/credit, but normal returns are absolutely allowed.

The person I’m replying to said “the only reason”, so no; they can’t.

This is just straight up false.

OLED productions costs have fallen, and the yields have gotten better — displays of all kinds have gotten cheaper, not just TVs; OLEDs have started showing up in products they haven’t before for cost reasons, etc.

The manufacturers make some profit on the data they harvest, sure; but the biggest BOM costs of TVs have definitely also dropped sharply.

It’s surprising that Twitter even supports that.

> May 19, 2026

I think you're talking past each other.

You're talking about the device that's in the blog post; the person you're replying to is talking about the thing that Apple is shipping soon.

Have you ever had anything go wrong that you could attribute to storing cables like this?

I understand the theoretical concerns here, but it feels like an overkill in real world situations.

I'm very much not a mathematician, but I find the meta-discussion about this case fascinating, and I am a messy bitch who loves drama.

I don't know whether I'm just paying more attention this time, but I found the discussion on this be a perpetual game of telephone, where people get small, but important, details just completely wrong.

The person "threatening" the mathematician was _sama_; and the person who the threats were being directed _to_ is not an Anthropic employee!

(And the person who _did_ say these things have come out and explained what they meant; whether you believe them is up to you.)

I don't know if this is worse because everyone is so tired/angry at the big AI Labs; whether something about people's reading comprehension and attention span has gotten markedly worse or if this is just selection bias on my end; but it's _very weird_ to keep seeing this.

Why do people always assume that people on H1Bs _want_ a citizenship?

There's tons of things you can do to make people on visas more empowered to push back at work without them become citizens; and in many cases cutting ties to their original countries.

The SMS forwarding is handled entirely within iMessage.

Phone call forwarding works when all the devices are nearby, and they can handoff the audio streams between themselves; but you can't pick up a phone call on your Mac if your phone is on the other side of the world/at the office/etc; the feature we're talking about here would not have this limitation.

Because it's one more thing that I have to own and maintain; versus a built-in feature?

It is precisely so I _don't_ have to touch the actual TV remote ever.

So I can turn it on/off using Home Assistant and my phone.

The whole business of airliners engines is fascinating in its own.

AIUI when you're buying a plane from Airbus, it's possible/frequent to own the _airframe_; but not the engines — the engines are often _leased_ (sometimes directly from RR/GE); I've even heard of cases where each engine will be owned by a different entity!

https://aviation.stackexchange.com/questions/12528/jet-engin...

I'm now very curious how does a UV/IR scan of an ID card looks like!

I imagine there are only maybe three people as stupid as me to try this, but just in case: it works fine when the battery runs out; but it does _not_ work during the OS update process.