5 ms·

Sure jQuery as a selector engine has more or less been replaced, css has advanced etc. But the jQuery UI widgets are battle hardened and easier to deploy, case

Sure jQuery as a selector engine has more or less been replaced, css has advanced etc. But the jQuery UI widgets are battle hardened and easier to deploy, case in point , date pickers, calendaries and well, slideshows. And you can kind of replicate some of reacts behaviour regarding state management. If all you need to do is keep state on a handful of elements, there is no need to develop in react. Infact, just like the jquery heydays, react is often overused, for the most simply web forms, menus, footers. And, no need for router and other state management tools. Might be a bit unpopular, but when its all said and done, its compiled to js either way, I kinda like jquery or vanilla js for the front end and node/express for the back end. The amount of react devs which struggle with css and vanilla js appears to be higher than during the jquery days.

flatiron 4y ago
My job has a lot of little customers with little projects and some older ones were made with jquery and we keep on keeping on. Why not? Also if we have to make similar projects we branch from older ones. So some of our current development uses jquery which raises some eyebrows but nothing like using 95% battle hardened code than starting fresh because…
texxtxxet 4y ago
Why not components from a React library like Material UI? jQuery UI is "in a maintenance state" and "older long-standing bugs may not get fixed" I'm afraid https://blog.jqueryui.com/2022/07/jquery-ui-1-13-2-released/ https://blog.jqueryui.com/2022/07/jquery-ui-1-13-2-released/
- mattmanser 4y ago
  Why? Material's dead, adding React is adding a massive amount of bloat and build steps. You need to have a reason to pay the price of React. Otherwise you're just being a sheep. I say this using React and Material UI in a present project, from my perspective development for what is a pretty simple form UI is massively slowed down by using them. Could have knocked out the whole site on my own in 1/2 the time using the 'old' stuff. But now we've got a lovely loading spinner while it downloads everything it needs piecemeal and a bunch of basic browser functionality is broken, we've got 10x the amount of code, have to deal with a whole extra API layer and it's a nightmare to debug sitting there watching network calls instead of being able to step through the code in a proper debugger, brilliant stuff. Completely worth it for that one datepicker we have.
  - deleted 4y ago
    [deleted]
  - farmin 4y ago
    Is Material dead? What replaced it?
  - nasmorn 4y ago
    In my clients company they usually even implement admin crud UI as api + React and it takes them so much longer than just whipping up some forms in Rails. They just do this as a default state of doing things not because they actually need an extra api for anything.
MuffinFlavored 4y ago
> date pickers <input type="date"> is too rough I'm guessing? I'm not exactly sure where it falls short personally.
- iambateman 4y ago
  There’s a million edge cases for dates that make it hard to use the bare-metal tools.
- Beltalowda 4y ago
  I really dislike how most desktop browsers display them. Plus you can't easily do things like "display start date while selecting end date".
Beltalowda 4y ago
I rather like jQuery as it just patches over so much of the DOM API, which offends my sensibilities of what a "good API" should look like. I don't think the jQuery API is perfect, but it's a lot better. But I never really liked jQuery UI, either as a user or developer. As a user, the whole "desktop semantics in your browser" is one of those things that was worth trying 15 years ago, but it mostly never really worked all that well, and pretty much everyone has dropped it. As a developer I feel jQuery UI is too complex for what it does, partly because of the above. At any rate, jQuery and jQuery UI are two entirely different projects.
- noidiocyallowed 4y ago
  Josh Comeau and the jQ team should sit down together and create a state of the art, kickass UI component library with nifty buttons and similar cool ui elements.
jamesfinlayson 4y ago
I don't use much jQuery any more but I thought it papered over a few bugs in browser bugs (I vaguely recall jQuery having to work around a DOM selector bug in mobile Safari in the last seven or so years).
PointyFluff 4y ago

flatiron 4y ago

My job has a lot of little customers with little projects and some older ones were made with jquery and we keep on keeping on. Why not? Also if we have to make similar projects we branch from older ones. So some of our current development uses jquery which raises some eyebrows but nothing like using 95% battle hardened code than starting fresh because…

texxtxxet 4y ago

Why not components from a React library like Material UI? jQuery UI is "in a maintenance state" and "older long-standing bugs may not get fixed" I'm afraid https://blog.jqueryui.com/2022/07/jquery-ui-1-13-2-released/ https://blog.jqueryui.com/2022/07/jquery-ui-1-13-2-released/

mattmanser 4y ago
Why? Material's dead, adding React is adding a massive amount of bloat and build steps. You need to have a reason to pay the price of React. Otherwise you're just being a sheep. I say this using React and Material UI in a present project, from my perspective development for what is a pretty simple form UI is massively slowed down by using them. Could have knocked out the whole site on my own in 1/2 the time using the 'old' stuff. But now we've got a lovely loading spinner while it downloads everything it needs piecemeal and a bunch of basic browser functionality is broken, we've got 10x the amount of code, have to deal with a whole extra API layer and it's a nightmare to debug sitting there watching network calls instead of being able to step through the code in a proper debugger, brilliant stuff. Completely worth it for that one datepicker we have.
- deleted 4y ago
  [deleted]
- farmin 4y ago
  Is Material dead? What replaced it?
- nasmorn 4y ago
  In my clients company they usually even implement admin crud UI as api + React and it takes them so much longer than just whipping up some forms in Rails. They just do this as a default state of doing things not because they actually need an extra api for anything.

MuffinFlavored 4y ago

> date pickers <input type="date"> is too rough I'm guessing? I'm not exactly sure where it falls short personally.

iambateman 4y ago
There’s a million edge cases for dates that make it hard to use the bare-metal tools.
Beltalowda 4y ago
I really dislike how most desktop browsers display them. Plus you can't easily do things like "display start date while selecting end date".

Beltalowda 4y ago

I rather like jQuery as it just patches over so much of the DOM API, which offends my sensibilities of what a "good API" should look like. I don't think the jQuery API is perfect, but it's a lot better. But I never really liked jQuery UI, either as a user or developer. As a user, the whole "desktop semantics in your browser" is one of those things that was worth trying 15 years ago, but it mostly never really worked all that well, and pretty much everyone has dropped it. As a developer I feel jQuery UI is too complex for what it does, partly because of the above. At any rate, jQuery and jQuery UI are two entirely different projects.

noidiocyallowed 4y ago
Josh Comeau and the jQ team should sit down together and create a state of the art, kickass UI component library with nifty buttons and similar cool ui elements.

jamesfinlayson 4y ago

I don't use much jQuery any more but I thought it papered over a few bugs in browser bugs (I vaguely recall jQuery having to work around a DOM selector bug in mobile Safari in the last seven or so years).

PointyFluff 4y ago