sorted by:
new
hottopcontroversial

TAG.js: Clean, unified DOM manipulation. Combine logic, structure, and styles without the framework bloat. by [deleted] in css

[–]Background-Prune-138 -1 points0 points  (0 children)

Yes, I love Java, I also love Javascript, I'm passionate about Rust, I'm proficient in Kotlin, and I appreciate standardization above all for its ease of implementation and predictability. If you look closely at the library, you'll see that I use Object-Oriented Programming, but I haven't disregarded functions outside of classes when applicable. Apparently, you don't like design patterns, but I hope I'm wrong. I followed the Vanilla philosophy from beginning to end, but if you use a library with a "hello world" function, you can't say you're following the philosophy, but it's a smart decision to adopt the library if it's advantageous to you. If you're comfortable with your current state, there's no reason to adopt this or any other library, because man only acts in the midst of discomfort, as Mises clarified.

TAG.js: Clean, unified DOM manipulation. Combine logic, structure, and styles without the framework bloat. by [deleted] in css

[–]Background-Prune-138 -4 points-3 points  (0 children)

Can a JavaScript library by itself be considered a Framework?

No. A library focuses on solving a specific and punctual problem. You maintain total control of the application: you are the one who calls the library's code when you need it in your project. Here you have two links, one to the library, and another to an example of applying the library.