kyle-ssg

Cheers! I'll be improving it as I use it every day, refusing to open old IDE haha.

Just to add to this, I also observed in some of these cases the frame rate dropped in a non-transient way on that it remained low. I think this should be covered by more of a soak test but it has still been very useful for me to see a constant fps.

Hey, I should have maybe made this more clear - I definitely don't care that it's 120fps more that the frame rate doesn't drop and we aren't seeing freezes. Initially the project was, with large files, with syntax highlighting especially or switching very large branches. The built-in FPS counter actually proved really helpful in observing these.

Hey, have you got any fundamental examples of why? I get pessimism towards AI, I've battled against using it after programming for so long, but I do intend to keep building on this and I'd genuinely appreciate things you saw that are icebergs.

Yep sure I'll take a look at lunch, this is much easier than Windows / Linux since I can actually QA it.

Yep of course, Syntax colouring will come. And it was intentionally left out first couple days due to critical path for me, I imagine I'll add intelisense too but I'm glad I decided to make language support installable - goal is fast + great Git.

>open in system:

Isn't that reveal in finder? I did add this if so :).

> selectively staging lines

Oh I've never actually done this! But I think I understand, so just pushing a few lines in a changed file. Fun! I've always used a different IDE where I don't think that's a thing. I'll add an issue.

> What models and tools did you use to create this?

Opus 4.8.

> What were your biggest challenges in making this?

UI that had to react due to things such as the window size changing, specifically with horizontal and vertical scrolling and getting it to work with mouse drag + text selection via shift and arrow keys. It was a lot of back and forth. In the end after getting it working for the main editor I (Claude) turned it into a with_scrollbars decorator method.

Knowing to splitting god functions before they sprawl / emphasising regression tests, and specifically frame rate regression has helped me a lot so far I think.

>That might be fine for you and your use cases, but it's not fine for CRUD app developers who are essentially passing and mutating data around databases and state machines.

I've done a mixed bag of these, but yep ultimately mainly just CRUD now days and yep that's all we're doing. It's what a lot of us are doing!

Haha I loved Netbeans, and in college(UK not US) got to the point when I taught actionscript instead of the teacher.

Hey! I don't think I'd want to do that (maybe you're joking). I'm going to have a lot more control over this, how familiar it is to my current setup and things such as a local history that I can add the hunk diff view to.

Also it's just quite fun.

A garden.

Haha fair enough, my colleague always says the same! Actually the theme's already separated into a JSON file so this will be trivial.

> If it were truly as easy as asking an AI once, then everyone would already be shipping successful products daily. AI just lowers the bar to entry.

I could not agree more! I think there's a finite group of people who have a strong software engineering background who really know the rewarding pain and are able to embrace AI in an optimistic way.

Fair enough. I always switch to my IDE for a big branch, actually that's why I never switched VSCode, I liked my original IDEs Git UI. But maybe that's just muscle memory using the same IDE from Java to web over the years.