6 ms·

React's prioritization of features has led to it being one of the most successful frameworks of all time, I'm not sure how useful it is to suggest they should h

React's prioritization of features has led to it being one of the most successful frameworks of all time, I'm not sure how useful it is to suggest they should have started with this from the beginning. It's been overwhelmingly successful without this feature.

manigandham 7y ago
It's popular so it's fine? The massive number of async-related workarounds, libraries, tooling and code practices says otherwise. jQuery is even more popular btw. It's the general state of Javascript and frontend code which is finally starting to understand what multithreading and concurrency is.
- ng12 7y ago
  JavaScript is not multithreaded.
  - manigandham 7y ago
    Javascript as a language isn't, but Javascript code can use multiple threads in various ways.
    - ng12 7y ago
      And you're implying asynchronous coding is new to JavaScript developers?
      - deleted 7y ago
        [deleted]
      - manigandham 7y ago
        As default architecture? Yes.
        ng12 7y ago
        I'd like to see some evidence to back that up. The event loop is one of the few things JavaScript did correctly and it's baked into everything but the most trivial of applications.
        manigandham 7y ago
        I'll refer to my quote: "The massive number of async-related workarounds, libraries, tooling and code practices says otherwise." It's surprising that JS has so much history with callbacks and events but async methods are unsupported or require workarounds by so many core frameworks and libraries which default to synchronous APIs for everything.
- paavohtl 7y ago
  jQuery is not an UI framework. It's a library of utilities for DOM querying and manipulation.
  - manigandham 7y ago
    The point being popularity has nothing to do with architecture.
dosy 7y ago
The illogical adoption of React must not be questioned, even in the face of its poor performance and ugly syntax. One must never note that perhaps it is simply a cultish adoration, or faddish adherence to popular mass opinions, that leads to "popularity" mattering more than practicality. So what if React is massively bloated, stupid syntax, can't use regular HTML, can't use regular CSS, can't use async/await, have to do everything a special way...literally, SO WHAT. It IS REACT! OMG behold it's glory. It came from FB, maybe if we use it we can scale like FB! Omg the idiocy. But keep on slavishly following the next front-end dev trend. I can't tell whether front-end dev culture is a massive circle-jerk or cargo cult. And don't mention the irrational hate attempted to be heaped onto anyone who dares question the programmatic thinking of the official line of the React Appreciation Society.
- hombre_fatal 7y ago
  Is there anything more in-bad-faith than assuming everyone who uses X is just an idiot, trend-follower, or beginner? Unlike you, the Enlightened One? Why not just ask people why they use X? Plenty of veteran developers on HN could tell you why they like React despite a sea of alternatives, but it's easier to just cast aspersions instead of understanding. It's a shame to see this on HN which is supposedly a community of craftspeople who build things. If you can only come up with insults for why another group of people do something, it's time for you to get up off your ass and ask someone in that group. And this extends beyond just engineering, it's how you understand other people in general.
  - dosy 7y ago
    That's a bit mean, don't you think? See I was addressing a group of people but you're directly saying that to me. Hmmm, well, why don't you take your own advice pal and ask me why I think so? Oh, that's right, I guess you were just trying to insult people rather than understand. Hahahaa. But anyway, I am thoroughly enjoying your attempt at self-righteousness. Keep working on that, you've nearly got it. And I'm very grateful to you for proving my point. You may be old, but are you sure I don't understand people and you do? I don't think "bad faith" means what you think it means, but I take it by the vehemence of your response that I struck a nerve. And I think you might just be projecting. See, I think you're angry because you must use React, and me reminding you other choices exist, which you nevertheless cannot access, reminds you of that embarrassing lack of freedom. So you choose to double down on defending something you don't really want anyway. But I guess you don't really understand how you feel about it, so you just project and blame somebody else. If you didn't like React, would you ever say no to an offer that insisted on it? See, I don't think you would. But I have. I wanna work with what I like. I think if you really loved it and knew why you wouldn't be so perturbed. I'm just curious, why no submissions? Why anonymous? Would you talk so big, if everyone knew your name? Or are you only a loud mouth if you've got no skin in the game, really? Anyway, have a good day thinkin about that, pal and if you wanna know more please read my answer for "debuzzybee" and my comment she linked.

