iosguyryan

The Rivian R2 makes Tesla’s look old and Android like. It’s very slick. The only thing I miss vs CarPlay is the voice Apple Maps uses, which is more natural.

The screen cut ins, typographic headlights, and crystal scroller wheels scream "teenager escaped room due to Bitcoin". BMW has many timeless designs to pull from in the last 30-40 years, but chose to pass the mature confident adult torch to the likes of Volvo and Rivian...

Accessibility > Vibration > Off

Removes a lot of purposefully rewarding/manipulating haptics. Makes a phone feel "quiet" and easier to put down.

Nicely conceived! This is the kind of feature Apple ought to have already delivered with on device models and private cloud compute.

Sending many whole screenshots to an indie mystery box, though, should be a non-starter for anyone without the skills to verify what any given update to this app is doing. Your website's featured use case highlights the risks (to you and users) unintentionally well: "How do I export my passwords?" (I did a double take: was this performance art from The Onion?) If a user opens a plain text file of secrets without closing this app/the help task, what gets captured, sent over the network, and saved to disk? What protections exist for, say, a computer-challenged elderly person's banking details?

A suggestion about the FAQ ...

"Where is my task history stored? Is it private? Your privacy is our top priority. Your task history is stored securely and encrypted on your local machine by default. You have full control over your data."

... This invites unanswered questions about what exactly from the screenshots is stored, for how long, and what design backs the "securely" claim. Being up front about this would invite trust and helpful developer feedback.

For an academic coffee paper, it is better than many.

A common sin remains: like most coffee papers, I was unable to find calibration procedures in the methods or supplementary sections for the espresso brewing instrument whose performance may vary between runs, days, or users. In this case, they claim/assume "The Opera allows for precise control of shot time, water pressure (PW), and temperature"). As a Decent owner, I'm less familiar with the Opera, but for either machine I would want to disprove any confounding variables by attaching independent sensors. Decent has openly discussed hurdles they've confronted for consistency and accurate measurement.

Their main takeaways, though, are interesting and track with how many now prefer to extract:

As we demonstrated in Figure 3, our model informs us that a reduction in dry coffee mass results in an increased EYmax (shown schematically in blue in Figure 6). Thus, a barista is able to achieve highly reproducible espresso with the same EY as the 20 g espresso by reducing the coffee mass to 15 g and counter-intuitively grinding much coarser (as shown in red, Figure 6B). This modification may result in very fast shots (<15 s), a reduction in espresso concentration, and a different flavor profile.

...

Beyond sensory science studies, a persistent difficulty is that there is no rapid route to assessing the quality of two identical EYs made with different grind settings or brew parameters. It is clear that espresso made at 22% EY in the partially clogged regime tastes more ‘‘complex’’ than a fast 22% EY obtained using the optimization routine presented in Figure 6. In an attempt to recover the same flavor profile as the partially clogged flow regime, a shot must contain a mixture of higher and lower extractions. Consider the tasty point in Figure 7: One can approximate its flavor pro- file by blending two shots: (1) a low extraction/high dose (purple point) and (2) a high extraction/low dose (green point). This procedure can more economically yield a shot with a flavor profile that should approximate that which was previously only obtainable in an economically inefficient partially clogged shot. Blending shots does double the total volume of the beverage, and the procedure comes with the added combinatorial complexity associated with calibrating two shots that, when mixed together, yield superior flavor. We expect only the most enthusiastic practi- tioners would consider this approach, but it may well be actionable in an industrial setting where extraction is carried out in bulk.

I often chuckle when (our) animations may have more complex math that consume more resources than the awaited logic/call that they gate.

Users will get used to ensuring a stable supply of said sponsored products, otherwise Optimus may get mad if said product was not in the fridge.

Apple rescued itself from bankruptcy with the iPod. When mobile phones began to gain storage for MP3s and internet access, Apple saw the writing on the wall for their cash cow. They pushed a multitouch acquisition from room-scale projection to another level for handheld devices, and then married that with its supply chain breakthroughs at the time. Now it sees the writing on the wall for iPhone and the relevancy of all the halo products and services once more ambient on-person computing becomes common.

A bike/stroller FLARM and auto manufacturers supporting it would be fantastic

Ingenuity's wobble from a color vs bw frame is a great example of solvable but surprising latency problems along the way.

“Coffee trade” is not monolith. There is commodity and specialty. The specialty side has been moving more toward just in time inventory for a while. It’s shocking how long the farm-to-processor(s)-to-distributors-to-roaster-to-brewer/consumer span can be and how many warehousing and exchange steps there are. Moving to just in time is quite disruptive for many business models; it’s not just this jump in price.

The amount of copium when it comes to China vs US is illogical. If you’ve ever done business in China, you know there are honest folk and there are officials who do backroom deals that flaunt or bend the law, particularly abroad. If there’s money to be had, it will be made. If there’s points to be scored on the latest edict, they will be scored. If it needs to be done, but the public can’t handle hearing about it for their own good, it shall be so.

Not hard at all.

Not to mention the footprint of making something new, disposing the old, and transport.

Huh? You have multiple marriage worthy relationships ongoing in other countries? Or you’re adopting fiancés from a shelter?

Do you turn the HRV off during a wildfire to stop smoke intrusion from destroying the house?

Is parking free?

Make it local and slow.

This is the way

Easily more elsewhere with less BS

June may be too late in the year, but some credits have an income cap.

Happened to me. Ranked near highest in company, promoted, pay bump two months before a layoff targeting US staff. They kept engineers in Australia who made 50-60% less. Before severance ran out, I landed a job that paid 50% more than before. Layoffs don’t indicate that much about the people laid off; they say a lot more about management.

Huh? Debt. Paid to another entity that was not the house seller. Walk me through the logic.

I usually read: you have so few users / care so little that I shouldn’t trust you because you’d have heard this complaint and fixed it. But in this case it was fixed up quickly. Which is great

Also. That said, autocomplete outside of Xcode is way more accurate. The latest beta predictive code is even worse than what we had… hallucinates APIs for the most vanilla of Foundation calls. Half my reflexive autocompletes now turn into — wtf I accepted this junk AI idea?

Leave the ecosystem. Microsoft and all Linux flavors have no bugs, including in all beta software.

Myopic take. Major tech companies adopted SwiftUI. Vision Pro is all SwiftUI and mixed declarative and imperative RealityKit.

To pile on: it’s in Scientific Reports. Not high impact, not highest quality. It’s a 9 day in lab study on mystery taste lab brew coffee (whose brewing was deemed so insignificant to a coffee study that its brew recipe was excluded from the methods section). These sort of setups are useful from a “help me isolate some test cases” point of view, but is obviously as much a perturbation in participants natural lives that it might even outweigh the impact of drinking coffee. Further, it draws conclusions from an acute 5 day caffeine exposure, whereas in real life these participants relationships and adaptations to caffeine are built over a long period of time. The power of the study is small and not scoped for conclusions, but rather pointing to an area of interest for further funding.

My god that’s such a moronic and sick quote. There are plenty of other companies where you can execute on that philosophy that aren’t consumed by assholism.

It is, until you're an adult and they want a tic-tac-toe rendition for a fintech. Ok, sure kid. A more serious fintech had a CoderPad that wouldn't compile a line of Swift; we laughed, switched to Xcode, and enjoyed our time together making actual software related to their SDK. The whole point is to understand how people think... so let them think with the tooling they think with.