4 ms·

Wasn't that true for tech in general though? I mean I have heard developers bitching about React for years now and every year I saw it get more adopted at the s

Wasn't that true for tech in general though? I mean I have heard developers bitching about React for years now and every year I saw it get more adopted at the same time. Of course some obviously do not like it but the decision was usually driven by business and not coders. I feel its a simillar thing happening with AI code taste being primarily developed by big tech firms which ofc love homogenization. But its not all bad, I don't think people will just give up working on what they like because agent expeirenxe got better but who knows though

afiori 1mo ago
A lot of the bitching about react always had the same flavour of the complaints that JavaScript dares to have a NaN To be fair it is stupid that NaN !== NaN but that is how IEEE and CPUs made floats to be
- jjgreen 1mo ago
  It's not stupid when you realise that NaN is not "not a number" but rather "not a particular number", this becomes clear from hypot(Inf, NaN) being Inf rather than NaN
  - afiori 1mo ago
    NaN means only NaN, 0/0 is NaN at the cpu level. to my weak undestanding only pow and hypot behave like this; pow for math reasons and i could guess that hypot does that to sorta have |x| <= hypot(x,y)
- bryanrasmussen 1mo ago
  I mean to me the whole point of NaN is that it should not equal NaN, so it seems sort of like you are making the complaint in the first sentence in your second sentence, only in a slightly more abstracted way. Unless you are of the opinion there is another better point to NaN? funny story, I was once interviewing for a job where the tech guy did not know that NaN existed. I guess JavaScript wasn't his language, but not sure what was, and the code was in JavaScript for a Web Dev role.
  - afiori 1mo ago
    my point is that that a lot of people shit on js for having "weird crazy stuff in it" and then the example is 0.1 + 0.1 + 0.1 !== 0.3 or NaN != NaN which has nothing to do with js semantics JS is weird, and not having a stronger separation between ints and floats makes NaNs more common than in other languages (eg parseInt would not return NaNs in C or python) but for many "weird" examples people are making fun of normal stuff.

afiori 1mo ago

A lot of the bitching about react always had the same flavour of the complaints that JavaScript dares to have a NaN To be fair it is stupid that NaN !== NaN but that is how IEEE and CPUs made floats to be

jjgreen 1mo ago
It's not stupid when you realise that NaN is not "not a number" but rather "not a particular number", this becomes clear from hypot(Inf, NaN) being Inf rather than NaN
- afiori 1mo ago
  NaN means only NaN, 0/0 is NaN at the cpu level. to my weak undestanding only pow and hypot behave like this; pow for math reasons and i could guess that hypot does that to sorta have |x| <= hypot(x,y)
bryanrasmussen 1mo ago
I mean to me the whole point of NaN is that it should not equal NaN, so it seems sort of like you are making the complaint in the first sentence in your second sentence, only in a slightly more abstracted way. Unless you are of the opinion there is another better point to NaN? funny story, I was once interviewing for a job where the tech guy did not know that NaN existed. I guess JavaScript wasn't his language, but not sure what was, and the code was in JavaScript for a Web Dev role.
- afiori 1mo ago
  my point is that that a lot of people shit on js for having "weird crazy stuff in it" and then the example is 0.1 + 0.1 + 0.1 !== 0.3 or NaN != NaN which has nothing to do with js semantics JS is weird, and not having a stronger separation between ints and floats makes NaNs more common than in other languages (eg parseInt would not return NaNs in C or python) but for many "weird" examples people are making fun of normal stuff.