#smalltech

6 posts · Last used 2d

I’m updating the Small Technology Foundation site (and our other sites) in preparation of today’s mammoth Kitten release that’s taken me seven months to prepare and it’s quite lovely to refactor something you could previously only do in HTML (see the IDs and class name) into Markdown and have it just work. The whole reason for this crazy round of dev was to ensure that Kitten is as rock solid as possible as its the foundation of Catalyst and Meow. (This is just a little thing – Kitten’s an entirely different beast in terms of stability, consistency, and security than it was in April.) PS. If you’re wondering about the <${FundUs} /> bit, that’s a Kitten component being instantiated in the Markdown. You can import them just like you can in JavaScript (and in the upcoming release, TypeScript) pages by including a script section in your front-matter. #Kitten #SmallWeb #SmallTech #markdown #authoring #JavaScript #web #dev
8
2
6
0
Replying to
@chrisstoecker@mastodon.social Nailed it! People running their own #software on their own hardware independently is 👻👹🕷️ SCARY 🕷️👹 👻 for every proprietary software/#SaaS corporation like "Open"AI. This reminds me, I probably should eventually check out local+libre AI tools myself, just to see how useful they are atm and if they are as ethical as they seem. I was never against #AI per se, just against the corporate excesses. #FAIL #SmallTech #OpenAI #capitalism #independence
0
1
0
0
Hey folks, can you help me out with a little something: trying to come up with a good number of files limit for a file scan (for Kitten so you don’t hit heap memory limits if you run it from the wrong directory by mistake) and I’d love some statistics from real JavaScript/TypeScript Node.js projects of the number of files in them (excluding .git and node_modules). Would you be kind enough to run the following command in Terminal in your largest projects and let me know what number your get (along with a short description of the project): find . \( -name "node_modules" -o -name ".git" \) -prune -o -print | wc -l Thank you :) #Kitten #SmallWeb #SmallTech #NodeJS #web #dev #stats #helpWanted
4
11
16
0
🥳 New Kitten Release This one fixes a bug that you would have encountered had you had an asynchronous component (component with asynchronous render method) nested more than one-level deep within synchronous components. (Kitten’s html renderer transparently supports both synchronous and asynchronous render methods.) So, this (taken from my unit test), for example, works correctly now: ```js class AsynchronousOtherName extends KittenComponent { async html () { await new Promise(resolve => setTimeout(resolve, 10)) return kitten.html`Balkan` } } class SynchronousName extends KittenComponent { /* NOT async */ html () { return kitten.html`Aral <${AsynchronousOtherName.connectedTo(this)} />` } } class SynchronousTemplate extends KittenComponent { html ({ SLOT }) { return kitten.html`[Before slot]${SLOT}[After slot]` } } class MyPage extends KittenPage { html () { return kitten.html` <${SynchronousTemplate.connectedTo(this)}> This should render all at once after a short delay.

Hello, <${SynchronousName.connectedTo(this)} />

3
3
3
0
Replying to
🥳 New Kitten Release I just reworked the fix for this to simplify the Kitten renderer (as this fix introduced a regression with components getting instantiated multiple times due to the fall-through logic between asynchronous and synchronous rendering). The renderer now treats every component render function as asynchronous, thereby avoiding the issue entirely. https://kitten.small-web.org Enjoy! 💕 #Kitten #KittenReleases #SmalWeb #SmallTech #web #dev #components #async #rendering
8
1
4
0