Pitch me on the pros and cons of your preferred web app framework

Comments

[huncyrus]

Slim

Pros

• Super small.
• Super fast.
• Advanced PHP ideas.
• Flexible.
• Easy to understand.
• Easy to extend.

Cons

• Some module/middleware ain't up-to-date for the latest version.
• Could be hard to not use for REST API.

[Klaus Donnert]

None.
Pros: Small size. Fast. Not over engineered. Breaking changes are rare. Learning curve shorter than other frameworks.
Cons: You might need to reinvent a wheel or 2.

[Adda Younes Abdelatif]

thanks for the article

[Anurag Vohra]

Created my own BLOC based JS framework to create webcomponent.
(Search for bloc-them in npmjs)
It's based on lit-html for creating HTML templates.
Pros:
Reactive
I know every bolt of my framework.
No need to search stack overflow.
Continuous improvement have made it much more better than any framework.
Easiest framework (its a relative term)
Fast enough to cater all my needs.
Uses BLOC based approach.
Based on HTML standard: webcomponents. Unlike JSX which is not HTML standard.

Cons:
Only I use it in the industry,for my own business.

[John Nyingi]

DotNet

Pros

• Improved performance (every new version gets faster than the last one)
• Cross platform
• A ton of libraries and packages to do pretty much anything( which can target multiple platforms)
• Open Source
• New version (6+ ) have Minimal APIs
• Multiple releases (LTS every 3 years and every year we get new versions with new features)
• It simply has the Best Documentation out there.

Cons

• Since it's a Microsoft product they pretty much control everything that goes into it.
• Alot of dependency on Microsoft packages (which is a good thing a single source of truth) but some good open source packages never get the limelight (just to mention ABP framework)
• Microsoft doesn't have a good reputation in the open source community but atleast .Net Foundation is changing the narrative.

For C#:

• Null checking is getting bloated (too many ways of getting nulls resulting in more features to check null)

[Camilo]

Phoenix Framework

phoenixframework.org/

Pros

• Elixir
• LiveView (Realtime with Websockets)
• Erlang VM (30+ years of production readyness)
• Surface UI (Similar to React.js)
• Similar to Ruby

Cons

• Although there are lots of packages (with access to the Erlang ecosystem too). Still behind from JS or Rails ecosystem. Nonetheless it worth it for the Pros.

[𒎏Wii 🏳️‍⚧️]

Okay, so I already gave an answer for the back-end, but I feel like talking about front-end as well, so here goes:

My own JS micro-framework

(Yes, I like reinventing the wheel)

Cons

• Everything is JavaScript. No extensions to the syntax.
• Very incomplete. Features get added as I need them.
• Building anything with it has me spend 20% of the time extending the framework.
• Browser support? Is that some sort of SEA dish I haven't heard of?

Pros

• Everything is JavaScript. No extensions to the syntax.
• Very small code-base, easy to copy-paste around for prototyping, or link from a CDN
• I've become comfortable with lots of weird JS features like Proxy or Reflect
• Ability to rely on the latest browser features for performance and simplicity

---

Meta-programming is fun 💜

[JWP]

Angular

Pros:

• Was once on par with Muhammad Ali in popularity and strength
• Version 2 broke out of taking Javascript hostage
• Made Component creation easy
• Refined continually
• TypeScript friendly

Cons:

• Like Mohammed Ali became old
• Best developers left
• Slow to make deep required changes. They implemented many things now native in Javascript but didn't obsolete them. Their framework now clashes with current Javascript standards, such as 'modules'
• Heavy weight with steep learning curve
• Error messages are terrible
• Their migration paths are bad.

[Alain D'Ettorre]

Angular

Pros

• RxJS <-- That's just great!
• Great developer experience
• Forms are easy and flexible
• Routing just works
• Modules are a good concept for code reuse
• Dependency Injection
• CLI
• It's a framework

Cons

• It's a framework
• Bad reputation due to old Angular.js, general verbosity and very different from all other frameworks and libraries
• Market share is shrinking
• Third-party libraries are incompatible and/or luckluster
• Build times and build sizes tend to be heavy