I am new to this LLM stuff to be honest. But seems like it's a default way to write code currently in many domains. I would be grateful if you could share framework related plugins/skills that you found great.
https://github.com/doors-dev/doors
Doors: Server-driven UI framework + runtime for building stateful, reactive web applications in Go.Some highlights:* Front-end framework capabilities in server-side Go. Reactive state primitives, dynamic routing, composable components.* No public API layer. No endpoint design needed, private temporal transport is handled under the hood.* Unified control flow. No context switch between...
My theory that I don't have to care a lot about gopls changes, because I rely on LSP protocol itself when doing conversion. I basically scan exchange JSONs for locations (sometimes recursively) that are related to `.gox` or generated `.x.go` and perform targeted patches.
About string literals completions.. I can't imagine how I could achieve even a 1/10 of feature set with this approach. Or at the end, it will turn out as something very similar to what I have, but achieved from a different starting point.
https://github.com/doors-dev/gox
I created a Go language extension that turns HTML templates into typed Go expressions and adds `elem` primitives. Works via own language server by proxying gopls with extra features on top + runtime package.In core ideas it's sumular to `templ` - it compiles to Go, has own extension (`.gox`), language server, CLI tool and IDE plugins, can write to `io.Writer`. But there are much more...
https://github.com/doors-dev/doors
It has reactive state, components, lifecycle control, SSR by default, and an HTTP API-free architecture.Highlights * Explicit and type-safe DOM manipulations * State is a communication primitive first, a render driver by choice * No coupling between state primitives, components, and dynamic containers — combine them into your own abstractions or use directly * URI decoded into a struct and...
It’s called doors. I've been working solo on this for a while. There’s so much I want to say about features, how it works and how I got here (10 years of career from php dev to CTO to this), I don’t even know where to start. Please check out the announcement site. What do you think about it? P.S. Doors will require a paid license for production use (lifetime, per-domain, very affordable). But...