kyle-ssg

Done, https://github.com/kyle-ssg/kyde/releases/tag/kyde-v1.2.0

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.

Hey, no worries, I don't think you were criticising! I guess this IDE was prominently started for me, and I wouldn't use an internal debugger vs debugging in Chrome for example. I think if I added one, the debugger would be opt-in/installable rather than always bundled.

Thanks! Yep same with my IDE.

I'm making a point about IDEs, I think their usefulness is declining. No, I do not expect other people to use this, but they can and I will.

I do agree with some of this principle, if I sat blasting prompts with all the things I could think of, of course it won't end well. Strong regression tests and good patterns are needed.

RE a month usage, that is a good idea, I will use it for a month and do a more long-form post.

I've been using it since I started building it, and have not touched my IDE, thats the goal. All commits to the repository have been made via the tool itself.

Hey, actually there's a script that generates the screenshots so that I don't have to adjust them every time the UI changes. I do get 120fps with a 37k line package-lock, try it yourself if you don't believe me.

Hey, actually my goal is to stop using my IDE, it'll be one less subscription for me. So I won't get tired of this, I plan on using it daily. I've spent quite a few years obsessing over software quality so I won't accept unpolished and buggy!

Hey, by this do you mean viewing a diff of before and after? If so I get what you mean, but given how important the review is pre-PR I do always come back to IDE.

<3

Hey! That's actually something I haven't checked, none of my active projects use them. I expect it won't break but I haven't designed the diff to account for that. I will take a look though it's a great point.

Hey! I'm a web and mobile developer for past 12 years and have wrote quite a lot of code over the years (github for receipts). I actually even written a mobile application profiler, it's on GitHub.

Debugging and profiling has always been outside of the IDE for me, except when I started out as a Java Developer.

Oh thanks that's made my day haha!

I think something to note on this as I already see this in the comments. There's always the suggestion of "Yeah that's easy we could do that".

To this I'd say it totally depends on the usecase, I've seen 10s of tech teams build this badly and end up causing more harm than good, some even just static config files that require a build to change which totally defeats the point.

I think looking for an open source tool is great, to this I'd say consider the following :

- Before anything else, you'd definitely want the ability to turn the flags off per environment (dev/prod etc) without having to deploy code.

- Do you want to control who can manage features? Quite often you'd want to enable non-tech people to manage / test features.

- How scalable does it need to be? Some people might want to just not have to worry about serving thousands or millions of flags.

- Do you want to serve flags based on users or maybe even groups of users? I've seen attempts at this but then you start having to worry about setting traits and building some sort of rules engine.