Out of curiosity, last year, I purchased some test strips to test my drinking water. The strips showed typical contaminates: arsenic, lead, copper etc. they all registered in the "acceptable range". In the test, there was a test strip for QUATs (https://en.wikipedia.org/wiki/Quaternary_ammonium_cation), which caught my attention. It wasn't something that I would have thought to test for, but my water tested positive. I was curious, so I started testing other local water sources including bottled water from various brands; to my surprise they all tested positive for QUATs. The only local water I could find that didn't contain QUATs was distilled.
I thought maybe it was just in my area, so I started taking the test strips with me when I traveled. In the last year, I've tested the drinking water in multiple states and countries, and only one source has tested negative for QUATs. It was the water from a drinking fountain in the San Francisco Airport, interesting enough.
My suspicion is that QUATs are often flushed down the drain, and the molecules must be too small to be filtered out in the water treatment process.
I haven't found much research on the impact of QUATs on the human body, but I can help but think our mitochondria would be susceptible to damage.
I switched to Apple Passwords and have been using the official Chrome extension for a few months. It's not as seamless as some of the password manager extensions, but has been working well enough.
Depends on the portfolio and strategy, but personally I think Intel is a Buy. They're burning money building new fabs with little indication that they can execute on their node or product roadmaps, but they've really took a chunk out of their cost-centre to the point where even during one of their worst quarters in the last 30+ years in terms of sales, they're still turning a profit. The Saphire Rapids Xeon is out finally out and making money after 3+ years of delays. The client products are the best they've looked in 15 years. They've got some big customers lined up for IFS. Considering the market was happy to price them at ~$64 just two years ago without all that information, makes me believe $33 is a poor market for where they're at. That's near enough their asset price.
> The problem is that you can’t use the 16” with an external display and the lid open without the fans spinning at full speed.
I had the same problem, when connected to a USB-C monitor I wanted to use the keyboard, but not the built in monitor. Even with the display backlight off the fan would still run. After a lot of searching I found that you can disable the built in monitor by:
- Booting into recovery mode
- Opening Terminal
- Entering `sudo nvram boot-args="niog=1"`
- Restarting
- Close the clamshell
- Plug in the external monitor
- Open the monitor
> "You pop it into a headset which has eye sensors on it, which enables the next iPhone to have a higher apparent frame rate and polygon count than a PC with a Nvidia 1080 card in it."
Interesting. Ive said that the touch bar was the first step in a new paradigm. Maybe the next step is connect your iPhone as the display. That would explain why Apple stopped investing in displays.
No. You can set the Touch Bar to show, by default, "App Controls with Control Strip", "Expanded Control Strip", or "App Controls". And you can change Fn so it shows "Expanded Control Strip" instead of the F-keys (e.g. if you never need F-keys). But you can't set the Touch Bar to default to F-keys and require Fn to do something else.
I suspect we will see the share desktop experience extend to other devices.
In an post release interview Jony Ive implied that the touch bar was the first step in a new paradigm.
Imagine the Photoshop toolbar being available on your iPad's touch screen, while you're editing a photo on your Mac. Or playing a video game while using your iPhone for controls.
I think good tactile feedback is fundamentally required as the first step. Touch, even with haptic feedback makes for a very poor experience compared to memorizing shortcuts that use real keys.
Then Apple should have waited until that type of integration was available. This is the first comment that has made me even the slightest bit excited for the touch bar interface paradigm. Controlling your system using your iPad/iPhone would be really cool and I think I would be on-board. As it is, this little touch bar thing on some MBP models is a big yawn.
Couldn't we take it one step farther and just use a switch statement? It seems like using pure JavaScript would be more idiomatic React. The URL pattern could be parsed in the data layer, and passed down as props. That way the components don't rely on global state, making them easier to test.
Thanks you are the only one talking about the new api style here, it seems very interesting. It is like the dual of the previous version where all routes were declared in the same place, here we dispatch the route fragments in the app.
It will simplify nested routes, but I hope it won't "infect" the app with routing concerns too much.
I've ranted before about react-router, maybe they should call it another name this time, I hope they will keep on maintaining the v3.0, the switching cost will probably be too much for my app.
One reason to go with components over a switch statement is so you can render a specific component on all '/about' pages along with an additional specific component on all '/about/team' pages. With a switch statement you can only match a specific branch.
You can still do nesting within a case, or add another case 'about-team': and add another {var} to your component. That's essentially what RR would do. React Router approach is probably a little cleaner, however.
It's more that you can get the information about the state of the browser or server's URL down deep into the component tree and then more easily act on it (with a few components, rather than a larger case statement).
It's basically idiomatic JS vs idiomatic React/JSX.
That's a fair point. Kind of like adding a redux @connect in a child component.
Edit: To the idiomatic point. The first thing that struct me when using React, was that instead of having to use a custom Component for a for loop I could just use someArray.map(). I see this as a similar situation.
This is actually a naive version of what I've been doing since I had to unwind a react/router/redux application once (I've since moved the components into an object and just reference it as component[value]).
While React-Router had a lot of great convenience features I found that it was surprisingly easy to roll my own redux-compatible version that fit my personal needs with a few lines of code and no additional dependencies.
Out of curiosity, last year, I purchased some test strips to test my drinking water. The strips showed typical contaminates: arsenic, lead, copper etc. they all registered in the "acceptable range". In the test, there was a test strip for QUATs (https://en.wikipedia.org/wiki/Quaternary_ammonium_cation), which caught my attention. It wasn't something that I would have thought to test for, but my water tested positive. I was curious, so I started testing other local water sources including bottled water from various brands; to my surprise they all tested positive for QUATs. The only local water I could find that didn't contain QUATs was distilled.
I thought maybe it was just in my area, so I started taking the test strips with me when I traveled. In the last year, I've tested the drinking water in multiple states and countries, and only one source has tested negative for QUATs. It was the water from a drinking fountain in the San Francisco Airport, interesting enough.
My suspicion is that QUATs are often flushed down the drain, and the molecules must be too small to be filtered out in the water treatment process.
I haven't found much research on the impact of QUATs on the human body, but I can help but think our mitochondria would be susceptible to damage.