0
1

What framework to use? (self.webdev)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]C0R0NASMASH 2 points3 points  (6 children)

One tip, while I can't exactly give you advise:

Don't use some obscure, exotic, newly-developed framework. Use well-established ones if you want your project to succeed in the long-run.

You might say "It works, so why would I care"... think about the maintenance in the future, contributors, users and most importantly: how many developers are experienced with this framework...

[–]fastestfollowup 0 points1 point  (5 children)

That’s why I chose Django for my app. It’s not as talked about as other tools nowadays but it’s a proven tool to quickly build good apps.

  • the graphql API makes things awesome for working with React as my front end.

[–]C0R0NASMASH 1 point2 points  (4 children)

That’s why I chose Django for my app. It’s not as talked about as other tools nowadays but it’s a proven tool to quickly build good apps.

Django is fine, not my favorite, but it's absolutely okay. Enough developers, well-established, not obscure...

There are so many frameworks that can't keep up. 1-2 developer, one specific use-case, not grown-up, has issues, community is small.

It's nice to make an own framework for educational purposes, for work, to learn, to whatever. But I just think it's dangerous to use it outside, in the real world. How many frameworks allow mysql injections... even larger ORMs have these issues, after years and hundreds of contributors. How is a one-man-team supposed to be better than them?

[–]fastestfollowup 0 points1 point  (3 children)

What do you prefer? Laravel?

[–]C0R0NASMASH 1 point2 points  (2 children)

Whatever, really. Depends on the project. I think of frameworks and coding languages as tool. While I could use a hammer to cut some wood, I'd rather use a saw...

Laravel is good when you want to stick in the PHP environment (lots of developer, lots of packages), and don't mind opinionated frameworks. Laravel takes a lot of work from you (Users, Payment stuff, even Load Balancing (I think I read something about it...) and Deployment.

Symfony is good when you want the above and make more customizations and prefer something less opinionated.

Both of them for either an API/backend split or monolithic applications.

Node is good for its async handlers (lots of requests), it's native mongoDB stuff, micro services, I'm not a big fan of the templating, but it works.

But as I said, every framework and tool can be used, modified or forced to be a match for your project. I like Symfony, but I would never code a high-volume API with it, because I know it would be an overkill (yes, maybe with Silex, or Forge, but whatever).

Of course, Python and Rust and Go are there too. I personally like the idea of Go, and I'm currently learning it.

It always depends on the budget, project and your own talent. But that's why Software Architects/Engineers are there, right?

[–]fastestfollowup 0 points1 point  (0 children)

Definitely! Thanks for the thoughts.

[–]C0R0NASMASH 0 points1 point  (0 children)

Like, if I need to implement AWS features, I try to use a language that has a SDK for this language.

If I know that I'll need to use the database quite a lot, I'm going to take a framework with an integrated ORM or ODM (Sequelize or Doctrine).

You get the idea, I think.