sequencer
clace
sequencer | clace | |
---|---|---|
2 | 14 | |
19 | 119 | |
- | 34.5% | |
3.6 | 9.6 | |
6 days ago | 12 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
sequencer
-
A Better Way to Code: Documentation Driven Development
I really love this idea in theory, and I believe that for some system, specially mature ones, it may work well. I see good documentation as a super power; it empowers readers and motivate people to understand more about the system without being caught in the weeds of reading the source.
The source has baggages, and the intent of every single function calls is not always evident. Writing documentation up-front can help direct the source, but this is a tug-of-war environment. Each affect the other in its own ways.
And for that reason, documentation driven development can be a real drag. You start writing documentation with the best intentions, everything works great for this first release. But 2 months down the road you need to modify something and it has a ripple effect on many of the things you documented. It's a non-negligible cost.
I've been working on this open-source tool(https://github.com/pier-oliviert/sequencer) and I've spent a lot of time on the documentation. And what I described above happened. I wanted to make a not-too-big change, and it required me to rewrite 30% of the documentation. I still love the documentation aspect of it, but it definitively has a cost.
-
piku: The tiniest PaaS you've ever seen
First time I read about piku. I have no idea why, but the feeling of `git push` to initiate a deployment like piku does always felt magical to me. There's nothing simpler than that.
This is timely for me as well as I just open sourced (yesterday!) a project that is in the same space, but for Kubernetes (https://github.com/pier-oliviert/sequencer).
All of this to say, congrats! It looks great.
clace
- piku: The tiniest PaaS you've ever seen
- An Overview of the Starlark Language
- Show HN: Web app proxy and container manager (Nginx Unit alternative)
-
ETag and HTTP Caching
An approach like https://github.com/benbjohnson/hashfs allows file names to be updated at runtime to be content hashed. This removes the need for the extra "304 Not Modified" API calls from the client. This content hash based file renaming is usually done using a build step which renames files. For applications where the static file serving and HTTP request processing are done in the same application, this can be done in memory without a build step for file renames.
I am using that approach in my project https://github.com/claceio/clace. It removes the need for a build step while making aggressive static file caching possible.
- Show HN: Clace – Nginx Unit alternative – app server for internal apps
- Show HN: Clace – Platform for hypermedia driven internal web tools
-
The End of Airplane.dev
I am building https://github.com/claceio/clace. It is focussed on building operational web apps, with a focus on security. The end goal is to build something between https://www.rundeck.com/ and https://retool.com/, allow automation of operational tasks through a web interface while also allowing fully custom web apps.
Clace also works great for running simple web apps locally. Building and deploying a web app should be as easy and common for backend engineers as creating a CLI app is.
-
Is Htmx Just Another JavaScript Framework?
Hypermedia based web applications are a great fit for developing internal and operational tools. I have been building https://github.com/claceio/clace for making development and deployment easier for such web apps.
-
Pocketbase: Open-source back end in 1 file
I have been building a project https://github.com/claceio/clace which aims to make building hypermedia based web applications easier. Clace is implemented in go, it uses Starlark (python syntax subset) for application configuration. With Clace, the apps are implemented using Starlark and (go) html templates, HTMX is used for web interface, app developer does not need to write any JavaScript.
-
Python Is Easy. Go Is Simple. Simple = Easy
Starlark in go https://github.com/google/starlark-go is a great way to combine the best of both, the ease of use of Python and the simplicity of go.
I have been building a platform for deploying internal web applications using this approach https://github.com/claceio/clace. Use Starlark to configure the application, the platform itself is built in go.
What are some alternatives?
- - Hyphen - An elegant custom element base class
DevSecOps - ♾️ Collection and Roadmap for everyone who wants DevSecOps. Hope your DevOps are more safe 😎
go-plugin - Golang plugin system over RPC.
hashfs - Implementation of io/fs.FS that appends SHA256 hashes to filenames to allow for aggressive HTTP caching.
tailgate - Client-facing generative-AI components without the fuss.
fragmentify-js - FragmentifyJs
chat-app - A contact us demo widget built using Saasufy.
certmagic - Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal
pocketbase-nuxt - A test project with pocketbase
Fragmentify - Django like template inheritance for XML
css-scope-inline - 🌘 Scope your inline style tags in pure vanilla CSS! Only 16 lines. No build. No dependencies.
starlark-go - Starlark in Go: the Starlark configuration language, implemented in Go