Hacker Newsnew | past | comments | ask | show | jobs | submit | veidr's commentslogin

This is funny, but Copilot is still an interesting case-study and (probably) failed predictor of where we are headed.

We all know, and have known for a long time, that the AI labs selling dollars for a nickel are going to pull that rug, and up that price, at some point.

Copilot, though, has been consistently the weakest mainstream AI coding offering. Inferior to Cursor or Windsurf at editor completions, inferior to Codex, Claude, OpenCode, blah blah blah, at agentic coding and also the old-school chat-style...

And now, it's no longer cheap AND now sucks even more than it has all along — the new $39/month plan is not only worse than all its competitors, but worse than its own $10 plan was a month ago — by a lot.

The thing is, you can't jack the price up unless you're good enough — at least on some axis, to some customer segment — to jack the price. And when you're not good enough, and you have vastly superior competitors who are not doing that yet... you're just forfeiting the game.

Which I agree, Copilot should do — it's the Windows Phone of AI coding assistants, after all — it still seems weird to me to just commit humiliating suicide rather that trying to make some deal with one of those superior competitors.

Instead of just jumping into a dumpster and lighting yourself on fire.


Microslop has lost their way from their ole acquisition investments and have instead hedged a bet on vibing their way into other industries.

turns out it was spelled "lusage" the whole time

Exactly the same way that the `cancelled` of my youth became `canceled`. By being misspelled so often that the misspelling won.

In this case, it's not clear who wins yet — "lose" may loose, or mount a comeback, resulting in "loose" being the one to lose.


I've said it a couple times in the past: That's so cringe!

Well I mean, recently because they have no idea how to make good UIs, and have not read their own enormously detailed (and excellent) Human Interface Guidelines tomes from 10, 20, and probably 30 years go, and have basically regressed to barbarism.

But before that relatively recent fall-off-a-cliff event (whatever it was that caused it, most of us will never know), it was pretty clear that they didn't want to implicitly endorse the lazy/anti-user/Windows-equivalent-UX antipattern of having apps that intentionally made themselves accessible only from a menu bar icon.

I hate the App Store shite that goes wildly too far the other way, but I don't quite understand wwhy they couldn't figure out a way to enable the menu bar widget API in a way that failed if your app didn't also have a way to open via all the normal ways (double-clicking the icon in /Applications, asking Siri to launch it, etc)


> they didn't want to implicitly endorse the lazy/anti-user/Windows-equivalent-UX antipattern of having apps that intentionally made themselves accessible only from a menu bar icon.

The single biggest complaint I had when I switched it to Mac was lack of this feature. Still miss it. .


> and have not read their own enormously detailed (and excellent) Human Interface Guidelines tomes

This seems to also apply to all new UIs produced by apple in the last 5 years.


It's true this is a mess, but no application should have a menu by icon as its only means of access. It's OK to offer that as an option, but all applications should be capable of presenting a user interface when launched from the Applications directory (or (rarely) ~/Applications, etc).

There's really no exception to this rule. For an (tiny) minority of applications, it makes sense to hide the dock icon, and to typically access the app via hotkey or menu bar widget. But those apps should still have an icon and should still be able to be invoked by opening it using any of the standard ways to do that. That's just how the Mac works.


It absolutely is, but the fundamental misunderstanding around this seems to be that "effectively using coding agents" is a superset of the 2023-era general understanding of "Senior Software Engineer".

At least when you're talking about shipping software customers pay for, or debugging it, etc. Research, narrow specializations, etc may be a different category and some will indeed be obsoleted.


Who's seeing this in the wild?


I don't think that's what is being said, mainly? Like that's why Anthropic wants to have it in the contract(s) with the government?

At the same time, it is expressly illegal in some circumstances; that was the whole core of the Snowden revelations. The NSA and CIA are expressly curtailed from doing that by law — there are cases where they may surveil citizens with a court order, but not "mass" surveillance. There are some restrictions on the military along those same lines.

Keywords: Executive Order 12333, FISA, National Security Act, Posse Comitatus Act


crazy take

like saying kids having internet-connected devices with built-in cameras doesn't increase the probability of sexting, they could do the same with film cameras and a fax machine


AI doesn't increase the amount of data captured or the processing throughput is the difference with your cameras metaphor. As said at best it can summarise things better sometimes.


I would say AI is very much increasing the processing throughput of labeling surveillance data.


Nobody gives a shit about jumping to #1 in the app stores, at this scale.

If US & A really goes full-Huawei on Anthropic, they can't IPO. It's an existential crisis for them. I think they can survive in some form, somehow, because their model is really good, probably the best.

And in other times, I would think the US government had sufficient intellectual horsepower to not cut off its own dick, and the golden goose's head, over some idiotic morning-drinker road-rage type beef. But these are not other times. These are these times.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: