Didn't we agree that calling your product "new" is poor planning? Are they going to silently rename it in 6 months?

https://en.wikipedia.org/wiki/IPad_(3rd_generation)

Or will they keep doing this with "neu", "nouveau", "nuevo" etc?

I honestly don't think "neo" invokes thoughts of "new" to most people (despite the Greek etymology, of which I'm well aware).

It's a subtle distinction, but I think the general connotation is more like "hyper-modern" or "reinvention/reinterpretation."

People won't see "MacBook Neo" and think "oh there's just a new MacBook."

I will be waiting for the MacBook Trinity.

It's a product category name at least, not a release name, so the next release can be Neo 2

> Are they going to silently rename it in 6 months?

Probably when they update it, if they decide to keep the product line going.

If they plan to sell any volume, they can't rely on leftovers.

Unless the "leftovers" in question are "leverover capacity on the previous process node that doesn't have pricing competition, so Apple's able to continue to demand all of the supply at their desired price point"

What counts as "meaningful volume" is probably very different for laptops than for smartphones.

Not true, but good riddance if it was.

That's what I thought, but the article says it does:

> The page behind that URL might use framer-motion, plain CSS animations [...]

And the code example does something with css:

`await seekCSSAnimations(currentTime); // sync CSS`

We already have a very succinct and precise way to communicate intent. It's called source code.

Write your code so that the intent is crystal clear. If it is not, you have failed.

The primary purpose of code is NOT for a computer to execute it, but for humans to communicate intent.

It's surely supposed to be the perfect bridge between both - but we know in practice it often isn't.

I'd also quibble minorly with intent being what the code should be clearly communicating - it's its place and function and meaning within the wider system, which isn't necessarily what the particular programmer wished. Free-form English is a good medium for intent - not so much for "what this thing actually does"

What's the use case? I'm guessing it doesn't actually have anything to do with getting the time?

Roughtime is a really cool protocol we came across when we were hardening a license server. It provides a distributed mechanism for cryptographically verifiable time via chained requests. It’s not as precise as NTP (hence rough) but in practice it’s more than precise enough. It also has some nice additional properties: for example, NTP servers are often used as DDOS amplifiers, whereas roughtime servers return a smaller payload than the request.

The ecosystem is currently very young. Each additional deployment meaningfully strengthens the ecosystem (ours is only the fifth server) and each additional implementation helps harden the spec (which is soon approaching 1.0).

We wrote a bit more about it in a separate article: https://blog.sturdystatistics.com/posts/roughtime/

Official protocol document: https://datatracker.ietf.org/doc/html/draft-ietf-ntp-roughti...

I think the better question is: If people want to go to work an hour earlier, why the F do they need to change the clock for that? Just leave the house at 6 instead of 7.

Changing the clock around is insane.

A lot of people must schedule their day around school hours. You can't decide those.

And yet I guarantee that with permanent DST, they will start pushing school start times later and later in the morning, then they're all right back to where they started.

That is pretty much what I hope will happen here.

Step 1 is to fix the time at any UTC+N. I don't particularly care what n.

Step 2 is adjust all times in society to work with whatever UTC+N we are now stuck with.

I think step 2 will sort itself out, as it has historically. Schools begin at a certain time because of whatever historical reason tied to what timezone we are in. If we change to a different timezone schools should naturally drift towards starting at some other time in the day, unless people for some unrelated reason changed their mind about what s good time for school start would be.

I really only care about fixing the clocks and stop doing the annual changes back and forth. What number should be seen on the clock for specific events during the day, like school starts, can be adjusted later.

> The Chinese law enforcement official used ChatGPT like a diary

But why? It’s like using photoshop for spreadsheets.

Is there a similarly simple implementation with tensorflow?

I tried building a tiny model last weekend, but it was very difficult to find any articles that weren’t broken ai slop.

Tensorflow is largely dead, it’s been years since I’ve seen a new repo use it. Go with Jax if you want a PyTorch alternative that can have better performance for certain scenarios.

Also, TPU support. Hardware diversity.

Any recommendations for Typescript?

I think the hard part is improving on the basic concept.

The current top of the line models are extremely overfitted and produce so much nonsense they are useless for anything but the most simple tasks.

This architecture was an interesting experiment, but is not the future.