2 ms·

> That's what I really like about the Elixir ecosystem; Phoenix is the automatic no-brainer choice. Just crack on with building your idea. Yes cohesion is grea

by hu3 3y ago

> That's what I really like about the Elixir ecosystem; Phoenix is the automatic no-brainer choice. Just crack on with building your idea. Yes cohesion is great! For C# we have ASP.NET dominance (and Java has Spring?). At the end of the day our job is to deliver value.

saila 3y ago
I've been learning .NET recently and there are several choices for building a webapp, such as MVC, Razor pages, and Blazor (further split into server vs web assembly). MVC uses Razor views, Razor pages use Razor pages, and Blazor uses Razor components. MVC without the V is apparently the recommended way to create APIs. I spent quite a bit of time trying to understand the distinction between these options and when you would choose one over the other, and I would have to disagree that it's a no-brainer choice. Perhaps if you've been in the .NET ecosystem for years and have followed the changes but definitely not if you're new to it.
- hu3 3y ago
  For something that was released 21 years ago, it's not that complicated: - Razor pages, views and components use the same templating language. - If you want MVC you can use Razor views and Components to render things from your Controller. - If you want something simpler like a website, you can use Razor Pages and Components. - Blazor is the new shinny thing. It still uses the same Razor templating language but targets for webassembly or Phoenix-style LiveView. And for APIs, it's just the ordinary Controller -> Action -> JSON as every other framework.
antihero 3y ago
> At the end of the day our job is to deliver value. If people just saw coding as that, none of this innovation would have happened.
- hu3 3y ago
  Delivering value and innovation are orthogonal concepts. Sometimes innovation is required to deliver value, but not always. Take Uber for example, it required no technological innovation (still great feat of engineering of scale). Meanwhile ChatGPT did. Both deliver value.

by hu3 3y ago

saila 3y ago

I've been learning .NET recently and there are several choices for building a webapp, such as MVC, Razor pages, and Blazor (further split into server vs web assembly). MVC uses Razor views, Razor pages use Razor pages, and Blazor uses Razor components. MVC without the V is apparently the recommended way to create APIs. I spent quite a bit of time trying to understand the distinction between these options and when you would choose one over the other, and I would have to disagree that it's a no-brainer choice. Perhaps if you've been in the .NET ecosystem for years and have followed the changes but definitely not if you're new to it.

hu3 3y ago
For something that was released 21 years ago, it's not that complicated: - Razor pages, views and components use the same templating language. - If you want MVC you can use Razor views and Components to render things from your Controller. - If you want something simpler like a website, you can use Razor Pages and Components. - Blazor is the new shinny thing. It still uses the same Razor templating language but targets for webassembly or Phoenix-style LiveView. And for APIs, it's just the ordinary Controller -> Action -> JSON as every other framework.

antihero 3y ago

> At the end of the day our job is to deliver value. If people just saw coding as that, none of this innovation would have happened.

hu3 3y ago
Delivering value and innovation are orthogonal concepts. Sometimes innovation is required to deliver value, but not always. Take Uber for example, it required no technological innovation (still great feat of engineering of scale). Meanwhile ChatGPT did. Both deliver value.