5 ms·

React was first released 9 years ago, more than a “hype”, it is still a great success! (And source of my economic wealth too) - a cheap developer

halostatue 4y ago
I’m glad you like it. Someone has to, I guess. I can’t stand it and find all the promotion on it to be promising far more than it delivers. It’s heavier, slower, less comprehensive, and less comprehensible than either Vue, Svelte, or most Vanilla JS implementations of component-oriented sites that I’ve seen. Every single thing about React bothers me, from hooks to JSX (which is so much worse than meaningful templates), and I’d rather use something that makes me happy.
- Spivak 4y ago
  After using Dominate, Hiccup, Slim, and JSX, CDK, I have no desire for templating HTML (or anything) on the level of strings anymore. It’s so stupidly clunky, doesn’t compose well, is hard to mutate, hard to test, you have to deal with all the weirdness of your templating language, logic is split across your controllers and templates.
  - halostatue 4y ago
    We’re talking about templates in the context of component libraries. In particular, I’m highlighting the template languages of smaller, more capable component library systems than React — Vue (2 and 3) and Svelte. In both Svelte and Vue (both versions), Single File Components are the standard. Yes, there’s logic in your template, but it’s closely related to the core business logic, and it reads a lot better than embedded logic in JSX droppings. On the rest of it, I’d agree that a lot of the JavaScript-based pure templating languages don’t really work well, but IMO that has more to do with JavaScript than the templating languages. I find EEX (Elixir), ERB (Ruby), and Jinja (Django-ish, plus others), Liquid (Ruby / Shopify), and Text Templates (Go) to all be pretty good for what they do — and most of them are templating languages that can be applied to HTML, but are not HTML "native" templating languages (even though some have HTML "native" variants, e.g., HTML templates for Go).
- selfmodruntime 4y ago
  > I’m glad you like it. Someone has to, I guess Millions of people and companies do. For mostly one reason: Getting started is incredibly simple. React's surface area is incredibly narrow. Almost anything in it is just JavaScript. Hooks or Classes? Syntax inside JSX? Just normal JavaScript. With hooks, there are basically two that can do 99% of what you want to do. > which is so much worse than meaningful templates Why? There is a zero bullshit approach here. No magic syntax. No "v-for" or two way binding. No receiver patters or context parameters.
  - ramesh31 4y ago
    >There is a zero bullshit approach here. No magic syntax. No "v-for" or two way binding. No receiver patters or context parameters. Amen. I have zero interest in learning Yet Another Template DSL ever again. React won the framework wars because it's just javascript.
    - Existenceblinks 4y ago
      It's not. Practically everyone is using JSX. And it doesn't run on browsers.
      - lucas_codes 4y ago
        JSX is just sugar for React.createElement(...)
        Existenceblinks 4y ago
        Doesn't invalidate that it doesn't run on browsers.
  - gentleman11 4y ago
    > Getting started is incredibly simple. Create react app drags in about a million dependencies, and I’ve never met somebody able to make a react app work without it. That’s not “simple” in my book, create-react-app is a tool that so many people are dependent on that it deforms a lot of architectures to avoid having to modify it, using proxies etc

halostatue 4y ago

I’m glad you like it. Someone has to, I guess. I can’t stand it and find all the promotion on it to be promising far more than it delivers. It’s heavier, slower, less comprehensive, and less comprehensible than either Vue, Svelte, or most Vanilla JS implementations of component-oriented sites that I’ve seen. Every single thing about React bothers me, from hooks to JSX (which is so much worse than meaningful templates), and I’d rather use something that makes me happy.

Spivak 4y ago
After using Dominate, Hiccup, Slim, and JSX, CDK, I have no desire for templating HTML (or anything) on the level of strings anymore. It’s so stupidly clunky, doesn’t compose well, is hard to mutate, hard to test, you have to deal with all the weirdness of your templating language, logic is split across your controllers and templates.
- halostatue 4y ago
  We’re talking about templates in the context of component libraries. In particular, I’m highlighting the template languages of smaller, more capable component library systems than React — Vue (2 and 3) and Svelte. In both Svelte and Vue (both versions), Single File Components are the standard. Yes, there’s logic in your template, but it’s closely related to the core business logic, and it reads a lot better than embedded logic in JSX droppings. On the rest of it, I’d agree that a lot of the JavaScript-based pure templating languages don’t really work well, but IMO that has more to do with JavaScript than the templating languages. I find EEX (Elixir), ERB (Ruby), and Jinja (Django-ish, plus others), Liquid (Ruby / Shopify), and Text Templates (Go) to all be pretty good for what they do — and most of them are templating languages that can be applied to HTML, but are not HTML "native" templating languages (even though some have HTML "native" variants, e.g., HTML templates for Go).
selfmodruntime 4y ago
> I’m glad you like it. Someone has to, I guess Millions of people and companies do. For mostly one reason: Getting started is incredibly simple. React's surface area is incredibly narrow. Almost anything in it is just JavaScript. Hooks or Classes? Syntax inside JSX? Just normal JavaScript. With hooks, there are basically two that can do 99% of what you want to do. > which is so much worse than meaningful templates Why? There is a zero bullshit approach here. No magic syntax. No "v-for" or two way binding. No receiver patters or context parameters.
- ramesh31 4y ago
  >There is a zero bullshit approach here. No magic syntax. No "v-for" or two way binding. No receiver patters or context parameters. Amen. I have zero interest in learning Yet Another Template DSL ever again. React won the framework wars because it's just javascript.
  - Existenceblinks 4y ago
    It's not. Practically everyone is using JSX. And it doesn't run on browsers.
    - lucas_codes 4y ago
      JSX is just sugar for React.createElement(...)
      - Existenceblinks 4y ago
        Doesn't invalidate that it doesn't run on browsers.
- gentleman11 4y ago
  > Getting started is incredibly simple. Create react app drags in about a million dependencies, and I’ve never met somebody able to make a react app work without it. That’s not “simple” in my book, create-react-app is a tool that so many people are dependent on that it deforms a lot of architectures to avoid having to modify it, using proxies etc