djfdat

Theorizing, but I'm guessing that before LLMs, people weren't using anything for situations like these. As people started using LLMs, people's use cases grew, LLMs got slower and more expensive, and people lost the wow-factor and are now worrying about price. Great timing to launch a product like this, where certain use cases can be distilled down into something faster and cheaper.

There's probably other areas where people are using LLMs where a more tailored ML solution might work better.

Title phrasing sounds like Cursor Origin is GitHub's new Git platform.

It's not, the the good old Cursor's (the IDE) new Git platform.

This is great and is also something that I've always had an issue with.

What I do now is open the HN comments, and then when I'm ready to look at the link + comments, right-click on the title and Open in Split View.

What's the frequency of this happening in modern times and what are the recourses we've set in place? Are there any forms of recourse that you'd recommend be added? And what representatives are running on such platforms to add those forms of recourse for workers?

Or are you just fear mongering about unions?

Thanks for posting this! Quickly turned off auto-update on Antigravity IDE. Don't really use it for coding, but it turned into my shell-scripting+data cleanup editor to keep that separate from my actual projects.

Perfect opportunity for browser or OS API to provide the feature, where we could make it more streamlined, secure, and consistent.

One issue is: when the Reminders app was simple, making a better reminders app just had to be a little more complex that a single developer could improve upon it and charge for it once and make a living. Now, the bar is so high, that it takes significantly more work/time to make a better app, and thus we have to pay subscription pricing in order to use it.

Instead of: let me buy this app for a few bucks and give it a spin, its now: even if I like this app, do I want to pay for it a few bucks a month for forever?

Just enable DLSS 5.

I'd wager that there are no great games without some amount of atrocious code.

I think the idea of the Window Chrome "getting out of the way" of the user is a good concept, but we fail to consider what the user expects at arms length. We also have to consider the chicken-or-egg problem

In the example, we have a sidebar for the formatting in the newer example vs havign that in the toolbar in Lion. Was it that back then, people were more likely to configure fonts & formatting settings, and we've gradually as a society de-emphasized our formatting in word processing? Or did UI changes such as this, hiding formatting options push us towards a world where we care less about formatting? I'd like to think it's a bit of both; as the user-based broadened, you had less percentage-based people that cared so heavily about formatting, so UI changes were made to optimize for that, further pushing people in that direction.

On a different note, I want to call out just how badly the sidebar is laid out compared to the toolbar. In the Lion toolbar, there were unlabeled sections but it was pretty clear what the purpose of each group was. Then you have the sidebar, where labels are added in some places, excessive space given where uneccesary, tabs that are sectioned off from the settings they'll show/hide, collapsible sections that can also be shown/hidden, some dropdowns using up/down caret while others just use the down caret, most dropdown carets being right-aligned but not the gear one, and in the liquid glass versions, the overlay of toolbar buttons over the sidebar creating confusion.

Sorry to pile on, but I also think that changing the background color in the before/after feels like you're purposefully trying to make the before one look worse. Like when in weight loss photos people don't smile and pose nicely in the before photos but they do in the after.

Really boils down to the benefits of first party software from a company that has billions of dollars of funding vs similar third party software from an individual with no funding.

GSD might be better right now, but will it continue to be better in the future, and are you willing to build your workflows around that bet?