← Back to context

Comment by leeman2016

7 years ago

> the future of a lot of web programming lies within .Net core

How is that, really?

How is it not? I mean, we’re a muniplacity, we operate around 500 IT systems, that are all moving toward becoming web apps in some form.

The core tech behind these is in 95% of the cases either .Net or JAVA.

Our in-house development has moved from .Net to JavaScript, mainly because we’re small and if our front end had to be JS then our backend might as well be, but now you have something like Blazor.net emerging, allowing for full stack C#, of course we’re going that route.

I didn’t say all, but I frankly think it’s obvious that .Net will play a big part of web development future, considering how big a part it already plays today and considering how Microsoft is moving it forward in all the right ways.

  • Historically many different companies and frameworks have targeted the web platform and almost always they lost to "plain old Javascript".

    That trend is going to continue, specially considering WebAssembly.

    But as of now there's no sign of Javascript becoming less dominant as almost all the innovation is in the land of React, Webpack, Babel, etc.

    I mean, what you're claiming "will emerge" is already there in form of Typescript, Node, React, Webpack etc and has a pretty good traction.

    • Does it JS really have that much traction on the backend? Maybe outside of Denmark, but our little department is actually one of the few places which uses Node for serious backend application in the entire country. At least that I know of.

      I mean, I can go on job databases or LinkedIn right now, and there isn’t a single full stack JS job available in my entire country. There is a lot of JS including jobs of course but they all require you to also/mainly do C#, JAVA, PHP or Python because JS is almost exclusive used on the frontend.

      Don’t get me wrong, I actually really like the JS environment. There’s a reason we moved to it, but it’s not like it doesn’t have its flaws either.

      I think WASM will absolutely change web development, but I think it’s already made it to the is, I mean, we’re launching our first minor Blazor app this week, and it’s something we typically would’ve build with vue and graphql Apollo, but now it’s all C#.

      The world of enterprise typically moves slow though. We’ve recently bought an on boarding system that’s made with web forms for instance. You may laugh at that, but the truth is, at least in my part of the world, that JS hasn’t seen that much adoption outside of hobbyists. Eventually these companies are going to upgrade their client sides, but would you pick modern JS or full stack C# if you were coming from web forms? Hell even if they go vue, react or angular chances are they’ll still use .Net on the backend, as that seems to be the trend pretty much everywhere except for us.

      2 replies →

    • A lot of (older) sites run ASP with some prebuilt or compiled c#/vb to js on top of that. No programmer would have to do JS if they want to.

      The technology is flawed in my view, but it does work and has no active js development needed.

      Note again: you can, but you don't have to.