Then Replit, V0, Lovable are all extremely popular.
I don't have a horse in this race just find it interesting. Your Coke vs Pepsi analogy is a good one though.
1,630 karma · joined October 13, 2013
Then Replit, V0, Lovable are all extremely popular.
I don't have a horse in this race just find it interesting. Your Coke vs Pepsi analogy is a good one though.
The second theory is an unbounded or inadequately bounded delete statement - essentially deleteMany on a single table.
From a more technical org I'd be interested in a write-up, but my intuition says one of those two paths to deleting technically a single table.
OK the car scraped my other car. I made it apologize and PROMISE not to do it again.
OH NO IT HITS THINGS AND PEOPLE EVEN WHEN IT SAID IT WAS GOING TO BE GOOD.
(Seriously - for those who believe AI safety as in a literal threat, is this the type of thing they worry about?)
(Sure -- that background is somewhat self earned.)
Yes, she was there at OpenAI and by all accounts a super respected non researcher.
Clearly she's incredible, her reputation proceeds her etc. but is operational strength (being a good exec) really what gets to AGI?
Feels almost like cargo-culting.
It's also been a lot of random stuff recently with their 3 separate Ross and Rachel acquisition storylines.
Some takeaways:
1. Devin/Cognition definitely have a legit AI dev agent now
2. It's crazy what Google passed on. The fact that it was worth it to them without the traditional best assets is wild. Guess that's what happens when you play on ultra hard mode with an infinite money glitch.
3. I am worried/pre-emptively sad that Windsurf will likely go away or get nerfed, more expensive etc.
It's very very rare to have winner takes all to such an extreme degree as code llm models
ALSO while JavaScript is a single threaded environment, the while solution would still basically work due to the scheduler (at least if you yield, await sleep, etc.)
A little way down a loading screen hits for a zone called "The Hole"; a high level raid zone. My levitate was removed by the loading screen, and retrieving my body would require a team of high level players - thus lose (meaning ALL my gear and inventory was permanently lost, and a heavy XP penalty).
I don't think experiences like these are as positive as your nostalgia has led you to believe.
That's like saying it's a security flaw in the Chrome store that you could enable dev mode, copy the malware and run it that way.
I much prefer the price, and pricing model, of Windsurf (although Claude 4 not being an option is odd)
Perhaps the specific idea is to harvest coding textbooks as training data for LLMs?
Cynical take: describing yourself as a full stack AI IDE company sounds very invest-able in a "what if they're right" kind of way. They could plausibly ask for higher valuations, etc.
Optimistic take: fine tuning a model for their use-case (incomplete code snippets with a very specific data model of context) should work. Or even has from their claims. It certainly sounds plausible that fine-tuning a frontier model would make it better for their needs. Whether it's reasonable to go beyond fine-tuning and consider pre-training etc. I don't know. If I remember correctly they were a model company before Windsurf, so they have the skillset.
Bonus take: doesn't this mean they're basically training on large-scale gathered user data?
Their stated goal is to improve on the frontier models. It's ambitious, but on the other hand they were a model company before they were an IDE company (IIRC) and they have a lot of data, and the scope is to make a model which is specialized for their specific case.
At the very least I would expect they would succeed in specializing a fronteir model for their use-case by feeding their pipeline of data (whether they should have that data to begin with is another question).
The blog post doesn't say much about the model itself, but there's a few candidates to fine tune from.
Realistically, we need to grant access to env variables, network, etc. So those flags are functionally useless as always enabled.
The issue we face is making sure our dependencies don't do something nefarious. Demo doesn't solve that. I would really, really like to be able to specify these flags at the package level.
First, perf you mention is from fundamentally CPU intensive workloads, not a sparse async environment like a typical server.
Second (far more important) the reason we do this is type safety. We don't want types to break at the handover or to maintain them twice. We eliminate a huge category of issues and mental overhead.
This maintainability and simplicity is worth more (to me at least) than perf.
As a bonus there's also directly shared utils, classes etc. which again can be reused across client/server but more importantly stay in sync.
There's no concept of "run this once" or eval. So it's a very heavy, deploy per run, model of iteration which is not suitable for the main use case of giving end users an editor to iterate with