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.
Why is it that python code always feels like it needs way less indentation and feels like the logic can be implemented much simpler. Or is it #django that makes this feel like it.
@fabian yep, compared to #JS. Sorry didn't say that, but I meant it, yes.
I somehow write nicer code without thinking much in Python, in JS I screw up code (beauty) a lot easier and faster.
@aeveltstra server side rending is a valid approach. i started with @astro and @solid_js . however, from what i guess, server side rendering is more cost intensive than static html
Last month's exclusive video at The Spicy Web demonstrating a CodePen example of Signals—what they are, how they work, and why frontend frameworks and fans of vanilla #JS alike are adopting them rapid-fire—is now available to view for free! Check it out:
On s'occupe de la partie serveur du site de loterie à partir de 10h30 sur ma chaîne #Twitch. Codage en #PHP maintenant que la partie #HTML/#CSS et #JavaScript est bouclée.
Hier j'ai fait un peu de #JS, ce ne fut pas si laborieux que ça. Voici comment seront choisis les numéros de ticket de loterie par les participants : https://youtu.be/vdTp7XzNmBE
Started writing a decision log for our #DesignSystem. Documenting why we chose to build plain ol' #HTML and #CSS where we can and #WebComponents where client-side #JS is needed is turning into a bit of a manifesto. Essentially we're using (and encouraging others to use) #ProgressiveEnhancement 😉