@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.
@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.
Announcing Rspack 1.0 - the next generation JavaScript bundler written in Rust, webpack compatible, 10x faster.
Check out the release blog for more details:
https://t.co/nOVJjKMRBo
@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.
@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.
@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.
@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.
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 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.