Live data from Hacker News

Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

github.com

51–60 of 71 posts

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#51

Earlier quoted context omitted.

When I write lambda code for my job, our code currently only supports the node 6 for it's runtime (our system automatically deploys it). I use nvm to help test my code all the time while still having the ability to switch to a more current node for other projects

Are you running your projects directly on your machine? Your’re not using a VM or containers? Don’t you have the “but it works on my machine” problem?

We never had that issue with node

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#52
post #32

Earlier quoted context omitted.

The ReasonML ecosystem is quite confusing for newcomers. ReasonML could be compiled to a binary out of the box thanks to the OCaml toolchain. Pesy is a tool for making native development easier. Regardings Javascript compilation backend, you only hear about that because it's what the ReasonML team selling.

And I get that, I think I heard somebody from Reason community to say on some podcast once "We want to get the frontend stuff right first", or something along those lines :-)

That makes more sense to me now why doing server side reason compiles to a node.js app and not a more performant OCaml app. Server is not a priority yet.

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#53
At this point, I use Docker for almost every project that I work on, and one of the reasons is that Docker allows me to create a separate environment for each project. I don't need to learn multiple version managers, and it works equally well for non-language tools, like Postgres and Redis.

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#54
post #14
post #9

Wait, I assumed this will be a js-app, but it actually is a executable binary? Is that the courtesy of https://github.com/jordwalke/pesy ? For some time I wanted to try ReasonML for server-side development, but for some reason I assumed, that most of the ecosystem would be node.js based.

Reason is merely a new syntax on OCaml. You can use BuckleScript (BS) to compile to JS, or not use BS to compile to native. There exists a fast http server in native OCaml: https://github.com/inhabitedtype/httpaf

[deleted]

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#55
post #32

Earlier quoted context omitted.

And I get that, I think I heard somebody from Reason community to say on some podcast once "We want to get the frontend stuff right first", or something along those lines :-)

That makes more sense to me now why doing server side reason compiles to a node.js app and not a more performant OCaml app. Server is not a priority yet.

Server side reason can already compile to native binaries (thanks to the OCaml compiler). While maybe smaller than the npm ecosystem there are a lot of high quality packages available on the OCaml ecosystem [1] that allow for a very pleasant server side development experience. For example https://github.com/rgrinberg/opium is a really nice high level toolkit. There are database bindings to Postgres, Mysql and the like, and high level interfaces to them like https://github.com/paurkedal/ocaml-caqti

[1] http://opam.ocaml.org/packages/

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#56
post #2

I use nvm currently. Can I ask how this compares to nvm, perhaps issues with nvm that it tackles? Is it performance? :o

this really does need a pitch comparison vs nvm. when I first saw yarn I switched almost instantly from npm because the pitch and improvement were clear

Is there still any reason to use yarn today?

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#57
post #3
post #2

I use nvm currently. Can I ask how this compares to nvm, perhaps issues with nvm that it tackles? Is it performance? :o

I second this question. I'm using nvm almost everywhere and have never had issues, nor did I ever experience it as slow.

I quit using nvm when it has become a pain to run it in non interactive situations such as from cron, from pm2 and from monit config. It needs changes on how it's launched all over and it was just not worth it.

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#58
post #48

Earlier quoted context omitted.

Sometimes you're limited in production by whatever version the OS supports. In the case of Debian installing nodejs doesn't necessarily land you the latest and greatest. The same happens with Python as well. I wish they had a good way to abstract this in Debian and I'm surprised Ubuntu hasn't fully resolved it, I mean Ubuntu does have Snap but I can't trust Snaps fully if the language vendors aren't backing the only…

You can absolutely install the newest version of Python and Node on Debian. It is a little harder than just an `apt-get install`, but very possible.

Of course you can install it. In many environments it's not considered maintainable to deviate from the distro provided and supported version. Especially when you have support contracts from your OS vendor.

If devs want something different from the distro provided libs we typically ask that they use containers or otherwise vendor them.

Ideally we would like our software to depend on the system for the bare minimum and security critical libs like OpenSSL so that Ops is free to switch out the underlying platform with minimal friction.

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#59

Maybe I'm completely out of the loop, but what's the deal with running multiple versions of Node? What particular problems or projects do you have where this is a pressing necessity? I just install latest LTS and keep that up to date, and I've yet to find a single thing not working.

I have a development server that has some projects mainly written by someone else and one of them specify an old version of nodejs as dependency which breaks by using latest LTS (and I'm too lazy to figure out how to make someone else's code to work on latest LTS) but I don't want to turn nodejs for the entire server to an old LTS.

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#60

Maybe I'm completely out of the loop, but what's the deal with running multiple versions of Node? What particular problems or projects do you have where this is a pressing necessity? I just install latest LTS and keep that up to date, and I've yet to find a single thing not working.

Sometimes you're limited in production by whatever version the OS supports. In the case of Debian installing nodejs doesn't necessarily land you the latest and greatest. The same happens with Python as well. I wish they had a good way to abstract this in Debian and I'm surprised Ubuntu hasn't fully resolved it, I mean Ubuntu does have Snap but I can't trust Snaps fully if the language vendors aren't backing the only…

Why don't you just install the official 'deb' package with the version of your choice?

https://github.com/nodesource/distributions/blob/master/READ...

Post reply on HN