I don't think the critique is that "welfare is objectively preferable" to a high paying career, but rather that the effort:reward ratio isn't scalable to society at large (without some level of social cohesion, I guess).
Glad to see at least a few mentions of K2 here. IIUC, excess Vitamin D can increase calcification in arteries or something like that, and K2 helps avoid that. But I've also seen mentions of people needing to be wary of K2 if they have heart issues or take blood thinners. It's an exhausting cycle of wondering whether you're truly helping or harming yourself unless you really become an expert in all these subtle things. I stopped taking the Zinc/Magnesium/Vitamin D combo from Costco as a result since it has no K2. Curious if anyone has any safe/vetted Magnesium, Vitamin D, and K2 combo recommendations.
I don't know what the tipping point is, but it'd probably take more than one. I've commuted through backed up/stopped/solid red sections on a motorcycle where I just get to lane-split and cruise through, and it'd still stay red.
Most of the spam calls I get these days are just silence. I'll answer them occasionally and just listen, but even after 5-10 seconds no one says anything. Who benefits from that? I really don't get it.
Is anyone satisfied with their Fossil watch? I have a Fossil Q Explorist and it's so slow and laggy that I almost wonder if I got a lemon. It takes like 3 taps to click or swipe before anything registers. I'm pretty sure my original Moto 360 is faster. I only wear it because it looks decent and occasionally works. I really wanted to like it, but my experience has just been ... bad.
Manuals just make driving fun IMO. I've been trying to find a manual 2013 to 2016 Audi A4 for weeks/months now, and its dishearteningly difficult to find any without expanding my search to be nationwide.
If you use a CI system that deploys each build of your webapp, where it might be deployed at a random url (<domain>/build1/index.html vs. <domain>/build2/index.html), then you would make all the url's in your app relative urls, which are then basically prefixed by the base url specified in the document head once the actual requests get sent. You can then write a different base href onto the document for each build, and everything will magically work.
Also, if ever use relative urls for assets or requests, and you deploy to different URL's (or your deployed URL path's don't map 1:1 to your filesystem paths), it can come in handy.
Are you trying to incite the mob with this post? If you read the latest comments by the Webpack team, it seems pretty clear that "Webpack" is not squatting on parcel scopes on npm.
As much as I'd like to buy a house outside of California, I can't imagine living in cold weather constantly. I really need sunlight/warmth, and I can't help but feel like I would miss California's weather.
What's the use case for this? Is this for crypto sensitive code or password matching that is vulnerable to timing attacks and such? Or is this for avoiding things like Spectre in a more general sense?
For the uninformed, what's the proper way to remove a tick these days? When I was younger I heard advice to put a flame or extinguished match near the tick until it unlatches, but I've also heard that that's a bad idea because it causes them to emit some irritant into your body or something to that effect. What's the correct way?
I always find it interesting that Chrome is charging ahead full steam on experimental API's like this while most other browsers have given no intent to implement them yet.
Did Chrome come up with Houdini? Are they being brave or pushy here?