It's not technically behind on window positioning. Rather, it was a deliberate choice not to support it. You can very reasonably object to that, but it is sorta a necessary measure to prevent clickjacking.
And common sense mitigations: if a new program I've never seen before drops an actionable control under my cursor, maybe just default to not immediately accepting the next input to it so I have a chance to see it.
I mean, you can create alternate APIs that would work for the pop-up use case: you could have a command to create a new window positioned relative to the current window’s coordinate space.
That limited capability still has a risk of denial attacks (just throwing up pop-ups that extend beyond the current window’s boundaries), but those can be mitigated in a number of ways (limit the new window’s boundaries to the current window’s, or just limit how many windows can be opened, etc.).
Anybody who's smoked a lot of weed knows that THC tolerance works very differently from alcohol tolerance. If you've been ripping dabs every couple hours for the last month, you might be well above the legal limit and barely feel different at all. On the other hand, if you haven't smoked in a year and take a single hit of a modern joint, you could be floored.
I'm not sure how THC intoxication could be measured, but blood THC concentration feels like an incredibly crude metric compared to BAC.
Rather than get another utility involved, I'd rather see far more incentives for installing home storage and ideally solar as well, especially for rental properties. Nothing's more resilient than a distributed grid.
It also involves around three or four "I know this could be dangerous" click-throughs. That is harder to get an audience of everyday, than settling for paying someone you are probably already paying.
The average person will not click through a security warning. And if they do, they don't know what they're expected to do on that settings page. They are trained _not_ to bypass security.
I think beginner programmers like the fact that they can just open one app and the AI chat box is right next to their editor window. Other than that, I agree that it's pretty silly to maintain a whole IDE just to attach an AI chat box to it.
Now that there's MCP, the community will out-innovate anything a single company can do in terms of bolting on features. It's easy enough to get all the LSP integration and stuff into Claude code.
So it all comes down to model differentiation. Can cursor compete as a foundation model creator? Maybe, but even so, that's going to be a very tough market. Margins will be razor thin at best. It's a commodity.
Anyway, the last thing I would want if I were them is to keep worrying about maintaining this IDE themselves.
I certainly don't envy young people entering the job market rn. But China's youth unemployment rate is far higher than America's. To come away from this thinking American capitalism is bad and "communism" (which doesn't really exist anymore on a large scale) would be better would be pretty misguided.
reply