2,161 karma · joined September 3, 2020
> Examples here are (again) the cryptocurrency scene which has been pretty good at othering critics as “no-coiners” or lately with the phrase “have fun staying poor”.
> Built-in concurrency and a robust standard library
I think that the joy of Go's async-first design really makes sense most to people who have experienced the awful pains of colored async-await in other languages.
In general it's interesting times for Java. With all of language improvements from Kotlin/Scala, and upcoming Go-like concurrency it really feels like a renaissance for the language.
> It seems fine to me for the spec not to guarantee anything about struct field order in memory. The spec doesn't operate at that level.
> That said, no Go compiler should probably ever reorder struct fields. That seems like it is trying to solve a 1970s problem, namely packing structs to use as little space as possible. The 2010s problem is to put related fields near each other to reduce cache misses, and (unlike the 1970s problem) there is no obvious way for the compiler to pick an optimal solution. A compiler that takes that control away from the programmer is going to be that much less useful, and people will find better compilers.
Interesting to see how IRC peaked around 2005. The current most popular network, Libera, has a fraction of the users that Quakenet did 17 years ago.
It's funny to think back to 2015 and the hagiographical void still left in tech journo hearts after Steve Jobs died.
https://www.inc.com/ilan-mochari/elizabeth-holmes-theranos-i...
> How Elizabeth Holmes Became America's New Entrepreneurial Icon
> She represents the part of entrepreneurship that is long-term dedication, when nobody's watching
>... That kind of walk-before-you-talk behavior is refreshing and respectable in today's hype-strewn entrepreneurial landscape.
Is this really worth a change to every HTTP client library out there to support this? The limited applications that really need this can easily use POST and document their own semantics around this.
If anything the trend with GraphQL is to ignore HTTP verbs outright because they are limited and inexpressive beyond simple CRUD tasks.
A programming language isn't going to bring you real joy, that can only come from within.
It's stupid, silly, old and outdated.
https://softwareengineeringdaily.com/2020/01/17/apollo-graph...
Typical user testing is monitoring your users as they succeed/fail to use your product. So I could imagine developers monitoring a sampling of Doordash drivers (with a dashcam or the like) as they use their apps in a typical delivery process.
White-collar Doordash engineers/CxOs doing a blue-collar tour for a day would provide insight into some of the initial onboarding struggles for the "new driver" persona, but seems like it would provide limited feedback for the "experienced driver" persona. Even then, app devs/designers are so familiar with getting around odd workflows in their apps that they wouldn't really represent a new driver. It risks biasing product development in a particular way.
"if another language is being discussed, Rust must be forced into the discussion, no matter how tenuous the connection"