Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript

Anthony c
Anthony c
20,907 Points
Posted by Anthony c
Anthony c
20,907 Points

When Does One Actually Create Client-side Objects?

In a production app that has a real database and uses a framework (angular/backbone) and libraries (react, etc.)..... how often are you called on to use plain javascript to create client-side objects and do wildly advanced and complicated client-side functions that you find in most javascript books?

Aren't you 95% of the time just HTTP requesting/responsing mongo collections? Then working with that data?

Then the other 5% of the time you may be using a constructor function to create an object on the client-side?

I'm concerned the majority of what I'm learning in these javascript books is irrelevant for modern-day programming... many frameworks have abstracted this away... ES6 has made most of the patterns (a.k.a work-arounds) obsolete in the book... HTTP2 will soon make even more "best practices" obsolete (like minification and sprite sheets)...

I have no doubt that somebody who knows plain javascript inside and out is better off than a person who doesn't... but with limited time and resources I wonder if the stuff I'm learning is only useful if I decide to write a javascript book or enter a javascript trivia contest.... or run into crockford in an elevator somewhere.

Maybe if somebody could point out an example of a situation in a popular web app that this would be needed...

Trevor Waddell
Trevor Waddell
17,643 Points
Trevor Waddell
Trevor Waddell
17,643 Points

From my experience, as a front end, i I think it's best to know the fundamentals of javascript and be able to quickly learn/pick frameworks when needed. You don't have to know everything and aren't expected to.

I think the full stack javascript track here on treehouse covers a lot if not all of the fundamentals that that a front-end dev would need to be successful. Also development, whether front or backend, is a on going process. Trends and popular frameworks change rapidly. So again, stick with the fundamentals and you'll be fine.