asnrk

If you'll accept the step of copying the values into the tool that figures out the complementary colors for you, macOS comes with Digital Color Meter, which will tell you the color of anything on your screen.

Square's guides and libraries in particular were a great place to start when last I worked on Android (2017). They filled in a lot of dumb gaps in basic, common functionality, and their guides and blog posts on Android topics generally left me feeling more confident in them than in Google's Android team. They were among the ones calling "the Emperor has no clothes!" over fragments, for instance, and they described and built alternatives.

It does look like they've abandoned a couple of their big view-related Java libs, which makes me wonder what they're using now. Seems they've switched to Kotlin for a lot of stuff.

Don't remember their blog being on Medium (ick) but it is now, looks like:

https://medium.com/square-corner-blog

Matching UI to designs was horrible on Android, at least as of ~1.5yrs ago. Even if designers were shooting for "Material". Plenty of rough edges. I wouldn't say 2x-3x longer for a typical project, though.

I could see there being issues with relatively new-to-Android developers not appreciating the degree to which advice from the official docs, especially relating to structuring applications, should be taken with a largish dose of salt, leading to slow-and-getting-slower development as an Android project went along.

I don't get why people name-drop Ricardo as the final authority on why free trade, in practice, is definitely in everyone's best interest. Ricardo's work was very narrow and didn't have much to say about the distribution of gains from free trade even under the conditions in which his work held.

The most useful ones are already free. So, probably none that I don't already. Development resources (free, hosted by companies with incentive to spread the info). Wikipedia. Rarely I still manage to stumble on some non-monetized hobbyist sites, despite their being hard to find under current search algos (infrequent updates, no attention to SEO, no padding things to look like "more unique content per page" to Google), and that's nice.

The rest I already pay for (Netflix, which just barely skates by being so cheap), are essentially utility things (bank sites, government), or are so low-value I'd probably be better off not using them, frankly. Or are simply piracy sites (library genesis / scihub), for that matter.

Any topic I scratch the surface of in online research I end up at excellent, totally free (not ad supported) resources or finding that I need to track down some books, or some combination of the two.

As someone who's always skipped breakfast more often than not, I too find calling that "fasting" kinda silly. I'd reserve that for going at least a whole day without food, before it deserves much consideration.

I rarely eat breakfast and often skip lunch. I find that when instead of doing that I focus on eating more meals but also driving up my vegetable and fruit intake to as high a % of my calories as I can stand, I feel healthier and have an easier time keeping weight in check.

Since most of the other OECD states are representative democracies of one sort or another, and since pretty much all of them have some form of universal health coverage, if the US system's an improvement over any of those in other OECD states, I expect there are strong, popular reform movements in at least some of them looking to move their system closer to that of the US. Right? Not to improve their systems in other ways, but specifically to move closer to that of the US. Since that'd be a clear improvement if they just "get real".

Yeah IDK if I'm just way worse at focusing on spoken words while doing other things than most people or what, but I can't get into podcasts or audio books at all. If I do other things while listening I miss so much that I have no idea what's going on, and even the supposedly very good ones are so dull that if I'm going to spend focused time consuming them I'd rather read, or watch something, or listen closely to some good music, or almost anything else.

I guess maybe if I got back into running they'd be good for that. Can't think of when else I could possibly use them.

It's not just Jira. Asana spins up the fans and causes UI hangs like crazy. The other day on my personal macbook my UI kept freezing for a few seconds at a time and... sure enough, I'd left a Trello tab open by accident.

For whatever reason, project management tools all perform like shit and grind my system to a standstill. PMs never seem to mind, which is why they keep being so awful I guess.

That the narrow result of a single vote is seen as sufficient justification to wildly swing a government's policy in a new direction with huge effects over decades is... baffling to me. Watching it happen is like seeing something announced by someone pretending to be a US President in a Saturday Night Live sketch and then, the next day, everyone treating it like a real thing that had happened and the whole state's policy shifting to reflect those statements, and no-one acting like that's extremely weird and insane.

I dunno. The market for something along these lines is probably as big as a substantial portion of the entire portable computer market was in, say, the late 90s. And it'd have basically no competition (at least at launch). Seems like it should be a viable product that could be brought to market at a non-insane price. Should.

Capitalism's weird. We end up with the most popular version of a thing being dirt cheap and common as air, and anything even slightly different or better being impossible to get or absurdly expensive.

Your statement and the one you're responding to are wholly compatible.

Experience at the agency I worked at until a couple months ago, which had continually followed this pattern with projects started after the yarn/npm split got serious:

1) Start or inherit a project using Yarn because that's what all the cool kids are using.

2) Develop for a while, everything's fine.

3) Lose a whole day when you eventually stumble on a Yarn bug or missing feature in Yarn.

4) Angrily switch the project to NPM, solving the problem immediately.

5) Continue developing as usual.

I think this happened on like half a dozen projects after the yarn/npm split occurred, and I saw it happen as recently as Fall 2018. Developers leaned trend-chasing there, but after being burned several times even the trend-chasier ones were tepid on yarn and tended to accept that if they started with it they'd probably end up switching before long.

FWIW I don't like npm much, but I still default to it so I don't, inevitably, hit the above situation at some point. Yarn doesn't provide enough benefits to make it worth having an even less-trustworthy tool in my build process than npm already is.

[EDIT] TL;DR: We all got sick of ending up on open GH issues for Yarn when trying to track down build and, worse still, run-time problems. So we started favoring NPM again as the lower (though far from zero) headache option.