Re: Proposal for a New Hyper-Modern JavaScript Solid Server

ne 30. 3. 2025 v 13:33 odesílatel Joshua Cornejo <josh@marketdata.md>
napsal:

> Hi,
>
>
>
> Apologies as I went from the search results from the photo in Google as it
> matches others I’ve reviewed in the past.
>

No worries—thanks for clarifying and for providing these links. Rust
certainly has impressive performance benchmarks and is excellent for
enterprise-grade applications.

I'd actually love to see a Rust-based Solid server if there's an appetite
for it. I could even be persuaded on that front myself, though personally I
prefer JavaScript simply because it's the language of the web.


>
>
> Finding “JavaScript” performance comparisons is for the project to replace
> “client-side” JavaScript with Rust.
>
>
>
> My original question wasn’t related to the broad popularity of the
> programming language to be used, but the “enterprise” nature of the
> objective.
>
>
>
> Companies like Microsoft have been moving core enterprise services to Rust
> for at least 3 years now (
> https://www.techzine.eu/news/devops/116080/microsoft-continues-push-to-switch-code-over-to-rust/
> )
>
>
>
> This one compares Speed on a single task with Node.JS (35-ish times
> faster):
>
>
>
> https://forgen.tech/en/blog/post/why-i-switched-from-typescript-to-rust
>
>
>
> [image:
> /Users/joshuacornejo/Library/Containers/com.microsoft.Outlook/Data/tmp/WebArchiveCopyPasteTempFiles/image?url=%2F_next%2Fstatic%2Fmedia%2Fbenchmark.505588c2.webp&w=3840&q=75]
>
>
>
>
>
> This one is for Node.js on concurrent transaction latency:
>
>
>
>
> https://medium.com/deno-the-complete-reference/node-js-vs-rust-performance-comparison-for-hello-world-case-2b548fb77c8c
>
>
>
> [image:
> https://miro.medium.com/v2/resize:fit:1400/1*15qvZtr6g0Gzx9TZ488OJA.png]
>
>
>
> Regards,
>
>
>
> ___________________________________
>
> *Joshua Cornejo*
>
> *marketdata <https://www.marketdata.md/>*
>
> smart authorisation management for the AI-era
>
>
>
> *From: *Melvin Carvalho <melvincarvalho@gmail.com>
> *Date: *Sunday, 30 March 2025 at 12:01
> *To: *Joshua Cornejo <josh@marketdata.md>
> *Cc: *public-solid <public-solid@w3.org>
> *Subject: *Re: Proposal for a New Hyper-Modern JavaScript Solid Server
>
>
>
>
>
>
>
> ne 30. 3. 2025 v 12:55 odesílatel Joshua Cornejo <josh@marketdata.md>
> napsal:
>
> Hi Melvin,
>
>
>
> One of the many sites that evaluates programming performance:
>
>
>
>
> https://strapi.io/blog/rust-vs-other-programming-languages-what-sets-rust-apart
>
>
>
> Hi Joshua,
>
> Just a quick clarification: the chart you shared isn't showing relative
> speed or performance—it's actually a popularity ranking. It indicates
> JavaScript is roughly six times more popular among developers than Rust,
> which would rather be an argument in favor of JavaScript here.
>
> Best,
> Melvin
>
>
>
>
>
> And it is not just performance – it is type safety, memory safety, not
> interpreted, no garbage collection.
>
>
>
> Regards,
>
>
>
>
>
> ___________________________________
>
> *Joshua Cornejo*
>
> *marketdata <https://www.marketdata.md/>*
>
> smart authorisation management for the AI-era
>
>
>
> *From: *Melvin Carvalho <melvincarvalho@gmail.com>
> *Date: *Sunday, 30 March 2025 at 11:53
> *To: *Joshua Cornejo <josh@marketdata.md>
> *Cc: *public-solid <public-solid@w3.org>
> *Subject: *Re: Proposal for a New Hyper-Modern JavaScript Solid Server
>
>
>
>
>
>
>
> ne 30. 3. 2025 v 11:05 odesílatel Joshua Cornejo <josh@marketdata.md>
> napsal:
>
> Curious –
>
>
>
> Is there any reason for preferring JavaScript and not enterprise-grade
> languages like Rust / Go / C++ / C#?
>
>
>
> You will need 6x more servers (or be 6x slower like-to-like) compared to
> Rust or Go.
>
>
>
> [image: stackoverflow-rust-top-performing-languages.png]
>
>
>
> Where is this chart from?
>
>
>
>
>
>
>
> And (as an example) you could do Rust as the foundation and use
> https://boajs.dev to enable the JavaScript layer.
>
>
>
> Regards,
>
> ___________________________________
>
> *Joshua Cornejo*
>
> *marketdata <https://www.marketdata.md/>*
>
> smart authorisation management for the AI-era
>
>
>
> *From: *Melvin Carvalho <melvincarvalho@gmail.com>
> *Date: *Saturday, 29 March 2025 at 15:48
> *To: *public-solid <public-solid@w3.org>
> *Subject: *Proposal for a New Hyper-Modern JavaScript Solid Server
> *Resent-From: *<public-solid@w3.org>
> *Resent-Date: *Sat, 29 Mar 2025 15:48:02 +0000
>
>
>
> Dear CG,
>
> As we all know, Node Solid Server (NSS) was originally conceived over 10
> years ago and has been instrumental in pioneering the Solid ecosystem.
> However, given its age and the evolving needs of today's web, NSS is now
> becoming long in the tooth and is effectively reaching its end-of-life in
> terms of scalability and enterprise readiness.
>
> Currently, alternatives such as CSS and Pivot, while commendable, also
> fall short when it comes to efficiently supporting thousands or even
> millions of users.
>
> I am proposing a new, hyper-modern JavaScript Solid server that leverages
> the latest JavaScript tooling, minimalist architecture, and advanced
> performance optimization techniques. The goal is to achieve
> enterprise-grade scalability while strictly adhering to the Solid
> specification, passing all tests in the Solid test suite.
>
> Key design points:
>
>    - *Minimalistic architecture*: A lean, modular core that focuses
>    strictly on Solid specification compliance.
>    - *Modern JavaScript tooling*: Utilizing the latest frameworks and
>    runtime environments (e.g., native async/await, modern V8 optimizations,
>    optimized network I/O).
>    - *Performance-first approach*: Built from the ground up with
>    scalability and speed in mind, suitable for enterprise-grade applications
>    and high user volumes.
>    - *Pure JavaScript*: Targeted specifically for the JavaScript
>    ecosystem and developers who prefer a JavaScript-only environment.
>
> I'm reaching out to gauge interest in this project. If this aligns with
> your interests or you have ideas and feedback, please share your thoughts.
> I'd also welcome collaborators interested in defining requirements,
> contributing to design decisions, or helping build an initial prototype.
>
> Looking forward to your feedback and discussion!
>
> Best Wishes
>
> Melvin
>
>