benlesh.bsky.social
RxJS lead. Dad. Art lover. I’ve worked at the NG in FAANG.
205 posts
2,696 followers
149 following
Regular Contributor
Active Commenter
comment in response to
post
It's UNFORTUNATE that it's a common term.
"Green" in particular, was a really poor choice. "green" means success or active 99% of the time in software.
Odd/even was right there. lol
comment in response to
post
From @domfarolino.com :
bsky.app/profile/domf...
comment in response to
post
spacer.gif
comment in response to
post
It would have to be a lot of extensions. In 25 years, I don't think I've worked at any two companies that had the same pairing of issue tracker and source control.
Teams of humans that are hustling are terrible at organizing information across multiple tools.
comment in response to
post
... not to mention a lot of the discussions about "why" some code is the way it is might happen in person, or in Slack, or elsewhere.
comment in response to
post
They could, but clearly it's vastly more complicated than just adding some jsdocs to methods or a one liner explaining "why" some code is the way it is.
Also it's not one-size fits all. There are a dozen version control systems and probably a hundred bug trackers and team management tools.
comment in response to
post
AH! That's a "lube station" (lol) I thought it was some sort of crazy keyboard you took the caps off of
comment in response to
post
Haha. I meant what model of keyboard is that big square keyboard, and what is the use case for such a keyboard?
I mean, I’m happy that you have your own system to lube things, believe me 😂
comment in response to
post
If you'd ask me in 2015 what will web dev look like one decade from now, my imagination would have gone WILD.
Instead, we just got Next.js
comment in response to
post
What the heck is that keyboard and what is it used for?
comment in response to
post
I know this is probably old news for some folks, but I'm always shocked at the number of broken GitHub links I find in the wild.
comment in response to
post
You shut your filthy mouth!
🤣
comment in response to
post
This is really good. Nice work!
comment in response to
post
Semi related: I’m doing some art with gliding (silver leaf, though, not gold) and Eytzinger is a manufacturer of materials related to that process.
Strange coincidence.
comment in response to
post
I’m not familiar with the algorithm. It seems to expect a sorted array to build a flattened, balanced binary tree?
It might be good to give more descriptive variable names for the uninitiated. But I can look up the algorithm.
comment in response to
post
Thank you, Alex
comment in response to
post
Any rough edges or quirks around iframes or the like? Just curious.
comment in response to
post
Progress photos part 2:
I used a simple 3 color palette: Ultramarine blue, cadmium yellow light, and alizarin crimson.
I used a relatively thin medium for the lower layers: 2:1 turpenoid to safflower oil. Getting heavier with more raw paint as I worked up.
comment in response to
post
Progress photos part 1:
The wash/underpainting is just burnt sienna and turpenoid.
comment in response to
post
Zeu Breu, nitro brew, or kombucha, or beer.
I'd buy it. Because I like saying it.
comment in response to
post
Explain "fine grained async" are you talking about controlled scheduling?
comment in response to
post
useState and useMemo are basically very explicit very poorly integrated signals.
comment in response to
post
Put differently, if we react has to build an object tree, and then diff it against another object tree in order to know what to update, then targeted updates aren’t really on the table. And reactive types like signals really don’t have any direct advantage for react.
comment in response to
post
Without a compiler, and with the virtualized DOM paradigm, I don’t really know that react is in a great position to benefit from signals.
Frameworks that use compilers and “templated“ DOM (including JSX usage) will always have an advantage using any reactive primitive for targeted updates
comment in response to
post
If you’re keeping state just to coordinate events, that’s probably something that should live in an observable.
But any state that you’re rendering? Signals.
comment in response to
post
Oh no. I can’t see the controls on iPhone.
comment in response to
post
Biches be crazy
comment in response to
post
"the compiler is real in our experience" - Dan Abramov