Ben Heidemann

@kavun @jarredsumner Presumably that’s been considered in the discussion

@jarredsumner Or refactor to make the answer explicit

Answers to PR feedback that don’t involve code changes usually should be serialized into code comments above the line mentioned

@rauchg Nothing?

Guess what this PR did

@thdxr Also it’s not like we had to pay for GC languages. Sure there’s a performance cost, and associated compute cost, but there’s no middleman trying to take a cut.

in software there has always been a pattern of "the kids these days don't even know how to x" i remember this from when i was younger - the more experienced people would talk about garbage collected languages killing people's understanding of memory they weren't exactly wrong but they cleared missed the larger picture - plenty of important and non-trivial things went on to be built anyway i'm now finding myself on the other side - i'm the one who feels like the kids aren't learning things i think are important history tells me i'll likely be wrong but just because it looks the same doesn't actually mean it's the same if i had to make a case for the difference - i think technologies that enable more software to be built will always win - GCd languages did that on the surface it seems like what a lot of devtools companies are pushing fits that "outsource functionality x to us so you can spend more time working on what's unique about your product" but if you look at what you can actually build with these tools it's pretty narrow - they scoped down to a very specific type of app and designed around that i don't feel the explosion of ideas - that feeling of "i can use this in a million ways" so that's why i think i could be right when i say "the kids are doing things wrong" - the path they're on has a very short ceiling that they won't even realize is there but i'm sure my predecessors had very smart sounding rationalizations too

@thisistechtoday I like the MagSafe charger because it just clicks into place. Not a big deal but I do plug in/unplug my laptop a lot, and I like the feel better.

I want to apologize to Apple for being amongst the many of us begging them to bring back MagSafe on the MacBook Pro. We were wrong about that one. My bad. I never use it. You can get rid of it again and put USB-C there instead. Whoooooops. 😂

@kennethnym For the good of man kind, Microsoft need to do like Apple did with MacOS.

literally nothing on windows happens instantly. you right click? wait a few seconds. open file explorer? feels like it’s downloading the html from a server on the moon. the notification center? yeah go get a coffee first before it loads in the one (1) notification

So… what happens to turbopack? 🤔

@iamjasonlevin Cave drawings were the OG dark mode and way predate paper.

Yes dark mode looks sexier. But there's no way it's more readable. Humans have been reading black on white for 1000s of years. You're gonna tell me suddenly reading white on black background is more readable? I call BS. We've hit Peak Dark Mode.

@morallawwithin Can’t tell if you’re being serious 😅

For the non-mathematicians out there: if something has a 50% chance but it happened 20 times in a row, the next time will almost certainly go the other way in order to even the distribution out.

@krzyzanowskim Well yes, but books are black on white because paper is white, and it’s much harder to print white text on a black background 🤔

dark mode (especially text editor) is not natural. books are white and letters are black for a reason.

@ploeh @TheBuzzSaw I don’t feel that this is good advice. I see junior developers do this all the time, and it makes it very difficult to review PRs, as you loose the context of the comments on the previous PR. You loose important information.

@TheBuzzSaw No, once you've shared Git history with another computer, it gets really confusing if you rewrite history. The commit IDs change. You can append to the PR if there are only a few issues to resolve. If there are many issues to resolve, close the PR and prepare a better one.

Please don't squash commits. You're throwing away data when you do that. If you want a 'pretty view' of history, you can always pretend to throw away data when it pleases you, e.g. git diff commit123..commit456

@ploeh This directly contradicts “I need to know what happened when. In detail”. If you rebase, you loose the information of what *really* happened when.

One more thing: People always jump to the conclusion that I'm against nice Git logs. Not so. I'm very meticulous with my Git history (just look at my GitHub), and I rebase A LOT. Before issuing a pull request, that is.

@ploeh > I need to know what happened when Exactly. And the commits that went into the PR never went to production. Many of them may be broken or WIP commits etc. I struggle to see how having tonnes of extra commits that were never deployed is useful.

As usual, this viewpoint elicits a few responses, all of which I've already seen. Re. 'keeping Git history sane'. You do you, but IMO, that's optimizing for the wrong thing. I rarely look at Git history to be told a story. When I do, I need to know what happened when. In detail

@t3dotgg Yeah it’s quite a shame. My background is in RN and recently I’ve done a lot of Flutter dev and really enjoyed it. Would be a shame to see it fade away.

Meta is investing more and more into React Native. Microsoft and Amazon are joining them. Meanwhile it feels like Google forgets Flutter exists

@samal_rasmussen @thdxr It’s not HTMX.

@thdxr It's HTMX.

unbundle: jquery -> just a lib for dom stuff bundle: angular -> help people build SPAs unbundle: react -> just a lib for views bundle: nextjs -> help people do SSR unbundle: ? -> just a ? for ? bundle phases curate a common use case they grow and are too rigid for other things so people crave an unbundling phase what's next?

@thdxr @JoeBiden 🤣

@JoeBiden why won't you do something about this???

the opioid crisis isn't nearly as bad as the nextjs crisis

About 👏 damn 👏 time 👏 Even if Node remains dominant, Deno and Bun have done amazing work to push the ecosystem forward. A perfect case study for why diversity is essential in driving progress.

@L33tHaxxor4lyf @cmuratori It’s not as simple as this. There’s been a lot of studies into human vision, and for most purposes 30-60 fps is sufficient, but there’s been experiments that have shown results at much higher rates (up to 500 under certain conditions).

@cmuratori The human eye can't see faster than 60fps.👁️👁️

I don't see what all the fuss is about.

@rebelavalon @cmuratori Umm… no 😅

@presotweets @cmuratori *mostly* being the operative word

@cmuratori It's like premium internet speeds, mostly bragging rights.

@cmuratori For some games FPS does matter, but not so much the monitor refresh rate. For instance, in RL input lag is inversely correlated with frame rate (higher frame rate, lower input lag). The effect is very noticeable.