glob-match VS bun

You might be interested in @devongovett's `glob_match` library (written in Rust): https://github.com/devongovett/glob-match

in practice, i don't see rust programs with memory unsafety, but i picked the first zig project that came to mind, bun, and it is riddled with segfaults https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3...

Inspired by the speed of Bun, the reliability of Yarn, and the efficiency of PNPM

An early incarnation of server-side JavaScript was created by Netscape around the same time, but it wan't particularly successful.  It wasn't really until Ryan Dahl created Node.js in about 2010 that server-side JavaScript really took off and became "a thing".  More recently a serious competitor to Node.js - Bun - has emerged: its main advantage over Node.js is its stellar performance.

I've previously tried out Lambda functions with a custom runtime using Deno, and it had great security and convenience benefits. But Deno isn't the only alternative to the Node.js runtime. Bun is a more recent entrant to the space, but it has an impressive number of features, including not requiring TypeScript to be transpiled, and it makes a lot of claims around speed. Bun also has everything for a custom Lambda runtime buried in its GitHub repository.

The first line is called a shebang. It tells the system which interpreter to use to run the script. In this case, I am using Bun. I also need to make the file executable for that to work; on Linux/Mac, you can do that with the following command:

Node.js popularized the concept of running JavaScript on the server. Today, there are more JavaScript runtimes intended for building server-based applications, with Bun and LLRT among the most recent I'm aware of. Deno has been around for some years, and their Version 2 release seems to hit a chord because it has better compatibility with the Node.js API.

All in all, before eventually migrating to some boring modern technology, I decided to try using Bun with it instead of Node. I didn't come up with this idea completely out of nowhere; I had some interesting experience with Bun already, and the promise of zero-config development had proven to be a working approach for me. So I decided to test the hypothesis of letting Bun handle the obsolete Node project to see what it would yield.

curl https://bun.sh/install | bash

FROM php:latest # Instalar unzip RUN apt update && apt install -y unzip # Instalar Composer de outra forma, mas com o mesmo resultado RUN curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer # Configurar as variáveis de ambiente ENV HOME="/root" ENV PATH="/root/.composer/vendor/bin:${PATH}:/root/.bun/bin" # Instalar Bun RUN curl -fsSL https://bun.sh/install | bash # Criar alguns symlinks para o executável bun RUN ln -s $(which bun) /usr/local/bin/npm RUN ln -s $(which bunx) /usr/local/bin/npx # Instalar o Laravel Installer RUN composer global require laravel/installer # Instalar a extensão pcntl RUN docker-php-ext-install pcntl

We'll begin by creating a Hono app. I'm using Bun as my package manager.