setup.py VS deno

When I look at projects using the toml files exclusively without a setup.py in the project, I noticed something. No one is taking setup.py best practices and applying them where applicable to their toml files. What I mean by that is - take a look at navdeep-g's setup.py. I'm assuming `.toml` files can't import a `__version.py__` file and do other py things? What about something like,

Yesterday I was curious how the Requests library was doing something, which led me down a rabbit hole to navdeep-G's setup.py and I rewrote my setup.py to be one of the best setup.pyfiles I've ever written.. But I should have been revising my main module. I did need to rewrite my setup.py, but the point is - it should have been on a to do list and set aside as its own thing. But I just kind of found a rhythm and things were really clicking, so I went with it.

Here is a wonderful setup.py template I like to use: https://github.com/navdeep-G/setup.py. But to be fair, I have also switched to poetry in the last year.

* Popular libraries for various use cases (i.e. Django/Flask for web applications)

setup.py (for humans) - https://github.com/navdeep-G/setup.py

This is my favorite setup.py example.

When building a JavaScript backend, should you choose Bun, Node.js, or Deno? Let's break it down.

There’s no acknowledgment of Node.js trademark on Deno.com … and the landing page is largely about how much better Deno is over Node.js.

Of all places to put trademark acknowledgement, it’d be there - and it’s missing.

https://deno.com/

Deno is a modern runtime for JavaScript and TypeScript built by Ryan Dahl, the creator of Node.js. Since its 1.0 release in 2020, Deno has positioned itself as a secure-by-default runtime that addresses many of Node.js's design challenges. With built-in TypeScript support, a standard library, and no package.json or node_modules, Deno represents a fresh approach to server-side JavaScript development. The project has garnered significant attention with 103,000 GitHub stars and active development from both the core team and community.

Learn more about Deno.

Jsdom should work in deno, can you open a [github issue](https://github.com/denoland/deno/issues) with some details and a reproduction?

All of the simple cases I've tried seem to work fine, e.g:

```typescript

Perfect for Cloud and Infrastructure: Major tools like firecracker (AWS Lambda microVMs), deno, and vector.dev are all written in Rust. It's becoming the de facto language for next-gen DevOps, cloud infra, and edge computing.

I thought - YOLO, lets go deno! 🦖. I loved how it is an all in one tool with fmt, lint, test, and what not. I wanted that. Okay so I decided to use fresh over deno because its native to deno, right?

Lume[1] is also a static site generator for Deno JavaScript Engine [2]. Indeed it is impossible to find a 4-letter name that doesn't clash using the Latin alphabet and that sounds like a name.

[1] https://lume.land/

[2] https://deno.com/