#JublFood (CMP 3144) #BUY_Trade

Is it good time to order Pizza on weekdays....?

@flyingvikas129 @dtbhat

Trump on climate: I don't believe it. Trump on Khashoggi: I don't believe it. Trump on Russia: I don't believe it. Idiocy? A canny game? Doesn't really matter as much as the underlying intellectual autocracy. In this administration only one opinion matters.

It's an assault on facts and reason. It's an assault on good governance. It's an assault on the bureaucracies that are being discounted. It's an assault on science and history. But it is also an assault on one of the underpinnings of democracy.

We live in a system that is grounded on the idea of collaborative government. Leaders may have a final word but even then, there are typically checks and balances. Hopefully, in this case, such checks and balances may work. But they also are being tested.

The president's position that he is smarter than all the world's scientists, than the entire intelligence community, than experts who have studied any issue all their lives, is, of course, asinine. But his belief that government turns solely on his opinion, is monarchic.

Louis XIV reportedly said, "L'etat est moi." That he was the state. Trump asserting that he knows better than all, discounts all advice, that his brain is enough to chart the course for America alone, is essentially saying the same thing.

The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.

I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.

npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.

I had the most bizarre experience outside of a bar yesterday, which my partner very aptly described as "toxic mask-unlinity." (A Thread.)

I was standing outside, waiting for a lyft to get home, when two cis men came out of the bar to smoke cigarettes. They're discussing the masks that folks are wearing in California at the moment because of the very dangerous air pollution from the fires happening.

I happen to be wearing one of those masks, because I think lungs are important and I like breathing. I dunno. One of the men notices me standing there, and says, "Like this f*cker right here. What is this shit?"

He goes on a homophobic rant about me, the pansy with a mask, and what a Very Manly Man he is because he's not afraid to smoke a pack of cigarettes while California is on fire. He doesn't need a mask, because something-something-heterosexual-something.

And part of me is just... impressed by the fact that this dude thinks he's Owning The Gay Libs by not wearing a mask to protect his lungs from smoke and particles in the air that are literally DANGEROUS... while chain-smoking. Outside of a bar.

So it turns out that Google Chrome was making everything on my computer slow *even when it wasn’t running*, because it installs something called Keystone which is basically malware.

I made a website because this shouldn’t

Wired first reported on how bad Keystone was 11 years ago when they put it into Google Earth (they seem to put it in all their popular

The fact that Keystone hides itself in Activity Monitor is bizarre. (The only sign of it was excessive CPU usage of WindowServer which is a system process).

I don’t know if Google was doing something nefarious with Keystone, or a third party figured out how to (which Wired warned about). But either way, I’m not inclined to give Google-the-organization the benefit of the doubt (despite the many good people who work on Chrome)...

...since it's been a decade+ and this still hasn't been "fixed".

There is no reason for auto-update software to need to do what Chrome/Keystone was doing. It also has a long history of crashing Macs.