Had it for 3 days running with nary a request. Perhaps it's the chosen model that I am serving (Gemma 4 26b)? I did see some WARN logs right after startup but the description don't suggest any problems that would block accepting requests or processing them.
As informative as this is, what is with the tendency to use Twitter where a blog posting would be more appropriate? Reading this with the character limit break cadence and understanding.
Guessing the idea is to expand viewership of the content. Easier for people to share content and stumble upon it when it’s hosted on Twitter versus a blog.
I am curious about this. Has there been an analysis comparing the contents in the two respective countries? Something that would be illustrative of this claim. I am not doubting you or your statement. Just looking for information to back it up.
My search consistently yields marketing stats. Perhaps I am using the wrong key words?
Would this be able to transfer your clipboard from Linux to an iOS device? Or at least via a roundabout way (like say a script that uses ssh to a MacOS based machine to utilize its `pbcopy` & `pbpaste`)?
Notwithstanding the other issues mentioned, but the MacBook Air is not exactly user repairable. IIRC, it is a SOC. So any part that breaks the entire thing needs to be replaced. I got a MacBook Pro 2018 and though it works it still makes wary.
In a decade of using MacBooks, I had faulty RAM twice, once a broken 'f' key, once a completely unusable keyboard (one of the butterfly generations, keys would often get stuck).
But at least the service of Apple Stores was very good. Unfortunately, many Apple authorized service providers are terrible.
I consider myself an advanced-beginner programmer untested in the real world (looking for my first coding job though!), and I understood it relatively quickly. It does appear more concise than many if-else statements. After the initial “what?”, I was able to quickly parse through it. I think this is faster than using the standard form.
A lot of the code you're going to have to be dealing with in the wild is going to look fine, until it breaks at 2am on a Saturday and you're 3 drinks in and production is down.
There should be a rule that forbids applying this reasoning to code that isn't triple-nested template SFINAE mess, or a code-generating-code-generating-code-generating-code Lisp macro.
This pattern isn't "cleverness", it's just a readability-improving trick that's cheap to figure out. The hundred seconds you spend on it seeing it for the first time is a one-time cost.
