igregoryca

6 ms·

1. 31.▲
   by igregoryca 1y ago

   If you're making enough money, you can hire a designer every now and then to tell you where your UX suffers and how to fix it. No investors necessary. (or: just solicit feedback in a space frequented by designers, and harness the power
2. 32.▲
   by igregoryca 1y ago

   Discovering and using private APIs is not a walk in the park. I doubt "laziness" is a common motivation for doing so. Lack of knowledge or bad docs, perhaps. But there's often no officially sanctioned way to do something that
3. 33.▲
   by igregoryca 1y ago

   Hm. You and parent comment have made me realize something: as much as I dislike how many useful abstractions are missing from Go, async for blocking syscalls is not one of them, since the "green thread" model effectively makes all
4. 34.▲
   by igregoryca 1y ago

   > the sync/async function coloring nightmare I'm with you that function "coloring" (monads in the type system) can be unergonomic and painful. > ... isn't that what Go is? I think out of all languages I use ex
5. 35.▲
   by igregoryca 1y ago

   > I do think it's likely more passive than active. People at Google aren't deviously plotting to hide buttons from the user. This is important, thank you for mentioning it: actions have consequences besides those that motivated
6. 36.▲
   by igregoryca 1y ago

   This aligns nicely with how things look in the "small-step" flavour of PL theory / lambda calculus. In the lingo, expressions are evaluated by repeatedly getting "rewritten", according to rules called reduction rule