I'd say IE11, because Microsoft does not support older versions anymore so your client should upgrade asap due to no security patches and stuff

Source: https://microsoft.com/en-us/...

@MrCSharp ofcourse mvvm in web, after all the client side models are almost always view models right

@AlexDeLarge you had my +1 at 'OOP overkill'

We use SASS and try to follow BEM. 1 scss file per route or logical section/big components and import them in main scss. Also a seperate scss for const variables like colors and such.

Flexbox

Use a linter (eslint or something). Should catch most of the runtime errors (no type checking tho)

Always taste your food before you serve it

@runfrodorun yea it's an opinion, not a fact. I guess both have there good and bad sides

FP > OO

Yea untill your health insurance is going up because you ordered to much fast food lol

Amen

The M in MVC are the models containing the data for the view aka classes mirroring your database

The V is the viewlayer where the data from the models is being displayed in a markup language

The C are the controllers responsible for passing the models to the viewlayers and also containing state about the views

Check out MVVM (should be MCVMV) where a View Model is added, which get's responsible for representing the whole state of the view (combination of models and UI state) which leaves the controller with the task to just present the models

Add some repositories and services with dependency injection and your good to go ;)

Sorry for the long comment, hope this helps

I also don't believe in the whole 'Wielder of all trades is the master of none' principle.

The trade is crafting software, not writing in a certain language right?

@lotd you mean the 18000 line universe classes ;) glad I left that company

@AlgoRythm you know what you need? jQuery!

@billgates and yea, we TDD 90% of the time so if someone breaks something the merge request cant be accepted

Wow that escalated quickly haha, ofcourse I document classes or complex functions when there intent is not obvious, but I always aim for self explainatory code

Good code explains itself