Комментарии:
Right, but when does one know enough JavaScript to learn a framework? I mean, vanilla JS is really extensive in my opinion, it's never enough.
ОтветитьWhy are people even asking you this. It’s so obvious why you do.
ОтветитьFar too many devs do not understand the basics and it is a massive problem
ОтветитьI know someone wh o is quite a good react developer and earns wel above six figures remote in the Netherlands (that's insane) and i've asked him for some help before and I was shocked to hear he had no idea how keyframes work in CSS and that he. doesn't know what a document.xSelector is...
jQuery was. different beast tho. That revolutionaired some aspects.
In this spirit of this video, I trust you and would also like to hear your opinion on the pros and cons of adding these frameworks on to our vanilla JS and CSS knowledge, especially Tailwind and other CSS-as-a-thousand-classes libraries.
ОтветитьAbsolutely agree .. people that cannot turn a simple HTML page into react really ought to go back to the basics
ОтветитьNot me, doing the exact same thing he was talking about
ОтветитьOn my experience about learning of react, well I didn't skip the basic fundamentals of javascript and then so on I still learning of the javascript while learning react so I don't have any problem with not mastering javascript before jumping on react because on react we still using javascript, I don't argue about using tailwindcss and not learning css well yeah that's a big problem, much better to learn css before taking a framework or library, we know that tailwindcss is css but we don't see actually or we don't code actually css code because we just putting a class we don't even code a css.
ОтветитьThank you, Kevin. As someone struggling in a bootcamp just now I'm just at the point, where to focus on. (It is probably inherent to bootcamps to race through the subject matter, to be confronted with React and Next while still contemplating arrays and loops, while parts of the brain still linger in fascination with the multitude of possibilities of CSS).
Your video provides me with a guiding light and also the excitement for further learning after this bootcamp. However, to be fair, the bootcamp at least enables me to understand what you are talking about. I am a complete beginner and hope to experience moments of enthusiasm again and again.
Sadly, more and more people is becoming frameworkers, and not actual programmers.
ОтветитьThis is the reason I stopped using tailwind - I felt like I wasn't learning CSS. Same w/ jQuery. I learned to use it; then did a deep dive into JS and wondered why I ever used jQuery.
ОтветитьLove it! I actually don’t like react and it’s a hard concept because I can do it faster in JS. It makes finding a high paying job difficult though.
ОтветитьI made this mistake and I'm still recovering.
ОтветитьCool cool, but how do I write vanilla js in React?
ОтветитьGreat takes, Kevin.
These could fall under the "common sense" category but the noise and hype around new tech are overwhelming.
Hope this video reaches people on their early education!
Thanks for the content.
Exactly! Thanks a lot for bringing up these points, Kevin.
ОтветитьSir. You speak much truth. Thank you.
ОтветитьBTW which frameworks you use regulary... or use own written html css and js?
ОтветитьHey Kevin, please consider adding RSS to your newsletter. It's a great alternative to having your email flooded with newsletter content.
ОтветитьBetter to have a strong foundation
ОтветитьJQuery is still quite popular according to the stackoverflow survey. I've switched to mostly vanilla years ago due to different libraries and frameworks never doing quite what I need and I was fed up with having to bend them to my will and then there's all the extra bloat. I got rid of almost everything and performance is way up and projects are actually simpler. I do still use JQuery (NOT jquery ui) as I do actually still find it quite handy.
Ответитьi fell for this..just discovered u recently with another full long length video and i wanted to thank you for putting this out there.
ОтветитьHey Kevin, You're amazing. Thanks for being you. Thanks for sharing your knowledge.
ОтветитьFun challenge idea:
Do one of Kevin's tutorials/projects using your framework/library of choice.
Love this! I think it’s sad that so many developers tout using Tailwind. I get it… it makes things a little faster. But I love making my own design systems from scratch. I love the craft. It’s the same reason I didn’t ride my bike with training wheels when I was a kid. Sure, you’ll fall and get hurt, but each of those moments (hopefully) teaches a valuable lesson.
ОтветитьI have often thought about trying out a Java Script framework, but when I see in the tutorials what simple things are programmed I ask myself why you need these frameworks when you can program such simple things much faster with pure Java Script and HTML... in the time where you try to install the framework. Also I don't understand why you need to install a 300 MB framework to code some buttons ect.
Ответитьi think you have a point. there is a gap between building tutorials and understanding fundamental tutorials
ОтветитьI totally get that. But I was actually just wondering what you use. Is there a video about that? cheers! :-)
ОтветитьThanks for this video, reached me just in time.😊
ОтветитьWell said. Start your journey with machine language / assembler. If that seems complicated: consider a career in accounting or politics...
ОтветитьI would say, before learning Javascript itself, try to do some coding in C or C++. Only then will you appreciate what kind of sophistication Javascript provides.
ОтветитьOk here are a list of reasons why React.js is bad.
1)Web components exist in pure vanila javascript without any external library or framework and react is literally abusing those to promote their own product.
And thats because developers lack of core JavaScript knowledge
2)Piles of junk, if you gave it some effort you would realize that actually creating your own framework for custom web componenets will be much more performance friendly and easier to maintain with no extra 90% of junk coming along with React.
3)Bad data manipulation being handled by third library’s like redux makes it even heavier and harder to use ,unlike JS global object - or session storages.
4)The syntax is terrible, it’s like learning new javascript and new CSS and new HTML.
starting with inline styles to little different things like onClick, that makes it hard to remember those small changes.
5(they say its good because its components are modular?!)
No one ever uses the same element arrangement and styles/animations in any serious design, so you end up with piles of files and importing/exporting and at the end of the day you end up creating a totally new component that suits your design.
The list goes on and on, but i cant write any more…
Blink!
ОтветитьI hate tailwind... It makes html structure difficult to read.. SCSS is much better.
ОтветитьSpot on, I have been working on the Fullstack Web ecosystem for a while, mainly React, and I got to a point where the line between React/Frameworks/SPAs gibberish was too far from native browser modules and behavior. I'm trying to work with vanilla a lot more since it seems like a better investment of my time. At the end of the day we write stuff that is rendered by a web browser and should stick to that.
ОтветитьI wish I could shake your hand! I am so grateful for everything you teach, and the principles with which you do so.
ОтветитьAfter stepping back and really taking the time to learn CSS, I now have whole new respect for CSS frameworks and what they can do for you. I also realized why I didn't really need them at all.
ОтветитьI love JQuery and used it for many years, but nowadays Vanilla JS can do anything and everything and I don't see the point of using any layer on top of it.
Frameworks are creating deep rooted dependencies, it will be a nightmares as soon as they loose a fraction of their support. No thanks!
Please when do you think one should learn tailwind?
ОтветитьNobody ever thought jQuery would die one day.
I started to shun frameworks in general, when a framwork I used died. So did the app. And it was a full program, which meant it had to be rewritten, or stick with the last version of the framework.
Written in vanilla language is slower in the beginning compared to a framework. But in the long run, you may never need to rewrite from scratch. That is when you save a ton of time.
I much prefer writing code in vanilla. I have full control over what the code is doing. I have no bloat from imported libraries that are doing what I am doing, only with extra code behind the scenes parsing the library implementation, and that also have extra things in their modules that I have no use for at that particular time. For my project, would I write a bunch of functions and classes I will never use? No. Why would I. Vanilla code is (to me) cleaner, and it is going to be more efficient to run, as it's not calling on functions and classes within a library to do same code that is basically the same as the vanila code I have written. Using a library is like writing vanilla code, but for everything you do, you add new functions to call on simply to do the thing you could have done in your first function. Oh, and to write a bunch of functions that you have no use for that is simply there, for that particular project. It's not like libraries invent things that doesn't exist. It's using the vanilla language too. There's nothing wrong with using libraries, but I prefer vanilla.
ОтветитьI wish more people would think this way. Its incredibly annoying that people use React as the default for JS now. As you mentioned, it was JQuery a decade ago.
ОтветитьTailwind is a tool for non-beginners to rapid prototype and manage component styles in a single file using CSS in a style attribute.
Being a paradigm fad of the moment is not a reason force it to be the hammer for every nail, especially for beginners.
The types pushing it as some sort of cultural truth are obnoxious in the same way as react brain; ignore them.
For me, it’s not even knowing the basics. Over the years frameworks have had a negative net result. I now use vanilla HTML, CSS and JavaScript only. And it’s sufficient. Nay, more than sufficient. CSS and EcmaScript is so useful and powerful, I’ll never use flaky frameworks again.
ОтветитьVanilla didnt have update❤
ОтветитьTBH dunno if it would ever make sense to do Tailwind content because half the stuff would have to use Arbitrary Properties (using the square brackets)... at that point it's just CSS with underscores instead of spaces.
Ответить