7 ms·

Node v8.5.0

195 points by bpierre 9y ago

pitaj 9y ago
> add fs.copyFile and fs.copyFileSync which allows for more efficient copying of files. FINALLY. I don;t know how long we could have come with this still being a thing you need a module for, or you have to code yourself. Hopefully we get `fs.mkdirp` and `fs.remrf` somewhere down the line. > Add support for ESM. This is currently behind the `--experimental-modules` flag and requires the `.mjs` extension. I don't like the `.mjs` extension, but I understand the need for it, and I'm just glad that modules are finally here.
- sintaxi 9y ago
  I like .mjs because this is a good example of exactly what file extensions are meant for.
- blitmap 9y ago
  I probably don't understand what I'm looking at. I would like sendFile/sendFileSync - which would abstract over TransferFile on Windows.
  - avaer 9y ago
    The reason you're unlikely to see that in the node binary is presumably the same reason copyFile has taken so long: node aims to have a small core that enables a rich userspace. There's gotta be a very good reason to bog down the core with more stuff, since that equals less other stuff and more bugs. Some of the few valid reasons are ubiquity (which HTTP is, but Windows and sending files are not), or things that were impossible before (like no overhead file copy).
    - coldtea 9y ago
      >node aims to have a small core that enables a rich userspace So, dogma? Because copying a file fits right in any kind of "small core" -- and helps create a more dependable and usable "rich userspace" which doesn't need to reinvent the wheel 200 times for basic stuff.
- spankalee 9y ago
  The problem isn't the .mjs extension, but the unfortunate ability to import CommonJS modules, when that can already be done via require(). Dependency edges out of module land should be explicit, because those aren't going to work on the web, and the web matters more than node.
  - styfle 9y ago
    I asked about the import syntax[0] and got an answer on GitHub. [0]: https://github.com/nodejs/node/pull/14369#issuecomment-329034997 https://github.com/nodejs/node/pull/14369#issuecomment-32903...
  - likeclockwork 9y ago
    I think this decision is also short-sighted since ES Modules are now JS and CommonJS should be phased out over time, but now CommonJS is the default and holds the .js extension just complicating everything for short-term ease of use. They should have left requiring for CJS modules and let things be crappy for a while as requires and CJS are phased out. Eventually only ESM would remain except for in some abandoned packages, which could still be required. But now CJS is going to live forever because it's the default and ESM is opt in.
- Johnny_Brahms 9y ago
  Wiuldnt implementing those be trivial? They are hardly going to be "too slow" like file copy might be, and with the JS love of small packages this should already be a solved problem.
  - jaredklewis 9y ago
    There most certainly are already packages that do this, as well as countless projects with a util.js file implementing a hodgepodge of such functions that are standards in many languages. But as a programmer I would say my biggest complaint against JS is the miserably small standard library. Thus every project has its own set of dependencies that have their own APIs. Two projects from different JS ecosystems are as different as projects in different languages altogether. There are trade offs to be sure, but I prefer the languages (and in this case platforms) that have batteries included.
    - amelius 9y ago
      > Thus every project has its own set of dependencies that have their own APIs. Yes, this means that if your project depends on ten other projects, and all ten projects implement their own copy-file routine, your project will end up with ten copy-file routines.
  - thom_nic 9y ago
    As Larry Wall said, "Easy things should be easy." When working on a project and you need to copy something for the first time, you shouldn't have to do: * Ok I need to copy... What npm package does that again? * search NPM for copy * figure out which package is "best" * npm i some-copy-package * require("some-copy-packge") * do thing The first 4 steps should be unnecessary.
    - wruza 9y ago
      I'll buy it if you remove just third step.
    - tkone 9y ago
