Next steps? We are all stuck at "Go"! about just

[frank-dspeed]

@ramezrafla would you want to help me to embedded a new Component System that replaces WASI and WASM ? and makes Imports Obsolute i am working on that at a bigger scale directly in chromium and v8 as also nodeJS

Just JS is already the implementation that comes most near to that goal but first of all let me enlighten you about the documentation and the current state.

[ramezrafla]

Hello @frank-dspeed
Thank you for pinging me. I am struggling to see the value-add of that new system.

1. WASM is meant as a way to get native-like code into JS. Namely transpiled native C++. WASM has no garbage collector (GC) built-in and has better support for typed variables. Useful for AI (OpenCV) and gaming (e.g. Unity) ...

2. Just-JS is able to provide us with native-like speeds on our API servers instead of NodeJS / PHP. It does this by being opinionated, light, worker-focused (vs. threads which increases GC overhead). Most applications are IO-limited so JustJS optimizes the 30-50% which are not IO. So in essence, any further optimization is going to hit diminishing returns (you invest more than you get back). At ~90% of native we are more than happy with its performance.

3. Any other improvements will relate to architecture (e.g. using Postgres which is the fastest open-source SQL DB at the moment, proper indexing, caching / redis etc) and improvements to V8. In other words we are hitting the theoretical limit at the moment. Just is even faster than some C++ framework.

[frank-dspeed]

@ramezrafla see:

• - #53
• - #54

[billywhizz]

hi @ramezrafla. i have got your DM and seen the above. apologies - am very busy with work right now but I will catch up with everything and get back to you over the weekend.

glad you were able to figure out the postgres issue - i think should be easy enough to add scram support - to date i just did what was required for techempower - there's quite a lot of functionality missing.

[ramezrafla]

Thanks for the detailed write up on the internal implementation of Just. Still going through the nitty gritty. I still don't see the benefits. We are at 90% of the best framework. We have a large code-base (porting from Node etc.). We already have integrations with critical elements (a few missing).

From a business or development perspective, not sure why another framework or addition is needed. Sorry. Maybe I don't see it.

[ramezrafla]

hi @ramezrafla. i have got your DM and seen the above. apologies - am very busy with work right now but I will catch up with everything and get back to you over the weekend.

Thanks so much @billywhizz
Looking forward! We are preparing what is needed to use in production. Would love to contribute as well.

glad you were able to figure out the postgres issue - i think should be easy enough to add scram support - to date i just did what was required for techempower - there's quite a lot of functionality missing.

The PG interface is very well-written. It's a great starting point for the community. We just need some guidance, will go a lot faster.

[lemanschik]

@ramezrafla i am trying to writing a book about the core principles and terminologies and all that so we can build up a community on the right fundamentals i identified many educational issues around the committee members of core infrastructure projects like nodejs and w3c cloudflare microsoft and so on.

would love to get input and even examples written in the easy simple terminologie distinguished.

so maybe create a issue about your pg experience and just: so that i can see what your problems where and how we can improve the communication with the world.

• https://github.com/lemanschik/simplicity-made-easy/blob/main/README.md