devinrhode2

We will then have fraudulent whistle blowing lol

Similar. When my baby lets air out of his esophagus, he makes a stuttering sound. I've started throttling my burps with my mouth and it's more comfortable.

I'd say highlighting environmental issues doesn't make it a bad metric

It highlights missing rules/regulations

Is it possible to only show recommendations for my own store’s products?

Who do you see using this?

Solid js there

Yarn 2 problems:

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)

You have .yarn/cache full of .tar.gz files.

I do think yarn 2/3 has some way to specially cater to easily editing your npm packages.

Works on firefox mobile with my extensions

Does yarn2 recommend also using LFS? Do you see any performance improvements when using LFS?

I understand where the docker devs are coming from.

Is it possible to download docker source from github.com, git checkout some version tag, build, and viola?

Loaded for first time on my pixel 3. Loaded fine I guess, but too small to glean anything :( I then zoomed in and nothing happened, then I was zoomed way too far in, and the page twitched again to be zoomed in on a different section, and I bounced. But it seems really cool. I'm curious what it would be like with dart and or solidJS

This whole thread makes me think that we should give our kids open source games, built and run locally.

Gosh, that feels so inefficient (as a js dev here). Then again... React had it's naysayers for sometime because 1. JSX, 2. nobody saw dom diffing as truly fast enough. But dom diffing is absolutely faster than asking the server to update a classname.

This is a lot like gittip and BountySource.

Furthermore, a project maintainer could put on his README, that, for a certain recurring donation, you get some level of direct personal contact.

I think the legal world needs to create abstractions and simplifications similar to the programming world. There should be standard definitions, that are simply referenced, ideally these standard definitions are available online.

For example: "No theft agreement" - employees/tenants/whoever shall not steal, etc etc etc

like how Medium displays reading time?

Google spent this much time on trying to get dumb users to learn to search from the omnibox? I think there is a solid opportunity to target highly skilled users with high performance machines. You can use more shortcut keys for things, and you don't have slow down from casual/confused users

At first read, I thought your point about routing was really good - why not have route('about').template('aboutTemplate').controller('aboutController') - and then I realized this is all reapeating the same mumbo jumbo. This is all automatically matched up by the naming convention (which frustrates me too, but until I figure out a better way...)