How this website works

I used a lot of different Content-Management systems (CMS) throughout my career as a web developer.
At first, there were only SPAs in the Javascript galaxies, but since 4~5 years, I used several JAMstacks:

  • Next.js, Gatsby and equivalents: it's nice at first, but beware if you need to include some libraries using other React versions!
  • SvelteKit: it's another language. When you come from Angular, Vue or React, the only thing remaining is HTML, CSS and the component pattern.
    Otherwise, it's a new learning curve. I still think it's great, you should try it!

For managing content, I really liked Strapi, because it's open-source and French, but also because it's largely customizable to your needs if you know Node.js and React. Right now, I don't even use a database, because my content is already hosted on other platforms such as Notion, Soundcloud or Youtube

However, there are many calamities revolving around the Node.js runtime:

  • Security: is there any need to explain? Node.js has full-access to the system, read/write anything anywhere!
  • Performance: even with the latest releases, Node.js is still kinda slow compared to compiled languages such as Rust or C#
  • Development: it's written with Javascript and compiled to C, C++ or assembly, according to the modules you use in your application

I just tested the newest Deno framework called Fresh, now I get the exact same experience as a classic JAM stack:

  • Everything is using Typescript natively, no configuration needed!
  • Preact is used instead of React: as I practiced React a lot, it's very easy to start building pages, components, and even what sits between them: islands
  • The runtime is working on top of a real permissions manager, giving your app (or even part of your app) what access they need, no more
  • You get a free all-in-one deployment option called the Deno Dashboard (a bit like Vercel, but fully serverless out of the box).

If you're using Javascript to build web applications, you should truly consider switching to Deno today

The community or working opportunities might not be as large as the Node.js/Next.js stack, but it's now more serious than ever in a digital age that's never been so threatened by dubious security layers, fast-paced coding practices and complex configuration/bundling tools.