go-ssc
kyoto
Our great sponsors
go-ssc | kyoto | |
---|---|---|
11 | 18 | |
116 | 531 | |
- | - | |
7.9 | 9.6 | |
over 2 years ago | almost 2 years ago | |
Go | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go-ssc
- Golang Front End Components
- Front end development with components and Golang
- Golang Front End Framework
- Golang frontend components, updates and ideas gathering
- Frontend components with Golang
- SSC, changes and propositions
- Golang Server Side Components
- [SSC] Frontend components with Golang, changes and propositions
- [SSC] Frontend components with Golang, new features and discussion
- Golang Server Side Components and Actions
kyoto
-
Embed the backend as a web worker
the only thing i need to do is port the htmx code to golang and then cross compile to wasm for web and then to mobile and desktop. I am currently seeing that there are other htmx style systems out there that are already written n golang. for example: https://github.com/kyoto-framework/kyoto
- 京都项目正在从GitHub转移到Sourcehut (Kyoto project is moving from GitHub to Sourcehut)
- Kyoto framework is moving to sr.ht from GitHub
- Kyoto project is moving from GitHub to sr.ht
-
Is there some server site rendering Go library that would offer Nuxt like things?
But this baby here https://github.com/kyoto-framework/kyoto is in the early development stages, which is a nice approach imho.
-
Feasible approach to SSR?
htmx requires you to return markup for specific components. So, you’ll need to maintain component template definition in two ways: embed directly into page template, and serve it as an api. IMO htmx is cool, but requires some tooling around it to simplify work. Our team is developing and using kyoto library, focused on server rendering and components approach: https://github.com/kyoto-framework/kyoto
- kyoto: Important update
What are some alternatives?
k8s-platform-lcm - A faster and easier way to manage the lifecycle of applications and tools, running and living around your Kubernetes platform
vugu - Vugu: A modern UI library for Go+WebAssembly (experimental)
ssceng - Project was renamed and moved to https://github.com/yuriizinets/kyoto
go-app - A package to build progressive web apps with Go programming language and WebAssembly.
forgefed - ForgeFed - Federation Protocol for Forge Services
yaegi-template - Use yaegi as a template engine.
GoatCounter - Easy web analytics. No tracking of personal data.
kyoto - Golang SSR-first Frontend Library [Moved to: https://github.com/kyoto-framework/kyoto]
uikit - Wake up, Samurai. We have a project to build
gomodest-template - A template to build dynamic web apps quickly using Go, html/template and javascript
killed-by-microsoft - Part guillotine, part graveyard for Microsoft's doomed apps, services, and hardware.