@gigasecure the title made no sense, and after reading, neither did the article.... written from a HA point of view and as such biassed and missing too many points 🤷♂️
For example, debugging in node-red can be far more detailed
It's been almost a decade since I've done a live coding stream. This will be fun!
Today I'll be migrating my website from React to Lit, which is a lightweight framework built around web components. I have the scaffolding set up mostly, so now it's time to get this done.
Come watch. Ask questions in chat! You don't need to create an account, just a username is needed to participate.
Hmm I've only ever built sites using #Django, bcos I'm most good at #Python and I'm just super familiar with all the features (and quirks) of Django and it's been great, but honestly being good at only Django (when it comes to web dev) does gimme huge impostor syndrome cos I know fuck all when people talk about #Node and whatnot :(
Maybe I can learn how to build a site using #Eleventy so I too can speak gibberish lingo I never understood before with other fellow programmers?
@skinnylatte thank you so much for the quick round-up and resource! 😭 It will be super helpful. And I can tell the community is great, and you too are part of it!
With other tools I usually start with a starter then don’t do anything coz I can’t figure it out, but here I was able to build sites from scratch really with just html and css
We just released Execa 9, which is our biggest release so far.
If you're currently using Execa, you should check out the new features! Also, if you're currently using zx or Bun shell, you might be interesting in this alternative.
#Fedify's tutorial, which previously assumed you were using #Deno, can now be followed using #Node.js and #Bun! (What is Fedify? It's an ActivityPub server framework.)
However, they are written for Fedify 0.8.0, which hasn't been released yet. You can test it with the pre-release version, 0.8.0-dev.164, though.
Wooooo did another #OpenSource contribution! I fixed the supported versioning of a tool I use to generate changelogs after I discovered that we weren't using a valid version of #Node.
I love doing open source, wish I could do it more often!
Why would you use #DDEV instead of a #Node or #Python server directly?
There are significant advantages to using a containerized setup like DDEV. We go over them in this article, and include a step-by-step guide to set it up.
@andy_blum helps introduce DDEV to a new audience that may not know about how useful it can be!
Best addition to any #Node package.json, #PHP composer.json or other dependency managers file would be a mandatory „why“ field for each single dependency which requires a minimum number of sensible words.
Could make devs think twice before adding and help (me) when upgrading projects after some time.
Also this is probably the reason I dislike JSON for configuration as I cannot add comments.
Browsing old git commits sometimes helps to find out reasons for dependencies but I also want to understand the same for the tree.
Every dependency in addition to the base framework you might use is a cost and it adds up.
So I would love to see the „cost“ of a dependency before even installing it. Several times I added one and removed it again after seeing what it came with.
@sebobo i think that in PHP this is a lot easier, since you can rapidly find where that code is used due to autoloading definitions, and also because you have tools like Composer Unused to check for unused packages..
I f*cking hate #Javascript and I hate #Node even more! All day I've been trying to get the latest version of #Strapi to build ... error after error after error and now, at random it's just decided to work after a whole wasted Sunday!