Like Kitten itself, it’s a baby but will be evolving quickly as they approach API version 1 together.
Enjoy!
💕
PS. Of course it’s written in Kitten itself. It doesn’t do anything fancy but here’s the source code if you’re interested: https://codeberg.org/kitten/site
Quick heads up: Kitten’s installer/downloads will be offline for a few minutes as I recreate kittens.small-web.org (the site that new Kittens are deployed to when they’re born) as it was originally on Ubuntu and sites deployed by Domain are now using AlmaLinux. Also, I am setting Kitten’s API version to 0 (it was initially set to 1) to signal that it is prerelease. When the version is back to 1 it will be because API version 1 is stable.
Well damn, that was a bit more than a few minutes…
So tell me kids, what happens when you nuke the Kitten distribution site, itself powered by Kitten, then try to redeploy it using Domain, which installs Kitten from… ah, yes, you guessed it… the Kitten distribution site… the one you just nuked!
🤦♂️
Then, you realise you hadn’t updated the site to run on the latest Kitten with breaking changes…
🤦♂️🤦♂️
So one manual server setup + one app update later, everything is back up and running.
🎉 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.)
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.
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.
@miki A few months back, a British broadcaster trialed a more descriptive, blind-friendly audio stream for a televised rugby match[1]. Of course, they only had the mono, low-bitrate AD channel to use, and presumably couldn't manage the fade values in realtime. So we ended up with US-SAP-style, crappy stadium audio.
@jscholes@jackf723@vick21@weirdwriter Poland does this somewhat regularly. We get audio description for quite a few football (soccer) matches here. It's quite surprising really, considering the fact that we barely get it for anything else. Soccer is the only thing that gets somewhat regular and consistent AD. The quality is quite crappy, I can't tell you the exact stream parameters but I know who to ask.
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)
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 [...]
Ce qui me plaît dans #gemini , c’est que l’auteur n’a pas à se soucier du design et peut se concentrer sur le contenu.
Le design, c’est l’affaire du visiteur qui peut, au choix, opter pour le minimalisme en lisant les pages dans un terminal, ou s’offrir un affichage sur mesure en configurant aux petits oignons un client Gemini comme Lagrange.
Là, ce n’est plus « orienté sur le lecteur » mais décidé par le lecteur. 😉
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. 🤷♂️
@JohannaMakesGames Haha, indeed. (Or is it worse if you’re ok the day after?) :)
Yeah, I know. And I think I’m way better than I was. I’ve convinced myself that some day you do a little, some days more, and the most important thing is to keep making progress. Harder when sometimes it feels like absolutely no one on the planet gives a single damn what you’re making but, hey, it’s the road I’ve chosen apparently. Better than being applauded from all sides for mediocrity, that’s for sure :)