- coldtea 9y ago
  >I don't like the `.mjs` extension, but I understand the need for it, and I'm just glad that modules are finally here. I read that a lot. Why do people don't like the new extensions? Seems like the most elegant and programmatically more performant and less hassle free, solution to the issue. Everything else looks like a terrible kludge.
  - _pmf_ 9y ago
    > I read that a lot. Why do people don't like the new extensions? Probably because you'll end up with .mts, .mjsx, .mts, .mtsx.
    - coldtea 9y ago
      So? If they are different types, it makes sense to have different extensions (e.g. if mts implies typescript module).
      - josteink 9y ago
        > mts implies typescript module Or mpeg transport stream: https://en.m.wikipedia.org/wiki/MPEG_transport_stream https://en.m.wikipedia.org/wiki/MPEG_transport_stream
        kdkdkdk333ke 9y ago
        They usually use .ts extension, or .tsv, .tsa according to the wiki article you just linked. .mts is unheard of.
        josteink 9y ago
        Ive seen it in the wild. May not be that common though.
        CptMauli 9y ago
        my camera (Lumix GH2) produces MTS files
maxpert 9y ago
Everyone busy with iPhone X bad day for such important post
- ZenoArrow 9y ago
  I think you could find plenty of people who couldn't care less about the iPhone X (you're speaking with one of them). I took one quick look, saw nothing of major interest, and moved on with my day. Moving back to the linked story, are there any long running issues with Node that are still not yet addressed? Are nearly all common issues resolved?
  - avaer 9y ago
    Which long running issues? All common issues are quickly resolved, almost by definition, in a long-running successful project like node. Lots of people depend on that being the case. It's just not always resolved in core (which is why npm/yarn/webpack and a hundred other awesome derived works exist).
    - coldtea 9y ago
      >All common issues are quickly resolved, almost by definition, in a long-running successful project like node. Lots of people depend on that being the case. Not sure about Node, but regarding other "long running successful projects" you'd be surprised.
- bdcravens 9y ago
  Not sure what that even means. I watched the keynote, decided I'll probably buy it when it comes out, had a few minutes of banter here on HN, and that was it. Then back to real life for the other 22.5 hours of today. :-)
argentenergy 9y ago
Does enable async stack traces mean useful stack traces? Node has been a frustrating language to switch to from C# from the perspective of stack traces. It seems in node they devolve into relative meaninglessness beyond the first line or two. I have fond memories of juicy stack traces like homing beacons. I'm secretly hoping somebody will jump in to tell me I'm just reading them wrong or something...
- deleted 9y ago
  [deleted]
- jadbox 9y ago
  Yes, this update will make async stack traces appear within its called context... allows for much better debugging. https://medium.com/the-node-js-collection/node-js-8-big-improvements-for-the-debugging-and-native-module-ecosystem-58454861f2fc https://medium.com/the-node-js-collection/node-js-8-big-impr...
ausjke 9y ago
switching between nodejs and laravel multiple times already, now I need try nodejs again.
- mattferderer 9y ago
  What are you looking for that you're not finding? Laravel borrows a lot from Ruby on Rails, so maybe that might be more your cup of tea. A lot of Rails developers are trying Elixir & Phoenix which is an awesome functional programming setup. PHP has also been trying to become more like C# it seems. So maybe .Net Core & C# are worth a try? If you go the C# route, I suggest using Visual Studio (the full IDE) as I find most of my joy typing C# comes from the IDE. Whereas a language like Elixir the joy is the language itself.
ssijak 9y ago
Any updates about the Node leadership disaster news from the 10 days ago? That left a bad taste in my mouth about node.
- deleted 9y ago
  [deleted]
- pgsandstrom 9y ago
  Do you have a link so I can read about this?
  - davman 9y ago
    https://www.theregister.co.uk/2017/08/24/nodejs_forks_ayo_code_of_conduct/ https://www.theregister.co.uk/2017/08/24/nodejs_forks_ayo_co...
    - gkya 9y ago
      tl;dr > On Tuesday, the thirteen-member steering committee came together to vote on whether to remove Rod Vagg, a TSC member and Node.js contributor, over his controversial statements on Twitter and GitHub that prompted complaints. They also voted on whether to ask Vagg to resign.
      - staticelf 9y ago
        I am always curious about what the statement was. When it comes to SJWs they usually do not want to display that because it is often such silly things.
        gkya 9y ago
        IDK what they were but I find it irritating that having unpopular ideas can get you in trouble like this. His views are probably opposite of my ones, but still, I cant stand the hypocrisy in these situations and how easily these supposedly smart people are successfully pushed to go witch-hunting.
