4 ms·
> many are lacking in quality for so simple stuff what you take for granted in the .net world that choosing the right one slows us down Do you have some exampl
by olalonde 10y ago
> many are lacking in quality for so simple stuff what you take for granted in the .net world that choosing the right one slows us down
Do you have some examples? I was under the impression that the JavaScript/Node.js ecosystem was bigger, but maybe that's the HN bubble.
- kodfodrasz 10y agoThe ecosystem is big. Too big, you spend almost as much time trying to find the right tool as it takes to do it from ground up. My example: I needed to work with dates. Under .Net the DateTime and TimeSpan types do this pretty well, and under Java 8 it is also well solved. Under JavaScript this is not so clean. I found the moments library to work well, but had some tries before. With one when I tried the example code from the homepage I received Nan/NaN/NaN NaN:NaN:NaN as a string representation for a valid date :D This is a thing which is "trivial" (you expect it to be there, and be solved) and you expect it to just work if not socialized in the JS world. Surely I'll encounter other such things, even as we use JS only for integration tests. Also the Java/.Net ecosystem is also big, but does not completely overlap with the JS world, and stuff doesn't get reimplemented so often. (JS attiute in the HN bubble: This library had no release and no tweets in 2 weeks. The project is dead! have to rewrite from ground up!)
- pjmlp 10y agoI keep focused on Java/.NET world (occasionally C++), only using JavaScript on the browser. Being bigger doesn't mean better quality, in tooling, performance or libraries. I had a laugh at a Code:dive lighting talk about the amount libraries in npm to create a directory!