TheDuffmaster@lemmy.world to Programmer Humor@lemmy.ml · 5 months agoSwitching to OCaml boislemmy.worldimagemessage-square91fedilinkarrow-up1417arrow-down124
arrow-up1393arrow-down1imageSwitching to OCaml boislemmy.worldTheDuffmaster@lemmy.world to Programmer Humor@lemmy.ml · 5 months agomessage-square91fedilink
minus-squareSubArcticTundra@lemmy.mllinkfedilinkarrow-up3arrow-down7·5 months agoIt becomes quite OOP if you use it with React
minus-squareel_abuelo@lemmy.mllinkfedilinkarrow-up14·5 months agoHuh? I’ve worked with TypeScript + React for the last 5yrs and the only time I see OOP is when someone’s done something wrong. Maybe you’re thinking of old react with class based components?
minus-squaretoastal@lemmy.mllinkfedilinkarrow-up2arrow-down1·5 months agoProving that adding the class keyword to the ECMAScript spec was a mistake that leads folks down a path they should not travel 🙃
minus-squareel_abuelo@lemmy.mllinkfedilinkarrow-up2·5 months agoI completely agree. I taught JS/TS for 5yrs and I always emphasised that the ‘class’ keyword was just syntactic sugar for what was already available in prototype inheritance of JS.
It becomes quite OOP if you use it with React
Huh? I’ve worked with TypeScript + React for the last 5yrs and the only time I see OOP is when someone’s done something wrong.
Maybe you’re thinking of old react with class based components?
Proving that adding the
classkeyword to the ECMAScript spec was a mistake that leads folks down a path they should not travel 🙃I completely agree. I taught JS/TS for 5yrs and I always emphasised that the ‘class’ keyword was just syntactic sugar for what was already available in prototype inheritance of JS.