I think the problem with touch bar was that, it completely replaced the function keys, instead of complementing them. Other than that, I actually liked it.
Hah, that reminds me! My first work issued Mac didn't have the ESC key, just the touch bar. IIRC a program hung in fullscreen, freezing both the app and the touch bar. So I had to reboot to get out of it because the esc key didn't work.
Its interesting the touch bar was also hung up, as from what I recall the touchbar was actually driven by a separate processor (the T1/T2 chip) and had its own version of watchOS running. I would have thought it would have continued working, just unable to continue syncing with the rest of the Mac.
Yeah, it locked up on me every couple months or so. Very glad to see it gone (as the primary ESC + F-row input).
I also would not mind it in addition to regular keys, there are some great interactions in there. But it's an extremely poor keyboard-emulator. Splitting off the escape key made a huge improvement, but it's nowhere near enough.
Yeah Apple has had a few missteps like this over the last 5 to 10 years. They assert themselves with that Steve Jobs mentality of “we know what’s best for you,” but he got it right more often than the current iteration. The touch bar was definitely not properly assessed by users before shipping.
Those 2019-2020 models are absolute trash. I don’t know what happened. My 2016 MBPro smokes the few we have bouncing around at work. They started falling apart like year 3, and my MBPro was the first iteration of their newer builds with the butterfly keyboard/non-optional Touch Bar!
You should have been able to Cmd-Tab to a different app; if that wasn't working, something more serious was going on. Also, if you have Spaces enabled, you can three-finger swipe, since a full screen app gets its own Space.
Another issue with the touch bar is that part of the laptop gets quite hot (especially on Intel CPUs), and so did the touch bar. I recall a few times feeling like I burned my finger just pressing esc during video rendering.
I think the lack of haptic feedback is what doomed the Touch Bar. If they'd been able to solve that problem, it could have been an acceptable replacement for the function keys.
and is it easier to implement id checks for each online account that people have, had, and will ever have in the future?
parents need to start parenting by taking responsibility on what their kids are doing, and government should start governing with regulations on ad tech, addictive social media platforms, instead of using easily hackable platforms for de anonymization, which in turn enable mass identity theft.
Hannibal was basically in a hostile land, without proper logistics support. There was no way that he can stay still and lay siege, only way he was able to survive so far was his ability to stay mobile and live off the land.
In case of siege, the Romans would not need to fight, they could simply wait until his army slowly died from attrition.
Can't emphasise that enough. Especially if you're into black clothing and have a black bike.
"This showed that for cars DRL reduces the number of daytime injury crashes by 3-12%. The effect on fatal crashes can be estimated as somewhat greater (-15%)."
It seems like a very similar issue arises with the "natural language query" problem for database systems. My best guess at a solution in that domain is to restrict the interface. Allow the LLM to generate whatever SQL it wants, but parse that SQL with a restricted grammar that only allows a "safe" (e.g. non-mutating) subset of SQL before actually issuing queries to the database. Then figure out (somehow) how to close the loop on error handling when the LLM violates the contract (e.g. generates a query which doesn't parse).
Then of course there's the whole UX problem of even when you restrict the interface to safe queries, the LLM may still generate queries which are completely incorrect. The best idea I can come up with there is to dump the query text to an editor where the user can review it for correctness.
So it's not really "natural language queries" more like "natural language SQL generation" which is a completely different thing and absolutely should not be marketed as the former.
People bring up this concept as a way to make systems "more friendly to novice users" which tbh makes me a little uncomfortable, because it seems like just a huge footgun. I'd rather have novice users struggle a bit and become less novice, than to encourage them to run and implicitly trust queries which are likely incorrect.
So it's a bit difficult to tell how much value is added here over some basic intellisense style autocomplete.
Looking to the world of "real tools" like hammers and saws, we don't see "novice hammers" or "novice saws". The tool is the tool, and your skill using it grows as you use it more. It seems like a bit of a boondoggle to try to guess what might be good for a novice and orient your entire product experience around that, rather than simply making a tool that's good for experts doing real work and trusting that the novices will put in the effort to build expertise.
Only if you give it unfettered accesss. AWS has an API called AssumeRole which can generate short-lived credentials with a specifically scoped set of permissions, which I use instead.
Parquet files being immutable is not a bug, it is a feature. That is how you accomplish good compression and keep the columnar data organized.
Yes, it is not useful for continuous writes and updates, but it is not what it is designed for. Use a database (e.g. SQLite just like you suggested) if you want to ingest real time/streaming data.
