Forum Discussion
No more jQuery?
This is actually a much better reasoning than I've read today for removing the library. That said, to silently pull it without any notification does put some of us in a bind. At the very least, some sort of announcement could have been made like "on Jan 1, 2021 will will discontinue using jQuery. We will be using "whatever" which is included as of our most recent release. Please make the modifications necessary for migration.
Technology will always follow trends, it will always evolve - that said, we should have some time to plan when these decisions are made for us. And I do completely understand that it wasn't supported (as JS isn't), but there are times when we have no choice but to use other methods to resolve either bugs that aren't fixed for months or years, or to make some functionality happen that we've asked for in feature requests that have never been implemented (i.e. detect changes in text fields as people are typing without needing to "blur" the field).
The other thing that is probably rarely considered is when folks build (via contract) courses for clients and hand them off. What happens when they update? What extra steps do they have to go through? Do these contractors have to dig through their records and notify all their clients to make the more-than-text changes they may not be comfortable doing (which is why they often hire contractors in the first place)?
There are just a lot of impacts to such a change that don't seem like they were considered.
- WaltHamilton6 years agoSuper Hero
The other thing that is probably rarely considered is when folks build (via contract) courses for clients and hand them off. What happens when they update?
Wait, If the newest version of SL doesn't support it, does that mean that published courses are affected, too?