Nintendo hardware IMO is mostly reasonably priced. Their first party game library is why many buy into the ecosystem and they charge a premium for it. The original Switch was under-powered but also the first of its kind. The Switch 2 was mostly a hardware bump with additional polish to the rough edges of the original Switch.
No "AI generated" markings or any indication provided that the video used in the ad isn't real. It brings forth a question we will soon need to face: how to regulate AI use in political advertisements designed to influence voters.
Sure, nobody’s saying it’s an inscrutable mystery but if your goal is to inform a wide audience it’s considered good form to expand all but the most common acronyms. It’ll even get you more internet points than petty smugness.
I'm sure lots of people have heard of CVEs, but have you actually read many? LPE is an extremely common term. It's like not knowing RCE. These are the terms used.
I'm as stunned as you are. I have to read CVEs on a weekly cadence (like contractually required to) and LPE/RCE are kind of the main keywords we look for in them. Also increasingly TOCTOU. If anyone who actually has to respond to CVEs told me they had never seen these terms before I would judge them as being unserious.
I'll raise my hand here and risk downvotes from very smart people who are smarter than me, but I've heard of CVE but not LPE or RCE. I know what the latter two terms are but am not used to seeing them in acronyms.
So what's missing is that keeping up-to-date with CVEs is important and some CVEs are Internet-nerd famous. Remember Heartbleed? Even some casual gamers I know had heard of it. And everyone who's mildly serious about sysadmin knows you want to defensively keep systems patched against important CVEs. The second layer of that, what the exploits actually are or do, is a second-layer term of art, one that one might miss the jargon for even if one has familiarity with the concepts.
To me, the fact that the page is obviously AI-assisted is way more upsetting than some guy not knowing what an acronym means. There's something about AI prose that is just so fucking tedious. It makes the mind glaze over.
To be clear, I'm not suggesting that you if have heard of CVEs therefor you must have heard of LPE. I'm saying if you have read many of them you would have seen these terms.
I obviously do not expect someone who has merely heard of various CVEs before to know anything about the contents of those CVEs. The other poster said they had "read many CVEs", which I took to mean they have read many CVE disclosures, where the term is extremely common. Perhaps they meant that they've read about CVEs, in which case I can see why the term would not be on their radar.
some people just don't have a good memory for acronyms. It's one thing to learn the concept of a privilege escalation, but an entirely different thing to play mental memory with TLAs (three letter acronyms). Acronyms remove all the context from a term which makes them way harder to memorize. A bit like knowing your friends vs knowing their phone numbers.
I think they've almost certainly seen it written out, just not as an acronym. I figured out what it stood for based on context and knowing the full phrase, but I don't recall actually seeing the LPE acronym in recent memory. Whereas with CVE it's the opposite: I almost never see it written out, and even now find it non-obvious what the E stands for, bizarrely enough.
The anti-Cursor sentiment here is baffling to me given how useful it is to me. I use it interactively and actively review everything it produces. I like how I can plan a feature and refine the plan before instructing the agent to implement it. Last I checked, vscode had none of those features. Do (seemingly most) people prefer Codex because it gives a greater degree of autonomy to the agents?
> I like how I can plan a feature and refine the plan before instructing the agent to implement it
You can do that with claude code, github copilot (built into vs code) and codex, in any of their IDE versions, plugins for other ides (jetbrains, vscode, anything else you care to name) and also, of course, the CLI versions of all of them. They're also integrated into github, jira, and everything else.
Seriously, try other tools! if only to get a more balanced perspective.
This all being said, its been a long time since I last tried cursor... I'll give it a go.
I am personally not a fan of VS Code regardless, but I guess I don’t understand what it buys you over one code editor window and a Codex window both being open?
I have, right now, a tmux session with Codex on the bottom and Neovim on the top. It does what I was doing in Cursor just fine.
I am not really “anti Cursor”, I just genuinely am confused as to what it actually buys me over the setup I just described.
Here's why I use Cursor. My company pays for it, although I could switch to Claude Code or use Codex more since I also have ChatGPT enterprise account.
* Perhaps could be solved with the right terminal software, but I like the GUI for seeing my running agents and viewing all my conversations
* Works with multiple model providers in the same tool. I probably worry about cost optimization more than my employer would care for me to, but I frequently switch between openai/anthropic and switch between model sizes to use the tool that I think can get the job done for the least money. Another thing I like is having a long conversation with an expensive model, then I can switch to 5.4-nano to cheaply extract some little piece of information or summary from the conversation. Really this is big being able to switch model providers throughout the months without having to change my interface.
* Good support for the various ways of providing context. Rules, AGENTs.MD/CLAUDE.md files (if you want it to automatically read those), skills. Good hook support.
* I think the agent diff review experience is pretty good, but maybe it works similarly when you hook the cli agents into an editor, IDK.
* The default shell sandbox behavior is quite good. Every shell command runs in some sort of sandbox so that read only commands work without approval. The model asks for more permissions when it tries to do something that needs more permissions like network access or writing outside of the workspace directory. I know Claude code has a similar feature you can use.
* Good fork / revert conversation to checkpoints, with the option of reverting the code or just reverting the conversation.
* Feels decent that I am an API customer through Cursor. I don't hit Claude limits. Cursor doesn't have an incentive to limit reasoning or token usage, although they do have an opposite incentive.
* They are reasonably responsive to bugs and feature requests through their forum.
* Works well with a lot of repos / folders added to your workspace. I probably should organize all my stuff under a single directory, but alas I have like 8 different folders added to my workspace and it handles this well. Perhaps Claude --add-dir support works fine too.
DOWNSIDES:
* They are not quickly adding the best open source models to Cursor. Like Kimi 2.6 or whatever. Possibly not incentivized to given their Composer models.
* Don't love the subagent support. I can define custom subagents although it is not easy to get models to use mine instead of the builtin ones. The builtin ones do not allow me to control what model they run, so they will always run something like composer-2-fast, which is a fine model for all I know, but I would like to control it. Also, I would like if you could optionally make the subagent experience more first class. Like browse all the subagents and continue conversations with them or switch their model etc, although that is probably tricky / weird.
My employer pays for Cursor and Claude but not Codex. I often find Claude dumb (yes, even Opus), thus I'm using Cursor with GPT-5.4. If you have Codex, you don't miss anything.
and I'm being completely neutral and objective in saying this: Elon Musk has been a horrible capital allocator but great at financial engineering. X is still struggling to win back advertisers (they will never come back) and still in the red. I have little reason to believe this is also another careful and shrewd financial decision.
He spun that story into "he was saving democracy" so it sounds like he paid for that reason. He will do the same here, he never does a wrong move you just can't see the 76D chess.
I've always passively wondered why this wasn't more of a thing. Something like pgAdmin is fine I guess, but it's always felt like "just barely good enough" rather than an immersive power tool to get things done, and done well. Possibly just a skill issue, but that's been my impression.
No I get it; and it’s not a skill issue because debugging with proper tools is a skill and the issue is that lack of those tools means you lack the ability to even use your skill. My last job used a lot of fancy internal pg stuff and we could never really reason about it properly. I wish I could debug it like I do with a Go app with delve, or in my IDE. Adding NOTIFY everywhere is print debugging which in my opinion is not a very good debugging strategy.
Someone did something interesting to them and shared it with the world. That you feel is a waste of time does not add to the conversation and more broadly acts as a chilling effect on others who might want to share their interests.
When it comes to something like this, mom's advice is golden: "If you don't have anything nice to say, don't say anything."
reply