This sounds interesting. I once tried to migrate to YugabyteDB, but PostgreSQL compatibility was not great, it required an extensive redesign of the existing PostgreSQL database. Might give this a try.
Interesting move. I'm also considering Remix.js. It's either an internal Next.js rewrite from Page Router to App Router, or a framework switch to Remix.js
I liked Remix.js even though I found the Action (kinda like Server Actions in Next.js) a bit limiting and formData hard to type (in TypeScript)
Third party plugins make an up-to-date WP install insecure. I think Core WordPress is probably more battle tested than any other framework. One could argue the core should protect against bad plugins, but a secure plugin API would mean a non-functional API.
The language/runtime certainly has an impact. But indeed, in reality there is no way to compare these scaling claims. For all we know people are talking about serving a http-level cache without even hitting the runtime.
- "It's extremely complex for someone with 0 experience to work with JavaScript tools"
- "JavaScript is terrible anything else than manipulating the DOM"
I guess the main issue was not liking / embracing JavaScript/TypeScript. Which is fine, but doesn't really make for a convincing article.
Another thing I would have loved to see was all the issues you ran into with htmx (apart from the ID collisions you expect to get). As we all know, everything is a tradeoff, there are no silver bullets.
req.ip, but also look at the x-forwarded-for header if you are using a proxy server. This header can have multiple ip's when you have say nginx terminate ssl and use cloudflare.
I have the Airthings Wave+ and one thing that bugs me is the relative humidity threshold. Anything above 60% will give a yellow led warning. If you have many indoor plants, live in a forest, or even just ventilate a lot on rainy days the sensor will show an air quality warning. I would like to take humidity out of the equation as I much rather focus on CO2, VOC and Radon. Otherwise a great sensor that was easy to integrate in my own scripts as you can easily get all sensor readings over bluetooth.
I switched from Vue/Nuxt 2 to React at the time of the V3 transition. The reason was horrible slow dev performance, lack of template type checking and overall slow transition of the ecosystem to V3.
Don't mindlessly follow your framework du jour's way of handling state mutations. It's healthy to keep these isolated. I've switched from Vue to React and kept my API server as is. If you intertwine mutations deeply inside Next.js server actions you will have a hard time adapting to new requirements.
> Where are the open source folks in Node.js producing equivalents of WordPress and Magento and Drupal?
I can't speak for the community at large, but I specifically switched from large opinionated frameworks to Node.js/TypeScript and a carefully selected stack and modules. Once you reach a certain level of complexity, these frameworks start to get in the way. For me, Node.js/TypeScript gives me type safety, easy refactors, an ergonomic language, and a large community.
On the other hand, if you have to churn out projects for clients, a rigid opinionated framework is probably more appropriate as it makes project handover easy and cuts down on decision fatigue.
I'm quite happy we don't have one dominant framework in JS. We have good tools for specific tasks and glueing them together is easy in JS land. Not having a big framework dictate your options is actually quite liberating.
In Spain they managed to make roundabouts with traffic lights. It's not uncommon but having traffic lights on small roundabouts can make roundabouts very hard to navigate.
I use an old Android phone with a long deprecated app called MobileWebCam (still available on certain sites) I removed the battery and connected the charger directly. It uploads a picture every minute, a Node.js backend creates the timelapse with ffmpeg. Currently experimenting with a TP-Link C520 cam and a Raspberry Pi. You can point the camera to different positions using ONVIF, use ffmpeg to grab the stream and take a snapshot, then process this again on the server. Downside is the wide angle / fish eye lens and occasionally a corrupted stream snapshot.
Been making timelapses with ffmpeg since forever, such a great tool. I try to always have a cam pointed at the sky and upload a snapshot every minute. A telegram command triggers the creation of a timelapse with a similar cli command like the OP. https://www.youtube.com/watch?v=5GvaFBzOu2c
Happy user of the Airthings Wave Plus (same as View but without a display). Major feature requirement was being able to fetch the sensor values with just a Bluetooth connection.