

-
The jQuery UI Datepicker widget[0] still remains my favourite date picker implementation, even though it sadly never supported mobile phones that well.
Non-confusing design, live-reacting to user typing the date with keyboard, accessible, configurable, and offering 0-effort localisation in 60+ languages[1].
Is there anything like this in React world?
[0] https://jqueryui.com/datepicker/#dropdown-month-year
[1] https://github.com/jquery/jquery-ui/tree/main/ui/i18n
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
headlessui
Completely unstyled, fully accessible UI components, designed to integrate beautifully with Tailwind CSS.
Guys, didn't you get the memo? We're doing this differently now, we've replaced
https://github.com/jquery/jquery-ui/blob/main/ui/widgets/tab...
with the much better, much simpler, more readable and not at all depending on 42(!) modules
https://github.com/tailwindlabs/headlessui/blob/main/package...
What joy!
-
I've been using the likes of PrimeVue (https://primevue.org/), PrimeReact (https://primereact.org/) and PrimeNG (https://primeng.org/) because they attempt to give you a library of components that work well out of the box and have a similar API across multiple technologies: Vue, React and Angular, respectively.
I feel like at some point I'll probably make a project with just jQuery and possibly jQuery UI for the sake of it, since what's there doesn't seem too flashy, but would probably work just fine for most we based CRUD needs. I might end up rediscovering up close why people moved to the above in droves instead of jQuery, but honestly something that you just drop in and that works has a lot of appeal. No complex toolchains, no configuring a bunch of plugins and registering them with the app, no endless abstractions for state management and things about render loops to keep in mind, just a silly JS import and writing some shlocky code that still sorta works.
I like to consider the UI of Kanboard as a good example. It's minimalist, but works great for what it is: https://kanboard.org/
-
I've been using the likes of PrimeVue (https://primevue.org/), PrimeReact (https://primereact.org/) and PrimeNG (https://primeng.org/) because they attempt to give you a library of components that work well out of the box and have a similar API across multiple technologies: Vue, React and Angular, respectively.
I feel like at some point I'll probably make a project with just jQuery and possibly jQuery UI for the sake of it, since what's there doesn't seem too flashy, but would probably work just fine for most we based CRUD needs. I might end up rediscovering up close why people moved to the above in droves instead of jQuery, but honestly something that you just drop in and that works has a lot of appeal. No complex toolchains, no configuring a bunch of plugins and registering them with the app, no endless abstractions for state management and things about render loops to keep in mind, just a silly JS import and writing some shlocky code that still sorta works.
I like to consider the UI of Kanboard as a good example. It's minimalist, but works great for what it is: https://kanboard.org/
-
I've been using the likes of PrimeVue (https://primevue.org/), PrimeReact (https://primereact.org/) and PrimeNG (https://primeng.org/) because they attempt to give you a library of components that work well out of the box and have a similar API across multiple technologies: Vue, React and Angular, respectively.
I feel like at some point I'll probably make a project with just jQuery and possibly jQuery UI for the sake of it, since what's there doesn't seem too flashy, but would probably work just fine for most we based CRUD needs. I might end up rediscovering up close why people moved to the above in droves instead of jQuery, but honestly something that you just drop in and that works has a lot of appeal. No complex toolchains, no configuring a bunch of plugins and registering them with the app, no endless abstractions for state management and things about render loops to keep in mind, just a silly JS import and writing some shlocky code that still sorta works.
I like to consider the UI of Kanboard as a good example. It's minimalist, but works great for what it is: https://kanboard.org/
-
I've been using the likes of PrimeVue (https://primevue.org/), PrimeReact (https://primereact.org/) and PrimeNG (https://primeng.org/) because they attempt to give you a library of components that work well out of the box and have a similar API across multiple technologies: Vue, React and Angular, respectively.
I feel like at some point I'll probably make a project with just jQuery and possibly jQuery UI for the sake of it, since what's there doesn't seem too flashy, but would probably work just fine for most we based CRUD needs. I might end up rediscovering up close why people moved to the above in droves instead of jQuery, but honestly something that you just drop in and that works has a lot of appeal. No complex toolchains, no configuring a bunch of plugins and registering them with the app, no endless abstractions for state management and things about render loops to keep in mind, just a silly JS import and writing some shlocky code that still sorta works.
I like to consider the UI of Kanboard as a good example. It's minimalist, but works great for what it is: https://kanboard.org/
-
indeed, good description. Noting that vue etc. are MVC in the browser, with (typically) calls to json http endpoints on the back end to read/write data.
JQuery was born in a time of server-side rendering (SSR) where, in essence, MVC happened in the back end and it shipped html to the browser. In that model, the browser is essentially a terminal that renders output formed in the back end. JQuery was one of the early libraries to promote behaviour in the browser instead of "browser as terminal".
It feels like there's bit of a swing back to the SSR model, e.g. with the growing popularity of htmx [0] though there are still many strong proponents of the MVC-in-browser approach.
[0] https://htmx.org/
-
Nutrient
Nutrient – The #1 PDF SDK Library, trusted by 10K+ developers. Other PDF SDKs promise a lot - then break. Laggy scrolling, poor mobile UX, tons of bugs, and lack of support cost you endless frustrations. Nutrient’s SDK handles billion-page workloads - so you don’t have to debug PDFs. Used by ~1 billion end users in more than 150 different countries.