Readit News logoReadit News
infogrind commented on Gemini Robotics   deepmind.google/discover/... · Posted by u/meetpateltech
chrisweekly · a year ago
Slightly off-topic, but why is it still referred to as "Google" and not "Alphabet"?
infogrind · a year ago
Names stick, it’s as simple as that. In most practical situations (such as this discussion), the distinction between Google and Alphabet doesn’t matter.

I once tried to rebrand an in-house, purely dev facing product. I failed.

infogrind commented on How to spot cult leader personalities   sashachapin.substack.com/... · Posted by u/insightcheck
infogrind · 3 years ago
An accurate description of a good many politicians.
infogrind commented on Google Chat spaces will be in-line threaded by default   workspaceupdates.googlebl... · Posted by u/infogrind
infogrind · 3 years ago
I'm a heavy user of Google Chat at work. Whenever I encounter a space with in-line threading, I ask the others if we can switch to the topical structure (with separate threads grouped together and brought to the bottom for new messages, but no in-line replies). Usually everyone agrees.

If in-line replies become the only option, I'll have the choice of wasting countless time to dig through past replies, or just stop checking chat altogether.

infogrind commented on Let It Fail   maxcountryman.com/article... · Posted by u/bo0tzz
taneq · 3 years ago
For most of the article I assumed that the “it” that they were letting fail was the project itself, in order to force organisational change, not the incumbent software system.
infogrind · 3 years ago
+1, the writing could certainly be improved there.
infogrind commented on Why Lisp macros are cool, a Perl perspective (2005)   lists.warhead.org.uk/pipe... · Posted by u/goranmoomin
dinom · 4 years ago
I'd like to point out that the strange occurrences of the "=3D" string are due to the fact that the message was originally a "quoted-printable" encoded email and for whatever reason this artifact wasn't removed when posted to the web. Perhaps this was pipermail's fault?

Anyway, when reading the code, you're safe in assuming "=3D" is just a single plain old equal sign. In the "quoted-printable" encoding scheme the two characters following an equal sign are the hex value of the intended character. In effect, equal signs need to be escaped using the "=3D" sequence.

This drove me a little nuts as I was reading and trying to code switch between the assorted languages used in the examples.

infogrind · 4 years ago
And I thought it was ascii for “goat dick”

u/infogrind

KarmaCake day8March 6, 2022View Original