I really wish people would stop writing what could be useful projects in #NodeJS.

@saper

1. I wish a horrible death upon Javascript
2. NodeJS creates RWX memory mappings
3. npm is crap. I only want to use my system package manager.

@lattera 3. is true. We have yarn now :)
2. That's a valid issue, is it V8 or libuv?
1. I am not a fan either, but at least I can program functionally in it.

I think that node is a great invention, not because of Javascript (with they picked up something else), but that little async + libuv thing is simply great (ofcourse #erlang guys would have said "I told you so long time ago).

@lattera but the real reason it will be growing in the future is that it took me less than 40 hours to build a working OAuth2 provider (meh) connected to some banking API - just had to glue existing small modules. The granularity level is getting almost right there.
@lattera Regarding (3) system package manager - those current managers build a per-app tree of dependencies, avoiding thus the #DLLhell when incompatible APIs are introduced. I don't think current pkg managers are ready for this (multiple versions of the "same" installed in different places). Would love a see a solution though ($LOCALBASE changing like crazy?)

@saper #FreeBSD's package manager now includes support for FLAVORS, which does just that. :)

This impacts Python directly as now you'll notice some Python projects have a py27- port and a py36- port (for example: py27-nyx and py36-nyx).

@lattera that's is not the same. You cannot patch ruby's or node's `require()` to magically look the same name somewhere else based on the system pkg manager imagination.
@saper Another reason for Node's death. ;)

@lattera no. I have used flavors (slots) in #Gentoo and this is a dead end. What bundler and composer are doing (local "vendor" directory) or node pkg managers (local "node_modules") is right.

This discussion will lose its significance as we will move to per-app filesystem layouts. Sadly https://github.com/3ofcoins/jetpack development stalled.

3ofcoins/jetpack

jetpack - **PROTOTYPE** FreeBSD Jail/ZFS based implementation of the Application Container Specification

@lattera (2) can you produce a backtrace (with -g) of node mapping RWX?
src/x64/code-stubs-x64.cc - v8/v8.git - Git at Google

@saper @lattera That's exactly it. Most JIT compilers use RWX mappings for performance reasons. Firefox has made a few strides in that area, but still has a bit of work to go.
@lattera @lattera so, the moon doesn't care, security researchers bark?