Why fucking around with framework. When I can build everything natively?

I don't understand why so much people just use framework to build their stuff!

Because some people want their software faster rather than slower, and some devs would rather not reinvent the wheel when there's a battle-hardened solution that exists already. And some devs that may succeed you don't want to have to learn your custom-built framework and have to solve problems with no community support whatsoever.

I suppose it's called code reuse, and it's not total crap. Whenever you intend to maintain your fundamental set of features, it's already a framework. (Hey, they've just mentioned "community support"; you don't usually neglect such opportunities.)
What particular project is this about, if it's not secret? :)

Frameworks remove the need to write everything yourself, but, this can lead to hacky code when you need to do something the framework is incapable of handling, especially if there's a rule not to touch the framework in the business, Ive seen some relentless bullshit to get around frameworks.

Which ever you choose, you'll need to know what you're doing, more so if you write it yourself.

@spongessuck framework vs non framework for speed is debatable, some frameworks are hogs while others are fine tuned, and visa versa, some devs are hogs with code and others are not.

@C0D4 sorry I meant delivered more quickly, not that a framework will necessarily perform better.

@vintprox I'm building a blog with a custom content management system (powered by a WYSIWYG editor)

The main problem that frameworks try to solve are dependencies between UI and state. You press button A, oh now widget B has to change. However, dynamic data source C has also impact.

Rinse and repeat with complex applications, and you get the typical spaghetti from the jQuery era before frameworks were invented. Now if you don't have that situation, you don't have the problem and don't need its solution.

Because after a few projects you realize that you're building the same common components over and over or reusing your old code and fixing its crappy parts. Meanwhile there's a good quality, battle-tested, peer-reviewed, future-proof alternative maintained by someone else, so you could just use it and focus on your goal. Trust me, a person who dedicates their time to understand a problem and become specialist will probably come up with something better than your quick solution.

Also, hobby projects can be developed and maintained by a single person, but anything more serious needs a team. And the team will change over time. You don't want new team members to spend time figuring out your custom solutions. Use something people are usually familiar with, so they can join and be productive almost immediately.

Coding things from scratch is good for learning how stuff works under the hood, but it's rarely a good idea to build a serious product from the ground up all by yourself.

Depends what you're up against.

On one of the few occasions I've delved into frontend development (not by choice), I initially had the same thought. Pah, screw JQuery and Angular (pretty much the only options at the time), I'm going to just use native JS!

It was a *nightmare*. I kept finding myself wanting to reinvent the wheel with functions that weren't available natively, and ended up with heaps of unorganised utility functions. There were cross-browser bugs everywhere because I'd relied on features that didn't exist in IE, and worked differently in some browsers to others. Fixing those required hacks on top of hacks on top of hacks, and the thing never really worked properly.

Was fine for me. I got to say a big fat "I told you so" to the guy that thought it'd be a good idea for me to do frontend rather than hiring someone dedicated for the job. But yes, in hindsight - I would have saved myself a heap of work and anguish if I'd just have used a framework.

Yeah, might as well make the language too,why fuck around with JS when you can 101 tf outta it, right guys?

@LOLjustCoding 🤣🤣🤣🤣

Probably because of DRY and KISS, don't repeat yourself and keep it simple stupid. Why do something someone else has done already? Isn't the point of os to help and share code for reuse and tweaking?I'd rather go grab this code from someone else than spend that time trying to do the same thing. If I cant do it better or more efficient than why waste time I could put towards other parts of a project?

Old thread, but I've found a brilliant on-topic quote:

"If you wish to make an apple pie from scratch, you must first invent the universe."

- Carl Sagan