I don't have a degree, an I found my first job at craigslist, and they only needed someone that knew some html and css. If you have a good portfolio that is good enough to get a job.

I would pay for none. If the game is good I would just buy it, and I am also expecting it not to have ads.

the simple fact is I don't see how it makes creating projects faster. This is something I've said for ages about jQuery, for ages about HTML/CSS frameworks, and it just continues to get worse and worse year after year! I think that "making things faster" part comes with the developer not having to reinvent the wheel, web development is getting very hard and a lot of times it is repetitive. DOM manipulations, state management, App re-rendering, accessing/storing data. All of these are parts of every application these days and a lot of them have been abstracted away. When the same repetitive keep coming up people find ways to solve these tasks more efficiently. Think about design patterns or some higler level abstraction. When you abstract something you make it "easier", by hiding internal workings in favor of some API, but with abstractions you have to pay a price, and sometimes it's worth it. I think that is what is happening with all of these new frameworks is that they abstract the re-rendering/DOM manipulations and state management so that you can focus un building stuff. After these abstractions have been adopted for a while the entry barrier into web development is somehow lowered because of less knowledge of these internal working. I believe this is where you will see developers struggle with DOM manipulations, and cling to frameworks, but in my opinion they do more good than bad.

These new frameworks allow you to create projects faster without having to reach into the DOM manually. The declarative nature of them allow you to create things without having to manually rig stuff up. To me that is an advantage because it speed things up development time, but there is no right or wrong answer. Whatever works for you.

Depends If I'm designing and implementing a solution from scratch or if I am working on an already existing implementation without any documentation.

How do you think cycle.js would do in a project where it uses a plugin architecture as one of it's main features? Each plugin must be it's own independent world, and must be able to be loaded from an external source.

There should be a more than 10 hrs option

There should be a more than 10 hrs option

Send me a link once you have that done. I would love to see the end result.

Can I use a .scss file?