🎉 You can now use components and fragments in your Markdown pages in Kitten.
Following on from yesterday’s Markdown pages feature, you can now import components and fragments and use them in your Markdown pages to add dynamic functionality (similar to how it works in mdx but without using JSX).
(The “SCARY” text in the screencast is being randomly animated by a component.)
You can now create .page.md files and use front matter to specify a layout template as well as any other props you want to pass to your layout.
(I’m working on the Kitten web site with docs, etc., so I thought I’d bite the bullet and add this feature this morning to make my life easier. Should make it easier to make this sort of site with Kitten in the future for everyone.)
Depuis quelques années, une partie de la communauté internet se tourne vers des solutions plus simples et moins gourmandes en ressources, en réaction à ce que beaucoup considèrent comme l’« #emmerdification » progressive du web. Le protocole #Gemini a émergé comme une réponse prometteuse à ce besoin, mais après l’enthousiasme initial, une certaine désillusion semble s’installer [...]
So Kitten’s build process (i.e., the time it takes to build Kitten itself) takes ~0.7 seconds on my ~1 year old desktop (Ryzen 7 5700G 3.8Ghz) vs ~1.4 seconds on my ~3-year-old Starlabs LabTop (renamed to the Starbook thanks to a suggestion by yours truly but sadly, not quickly enough).
So, in summary, it’s bloody fast for something that results in a ~9MB bundle.
Note that when you’re working with Kitten, your apps do not have a build process.
You write HTML, CSS, JavaScript and, optionally, extend using first-class support for htmx and alpine.js as well as Kitten’s own Streaming HTML workflow¹. There’s also no scaffolding or generating a project with hundreds of files or anything. You just write the code for your app.
I find #NodeJS deprecation warnings hit the sweet spot between jarring enough to be annoying and not informative enough to be useful.
So, in Kitten, the first time you hit a deprecation warning, you get a message telling you there are deprecation warnings.
If you care, you can open the interactive shell and view the kitten.deprecationWarnings list, which will show you full details including the stack trace.
There might be space for a few people from outside the university to attend so if you want to drop by, make some noise and I’ll have a chat with the university.
Thanking @mirela for organising this and looking forward to hopefully meeting some of you in the Netherlands soon.
• Runtime is now Node 22 (22.1.0 as 22.2.0 has a bug that can crash on deprecation warnings). This might be a breaking change for your code (e.g., import…assert is now import…with, etc.) Remember, Kitten is pre-release/not API-versioned yet.
• Applied all semver-compatible dependency version upgrades.
• Fixed tests & coverage. Tests are still woefully inadequate but will improve.
Wanted: personal websites (with curated collections of bookmarks/links to other websites) or link directories that are titled anything starting with the letters "W", "X" or "Z".
Why? To complete the alphabet, of course!
(in terms of the bukmark.club's directory index)
So Apple destroys pianos with a hydraulic press, Microsoft invents TotalSurveillance™️ and Google tells us to put glue in our pizza and eat at least one rock a day.
「 In the same time library books have seen a lot. They were touched by a lot of greasy fingers, seen a lot of toilets. Just look at those two. Both are still fully usable, despite the tired look. 」
Code drunk, debug sober. Bah! Just fixed three bugs after a pint of Tundra.
(This is in no way meant to be role model behaviour. There just happens to be a lovely pub by the seashore in Bray where you can sit outside and it’s a nice distraction in the evenings when the weather is good and I don’t feel I’ve done enough in the day* and need a change of scene.)
It doesn’t help that I never think I’ve done enough in the day. 🤷♂️