Hacker News Reader

Comment by 35bge57dtjku | Hacker News Reader

The original asp.net was pretty shit, too.

I think webforms, or JSF, or coldfusion at the time served a critical purpose. In the early 2000s most of the growing web was indeed just forms with state (much of it still is).

It's obviously changed much since then with client-side heavy rich applications, but those technologies at the time were very successful in RAD for basic CRUD, e-commerce, or basic data display.

I think most of the "shit" in this article comes from Angular. The asp.net part is pretty lean.

I think the commenter meant ASP.NET WebForms, which is pretty awful.

It tried to make web dev look like Winform devs, which Winform devs liked. It's no different from JSF and all that stuff and make sense in the enterprise context. If you are writing APIs, then no it doesn't. Ironically ASP.NET MVC is kind a going back to XML like declarative syntax, because it's actually useful. And Angular 2 is close to JSF/Webforms in spirit... the irony, things that looked obnoxious to JS hipsters and now hip again ...

Yeah for sure. Angular2 is like RAD development in Delphi all over again. Controls connected to DataSources connected to ClientDataSets ...

I hate asp.net webforms as much as the next guy, but this is the same program in webforms:

    <html>
      <head>
	<title>Hello world</title>
      </head>
      <body>
	<p>Hello <%= Request["name"] %></p>
      </body>
    <html>

How many lines of code and config files are in that blog? 100? Compared to the 1 line of actual code in this...

It's not really the same. The tutorial shows how to setup two frameworks to work together, so it's easy to extend the application in both front- and backend with other functionalities. Noone in their clear mind wouldn't combine asp.net and angular to display simple message

Keep moving the goalposts.

I think it's just a bad use case. No one in their right mind is going to lay down this much pipe just to display a query string variable in a page.

It's a tutorial, not code golf. Their example teaches me a lot more about ASP.NET Core + Angular2 than your example teaches me about ASP.NET WebForms.

ASP.NET WebForms would have a bunch of <asp:Label id="myLabel"></asp:Label> (ASP namespaced form controls), with associated event handlers using the "page lifecycle" [1].

Your code here is much closer to ASP.NET MVC.

[1] https://msdn.microsoft.com/en-us/library/ms178472.aspx?f=255...

You don't have to use label controls.

I might have been happy to use ASP.NET if I only had to write this one hello world program with it.

Reply on news.ycombinator.com