throwme211345 9y ago
gigo

195 points by bpierre 9y ago

> add fs.copyFile and fs.copyFileSync which allows for more efficient copying of files. FINALLY. I don;t know how long we could have come with this still being a thing you need a module for, or you have to code yourself. Hopefully we get `fs.mkdirp` and `fs.remrf` somewhere down the line. > Add support for ESM. This is currently behind the `--experimental-modules` flag and requires the `.mjs` extension. I don't like the `.mjs` extension, but I understand the need for it, and I'm just glad that modules are finally here.

sintaxi 9y ago
I like .mjs because this is a good example of exactly what file extensions are meant for.
blitmap 9y ago
I probably don't understand what I'm looking at. I would like sendFile/sendFileSync - which would abstract over TransferFile on Windows.
- avaer 9y ago
  The reason you're unlikely to see that in the node binary is presumably the same reason copyFile has taken so long: node aims to have a small core that enables a rich userspace. There's gotta be a very good reason to bog down the core with more stuff, since that equals less other stuff and more bugs. Some of the few valid reasons are ubiquity (which HTTP is, but Windows and sending files are not), or things that were impossible before (like no overhead file copy).
  - coldtea 9y ago
    >node aims to have a small core that enables a rich userspace So, dogma? Because copying a file fits right in any kind of "small core" -- and helps create a more dependable and usable "rich userspace" which doesn't need to reinvent the wheel 200 times for basic stuff.
spankalee 9y ago
The problem isn't the .mjs extension, but the unfortunate ability to import CommonJS modules, when that can already be done via require(). Dependency edges out of module land should be explicit, because those aren't going to work on the web, and the web matters more than node.
- styfle 9y ago
  I asked about the import syntax[0] and got an answer on GitHub. [0]: https://github.com/nodejs/node/pull/14369#issuecomment-329034997 https://github.com/nodejs/node/pull/14369#issuecomment-32903...
- likeclockwork 9y ago
  I think this decision is also short-sighted since ES Modules are now JS and CommonJS should be phased out over time, but now CommonJS is the default and holds the .js extension just complicating everything for short-term ease of use. They should have left requiring for CJS modules and let things be crappy for a while as requires and CJS are phased out. Eventually only ESM would remain except for in some abandoned packages, which could still be required. But now CJS is going to live forever because it's the default and ESM is opt in.
Johnny_Brahms 9y ago
Wiuldnt implementing those be trivial? They are hardly going to be "too slow" like file copy might be, and with the JS love of small packages this should already be a solved problem.
- jaredklewis 9y ago
  There most certainly are already packages that do this, as well as countless projects with a util.js file implementing a hodgepodge of such functions that are standards in many languages. But as a programmer I would say my biggest complaint against JS is the miserably small standard library. Thus every project has its own set of dependencies that have their own APIs. Two projects from different JS ecosystems are as different as projects in different languages altogether. There are trade offs to be sure, but I prefer the languages (and in this case platforms) that have batteries included.
  - amelius 9y ago
    > Thus every project has its own set of dependencies that have their own APIs. Yes, this means that if your project depends on ten other projects, and all ten projects implement their own copy-file routine, your project will end up with ten copy-file routines.
- thom_nic 9y ago
  As Larry Wall said, "Easy things should be easy." When working on a project and you need to copy something for the first time, you shouldn't have to do: * Ok I need to copy... What npm package does that again? * search NPM for copy * figure out which package is "best" * npm i some-copy-package * require("some-copy-packge") * do thing The first 4 steps should be unnecessary.
  - wruza 9y ago
    I'll buy it if you remove just third step.
  - tkone 9y ago
