Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 20:43
    Nixinova edited #44637
  • 20:38
    mjbvz edited #44637
  • 20:38
    Nixinova opened #44637
  • 20:35
    ahejlsberg demilestoned #44281
  • 20:35
    ahejlsberg milestoned #44281
  • 20:00
    typescript-bot closed #44597
  • 20:00
    typescript-bot closed #44598
  • 18:32

    weswigham on v4.3.4

    (compare)

  • 18:19

    elibarzilay on main

    `services/utilities/getMeaningF… (compare)

  • 18:19
    elibarzilay closed #44622
  • 18:19
    elibarzilay closed #44167
  • 18:12
    DanielRosenwasser milestoned #28491
  • 18:12
    DanielRosenwasser demilestoned #28491
  • 18:12
    DanielRosenwasser milestoned #28491
  • 18:12

    DanielRosenwasser on main

    feat(28491): add QF to declare … (compare)

  • 18:12
    DanielRosenwasser closed #44576
  • 18:12
    DanielRosenwasser closed #28491
  • 18:06

    amcasey on main

    Make export-module and referenc… (compare)

  • 18:06
    amcasey closed #44402
  • 18:01
    polkovnikov-ph edited #44636
webstrand
@webstrand
well, TIL. This wasn't an issue in the past
AnyhowStep
@AnyhowStep
Weird. I've used BarraCuda before, too, and never noticed anything slow
webstrand
@webstrand
they have pretty good caching on them. For the first hour of writes, it was a semi-reasonable 54MiB/s
Bruce Pascoe
@fatcerberus
Only 5400RPM? How do you get 190 MB/s out of that?
webstrand
@webstrand
that should be 80-90 MiB/s
AnyhowStep
@AnyhowStep

I wonder what the reviewer meant by,

Needless to say I am returning it, but beware for those that think these drives are the same ones from a year ago. They are not, and you have been warned.

Bruce Pascoe
@fatcerberus
That’s… rather vague if its meant to be a warning
webstrand
@webstrand
may have been a different model of "compute"
for instance the 1TB version isn't crippled
AnyhowStep
@AnyhowStep

I'm working on some legacy redux saga code and I hate it.
Never used redux sagas before but they seem fragile as heck.

If a saga has an uncaught exception, it can break all the other sagas, even if they seem unrelated.

Right now, I'm just shoving try-catch where ever I see an uncaught exception and then slowly fixing them
The TS types for these things are terrible, too
Bruce Pascoe
@fatcerberus
if (this.sucks) { getANewJob(); }
Keith Layne
@keithlayne
can't remember, is saga the one with the generators?
there was one I used for async actions
webstrand
@webstrand
job market seems like it's kinda dead, right now.
Keith Layne
@keithlayne
ah, redux-thunk. That got very painful very quickly.
I dunno, I need to quit, had a couple of interviews, pretty much went as badly as I could have imagined. Yay me.
AnyhowStep
@AnyhowStep
redux-saga uses generators
Keith Layne
@keithlayne
"thunk" is one of my all-time favorite words.
Bruce Pascoe
@fatcerberus
I still don’t really know what it means
webstrand
@webstrand
as I understand it: A thunk is something that proxies for another operation
Keith Layne
@keithlayne
it's just a thunk, you know?
AnyhowStep
@AnyhowStep
they call them callbacks or middleware or sth now
webstrand
@webstrand
so const foo = () => this.foo() would be a thunk
I always think of vtables, though. Where calling a virtual method is actually calling a thunk that resolves the real method from the class's vtable.
Keith Layne
@keithlayne
I usually think of them as some kind of deferred action I guess. Like a think that's wrapped up and ready to be called.
but that's too narrow I guess
webstrand
@webstrand
that works too, though I don't think thunk implies any kind of asynchrony
Keith Layne
@keithlayne
not in my mind either, even though that's what makes sense in JS mostly
Bruce Pascoe
@fatcerberus
They just need to make them actually make a “thunk” sound when called and that would make it complete
webstrand
@webstrand
I always imagine the sound of a large relay closing
Keith Layne
@keithlayne
onomatopoeia is also fun. prolly spelled it wrong.
webstrand
@webstrand
RPCs probably also qualify as "thunks"
Keith Layne
@keithlayne

fun fact for today:

Eunoia, at six letters long, is the shortest word in the English language that contains all five main vowels.

AnyhowStep
@AnyhowStep
It repeats "u" twice. The second "u" is just upside down.
webstrand
@webstrand
huh a -noia word with no negative connotations
Gerrit Birkeland
@Gerrit0
@keithlayne that looked like a base url setup not paths to me - fine if you aren't writing a lib
Gerrit Birkeland
@Gerrit0
Also, are interviews just an awful way of figuring out if people are good? I'd be glad to have you on my team from what I've seen here & on Discord...
Shanon Jackson
@ShanonJackson

redux is not a good solution in general, its built framework agnostic so you end up with many layers of heavy abstractions just to change state.

"redux" for the store,
then to consume redux in react "react-redux"
then because you need logging so redux-logger
then you can't run async actions or debounce so you need redux-thunk or redux-sagas.
then because you get stuck in boilerplate hell you need redux toolkit
and then redux-toolkit imports immer

And then you haven't even reached the code-level abstractions. Then you need to implement actions/reducers/rootReducer to change your state from the top-down this strategy can't be codesplit on a route-level (in the sense that your rootReducer is always imported into the root of your application), The result is the promise of "scaleable" state management is really undermined from the get-go.

Try recoil instead, only uses the React library to achieve everything so feels free fluid to use and its bottom-up state management so codesplits easy.

Keith Layne
@keithlayne
Shanon you're always a bundle of sunshine :P
Shanon Jackson
@ShanonJackson
Very true haha
webstrand
@webstrand
@ShanonJackson What about jotai? I currently have it pegged as the next framework to learn after redux
I've been using useReducer but it's a pain, esp. having to avoid accidentally mutating objects.
AnyhowStep
@AnyhowStep
recoil does seem way better
That shareable URL thing is perfect. My team keeps implementing those a different way every project <.<
And it's always buggy in a different way. I'm so sick of fixing those bugs
AnyhowStep
@AnyhowStep
Seems like you could just add an atom to a prop, if you don't like the idea of globals
Or if you don't like to mock hooks for unit testing