NectarJS VS redwood

The first google result for "JS to binary" was this: https://github.com/NerdLang/nerd, you might try to give it a spin. However these kinds of solutions come with a lot of caveats as of how to handle stdio, memory, and many other things that other languages, such as C and Go, handle natively as part of their stdlib...

for anyone else interested in approaches to this here's another abandoned attempt to transpile js to c https://github.com/NectarJS/nectarjs

The question is just whether there's sufficient purpose and value for that. https://github.com/NectarJS/nectarjs

Rails/Ruby performance has improved:

https://medium.com/retention-science/ruby-is-still-a-diamond...

Alhough, compiling Javascript to binary makes code even faster https://nectar.js.org , although I wish that project would get more love with bugfixes https://github.com/NectarJS/nectarjs/issues

Technically speaking, this is bollocks. You can compile javascript to machine code for Windows, Mac, and Linux if you so choose, there is even a compiler for arduino, which quite obviously does not and cannot run a javascript interpreter. The point is that, in our modern world, there is no such thing as a scripting language. Virtually any language can be compiled to bytecode to run in the Java JVM, and many (even surprising ones like javascript) can be compiled AOT to native machine code.

Object pascal to JS? Why not just write JS directly? Can you leverage Lazarus? For JS to WASM, there's NectarJs https://github.com/NectarJS/nectarjs but docs appear to be nonexistent :(

Frameworks are a theme with this month's Release Radar, so here's another. Redwood is a full-stack, JavaScript/TypeScript web application, designed to scale with you. It uses React frontend for the frontend and links to a custom GraphQL API for the backend. The latest version includes a bunch of breaking changes such as moving to Node 20.0, the Redwood Studio, and highly requested GraphQL features such as Realtime, Fragments, and Trusted Documents, the server file, new router hooks, and heaps more. If you've previously used Redwood, you'll probably want to upgrade to version 7.0. The team have put together a handy migration guide for you to follow.

The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.

Although there are quite a few opinionated battery-included frameworks that have picked up everything for you like RedwoodJS, Blitz, and Create-T3-App, you still need to choose between them and hope that they will remain mainstream and well-maintained in the future. So how should we choose?

Web development frameworks in JavaScript, such as NextJS and RedwoodJS, have gained popularity among developers. Choosing the right framework, library, or tool for a project is crucial for efficient development. Developers often seek the best tools to save time and avoid reinventing the wheel.

The community here is pretty friendly. https://redwoodjs.com/

Next.js 13 ignited the first wave of attention to React Server Components (RSC) around the end of last year. Over time, other frameworks, like Remix and RedwoodJS, have also started to put RSC into their future road maps. However, the entire "moving computation to the server-side" direction of React/Next.js has been highly controversial from the very beginning.

I'm currently experimenting with the fantastic Redwood framework. However, while going through the excellent tutorial, I didn't find any guidance on using data validation libraries like Yup, Zod, Vest, etc. So, I had to do some investigation and came up with a solution. This article describes the implementation of validation with Zod in a fresh Redwood app. You can find the sources at this github repository.

RBAC is one of the most common authorization models - users are assigned different roles, and resource access privileges are controlled at the role level. Despite its limitations, RBAC is a popular choice for simple applications, and some frameworks (like RedwoodJS) have built-in support for it.

Check it out here: https://redwoodjs.com/