manigandham 7y ago

It's popular so it's fine? The massive number of async-related workarounds, libraries, tooling and code practices says otherwise. jQuery is even more popular btw. It's the general state of Javascript and frontend code which is finally starting to understand what multithreading and concurrency is.

ng12 7y ago
JavaScript is not multithreaded.
- manigandham 7y ago
  Javascript as a language isn't, but Javascript code can use multiple threads in various ways.
  - ng12 7y ago
    And you're implying asynchronous coding is new to JavaScript developers?
    - deleted 7y ago
      [deleted]
    - manigandham 7y ago
      As default architecture? Yes.
      - ng12 7y ago
        I'd like to see some evidence to back that up. The event loop is one of the few things JavaScript did correctly and it's baked into everything but the most trivial of applications.
        manigandham 7y ago
        I'll refer to my quote: "The massive number of async-related workarounds, libraries, tooling and code practices says otherwise." It's surprising that JS has so much history with callbacks and events but async methods are unsupported or require workarounds by so many core frameworks and libraries which default to synchronous APIs for everything.
paavohtl 7y ago
jQuery is not an UI framework. It's a library of utilities for DOM querying and manipulation.
- manigandham 7y ago
  The point being popularity has nothing to do with architecture.

dosy 7y ago

The illogical adoption of React must not be questioned, even in the face of its poor performance and ugly syntax. One must never note that perhaps it is simply a cultish adoration, or faddish adherence to popular mass opinions, that leads to "popularity" mattering more than practicality. So what if React is massively bloated, stupid syntax, can't use regular HTML, can't use regular CSS, can't use async/await, have to do everything a special way...literally, SO WHAT. It IS REACT! OMG behold it's glory. It came from FB, maybe if we use it we can scale like FB! Omg the idiocy. But keep on slavishly following the next front-end dev trend. I can't tell whether front-end dev culture is a massive circle-jerk or cargo cult. And don't mention the irrational hate attempted to be heaped onto anyone who dares question the programmatic thinking of the official line of the React Appreciation Society.

hombre_fatal 7y ago
Is there anything more in-bad-faith than assuming everyone who uses X is just an idiot, trend-follower, or beginner? Unlike you, the Enlightened One? Why not just ask people why they use X? Plenty of veteran developers on HN could tell you why they like React despite a sea of alternatives, but it's easier to just cast aspersions instead of understanding. It's a shame to see this on HN which is supposedly a community of craftspeople who build things. If you can only come up with insults for why another group of people do something, it's time for you to get up off your ass and ask someone in that group. And this extends beyond just engineering, it's how you understand other people in general.
- dosy 7y ago
  That's a bit mean, don't you think? See I was addressing a group of people but you're directly saying that to me. Hmmm, well, why don't you take your own advice pal and ask me why I think so? Oh, that's right, I guess you were just trying to insult people rather than understand. Hahahaa. But anyway, I am thoroughly enjoying your attempt at self-righteousness. Keep working on that, you've nearly got it. And I'm very grateful to you for proving my point. You may be old, but are you sure I don't understand people and you do? I don't think "bad faith" means what you think it means, but I take it by the vehemence of your response that I struck a nerve. And I think you might just be projecting. See, I think you're angry because you must use React, and me reminding you other choices exist, which you nevertheless cannot access, reminds you of that embarrassing lack of freedom. So you choose to double down on defending something you don't really want anyway. But I guess you don't really understand how you feel about it, so you just project and blame somebody else. If you didn't like React, would you ever say no to an offer that insisted on it? See, I don't think you would. But I have. I wanna work with what I like. I think if you really loved it and knew why you wouldn't be so perturbed. I'm just curious, why no submissions? Why anonymous? Would you talk so big, if everyone knew your name? Or are you only a loud mouth if you've got no skin in the game, really? Anyway, have a good day thinkin about that, pal and if you wanna know more please read my answer for "debuzzybee" and my comment she linked.