- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Sun, 30 Mar 2025 13:23:22 +0200
- To: John Erickson <olyerickson@gmail.com>
- Cc: public-solid <public-solid@w3.org>
- Message-ID: <CAKaEYhJ37HpTq+OxwQgxV7vb-rikJyxQ9XfN=0w4ikZB5=5_6Q@mail.gmail.com>
ne 30. 3. 2025 v 13:04 odesílatel John Erickson <olyerickson@gmail.com> napsal: > RE the assertion, "...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," where is the > evidence? Has NSS had anywhere near the levels of adoption to declare it > isn't scalable? > Modern JavaScript frameworks and runtimes are considerably faster. I'm unsure anyone who has run NSS feels it can scale massively, simply because that wasn't a design goal from the start—NSS was always intended to be refactored, but that never happened. If you have benchmarks demonstrating that NSS can scale significantly, I'd certainly be interested! > > John > > On Sun, Mar 30, 2025 at 6:57 AM Joshua Cornejo <josh@marketdata.md> wrote: > >> Hi Melvin, >> >> >> >> One of the many sites that evaluates programming performance: >> >> >> >> >> https://strapi.io/blog/rust-vs-other-programming-languages-what-sets-rust-apart >> >> >> >> 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 >> >> > > -- > Have a GREAT one! > > John S. Erickson, Ph.D. > Director of Operations, The Rensselaer IDEA > Deputy Director, Web Science Research Center (RPI) > <http://idea.rpi.edu/> <o <erickj4@rpi.edu>lyerickson@gmail.com> > Twitter & Skype: olyerickson > Fediverse: @olyerickson@fosstodon.org > *Not sent from my iPhone...because I don't own one!* >
Attachments
- image/png attachment: image001.png
Received on Sunday, 30 March 2025 11:23:39 UTC