They can get away with not implementing even basic stuff, becauase their core feature is all 99% of the users even care about.

However drizzle makes it very very straightfoward to handle DB migration / versioning, so I like it a lot for that.

I've used LLMs for code gen at work as well as for personal stuff.

At work primarily for quick and dirty internal UIs / tools / CLIs it's been fantastic, but we've not unleashed it on our core codebases. It's worth noting all the stuff we've got out of out are things we'd not normally have the time to work on - so a net positive there.

Outside of work I've built some bespoke software almost entirely generated with human tweaks here and there - again, super useful software for me and some friends to use for planning and managing music events we put on that I'd never normally have the time to build.

So in those ways I see it as massively increasing productivity - to build lower stakes things that would normally just never get done due to lack of time.

I have a couple projects I could see this being really useful in, at least as an option instead of pure plain text. I still feel like consumers don't like markdown though, it's frustrating.

One thing I noticed, when doing a list (bullet, numbered etc) it would be great if the list continued on barrage return (enter) - most general users would expect that I think.

A tiny island is fine for a tool like this - not everything needs an 'ecosystem'.

This is always a fun one...

"Who wrote / designed this garbage... Oh wait, it was me"

God forbid you have to remember to save your work!

I would imagine this will set you up incredibly well for a career in the industry, arguably moreso than your actual degree. Any reasonable prospective potential hirer is gonna be super impressed by it I think.

Nothing sinks in to anyones brain because they're not actually talking about it and they don't need to actually learn it for any reason in school because they can just ask the chatbot again at any moment.