168 karma · joined August 18, 2015
Ion has the option of using symbol tables to replace strings (e.g. in struct/map keys or in values). So, if you benchmark had a large number of records with similar structures, I would expect Ion to pull ahead. On the other hand, if each record had nothing in common, I'd expect them to perform similarly.
One feature of the Ion libraries that I've liked is the parser will take any of the formats and figure out what to do with it (text, binary, compressed binary). It's one less thing to worry about. You can switch encodings later without breaking consumers, you can write plain text Ion when you're testing, etc.
AWS is starting support PartiQL (https://partiql.org/) queries in some places and PartiQL uses Ion's type system internally.
Fast-forward to 2023 and many individual Android apps are 100-500 MB each.
I went to my google account and clicked "Create a passkey", but apparent my "device doesn't support creating passkeys" (Linux, Firefox).
The page said my Pixel 2 has an automatically created passkey, so maybe I could experience the "use another device to sign in" flow. Opened a private window and my only option was a password (but there was a feedback prompt asking why I still wanted to use a password).
I tried again with Firefox on Android, but the "Create a passkey" button doesn't even appear. Same story with Chrome on Android.
Is it just me, or does the future look a lot like Internet Explorer in the early 2000s?
The five were: a stopper knot, to keep a line from pulling through something, a fixed loop, a running loop, a hitch (attach a line to a thing), and a bend (attach a rope to a rope).
My go-to knots were a figure 8, bowline, running bowline, clove hitch, and sheet bend respectively.
We invented machines to build large amounts of simple things cheaply, so we designed simpler things.
MOV is still the top, but it was followed by PUSH and CALL.
I have about 4-5 knots memorized for each of those category, but sailing I typically only use a cleat hitch, bowline, and clove hitch (in order of frequency).
The ABoK was something I always wanted to see, but never bothered to buy... until I found that PDF. Scrolling through it finally convinced me to buy a hardcopy. It's one of my favorite books to just flip through. There's more than just the knots: the history and the anecdotes are a fascinating window into the past.
With typical work weeks in mind, midweek makes more sense to avoid conflicting with weekends.
(and here's why we don't have unanimous agreement—it's always the little details that hang people up)
PHP's phpinfo() function comes to mind immediately: https://www.php.net/manual/en/function.phpinfo.php
We'll start off with a topic and give everyone, say, 15 minutes to write ideas in the doc on their own. Then take the next 15 minutes to read digest what everyone else wrote, and then rest of the time to discuss as a group.
It's great because it gives everyone a chance to think through the topic and share their perspective, but also you can quickly see the common themes.
I recently started driving a drive-by-wire vehicle. A while ago I had an issue where the engine dropped to a near-idle (on the freeway) and the pedal was effectively non-operative. The diagnostics said the computer wasn't getting the expected results from moving the throttle body, so it went into some kind of safe mode.
Now, there are plenty of ways that drive-by-cable could fail, but in this case I was slightly resentful because I could have mitigated the computer's loss of senses with my own.
When I'm cooking/baking, I use butter, olive oil, and (lately) bacon grease, depending on what I'm making.
Coincidentally, in January I had made a list of everything in my fridge and pantry. The only things left with soy were mayonnaise, tortillas, and hamburger buns. I started making the bread products myself for fun. I haven't tried to replace the mayonnaise yet (I really dislike avocado mayo), but it's next.
I wonder why? Is IPv6 adoption significantly higher for residential internet connections vs. corporate networks?