bobogei81123

I don’t claim this is their entire motiv, and I’m sure plenty of people internally are genuinely concerned about AI risks and the disruptions caused by moving too fast. But I can’t help but feel that part of the push to "pace the frontier" is an attempt to form a "Phoebus Cartel" for AI labs.

Now the risk of an AI bubble isn't that AI lacks real world utility. Rather, it's that AI is advancing so quickly that capabilities are already saturating for most everyday tasks, and it is becoming commoditized. I didn't feel much difference between Opus 4.8 and Fable 5.1, and most tasks don't require a Fields Medalist.

We don't need smarter models but we need faster and cheaper ones. Also, for almost every frontier model released, an open-weights equivalent follows within six months. Unless this dynamic changes, the business becomes far less lucrative.

When I started a typescript server project, I spent quite some time - setting up dependency injection framework to pass context (tsyringe) - finding a good schema validation library (zod) - use neverthrow for typed error. - wrote a few withSpan, recordDuration OTEL helper functions.

Then I heard about Effect-ts, checked the doc, and realize that Effect-ts already has all these things, in a single package.

IMO Effect-ts is currently the most practical effect system right now. While it does not support resuming like in other algebraic effect languages, it is powerful enough to express common patters, but not too powerful so that the code becomes hard to understand.

I hope effect-ts gets more traction. The biggest obstacle to sell it right now is that the API doc is not great. I had to trace the source code several times just to see how a type is defined. I hope Effect-ts team is aware that more people will use it if it has a proper documentation.

This is just AI trying to tell us how bad we designed our programming languages to be when exceptions can be thrown pretty much anywhere

Back when I was a kid learning go, I was taught that the kick joseki (a standard sequence of moves, similar to chess opening) [1] is a bad move, and you were considered trolling (and the teacher would not be pleased) if you played a 3-3 invasion [2] during the opening phase. These are all vindicated thanks to the AI and played pretty commonly nowadays. AI definitely helped eliminate many dogma and myths in go.

[1] https://senseis.xmp.net/?44PointLowApproach#toc6

[2] https://senseis.xmp.net/?33PointInvasion#toc2

> “What do you mean, it’s not a matter of taste? I like using ligatures when I code.” Great! In so many ways, I don’t care what you do in private. Although I predict you will eventually burn yourself on this hot mess...

I've been using programming fonts with ligatures for years. I had wasted several hours because of those stupid bugs when I mixed up O and 0, - and _, but ligatures never caused me any problem. It is obvious when they are there, and you rarely see non-ascii characters when programming (unless you are writing Lean).

I thought the article will mention ①②⑦.⓪.⓪.①

$ ping ①②⑦.⓪.⓪.① PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.

And not understanding that can have fatal consequences: https://youtu.be/VVE79XT8-Mg

My guess is that they did not add in the client delay.

If someone is creating a new language now, that is a concept that would definitely not be included.