• 6
    It's a runtime for the worst language written in the best language 😆
  • 1
    @bittersweet Maybe mixing the worst with the best will make something… average ?
    I don't know what to think about it
  • 0
    @CodeTalker nah the worst is even worse even though it is better at "secur"ity
  • 4
    @CodeTalker @melezorus34

    It's way better than Node.

    I personally prefer coding in Rust directly, but a modern Node replacement which has no need for NPM, is extremely resource efficient, uses Rust's Tokio library to do JS async, uses ES modules instead of CommonJS, and encourages the use of typescript & webassembly... that almost makes Javascript acceptable as a Backend language.
  • 2
    @bittersweet I better finish the TODOs on my benchmark project then 😂
  • 0
    @bittersweet @melezorus34 While I'm revisiting the project, you can grab the old iteration from tuppitak.atwebpages.com/scripts/Primehunter/PrimeHunter.js

    usage: given by @highlight

    BEWARE that I didn't care about optimization so it will take hella load of memory. (after 2,000,000 it will require at least 1G RAM so install x64 versions :P)
  • 0
  • 3
    @bittersweet how is npm bad? How is just importing the library through a link better? It feels like they did a fucking 180 back to the days you would just paste the jquery cdn after the body tag...
  • 2
    @REXTON Maybe that's not necessarily a bad thing.

    No centralized registry, download on compile. The Golang Module system is also one of the few things I really like about Go: Import from URL, you can use both v2 and v3 of a library in your app without conflicts.
  • 1
    @bittersweet yes, I can't wait for when the damn cdn goes down unexpectedly so that I have to go back and import a new one... Oh boy!
  • 0
    @REXTON It's not CDN based though, it's URL imports — it downloads the library and compiles it with your app.
  • 0
    @bittersweet what if there was no server to respond 304 to me? Will I still used cached/compiled version?
Add Comment