Live data from Hacker News

A list of front end development resources

gist.github.com

41–50 of 93 posts

Re: A list of front end development resources

#42
post #33

Seeing this mess again tells me that there's something fundamentally wrong with the web or at least with the standardized technologies that are supposed to solve the problem of frontend development (namely HTML, CSS and JS). I think the web really needs a fresh start before I would even consider becoming a web developer (I'm a CS student atm)

It's not as big of a mess as the list would make it seem. None of the resources provided are required, and however useful they may seem, I've never found them to speed up development time. I do all of my HTML, CSS, and JavaScript from scratch for every site I build. It's a max of one day on only the most complex projects.

Uh... you're not building very complex projects then :) Before you get defensive, consider something like Amazon.com as an easy extreme example. Or a banking website or non-trivial html5 based onlline game as less extreme ones. None of those are getting built in a day, and probably not without the use of libraries (though for something like amazon the libraries may be mostly proprietary/internal)

Re: A list of front end development resources

#43
post #18

The trouble with managing a list like this is that it's not exactly easy to update/correct? It's always owned by one person, and errors (like Foundation 3 being mentioned) aren't easy to correct - or to expand and add new items to. Great resource, but wouldn't a collaborative wiki be easier - or are such lists maintained for the original author's reputation not to become a fount of collective knowledge?

I started one at http://pineapple.io - the wiki isnt nearly even close to complete, but the site itself has a lot of highly-moderated content (pruned regularly, all my users check for broken links, make comments on resources, etc)

Re: A list of front end development resources

#44
post #42

Earlier quoted context omitted.

It's not as big of a mess as the list would make it seem. None of the resources provided are required, and however useful they may seem, I've never found them to speed up development time. I do all of my HTML, CSS, and JavaScript from scratch for every site I build. It's a max of one day on only the most complex projects.

Uh... you're not building very complex projects then :) Before you get defensive, consider something like Amazon.com as an easy extreme example. Or a banking website or non-trivial html5 based onlline game as less extreme ones. None of those are getting built in a day, and probably not without the use of libraries (though for something like amazon the libraries may be mostly proprietary/internal)

I think you're getting defensive :). By saying I'm not building complex projects without any knowledge of what I create, you're trying to circumvent your own self-invented inadequacy without actually putting the pressure on yourself. Whether this was done subconsciously or not, I can't say.

I suppose it depends how you interpret the term web developer, since that's what simfoo was discussing. Myself, building browser-based games isn't web development, it's game development, which I feel is an entirely separate domain. Building a website, you really shouldn't need more than a day to put together the HTML, CSS, and JavaScript. The front-end of the majority of most websites is very similar. Normally, this would indicate regular code reuse or warrant a framework, but as indicated in my original post, I haven't found any framework that actually significantly speeds up my development time.

Re: A list of front end development resources

#45
post #42

Earlier quoted context omitted.

Uh... you're not building very complex projects then :) Before you get defensive, consider something like Amazon.com as an easy extreme example. Or a banking website or non-trivial html5 based onlline game as less extreme ones. None of those are getting built in a day, and probably not without the use of libraries (though for something like amazon the libraries may be mostly proprietary/internal)

I think you're getting defensive :). By saying I'm not building complex projects without any knowledge of what I create, you're trying to circumvent your own self-invented inadequacy without actually putting the pressure on yourself. Whether this was done subconsciously or not, I can't say. I suppose it depends how you interpret the term web developer, since that's what simfoo was discussing. Myself, building browser…

Maybe if you're building a plumbing website for a client, most people here I would imagine build apps and complex works of art though, which definitely take longer than a day to put together.

These tools are crazy helpful in that regard.

Re: A list of front end development resources

#46
post #42

Earlier quoted context omitted.

Uh... you're not building very complex projects then :) Before you get defensive, consider something like Amazon.com as an easy extreme example. Or a banking website or non-trivial html5 based onlline game as less extreme ones. None of those are getting built in a day, and probably not without the use of libraries (though for something like amazon the libraries may be mostly proprietary/internal)

I think you're getting defensive :). By saying I'm not building complex projects without any knowledge of what I create, you're trying to circumvent your own self-invented inadequacy without actually putting the pressure on yourself. Whether this was done subconsciously or not, I can't say. I suppose it depends how you interpret the term web developer, since that's what simfoo was discussing. Myself, building browser…

>Building a website, you really shouldn't need more than a day to put together the HTML, CSS, and JavaScript

https://news.ycombinator.com/item?id=5834227

Re: A list of front end development resources

#49
post #42

Earlier quoted context omitted.

Uh... you're not building very complex projects then :) Before you get defensive, consider something like Amazon.com as an easy extreme example. Or a banking website or non-trivial html5 based onlline game as less extreme ones. None of those are getting built in a day, and probably not without the use of libraries (though for something like amazon the libraries may be mostly proprietary/internal)

I think you're getting defensive :). By saying I'm not building complex projects without any knowledge of what I create, you're trying to circumvent your own self-invented inadequacy without actually putting the pressure on yourself. Whether this was done subconsciously or not, I can't say. I suppose it depends how you interpret the term web developer, since that's what simfoo was discussing. Myself, building browser…

It would be helpful if you could provide some examples of your work. "Complex" means something different to everybody, so your claim is hard to place in context.

"Less than a day" for "complex" web sites using nothing but raw JavaScript and hand rolled HTML & CSS does sound unusual, both in terms of the result as well as the workflow. Given the verbosity of JS DOM manipulation, I can't really envision a particularly good reason to go down that route for anything but the most performance pegged web applications.

Re: A list of front end development resources

#50
post #33

Seeing this mess again tells me that there's something fundamentally wrong with the web or at least with the standardized technologies that are supposed to solve the problem of frontend development (namely HTML, CSS and JS). I think the web really needs a fresh start before I would even consider becoming a web developer (I'm a CS student atm)

You don't actually mention anything that's wrong with any of the libraries. Most of them seem well written. So why would the web need a fresh start?

It's not so much the libraries themselves as the very need for all of them. I'm a fairly new front-end developer (for anything complicated, that is), and the browser as a platform can't help but feel like what it is, some good ideas with a lot of hacks and inconsistent philosophies accreted over time. It's a pain in the butt, even something like a two-column layout without tables. And that's just to get it working in one browser. Then you try your page in Firefox, and maybe it breaks in some obscure way. That's when you start breaking out the libraries, like bootstrap.

Right now, web is the best place for my app to be (assuming I can figure out offline support), but I tear my hair out every time I run into one of these issues. Just the other day I had some bizarre issue where offsetBottom and offsetTop + height were returning contradictory values, or something like that. And that was with jquery helping me. The web platform is cool for what it enables, but stinks for what it makes you do to get there.

Post reply on HN