41–50 of 57 posts
Earlier quoted context omitted.
> 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.
So? If they are different types, it makes sense to have different extensions (e.g. if mts implies typescript module).
Or mpeg transport stream:
Earlier quoted context omitted.
Do you have a link so I can read about this?
https://www.theregister.co.uk/2017/08/24/nodejs_forks_ayo_co...
That's it? I'm happy. The toxic SJWs are out. Sounds good for the project as a whole.
Earlier quoted context omitted.
So? If they are different types, it makes sense to have different extensions (e.g. if mts implies typescript module).
> mts implies typescript module Or mpeg transport stream: https://en.m.wikipedia.org/wiki/MPEG_transport_stream
.mts is unheard of.
switching between nodejs and laravel multiple times already, now I need try nodejs again.
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.
Earlier quoted context omitted.
> mts implies typescript module Or mpeg transport stream: https://en.m.wikipedia.org/wiki/MPEG_transport_stream
They usually use .ts extension, or .tsv, .tsa according to the wiki article you just linked. .mts is unheard of.
Earlier quoted context omitted.
> mts implies typescript module Or mpeg transport stream: https://en.m.wikipedia.org/wiki/MPEG_transport_stream
They usually use .ts extension, or .tsv, .tsa according to the wiki article you just linked. .mts is unheard of.
Earlier quoted context omitted.
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.
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.
Earlier quoted context omitted.
> 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.
> 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.
> 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…
> 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.
Changing from js to ts is an inconvenience sufficiently big enough to adopt flowtype instead.
Earlier quoted context omitted.
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.
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.
fs.createReadStream('file.txt').pipe(fs.createWriteStream('new-file.txt'))
Streams are too slow you say?
fs.writeFileSync('new-file.txt', fs.readFileSync('file.txt'))
I've never had a problem with no explicit copy, but I am very happy it has been added...