6 ms·

I just went back to plain JS & jQuery for all of my front-end work. None of my clients are bothered. Frameworks maybe make more sense from an organisation pers

I just went back to plain JS & jQuery for all of my front-end work. None of my clients are bothered. Frameworks maybe make more sense from an organisation perspective of having to create the same thing in different variations but for sheer simplicity & understanding of what's actually happening plain JS/jQuery seems like a breath of fresh air.

rgbrenner 6y ago
Why jquery though? Is it even being maintained anymore? You know you can use vuejs on a single page.. just add it like you would jquery.. much nicer if you’re going to go that route.
- ijidak 6y ago
  > Why jquery though? Is it even being maintained anymore? I see they're pushing one release a year. Last release was in April/May. I hope it's being maintained. At this point, I view jQuery as a foundational library. I know newer versions of HTML and browser APIs are replacing some of the need for jQuery. But its ergonomics are universally understood. For me that's as important as the APIs themselves. And I don't trust browser vendors to maintain uniformity long-term. Too many egos involved. I hope jQuery never dies.
- cheschire 6y ago
  As long as jquery keeps getting pushed in the default .NET templates, it will keep living.
commandlinefan 6y ago
I spent a LOT of time staring at Angular trying to figure out what problem it was actually supposed to be solving and finally gave up. If it actually does something useful, it's beyond my comprehension.
- ozim 6y ago
  Did you ever had to manage or lead team of 5 to 10 developers? Have you seen web application implemented in MVC+jQuery where each page was developed by different person and everyone was just making their own approach. Then when something was to be fixed and other person was taking over he was introducing his own ideas to code already written by someone else. That is what angular solves for me, I don't have to spend time introducing new person to the project structure. I don't have to argue with "I know better juniors", I don't have to deal with condescending seniors "who wrote it that way it is total mess". Maybe you have seen some project handover to different team or you got project inherited from someone. It will be a lot easier to understand if that other team speaks "angular". I don't say code is perfect, you can still write total mess with it, but having angular saves a lot of digging into some insane monstrosities that I have seen in jQuery. In the end you might never need it, because everyone has different requirements and different projects.
  - commandlinefan 6y ago
    See that's the thing - and I'm not being confrontational or sarcastic, I genuinely don't understand - when I've seen Angular code it still looks to me like each page was developed by a different person and everyone was just making their own approach (unless, of course, it was all written by a single person). It seems to me that what you're suggesting is that using Angular forces developers "into a box" (in a good way), but I can't figure out what that box actually is.
    - ozim 6y ago
      I would like to have a good explanation that might suit you. But I don't think there is a way to find it out without sitting together and working through some code.
- villgax 6y ago
  The uncertainty of issues ever being fixed or given importance is a huge concern which people when looking for suitable MVC framework overlook. Something simpler than ng/React, yet able to compose architectures with plain JS, all without compiling front-end.
lcfcjs 6y ago
Binding variables alone is worth the switch. EDIT: by binding variables i mean displaying variables in HTML, changing the variable within the component and have it re-render automatically. Anyone who builds anything beyond "hello world" will recognize this.
IggleSniggle 6y ago
I started in web after jQuery was on its way out (and many of its most useful features had already been incorporated into vanilla JS). What is actually the point of jQuery in greenfield projects in 2020? Is it just that it's a more concise syntax for DOM queries, or is there something more?

rgbrenner 6y ago

Why jquery though? Is it even being maintained anymore? You know you can use vuejs on a single page.. just add it like you would jquery.. much nicer if you’re going to go that route.

ijidak 6y ago
> Why jquery though? Is it even being maintained anymore? I see they're pushing one release a year. Last release was in April/May. I hope it's being maintained. At this point, I view jQuery as a foundational library. I know newer versions of HTML and browser APIs are replacing some of the need for jQuery. But its ergonomics are universally understood. For me that's as important as the APIs themselves. And I don't trust browser vendors to maintain uniformity long-term. Too many egos involved. I hope jQuery never dies.
cheschire 6y ago
As long as jquery keeps getting pushed in the default .NET templates, it will keep living.

commandlinefan 6y ago

I spent a LOT of time staring at Angular trying to figure out what problem it was actually supposed to be solving and finally gave up. If it actually does something useful, it's beyond my comprehension.

ozim 6y ago
Did you ever had to manage or lead team of 5 to 10 developers? Have you seen web application implemented in MVC+jQuery where each page was developed by different person and everyone was just making their own approach. Then when something was to be fixed and other person was taking over he was introducing his own ideas to code already written by someone else. That is what angular solves for me, I don't have to spend time introducing new person to the project structure. I don't have to argue with "I know better juniors", I don't have to deal with condescending seniors "who wrote it that way it is total mess". Maybe you have seen some project handover to different team or you got project inherited from someone. It will be a lot easier to understand if that other team speaks "angular". I don't say code is perfect, you can still write total mess with it, but having angular saves a lot of digging into some insane monstrosities that I have seen in jQuery. In the end you might never need it, because everyone has different requirements and different projects.
- commandlinefan 6y ago
  See that's the thing - and I'm not being confrontational or sarcastic, I genuinely don't understand - when I've seen Angular code it still looks to me like each page was developed by a different person and everyone was just making their own approach (unless, of course, it was all written by a single person). It seems to me that what you're suggesting is that using Angular forces developers "into a box" (in a good way), but I can't figure out what that box actually is.
  - ozim 6y ago
    I would like to have a good explanation that might suit you. But I don't think there is a way to find it out without sitting together and working through some code.
villgax 6y ago
The uncertainty of issues ever being fixed or given importance is a huge concern which people when looking for suitable MVC framework overlook. Something simpler than ng/React, yet able to compose architectures with plain JS, all without compiling front-end.

lcfcjs 6y ago

Binding variables alone is worth the switch. EDIT: by binding variables i mean displaying variables in HTML, changing the variable within the component and have it re-render automatically. Anyone who builds anything beyond "hello world" will recognize this.

IggleSniggle 6y ago

I started in web after jQuery was on its way out (and many of its most useful features had already been incorporated into vanilla JS). What is actually the point of jQuery in greenfield projects in 2020? Is it just that it's a more concise syntax for DOM queries, or is there something more?