Well, if you have ever heard of NodeJS then this might be of interest to you :)

NodeJS has been around for quite some time, and used by a lot of large companies - but it did have some issues (not to mention the whole NPM world!).

The creator of NodeJS went away a few years ago to create DENO (yes, switch those letters around!). DENO aimed to fix some of the failings of NodeJS but didn’t support a lot of the existing NodeJS ecosystem.

DENO 2 does let you use the older NodeJS modules as well as it’s own newer modules which are, apparently, a lot safer.

Also, I didn’t quite do my research - DENO 2 is built with RUST :)

Deno is written in Rust and based on the V8 engine that powers Chromium browsers. "Rust has been crucial to Deno’s development, especially with Rusty V8, recently stabilized," Dahl told The Register. "Rust's unified build system simplifies adding third-party functionality compared to C++, keeping Deno fast and reliable for server-side apps."

Anyway, take a listen and here are a few links if you need them.

https://deno.com/

https://fresh.deno.dev/

DENO 2 Serverless hosting

Okay, take care until the next time!

Well now, are you using Docker? never heard of Docker? well perhaps you might want to ask AI to help there.

If you do use Docker to create containers of your apps/micro-services then what about Fly.io?

Fly.io is a public cloud infrastructure platform. Users deploy applications as Docker images, but Fly.io does not utilize Docker to run the applications.

Docker images are actually OCI (Open Container Initiative) images, which are essentially stacks of tarballs (are these similar to harballs that a cat has?). Fly.io unpacks these layers onto virtual machines and can retrieve the container manifest from the Docker registry.

Fly.io employs a custom registry to fetch and unpack image layers. It utilizes Firecracker microVMs for virtualization. Firecracker is a virtual machine manager that creates lightweight microVMs. Fly.io uses Firecracker to orchestrate these VMs, along with containerD for isolation. ContainerD is responsible for managing and unpacking application images, with each app instance running on its own isolated kernel.

There are some generous free options described here.

Well, what do you know? back to some frontend web stuff no less!

I have been using bootstrap CSS for years, and still do, but when I eventually realised Tailwind CSS was “something”, I have since been trying a few projects out with Tailwind CSS. However, because I am lazy and have been using WordPress with Elementor (page builder), I stumbled across dev dojo and some of their product offerings, one of which is “tails” - a page builder using Tailwind CSS no less! It looks really cool and produces a webpage/site with Tailwind CSS for the display aspects.

Interestingly, dev dojo also have a product called “pines” which using AlpineJS and TailwindCSS to build really stylish websites too… AlpineJS is an ultra-minimal JavaScript framework that I really must rediscover!

Until next time, take care!