loading...

re: Why You Shouldn't Use A Web Framework VIEW POST

FULL DISCUSSION
 

Disagree. Completely. Especially beginners should use frameworks, because they teach you how to structure your code. You don't learn MVC by reading a book, you learn MVC by grabbing Rails or Django and getting your hands dirty. (The same is true for all the other architectural patterns.)

I don't say that you should keep using frameworks all your live in all your projects, but frameworks take away some of your freedom - your freedom to code bullshit. Frameworks raise additional errors, they complain about stuff that might be completely fine outside the framework, but is not in the framework. It's not enough to learn the language when using a framework - frameworks make you read additional tutorials and documentation so that you learn how to apply the language.

 

Well I disagree completely too - so at least we have that in common!

you learn MVC by grabbing Rails or Django and getting your hands dirty.

I think all you'll learn is Rails or Django.

frameworks take away some of your freedom - your freedom to code bullshit.

Sure. But, in the words of Jeff Goldblum, "Bullshit finds a way". Frameworks just mean you'll code your bullshit in new mutant strains around the framework's constraints.

frameworks make you read additional tutorials and documentation

Isn't this a bit of a smell? When half of the books published on programming seem to be about how to use a particular framework? Always seems weird to me...

 

I give you a "like" because of Jeff Goldblum. :-))))

code of conduct - report abuse