coldtea 9y ago
>I don't like the `.mjs` extension, but I understand the need for it, and I'm just glad that modules are finally here. I read that a lot. Why do people don't like the new extensions? Seems like the most elegant and programmatically more performant and less hassle free, solution to the issue. Everything else looks like a terrible kludge.
- _pmf_ 9y ago
  > I read that a lot. Why do people don't like the new extensions? Probably because you'll end up with .mts, .mjsx, .mts, .mtsx.
  - coldtea 9y ago
    So? If they are different types, it makes sense to have different extensions (e.g. if mts implies typescript module).
    - josteink 9y ago
      > mts implies typescript module Or mpeg transport stream: https://en.m.wikipedia.org/wiki/MPEG_transport_stream https://en.m.wikipedia.org/wiki/MPEG_transport_stream
      - kdkdkdk333ke 9y ago
        They usually use .ts extension, or .tsv, .tsa according to the wiki article you just linked. .mts is unheard of.
        josteink 9y ago
        Ive seen it in the wild. May not be that common though.
        CptMauli 9y ago
        my camera (Lumix GH2) produces MTS files

maxpert 9y ago

Everyone busy with iPhone X bad day for such important post

ZenoArrow 9y ago
I think you could find plenty of people who couldn't care less about the iPhone X (you're speaking with one of them). I took one quick look, saw nothing of major interest, and moved on with my day. Moving back to the linked story, are there any long running issues with Node that are still not yet addressed? Are nearly all common issues resolved?
- avaer 9y ago
  Which long running issues? All common issues are quickly resolved, almost by definition, in a long-running successful project like node. Lots of people depend on that being the case. It's just not always resolved in core (which is why npm/yarn/webpack and a hundred other awesome derived works exist).
  - coldtea 9y ago
    >All common issues are quickly resolved, almost by definition, in a long-running successful project like node. Lots of people depend on that being the case. Not sure about Node, but regarding other "long running successful projects" you'd be surprised.
bdcravens 9y ago
Not sure what that even means. I watched the keynote, decided I'll probably buy it when it comes out, had a few minutes of banter here on HN, and that was it. Then back to real life for the other 22.5 hours of today. :-)

argentenergy 9y ago

Does enable async stack traces mean useful stack traces? Node has been a frustrating language to switch to from C# from the perspective of stack traces. It seems in node they devolve into relative meaninglessness beyond the first line or two. I have fond memories of juicy stack traces like homing beacons. I'm secretly hoping somebody will jump in to tell me I'm just reading them wrong or something...

deleted 9y ago
[deleted]
jadbox 9y ago
Yes, this update will make async stack traces appear within its called context... allows for much better debugging. https://medium.com/the-node-js-collection/node-js-8-big-improvements-for-the-debugging-and-native-module-ecosystem-58454861f2fc https://medium.com/the-node-js-collection/node-js-8-big-impr...

ausjke 9y ago

switching between nodejs and laravel multiple times already, now I need try nodejs again.

mattferderer 9y ago
What are you looking for that you're not finding? Laravel borrows a lot from Ruby on Rails, so maybe that might be more your cup of tea. A lot of Rails developers are trying Elixir & Phoenix which is an awesome functional programming setup. PHP has also been trying to become more like C# it seems. So maybe .Net Core & C# are worth a try? If you go the C# route, I suggest using Visual Studio (the full IDE) as I find most of my joy typing C# comes from the IDE. Whereas a language like Elixir the joy is the language itself.

ssijak 9y ago

Any updates about the Node leadership disaster news from the 10 days ago? That left a bad taste in my mouth about node.

deleted 9y ago
[deleted]
pgsandstrom 9y ago
Do you have a link so I can read about this?
- davman 9y ago
  https://www.theregister.co.uk/2017/08/24/nodejs_forks_ayo_code_of_conduct/ https://www.theregister.co.uk/2017/08/24/nodejs_forks_ayo_co...
  - gkya 9y ago
    tl;dr > On Tuesday, the thirteen-member steering committee came together to vote on whether to remove Rod Vagg, a TSC member and Node.js contributor, over his controversial statements on Twitter and GitHub that prompted complaints. They also voted on whether to ask Vagg to resign.
    - staticelf 9y ago
      I am always curious about what the statement was. When it comes to SJWs they usually do not want to display that because it is often such silly things.
      - gkya 9y ago
        IDK what they were but I find it irritating that having unpopular ideas can get you in trouble like this. His views are probably opposite of my ones, but still, I cant stand the hypocrisy in these situations and how easily these supposedly smart people are successfully pushed to go witch-hunting.

throwme211345 9y ago

gigo