netghost

And here we are on HN discussing it.

I think what's most interesting is not that this works well for common languages, but it seems to be useful for languages that don't exist yet. If you want _some_ highlighting for your SQL variant, or your language that borrows many common idioms, or just sloppy code that's close enough to the target language, this could be useful.

You can play with it online. I was pretty impressed with the speed/quality given it's size.

It's definitely not going to replace a larger frontier model, but it's worth keeping an eye on.

I don't use them as coding agents, but they can be very useful for things like text transformation, summarizing, or text extraction.

That said, if you have a subscription to a paid model already, you're not necessarily winning out on anything except perhaps privacy, which isn't nothing.

TIL about `gum`. I love this and endeavor to integrate it into something sometime. Thank you for mentioning it!

They might have opinions about it, but look at the pay for frontend engineers at the same company. It's not uncommon to see the same seniority be 20% lower than a backend role.

I see a lot of people say you have to use methodology X, or that methodology Y is worthless.

I'm the end, I think we have maybe different uses for notes. Journaling, scratchpads, to-do lists, research, etc.

Take a methodology with a grain of salt. If it doesn't fit, there's a good chance it's solving someone else's problem, but you can always inform your own approach with it.

Looks great on mobile in portrait mode. Bonus points for the audio.

I think you're operating in a scale that is small enough that there's little risk.

You'll be able to iterate if you run into anything that doesn't work. You should however be clear on what problem you and your team are solving, and not just "get some rag".

That seems like a reasonable tradeoff, thanks.

Bun ships with lots of tools built in. It has support for bundling js, html, etc for the browser.

I suspect that if you want the best results or to hit all the edge cases you'd still want vite, but bun probably covers most needs.

Thank you. This looks like a nice improvement on pgtyped, and another good option.

I'm curious if there are any good patterns for dealing with dynamic query building or composing queries?

Out of curiosity, the post you linked mentions that it won't work for renames. What's the approach for these and other types of procedural migrations, such as data transformations (ie: splitting a column, changing a type, etc.)

With a declarative model, would you run the migration and follow immediately with a one off script?

Seems great for really small apps where you want your resource definitions colocated with the code using them. I'd imagine the benefits start to break down as your infrastructure gets more complicated.

The bigger answer is that if you're proficient and happy with CDK or anything else to wire resource up, you're probably not going to see much (if any) benefit.

Wonderfully done, thanks for sharing!