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.
The thing that I like about California is that it’s warmer than the rest of the country in the winter and cooler in the summer, generally expressed by the locals as “if the temperature is below 60 or above 80, everyone complains.”
There are no other states that have mostly Mediterranean hot/warm summer climates (Csa/Csb) - Oregon being the exception if you enjoy a colder/wetter Csb than what you find in the Bay Area:
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?
That's terrible advice. The flame will cause the tick to unlatch, but it can also cause it to vomit, giving you any pathogens it's carrying.
The correct way is to take tweezers, side on grasping the top and bottom of the head and pull gently straight up (perpendicularly from the surface of your skin). Be patient. Taking a few minutes to do it right is better than rushing; you have about 24 hours before any significant risk of infection. Make sure you identify the head first and grasp that, as sometimes the head is buried. If you grab the body, you'll just decapitate the tick by pulling.
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?
It's a joint W3C Technical Architecture Group and CSS Working Group initiative, you can find a lot of details in this post from the Opera developer blog [1].
Houdini is a task force that consists of people from Apple, Mozilla, Microsoft, Chrome, even IBM and Samsung. It’s by no means a Chrome-only thing or us being pushy.
Servo has an experimental implementation, but it’s the part of Servo that hasn’t been merged into FF. All participating browser vendors have given very positive signals about CSS Paint API.
Most certainly not. I know people at Mozilla who've been working on Houdini-related features for a while now (cf. https://wiki.mozilla.org/CSS/Houdini). Chrome is just the first to release here.
Assuming you're referring to the licensing part, it's probably because they've gotten a lot of public backlash for their previous licensing scheme that has caused some to avoid React altogether.
"One thing to pay attention to when preloading fonts is that you also have to set the crossorigin attribute even if the font is on the same domain: <link rel="preload" href="font.woff" as="font" crossorigin>"
