5 ms·

I second tailwind as the way, and I'm using it along with web components. I think the important aspect of React/Vue was to inspire Web Components to exist. Now

I second tailwind as the way, and I'm using it along with web components. I think the important aspect of React/Vue was to inspire Web Components to exist. Now that I can leverage Web Components, I don't see a real need for React as the browser is very capable. For me, I'm building https://www.adama-platform.com/ https://www.adama-platform.com/ which is a reactive backend which then makes building reactive/interactive applications very simple. With tailwind, I can just copy and paste HTML snippets and make it live with data. So much fun!

nickcox 4y ago
> I think the important aspect of React/Vue was to inspire Web Components to exist Web Components predate React as an idea, don't they? Admittedly it too hella long to get them properly standardised.
- bigDinosaur 4y ago
  React as an idea predates React too ;-P
dmitriid 4y ago
> Now that I can leverage Web Components, I don't see a real need for React as the browser is very capable. Except for the long list of issues that WC proponents pretend doesn't exist: https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728
- mathgladiator 4y ago
  Damn, now I have to pretend those don't exist. I have to investigate how it breaks a11y as that seems to the the core killer in my case. How does that list square with https://shoelace.style/ https://shoelace.style/ ?
  - dmitriid 4y ago
    The linked tweet in the linked tweet gives one such example: https://twitter.com/sarahmei/status/1198069119897047041 https://twitter.com/sarahmei/status/1198069119897047041 I remember there being more, but I can't remember the links off the top of my head (and on mobile).
- ramesh31 4y ago
  >Except for the long list of issues that WC proponents pretend doesn't exist: https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728 This is the sad reality for web components. You end up needing so many libraries to do basic things that a framework would handle, that your project just becomes a defacto custom framework.
ssorallen 4y ago
Alex Russell introduced Web Components in 2011. React was released in 2013. Web Components originally used a view-model architecture, which I would guess was heavily inspired by the most popular JS framework leading up to 2011: Backbone. React was a massive departure from Backbone, and sadly the Web Components spec was developed before React had matured and changed the landscape.
- mathgladiator 4y ago
  Thanks for the correction
- Shorel 4y ago
  I think it was Angular.js the framework that made us jump from JQuery to the modern way to do things. Backbone was never that popular. Angular.JS was created in 2009 and released in 2010.
  - ssorallen 4y ago
    Yup good call, Angular.js seems more likely than Backbone now that you mention it.
darepublic 4y ago
Sorry to say but you should brush up your UI on mobile firefox

nickcox 4y ago

> I think the important aspect of React/Vue was to inspire Web Components to exist Web Components predate React as an idea, don't they? Admittedly it too hella long to get them properly standardised.

bigDinosaur 4y ago
React as an idea predates React too ;-P

dmitriid 4y ago

> Now that I can leverage Web Components, I don't see a real need for React as the browser is very capable. Except for the long list of issues that WC proponents pretend doesn't exist: https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728

mathgladiator 4y ago
Damn, now I have to pretend those don't exist. I have to investigate how it breaks a11y as that seems to the the core killer in my case. How does that list square with https://shoelace.style/ https://shoelace.style/ ?
- dmitriid 4y ago
  The linked tweet in the linked tweet gives one such example: https://twitter.com/sarahmei/status/1198069119897047041 https://twitter.com/sarahmei/status/1198069119897047041 I remember there being more, but I can't remember the links off the top of my head (and on mobile).
ramesh31 4y ago
>Except for the long list of issues that WC proponents pretend doesn't exist: https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728 This is the sad reality for web components. You end up needing so many libraries to do basic things that a framework would handle, that your project just becomes a defacto custom framework.

ssorallen 4y ago

Alex Russell introduced Web Components in 2011. React was released in 2013. Web Components originally used a view-model architecture, which I would guess was heavily inspired by the most popular JS framework leading up to 2011: Backbone. React was a massive departure from Backbone, and sadly the Web Components spec was developed before React had matured and changed the landscape.

mathgladiator 4y ago
Thanks for the correction
Shorel 4y ago
I think it was Angular.js the framework that made us jump from JQuery to the modern way to do things. Backbone was never that popular. Angular.JS was created in 2009 and released in 2010.
- ssorallen 4y ago
  Yup good call, Angular.js seems more likely than Backbone now that you mention it.

darepublic 4y ago

Sorry to say but you should brush up your UI on mobile firefox