node.native icon indicating copy to clipboard operation
node.native copied to clipboard

this project still active? :(

Open nexflo opened this issue 10 years ago • 6 comments

nexflo avatar Nov 20 '14 13:11 nexflo

It's somewhat dormant. I started using it in a project, and was successfully compiling and running a program based on node.native. I then moved off that project and haven't needed it in anything else. SSL support was going to be an issue in that project, and I was thinking I'd have to code that into node.native. I think the fact that SSL support is missing is probably a big impediment to anyone making serious use of this code unless they want to implement SSL themselves.

sebjameswml avatar Nov 21 '14 15:11 sebjameswml

This project deserves life! I'm mad I didn't discover it a year ago.

lordnynex avatar Feb 11 '15 22:02 lordnynex

This project is not in active development to be honest. There are several technical challenges that need to addressed or clarified. See https://github.com/d5/node.native/issues/26 for prior discussion. Just to name a few: library/dependency management, memory management challenges (even smart pointers can break or leak very easily in async patterns), API resemblance, and so on. While the very first idea was to bring the concept of async event-loop (libuv in this case) into C++ 11, there were lots of troubles with having node in the project names. Maybe we can clarify the scope (goals) of the project again. Maybe we can focus on HTTP routing to begin with.

Btw, @sebjameswml: HTTPS support is definitely important, but in practice, I normally end up doing reverse proxing and having SSL termination in outer level (like load balancer or even things like CloudFlare).

d5 avatar Feb 11 '15 23:02 d5

How about bootstrapping it on frameworks such as SeaStar ?

Win-Win for both projects, IMO

KrishnaPG avatar Jun 09 '16 15:06 KrishnaPG

I developed uvw as a C++ wrapper for libuv with a node.js-like interface. More or less the same principles that were behind node.native when started. Since a while ago I'm planning to add http(s) support and a few other things to the library. I would take the best out of node.native, or at least what is missed in uvw (someone said http parser?) and try once more to create a C++ library that resembles somehow node.js in terms of functionalities. Of course, with a different API, more C++-ish and with no JS engine anywhere. For this project seems to be abandoned, if anyone is interested I'd be glad to collaborate on the topic.

skypjack avatar May 12 '17 17:05 skypjack

Hi @skypjack thanks for your comment. I don't have need for code like this at the moment, so can't help or collaborate. Nice to know about uvw though.

sebjameswml avatar May 16 '17 15:05 sebjameswml