Hacker News Reader

I remember a bunch of problems have been discussed earlier [1] concerning node.js on Windows, such as file-system path length limits and broken symlinks and lack of modules actually tested on Windows.

That was almost a year ago, so how do the things stand now?

[1] https://news.ycombinator.com/item?id=7914566

View on HN

windows not being a priority won't change, because windows as a deployment target is pretty much a joke.

I mean... desktop environment on your application server ... lol?

There's so much friction legality and culture wise to getting a windows server to spin up, get developers to use good practices, encourage automation and resusability...

> windows not being a priority won't change, because windows as a deployment target is pretty much a joke.

I take it you haven't done .Net development? It's incredibly easy though Docker and similar tech wasn't developed for Windows so some of that has lagged behind.

> I mean... desktop environment on your application server ... lol?

This is a pretty old way of thinking; it's simply another way of managing your application server. This really isn't a big deal anymore.

Reply on news.ycombinator.com