written-beyond

I hope you find relief from your disease.

I got our pocket god ChatGPT to fact check this discussion. No lab is profitable, it is a moonshot to expect they'll ever recover the billions frontier labs have put in behind these DCs. I never understand this argument everyone tries to make, AI is too expensive -> It will get cheaper as they scale -> AI is too cheap and not sustainable -> No it's very profitable on API -> go back to 1.

I am not an AI denier, I use it and I find it very useful. That said I can disagree with the current economics of the industry and their business model.

Define profit? If by profit you mean covering compute costs then yes you're correct. If by profit you mean covering spent RnD budget and future RnD budget allocations then no, by no means are any of these AI companies running at a profit.

Also these third-party providers are running magnitude smaller models than what Anthropic and OpenAI's power users expect from them. Yes the average chat message isn't being routed to the 1+ Trillion param model but people running CC or Codex on Ultra probably are. Those are objectively more expensive.

It doesn't on windows FF

This is the first time, in my entire life I have experienced a website overriding pinch to zoom. I couldn't pinch to zoom, just on top of pictures, which would expand the image then zoom into it.

Why would the author do that, very frustrating.

They're all building the "Her" companion device. It's almost like those transparent touchscreen phones you'd see in SciFi movies that every phone maker would have their research Labs working towards, Nokia morph was one of them.

Those things all look this in concept and in movies, but their practical utility in real life always seems to be lacking. I'd imagine this is the reality what everyone building companion devices are facing.

With the amount of money, RnD and engineers these firms have this seems to be the only reason.

I mean cartesia did one of their first demos on a Mac book pro, live.

Still extremely impressive but not unheard of.

Too late I just shipped tsvhdl so you have a hardware implementation of the actual TS compiler. Why steal valuable CPU cycles from agent workflows, off load all transpilation and type checking to a dedicated TSC chip.

lol, I made the same comment the last time this website was shared here.

After reading the title, but before visiting the link, thought this was a backup of all of Terrance Taos work.

You're right but also very wrong.

You can never prove that there aren't any bugs. The definition can also change according to time and expectations.

I've made tens of internal developer tools because I couldn't gaf about using some third party vendor, all before vibe coding. Even then we purchased software from vendors, and we still do it now.

You can't cherry pick 2-3 pieces of problematic software, imply that it's how everything works. You're vibe coded Photoshop will never be used seriously, unfortunately. Same goes for the video editor, if you're fine with an autonomous AI agents listening to some internal github repo for issues that get auto or human reported and attempting to provide live fixes and feature enrichment, you aren't going to get that.

The problem really does stem from the fact that these agents, no matter how good you keep making them are still limited by a time horizon. AI companies have gotten really good at extending that horizon. The contexts get longer, prompts get less specific but theres a deadline to all of this. Take that LLM point it to a specific problem let it run, pull it out start new. The LLM will inevitably accumulate technical debt in it's own context, that starts to create a rot. You can try to improve this problem by making sub agents, etc. but you will 100% run into context rot after a period of time for the lead agent.

They aren't, they did some much needed API changes after adopting signals. It reduced some of the magic but it's pretty much the same as it's always been. I agree that API stability is something a lot of mature frameworks need, but svelte has always been at the forefront of provided high quality migration tooling.

We weren't asking which tools integrated LLMs, we specifically asked which got better by building them with LLMs.

Cursor, Codex and Claude Code all have terrible desktop applications, which are a laggy mess on Windows.

What improvements did UV do with auto research loops, I wasn't aware of that.

I thought this was posted on a Dbus hate website when I saw the URL.

Night and day, thank you!