Live data from Hacker News

Windsurf SWE-1: Our First Frontier Models

windsurf.com

61–64 of 64 posts

Re: Windsurf SWE-1: Our First Frontier Models

#61

Earlier quoted context omitted.

this is clearly the right take… it’s fun to semi-dunk on “how on earth is that the valuation”, but this is one of those rare cases where the tech and platform are genuinely more valuable in the hands of the acquirer than they ever could be in the hands of the acquiree. because i think windsurf has executed as well as one possibly could in the space, but openai is the SOTA model king, and i don’t see that changing any…

Minor nit: OpenAI is in a three way tie for SOTA models with Google and Anthropic. They are the king of marketing attention, studio Ghibli imitation, and consumer subscriptions, though.

First mover too

Re: Windsurf SWE-1: Our First Frontier Models

#62
post #53

Earlier quoted context omitted.

Aider runs in your terminal and you can make comments against your code in any editor and it will execute your requests. It can use any model. CLine, mentioned in sibling comment is is same space.

Aider wastes tokens like crazy.

In which cases?

Re: Windsurf SWE-1: Our First Frontier Models

#63
Sorry, but as a paid Windsurf user, I think Windsurf should stop chasing shiny frontier models and focus on building better predictable & manageable workflows to build real-life products. - How about providing a Jira/Trello-style dashboard with subtasks for our AI, instead of copy-pasting "Cline Memory Bank" to .windsurfrules? - How about supporting TDD and regression-fixing by default? - How about using git with branches instead of the current undo-redo system? - How about a better way of syncing documentation vs real code?

We are paying for more "manageable" AI agents to get stuff done, not a chaotic "genius-hacker" to hack together quick prototypes.

Re: Windsurf SWE-1: Our First Frontier Models

#64
post #18
post #15

So because they need to have a better business model, they will try to move users to weaker models compared to the best available? This "AI inside the editor" thing makes every day less sense in many dimensions: it makes you not really capable of escaping the accept, accept, accept trap. It makes the design interaction with the LLM too much about code and too little about the design itself. And you can't do what many…

I don't think they are targeting software engineers as users. They are seeking those on the software engineering margins, users who know what Python and for-loops are but don't care to configure Aider and review each of the overwhelming number of models released daily. They want to tell the editor to add function foo to bar.py. I suspect this latter market segment is much larger than the former!

When I got my first job in 1986, the company had a tool that allowed non engineers to write code. Of course it didn't work. They could write code, but it ended up as a buggy, unreliable, unmaintainable mess. It turned out it was a good sales tool, get our technology into the company, then we would get paid to write the programs.

Then the were the the MS Access and Excel amateur efforts. I worked at a company that for years had a very profitable business replacing in house MS Access spaghetti with our well designed application.

Aaaand..... here we go.... deja vu all over again....

Post reply on HN