remote-standalone
clace
remote-standalone | clace | |
---|---|---|
2 | 10 | |
0 | 72 | |
- | - | |
10.0 | 9.5 | |
over 10 years ago | 5 days ago | |
JavaScript | Go | |
- | 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.
remote-standalone
-
HTML First – Six principles for building simple, maintainable, web software
I published this article on Template Animation (aka DOM Templating) 12 years ago:
https://benkoworks.com/your-templating-engine-sucks-and-ever...
It fits nicely with this goal. My colleagues and I created a tool that allows HTML developers to work in HTML by compiling HTML using a Chrome extension, and then allowing developers to compile the same in their code platform of choice and operate on the DOM:
https://github.com/iaindooley/Fragmentify
https://github.com/iaindooley/fragmentify-js
Even if you're doing a SPA you can use this same method, by sending updates over the wire and doing the processing on the server. We created a standalone package that facilitated that by loading the initial page from the server then transparently allowing the server to send just the changes to the page and having them applied on the client side:
https://github.com/dgrinton/remote-standalone
The combination of "remote" and "fragmentify" and Template Animation/DOM Templating, in my opinion, would be a tremendous "retreat to move forward" in web development technologies.
-
We're breaking up with JavaScript front ends
Many years ago a colleague and I wrote a stand-alone version of a package for my own arcane php framework called Remote.
The idea was that you write in Web 1.0 and immediately get a Web 2.0 front end because it just updates what it needs to.
I still think this is the holy grail of frontends:
https://github.com/dgrinton/remote-standalone
clace
-
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.
-
HTML First – Six principles for building simple, maintainable, web software
I have used this approach for internal tools and it has been great. It makes it much easier for one person to build the whole app, frontend and backend, and makes ongoing maintenance much easier.
I am working on https://github.com/claceio/clace which takes this no build approach and makes it easy to build portable applications, using Starlark running in go to configure the backend.
- Clace – Secure hypermedia web applications using Starlark and go
- Show HN: Clace – Platform for secure internal web applications