3 ms·
One thing about being a JavaScript guy is that it's quite fragmented. For instance, this guy's hiring for a position that uses MooTools. In my experience, MooTo
by elliottkember 13y ago
One thing about being a JavaScript guy is that it's quite fragmented. For instance, this guy's hiring for a position that uses MooTools. In my experience, MooTools (while a great framework) isn't used very often. The framework you know and love, and the job you want don't always match up - especially if you're going to work on a product that's a few years old.
- disposition2 13y agoThis is my problem with JS. I've worked primarily with C#, done some Java and am currently doing some work with Python...all of which seem to be fairly consistent on functions that deal with problems, granted you get some overlap and redundant tools but there is some what of a standard. With JS, where does one start? Maybe I've just been too spoiled with what I've worked with thus far (jr programmer here) but in the times I've worked with or attempted to work with JS it has always left me looking for some kind of foundation or standards. So if any one out there enjoys JS and has some pointers on building a foundation, please advise...because a lot of the tools I see seem useful but I can't find any consistency in the projects I look at. Or rather, the only constant is that everything is always different.