clace
WHATWG HTML Standard
clace | WHATWG HTML Standard | |
---|---|---|
10 | 137 | |
73 | 7,726 | |
- | 1.4% | |
9.5 | 9.4 | |
6 days ago | 4 days ago | |
Go | HTML | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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
WHATWG HTML Standard
-
Here are the 10 projects I am contributing to over the next 6 months. Share yours
WHAT-WG HTML
- Add Writingsuggestions="" Attribute
-
Streaming HTML out of order without JavaScript
There's a long-standing WHATWG feature request open for it here: https://github.com/whatwg/html/issues/2791
And several userland custom element implementation, like https://www.npmjs.com/package//html-include-element
One of the cool things that you can do with client-side includes and shadow DOM is render the included HTML into a shadow root that has s, so that the child content of the include element is slotted into a shell implemented by the included HTML.
This lets you do things like have the main page be the pre-page content and the included HTML be a heavily cached site-wide shell, and then another per-user include with personalized HTML - all cached appropriately.
- An HTML Switch Control
-
YouTube video embedding harm reduction
The `allow` attribute on iframes is a relatively recent API addition from 2017
https://github.com/whatwg/html/pull/3287
-
Htmz – a low power tool for HTML
I think there's a pretty strong argument at this point for this kind of replacing DOM with a response behavior being part of the platform.
I think the first step would be an element that lets you load external content into the page declaratively. There's a spec issue open for this: https://github.com/whatwg/html/issues/2791
And my custom element implementation of the idea: https://www.npmjs.com/package/html-include-element
Then HTML could support these elements being targets of links.
-
The Ladybird Browser Project
> Consider https://www.ietf.org/rfc/rfc1866.txt vs https://html.spec.whatwg.org/multipage/
I thought, oh, that's not so bad. Then I realized what I was looking at was a 10 page index.
- HTML Living Standard
-
Is Htmx Just Another JavaScript Framework?
I'd love to see something like HTMX get standardized, but I'm extremely pessimistic for HTMX's prospects for standardization in HTML.
In talking to a few standards folks about it, they've all said, "oh, yeah, you want declarative AJAX; people have tried and failed to get that standardized for years." Even just trying to get
to target a section of the page that isn't an has been argued about and hashed out for years.<p>Why is that? Well, for example, here's the form you have to fill out to start standardizing a front-end feature. <a href="https://github.com/whatwg/html/issues/new?assignees=&labels=addition%2Fproposal%2Cneeds+implementer+interest&projects=&template=1-new-feature.yml">https://github.com/whatwg/html/issues/new?assignees=&labels=...</a><p>It asks three main questions:<p>* What problem are you trying to solve? -
New in Chrome 120 back button detection
The issue with a single global event handler is discussed here: https://github.com/WICG/close-watcher#a-single-event
If you use popover="", you get the kind of functionality you're discussing for free. For
, the discussion is in progress and reaching a conclusion: https://github.com/whatwg/html/issues/9373
What are some alternatives?
- - Hyphen - An elegant custom element base class
caniuse - Raw browser/feature support data from caniuse.com
go-plugin - Golang plugin system over RPC.
WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
DevSecOps - ♾️ Collection and Roadmap for everyone who wants DevSecOps. Hope your DevOps are more safe 😎
standards-positions
hashfs - Implementation of io/fs.FS that appends SHA256 hashes to filenames to allow for aggressive HTTP caching.
Retroactive - Retroactive only receives limited support. Run Aperture, iPhoto, and iTunes on macOS Sonoma, macOS Ventura, macOS Monterey, macOS Big Sur, and macOS Catalina. Xcode 11.7 on macOS Mojave. Final Cut Pro 7, Logic Pro 9, and iWork ’09 on macOS Mojave or macOS High Sierra.
fragmentify-js - FragmentifyJs
browser
tailgate - Client-facing generative-AI components without the fuss.
exploits