deno VS Koa

Deno. https://deno.land/

Only briefly skimmed this but it looks like this is built on top of SQLite https://github.com/denoland/deno/pull/18232/f

The products should not impact the base FOSS software here https://github.com/denoland/deno.

I would use Deno or Go over Nodejs or PhP. Deno is the new Node, made by the guy who made Node, but improved (more secure, better tooling, etc).

Since `.ts` extensions were in alpha, our repo has been set up so that you can switch between Node and Deno seamlessly in-editor and continue developing with no config or source changes.

Personally, I found all the `npm` integration stuff to be a bit overkill for what we were looking for, and honestly Deno's network requests while installing from npm were constantly flaking out in our CI. We ended up just disabling it via Deno's `--no-npm` flag (https://github.com/denoland/deno/issues/17916) and reverting back to a simple set of import_maps to get the node deps we needed. Works like a charm!

Feel free to reference if it's useful:

https://github.com/arktypeio/arktype

I'm actually working on a site that lists staking services and defi projects audit history. It shows when/how many commit changes happen to different repos associated with the projects, last audit date/by whom, and other things. I'm hoping to have it done soon but my full time job makes progress a little slower, and I'm using this to learn/try out deno for the first time so there's a small learning curve to that.

Monoio:

> Rust async runtime based on io-uring.

Awhhh heck yeah!

It's been a bit disheartening that neither Node.js/libuv[1] nor Deno[2] have adopted io_uring. Nice to see some signs of adoption. Bun too.

Side note, I was a bit confused about you mentioning ByteDance, but if I go to the web-infra-dev[3] github page, the description is We are from ByteDance, our goal is to build an open technical ecosystem to promote the development of frontend technology, so now it make sense. Just sharing in case anyone else is confused.

[1] https://github.com/libuv/libuv/issues/1947

[2] https://github.com/denoland/deno/issues/16232

[3] https://github.com/web-infra-dev

On the other hand, Deno is also a great option for running programs faster, but it also provides an easy way to handle permissions, which enhances security. You can learn more about Deno at https://deno.land.

Oh, and if you're looking for even better security, you should give "Deno" a try. It's another JavaScript runtime that runs programs faster and has an easy way to handle permissions. Plus, it's more secure than Node.js. Here's the link: https://deno.land

Koa.js: https://koajs.com/

Koa -Next Generation Node Microservice Framework

Backend is more tricky. - RESTful APIs I prefer Koajs - For a RPC/microsevice, I have only used gRPC - For a CLI, yargs and inquirer

There are lot of different frameworks out there. If you learn one, there is no guarantee that the next job you find will use the same. For example if you learn Express and the next one used Koa or Nest.

Koa.js is a minimal and flexible Node.js web application infrastruc­ture, which provides a robust set of features for web and mobile applica­tions. It is an open-source framework developed and maintained by the creators of Express.js, the most popular web framework for Node.js.

Speaking of which... there's a long-standing issue with express when it comes to async route handlers. There's backstory to this is complicated and controversial, but the tl;dr: is that (in my humble, and very controversial, opinion) you can use express-async-errors as a workaround hack for legacy projects, but if you're starting a new project you should avoid Express and switch to Koa instead.

Koa is a new web framework designed by the team behind Express, which aims to be a smaller, more expressive, and more robust foundation for web applications and APIs. By leveraging async functions, Koa allows you to ditch callbacks and greatly increase error-handling. Koa does not bundle any middleware within its core, and it provides an elegant suite of methods that make writing servers fast and enjoyable. site Koa - next-generation web framework for node.js *A Koa Request object is an abstraction on top of the node's vanilla request object, providing additional functionality that…*koajs.com

Vite leverages the browser’s native ESM to parse and compile your code as the browser requests it. Then it serves the source file using a plugin such as Koa (a lightweight Node.js web server) to create a dev server with support for Hot Module Replacement (HMR) for updating served modules and Rollup for production builds.

In today's article we are going to create a GraphQL api using the Koa framework together with the GraphQL Yoga library and Pothos. In addition, we will use Kysely, which is a query builder entirely written in TypeScript.

KoaJS