"If the jury determines that at any time before those dates, Musk either knew — or had or should have known — that he had a claim that he could bring, then his suit was brought too late. The consequence of being too late is swift and absolute. If the lawsuit was filed late for a particular claim, that claim is out of the case; if it was too late for all of Musk’s claims, the lawsuit is over."

That's where the question of fact (i.e., the requirement for a jury decision) came in: "What was the statute of limitations?" is a question of law, but "When should Musk have known that OpenAI was moving too much toward for-profit?" is a question of fact (and, here, determines whether the statute of limitations applies).

I want software that works.

Yet the economics of the software industry, and perhaps the economy as a whole, seem to inexorably push toward the former.

> TypeScript 6.0 arrives as a significant transition release, designed to prepare developers for TypeScript 7.0, the upcoming native port of the TypeScript compiler. While TypeScript 6.0 maintains full compatibility with your existing TypeScript knowledge and continues to be API compatible with TypeScript 5.9, this release introduces a number of breaking changes and deprecations that reflect the evolving JavaScript ecosystem and set the stage for TypeScript 7.0.

Most date/time libraries that I've seen have a only single "date/time" or "timestamp" type, then they have to do things like representing "January 13 2026" as "January 13 2026 at midnight local time" or "January 13 2026 at midnight UTC."

Temporal has full-fledged data types representing the different concepts: an Instant is a point in time. A PlainDate is just a date. A PlainTime is just a time. ("We eat lunch at 11am each day.") A ZonedDateTime is an Instant in a known time zone. Etc.

Temporal draws a lot of inspiration from Java's Joda-Time (which also went on to inspire .NET's Noda Time, Java's official java.time API, and JavaScript's js-joda). This is helpful; it means that some concepts can transfer if you're working in other languages. And, more importantly, it means that it benefits from a lot of careful thought on how to ergonomically and effectively represent date/time complexities.

I interpret this as meaning there was an implied "if you screw this up" at the end of "they could kill three major product lines with an email."

As phiresky points out, you're still "download[ing] arbitrary code you are going to execute immediately afterwards" (in many/most cases), so it's far from foolproof, but it's sufficient to stop many of the attacks seen in the wild. For example, it's my understanding that last month's Shai-Hulud worm depended on postinstall scripts, so pnpm's restriction of postinstall scripts would have stopped it (unless you whitelist the scripts). But last month's attack on chalk, debug, et al. only involved runtime code, so measures like pnpm's would not have helped.

Dr. Hipp's position is paraphrased as, “I cannot trust the compilers, so I test the binaries; the source code may have UBs or run into compiler bugs, but I know the binaries I distribute are correct because they were thoroughly tested" at https://blog.regehr.org/archives/1292. There, Dr. John Regehr, a researcher in undefined behavior, found some undefined behavior in the SQLite source code, which kicked off a discussion of the implications of UB given 100% MC/DC coverage of the binaries of every supported platform.

(I suppose the argument at this point is, "Users may use a new compiler, flag, or version that creates untested code, but that's not nearly as bad as _all_ releases and platforms containing untested code.")

https://fortune.com/2025/09/18/sardar-biglari-war-against-cr...

Or maybe it's a small enough API but a lot of concepts. Or maybe I'm just grumpy that the days of "it's just a view layer" feel long ago.

https://hacks.mozilla.org/2010/06/beyond-html5-database-apis...

Not necessarily. My take was that the practice of choosing may well be more valuable than the harm of the occasional regretted choice.

I'm disgusted with the executive branch's actions and congressional GOP's enablement. And, since the administration at times seems to want a fig leaf of legality, maybe the bill would make a difference after all by giving them more coverage. But, overall, I'm not sure that it's the "game over" step change that some commentary makes it sound like it is.

I could be misunderstanding - comments / counterarguments welcome.

1. Cook only cares about pursuing profits, but at a shareholder meeting where shareholders were pressuring him to pursue profits, he lied to them (and had the presence of mind and acting chops to pretend to be uncharacteristically angry about it), because he believed that the story would get reported on and Apple fans would want to hear it, and he made the calculation that that would be more beneficial to his bottom line than being honest (or at least more politically neutral) with his shareholders.

2. Cook really does believe about accessibility, environmental issues, and worker safety, and he tries (or at least likes to think that he tries) to take steps toward those causes at the expense of profits, but he's also a complex and flawed mixture of motivations and is capable of compromising his values (and/or of letting those under him compromise their values) to varying degrees in the face of financial rewards or the pressures of the capitalist system.

#2 seems more likely and is more consistent with my view of humanity in general.

> “When we work on making our devices accessible by the blind,” he said, “I don't consider the bloody ROI.” He said that the same thing about environmental issues, worker safety, and other areas where Apple is a leader.

> As evidenced by the use of “bloody” in his response—the closest thing to public profanity I've ever seen from Mr. Cook–it was clear that he was quite angry. His body language changed, his face contracted, and he spoke in rapid fire sentences compared to the usual metered and controlled way he speaks.

More broadly, I know that for-profit businesses are concerned with their bottom line, and I know businesses regularly throw other values under the bus in pursuit of profit. But I'm not sure it's possible to build a successful business (in terms of maintaining consumer trust, attracting and motivating decent employees, etc.) without some values beyond what's immediately quantifiable on the bottom line.

(Our project mostly uses Chart.js, so I'm more familiar with it.)

First is if you compile with `-Werror -Wall` or similar; new compiler diagnostics can result in a build failing. That's easy enough to work around.

Second, nearly any decent-sized C program has undefined behavior, and new compilers may change their handling of undefined behavior. (E.g., they may add new optimizations that detect and exploit undefined behavior that was previously benign.) See, e.g., this post by cryptologist Daniel J. Bernstein: https://groups.google.com/g/boring-crypto/c/48qa1kWignU/m/o8...