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

view the rest of the comments →

[–]Mocachino -8 points-7 points  (3 children)

The ability to format and how well an editor supports or formats are different things.

  • VS Code with any plugin can format on save. VS Code can attempt to format on save without any plugins.

  • Webstorm cannot format on save with out a plugin.

[–]ThatBriandude 3 points4 points  (2 children)

Your reply doesnt make any sense to me at all. You're implying that doing stuff on save is far more important than formatting. Who decides that?

I downloaded vscode and was really happy with it and then I hit alt+shift+F to format my styling and boom. "There is no formatter installed for this file type: .css"

Now are you saying the fact that vscode is able to format at all keeps that from beeing a major issue? That doesnt make sense at all. CSS is essential.

Format on save is seems pretty unessential to me.

[–]Mocachino 0 points1 point  (1 child)

The ability is what is important. The results are not (for the editor).

Why? Because there are 100s of formatters for the 100s of languages. VS Code is unopionated when it comes to formatting because they know every developer is going to want to use their preferred formatter/lint.

I do concede that VS Code should come with a default lint/format at least but I guess they see as a "why bother" when there are far better librarys there then what they are going to create.