70 karma · joined March 13, 2011
It highlights missing rules/regulations
uses patched version of typescript. Using latest version of typescript is not reliable IME.
Bugs with npm scripts are really hard to notice, the terminal output is much more pretty, but imo has regressed.
Many npm scripts are not supported. You don't get a warning for which ones are ignored.
Simply viewing the output of your npm scripts is quite annoying, if you can figure it out.
Where yarn 1 "just worked" for my co-worker on windows (I'm on mac), yarn 2 did not "just work" - he got some security prompt (Yes, Corporate Sludge)
Our security scanner (blackduck) could not properly parse the newly formatted yarn.lock file, but, thankfully, I could create a work-aroung by telling yarn2 to use `yarn2.lock` instead... and just maintain 2 lock files. (Yes, more corporate Sludge)
Also, Svelte has a variety of issues with yarn2. In theory should be solved with yarn3.
I am hopeful for yarn3. May try again once it's been iterated on a bit. Maybe once yarn4 beta is out, yarn3 will be well worth trying again.
Biggest thing to me is the typescript situation. Yarn should be completely up-front about hacks like this. Yarn2 should immediately tell you to modify your package.json to point directly to the forked version of typescript when you first run yarn install, and in the migration guide.
zero installs is very neat, but, upload speeds are always slower than download speeds. Proper CI caching+not uploading truckloads to git will be the fastest+best strategy (as long as upload speeds are slower than download)
I do think yarn 2/3 has some way to specially cater to easily editing your npm packages.
Is it possible to download docker source from github.com, git checkout some version tag, build, and viola?
Furthermore, a project maintainer could put on his README, that, for a certain recurring donation, you get some level of direct personal contact.
For example: "No theft agreement" - employees/tenants/whoever shall not steal, etc etc etc
The 4th allowed value for html5 iframe sandbox is allow-top-navigation, which allows a script to do window.top.location.href = 'http://google.com and redirect someone like me.
Google is doing the same thing to Facebook with Google+.
Has anyone heard anything about any potential legal action Facebook might take?
Please contribute on Quora ;)
The next thing I plan on doing is taking the screenshot, and making is a auto-play as a screencast, just like path (http://path.com)
Basically, the whole page is viewable, you can interact with it, and it looks great too!