Thread by @AxleHellfire

A thread on JavaScript technology, application architecture, frameworks, and #EmberJS:

When it comes to choosing your technology stack for web applications, your personal philosophy of architecture design comes into play. I want to talk a little about my perspective.

1/11

Some developers are tinkerers. They really enjoy being an architect of *things*. It's a great feeling to point to something and say "I designed that myself!". Everyone has a different level of tolerance for how deep they're willing to go to build bespoke architecture.

2/11

That's not inherently a good or bad thing, but it comes down to a matter of preference. At what level do you want to be tinkering? The compiler? The framework? The application? The component? Everyone has their own desires and goals, which drive their technology choices.

3/11

Whether those personal preferences should be applied to a particular project is a different matter altogether. Then, it's less about your personal preference and more about the purpose, scope, and scale of the project. Additionally, the size of the team/company matters.

4/11

So, let's talk about my personal preferences. I *don't* like reinventing the wheel. If it's already been built, I almost always want to use it. I don't enjoy agonizing over choices for solved problems, when community standards can be set that solve them for me.

5/11

I would rather have an organized, purpose-built toolbox that can be used to build the vast majority of things than have to create my own toolbox from a massive bin of tools that may or may not work well together. Some assembly required, as they would say.

6/11

My drive, when it comes to architecture, is toward building things that haven't been built before. It's about creating amazing abstractions using the available tools as building blocks. It's about designing ergonomic APIs through meticulously planned component architecture.

7/11

So how does this tie into #EmberJS? In my professional experience, these are the things that draw me to choose Ember for my projects, both at work and at home. I don't need to build another bespoke framework, I want something that lets me hit the ground running.

8/11

#EmberJS gives me all the tools I need to build a professional-quality web application from Day 1. No squabbles over state management, routing, etc. The things the framework doesn't provide by default are available as easy, zero config plugins via Ember addons.

9/11

For me, choosing #EmberJS is choosing to prioritize productivity, ergonomics, and developer experience. It's choosing world-class tooling that is both powerful and easy to use. It's being able to hire any Ember developer and them being immediately able to contribute.

10/11

Ultimately, you might have different goals and priorities than I do. The things that are important to me might not be important to you. However, if anything I said just resonated with you, I encourage you to give #EmberJS a try!

guides.emberjs.com/release/gettin…

11/11

@threadreaderapp unroll

Prefer to read it in @threadreaderapp? Go here:

threadreaderapp.com/thread/1267996…

In closing, #BlackLivesMatter. Go support your local protests and fight for police reform and defunding of law enforcement! Talk to your friends, family, and colleagues about deepening your understanding of antiracism efforts. Work to create a more equitable community together!