1,312 karma · joined June 23, 2014
But I do see ES6 modules in the wild, some of them I'm using with other languages. So I guess it's fine to leave it as-is. Or if you want to ensure maximum compatibility, use babel as I suggested but add the sources to .npmignore so they're not duplicated in the published packages.
Additionally, ES6 default exports don't mix well with commonJS, sometimes I have to add require('foo').default for no apparent reason.
> Also with npm scripts, local deps that expose executables are added to your PATH
I think it didn't work reliably on windows or cygwin or something. I just tried and it works everywhere. Good to know! The only gotcha is that ";" and "&&" must have spaces around.
Don't do this:
module.exports = IPFSDropzone
Do this (and change documentation accordingly) module.exports = {IPFSDropzone}
or to go full ES6 do this export {IPFSDropzone};
add the package babel-env and add this script to package.json: "scripts": {
"prepublish": "node node_modules/babel-cli/bin/babel *.js -d build/"
},
and change main to "build/index.js".Run "npm run prepublish" to test.
Edit: Now that I think of it, compiling with babel is probably unnecessary. But it doesn't hurt and can help old setups.
> That this nearly 50 year old crappy design choice has come to this astonishes me.
That makes me feel old. For me Unix was always invented 30-something years ago...
Specially interesting those from works made in the 1800s: Most of those would have been copyrighted under the current law if it applied at the time they made the movies!
Did you try any game like Lone Echo? It's so good it's the only game I broke my "not buying exclusives" rule with (I have a Vive). I paid for about 30-40 VR games in Steam, so it's not exactly a 3DO.
It's spelled Oculus, by the way.
Not really. The user only has to wait for the computation once, a few times at most, and it can easily take less time than typing the passwords.
> * Use long secrets (ie. not human-rememberable passwords)
That's very often not the case. Some people like me put truly random passwords on every service. But 99.9% don't.
Also, you can perfectly combine _both_ long keys and expensive hashes.
Pedantic note: JS iterates through UTF-16 2-byte code units. It's that way for compatibility reasons (used to be UCS-2), but it's the worst of both worlds: not as good as UTF-8 for ASCII, can't do operations in O(1) time like UTF-32.
How does that work? Isn't it being emulated on binary hardware?
How does that work? Trying to find information, it looks like it's designed for devices of the future that don't exist; so it's built on assumptions that may be plain wrong.
Have you calculated how much does that really cost? I'd say it's several orders of magnitude lower[0] than the consequence of other regulations that are the real cause there are no more ISPs.
[0] (response to a comment I made wrongly stating it doesn't cost a cent) https://news.ycombinator.com/item?id=15891156
Disney won't _die_ if their early characters become public domain. If they're hurt it will be very slowly, with enough time for jobs to shift.
And it's not clear that copyright is necessary for creativity. In some ways it can hindrance sometimes. See the case of the fashion industry https://www.ted.com/talks/johanna_blakley_lessons_from_fashi...
I guess people somehow think that only the lowest quality versions of public domain works will be popular, when the opposite is frequently the case. Like it happened, for example, with Disney versions of the Brothers Grimm fairy tales. Which is rather ironic: Disney created an empire in big part thanks to public domain.
Since it seems you can access github, you can install dependencies without touching npmjs, with one of these:
npm install git+ssh://git@github.com:<githubname>/<githubrepo.git[#<commit-ish>]
npm install git+ssh://git@github.com:<githubname>/<githubrepo.git>[#semver:^x.x]
npm install git+https://git@github.com/<githubname>/<githubrepo.git>
npm install git://github.com/<githubname>/<githubrepo.git>
npm install github:<githubname>/<githubrepo>[#<commit-ish>]
(add --save if your npm is old)Why would a country ban npmjs?
if(window.WebAssembly != null){
loadScript('script.wasm.js');
}else{
loadScript('script.asm.js');
}So NN is not a problem, just a temporary fix. And it doesn't limit competition (it costs nearly zero to comply). The problem are _other_ regulations. So why are some people so obsessed with removing NN?
It's more complex than that. And in any case Netflix gives CDN boxes to ISPs for free.