News for hackers. Stuff that matters.
Re:.NET Blazor by xnorswap on Tuesday November 21, 2023 @03:55AM (#38361132)
Despite working with .Net for decades, I've not jumped to blazor.

The reasons are varied, many of which are well articulated in the article, but the most notable throughout various workplaces I've worked at, there's been a hesitance to jump on MS web frameworks in fear of a repeat of silverlight.

Silverlight burned a lot of small businesses hard, almost everywhere I've worked has had a silverlight horror story of a project they experimented in it with only for it to languish. So now they either have some outdated dependencies they'll never update or had to re-write it back into something else.

Even without silverlight concerns, most .net places I've worked have very much been legacy focused. This might be my own culture fit at interviews so I end up with places with lots of legacy of course.

But these giant legacy systems already have a plethora of mixed web technologies from ASP.net webforms, asp.net MVC, through .net core MVC, and many others. The willingness to add another different technology into the mix isn't relished.

For small companies, the cost of migrating older projects to new technologies is a significant burden which gets ignored for as long as it can be reasonably done so.

Re:.NET Blazor by xupybd on Tuesday November 21, 2023 @05:00AM (#38361629)
I was helping to maintain an Adobe Flex system a few years back. It really sucks when your framework is simply obsolete like that. I don't know how to protect against that with the rate of change.
Re:.NET Blazor by jsiepkes on Tuesday November 21, 2023 @05:25AM (#38361789)
> there's been a hesitance to jump on MS web frameworks in fear of a repeat of silverlight.

That's not really fair to MS since all the web frameworks which were born in that era (Adobe's AIR, JavaFX as a web tech, etc.) died because IE died. And also because Apple killed off browser plugins since they didn't work on the iPhone. Chrome and Firefox took over and there was no longer a need to use browser plugins for SPA's. HTML, CSS and Javascript finally got the features needed to create a proper SPA.

While JavaFX did live on outside of the browser both Adobe RIA and Silverlight were far worse positioned for life outside of the browser (even though both claimed to be usable outside of the browser). Simply because JavaFX was meant to replace Java Swing.

Re:.NET Blazor by pjmlp on Tuesday November 21, 2023 @05:33AM (#38361859)
JavaFX never really became a thing, because even at Sun it had a bumpy start with the scripting based language before it got rebooted into Java, just before Sun went down.

Oracle isn't a GUI company, beyond the stuff needed for their database products and IDEs, so they also didn't invest that much into it.

Thus most of the Java ecosystem, kept targeting Swing, and for the extent native desktop applications are still around, Swing is good enough.

Android is its own thing, so even one less reason to care about JavaFX.

Re:.NET Blazor by HeckFeck on Tuesday November 21, 2023 @05:59AM (#38362039)
javax.window.JOptionPane.showMessageDialog("Hello!");

Forever burnt into my mind from Programming 1008. And in fairness, much easier to get off the ground than the legions of XML required for JavaFX.

Re:.NET Blazor by bad_user on Tuesday November 21, 2023 @06:06AM (#38362085)
You can say that, but at the same time, whenever people complain about technology changing, leaving them behind, they usually mean tech by Microsoft.

The reason Java and JavaFX survived is that they went Open Source, with a large FOSS ecosystem, targetting FOSS operating systems as well, all while there still was interest. And their maintenance and evolution continued. Adobe RIA and Flash were proprietary platforms, just like Silverlight.

In fairness, projects that survive tend to be FOSS, and AFAIK, .NET Blazor is open source. OTOH, the .NET ecosystem tends to prefer Microsoft's solutions, with alternatives languishing, they basically killed Xamarin's projects, and they have had several noteworthy conflicts with the FOSS community. So the jury is still out on whether Microsoft's projects can escape the deprecation curse.

---

The lesson here, for all, if you want for your knowledge and work to stay relevant, look towards Open-Source platforms and open standards. If seeking stability, the older, the better, actually. FOSS platforms age like fine wine.

Re:.NET Blazor by BurnGpuBurn on Tuesday November 21, 2023 @05:56AM (#38362013)
Don't forget all the other products Microsoft managed to screw over developers with. Like discontinuing Xamarin.
Re:.NET Blazor by jve on Tuesday November 21, 2023 @07:00AM (#38362480)
Sorry for not being up-to-date. I can't read anything about discontinuing Xamarin on wiki: https://en.wikipedia.org/wiki/Xamarin

Ok, MS says this: https://dotnet.microsoft.com/en-us/platform/support/policy/x...

> Xamarin.Android, Xamarin.iOS, Xamarin.Mac are now integrated directly into .NET (starting with .NET 6) as Android, iOS, and Mac for .NET. If you're building with these project types today, they should be upgraded to .NET SDK-style projects for continued support.

> Xamarin.Forms has evolved into .NET Multi-platform App UI (MAUI) and existing Xamarin.Forms projects should be migrated to .NET MAUI.

So to those of you using Xamarin: how painful it is? How compatible Xamarin.Forms or not is with .NET MAUI? Are they totally different tech?

How easy/hard it is to go from Xamarin.{Android,iOS,Mac} to .NET6+ ?

Re:.NET Blazor by throwaway2990 on Tuesday November 21, 2023 @08:24AM (#38363287)
Xamarin for iOS and Android just works…

Maui on the other hand is a turd. It’s such a pain to work with, workloads just plain suck. And if you install . Net 7 and your project targets 6, It will download .net 7 workloads and fail to build. Then 8 comes out and same problem. Have to pin the SDK.

Re:.NET Blazor by rqtwteye on Tuesday November 21, 2023 @08:59AM (#38363668)
And by the time Maui starts to mature and work, they will announce a new framework and the cycle starts again. I still don’t understand why they couldn’t keep working on WPF instead of cranking out a new framework every three years.
Re:.NET Blazor by progmetaldev on Tuesday November 21, 2023 @11:55PM (#38374888)
It's because WPF was too heavily tied to Windows technology.
Re:.NET Blazor by pjmlp on Wednesday November 22, 2023 @04:55AM (#38377184)
Only because they didn't want to put the work to make it portable, as proven by Avalonia folks.
Re:.NET Blazor by cxr on Tuesday November 21, 2023 @08:58AM (#38363646)
> That's not really fair to MS since all the web frameworks which were born in that era (Adobe's AIR, JavaFX as a web tech, etc.) died because IE died. And also because Apple killed off browser plugins since they didn't work on the iPhone.

Who could have foreseen that hitching your horse to derpy, single-vendor RIA frameworks that were closed source proprietary and worked on the basis of shoving foreign content into the browser to get it to do non-Web things was a bad idea? Oh wait, anyone.

In that vein, in response to the earlier remarks by the original commenter:

> Silverlight burned a lot of small businesses hard, almost everywhere I've worked has had a silverlight horror story of a project they experimented in it with only for it to languish. So now they either have some outdated dependencies they'll never update or had to re-write it back into something else.

Yeah, good. That pain is well-deserved. Almost self-inflicted, even.

Re:.NET Blazor by Yodel0914 on Tuesday November 21, 2023 @06:29PM (#38372123)
It's not just web frameworks - it's all MS UI frameworks. On the desktop there WinForms, WPF, UWP, WinUI, Blazor, MAUI... it's really seems like a mess with no clear direction.
Re:.NET Blazor by torginus on Tuesday November 21, 2023 @05:54AM (#38361992)
I like .NET, and I believe Blazor represents an unique capability for that tech stack, but using Blazor essentially means eschewing all the traditional web stack tooling that was built up around TS/JS during the past decade for proprietary Microsoft weirdness.
Re:.NET Blazor by jcmontx on Tuesday November 21, 2023 @06:20AM (#38362180)
> proprietary Microsoft weirdness

.NET (and Blazor) has been open source for at least 7 years now

Re:.NET Blazor by ajryan on Tuesday November 21, 2023 @08:15AM (#38363220)
Call it Blazor weirdness then. This obviously wasn’t a swipe at Microsoft being closed, just a point that Blazor stuff is not general standard web stuff.
Re:.NET Blazor by cxr on Tuesday November 21, 2023 @09:09AM (#38363787)
Something can be both open source and proprietary. Flex has been open source for even longer. Still proprietary. See also: XUL.
Re:.NET Blazor by keyle on Tuesday November 21, 2023 @06:20AM (#38362173)
I professionally saw the rise, the peak and the burn of Director (Shockwave), Flash and Silverlight...

By far, the most devastating one, was Flash.

One good thing came out of Silverlight, and it's not really getting the credit it deserves: MVVM.

As far as I know, Silverlight brought that pattern to light, before that, it was MVC and OO hell. And MVVM paved the way to modern paradigms, imho.

Re:.NET Blazor by sanitycheck on Tuesday November 21, 2023 @06:33AM (#38362281)
Oh, me too. So much now-obsolete knowledge accumulated!

Flash was always going to die someday though, as HTML/JS caught up with it. In the end it was killed (arguably) prematurely, but it probably wouldn't have lasted more than another 5-6 years anyway.

Silverlight, I think, was worse - only a few years between initial launch and discontinuation. Pretty much every client app based on Silverlight would have had to have been rewritten from the ground up within a couple of years of completion.

I try to learn lessons, in life. One of them is to not rely much on any Microsoft technology that's less than 10 years old.

Re:.NET Blazor by keyle on Tuesday November 21, 2023 @06:34AM (#38362286)
I remember the transition to WPF apps was awfully painful.
Re:.NET Blazor by throwaway_0235 on Tuesday November 21, 2023 @09:02AM (#38363695)
> Flash was always going to die someday though, as HTML/JS caught up with it.

I'm not sure that would happen. I think Flash would evolve to just "compile" to HMTL/JS. IOS/Android could be other targets as well, once they found a way that would not upset the Eye of Apple.

Re:.NET Blazor by acdha on Tuesday November 21, 2023 @09:18AM (#38363904)
Not if Adobe was developing it. Flash was terrible for performance and battery life, and it was wedded to the classic fixed-size window with a keyboard and mouse. Even Android users who had access hated it.

Now, it’s possible that some of that could’ve improved (battery life would’ve been hard due to the scene timing model) but Adobe just isn’t a platform company. They didn’t even want to fix the security problems, much less all of their half-assed APIs - they were even worse than Sun for announcing ambitious frameworks duplicating built-in OS features, shipping the easiest 40%, and then letting it stagnate because there was no way fixing the hard stuff would get them a second keynote.

Re:.NET Blazor by jen20 on Tuesday November 21, 2023 @10:24AM (#38364821)
MVVM was also the prescribed pattern for WPF (which shares some other things like XAML with Silverlight). WPF debuted a year earlier though!
Re:.NET Blazor by keyle on Tuesday November 21, 2023 @07:25PM (#38372738)
Ah, there you go! TIL.
Re:.NET Blazor by oaiey on Tuesday November 21, 2023 @07:32AM (#38362759)
I have to disagree. What you describe is every legacy stack and 20 years evolvement. Java with how many EE systems. JS with how many SPA frameworks. Python I know too little. Go/Rust are too young to have history.
Re:.NET Blazor by kgwxd on Tuesday November 21, 2023 @02:11PM (#38368419)
Silverlight was an obvious bust from the beginning, no one with longevity in mind jumped on that ship and fought against anyone pitching it at the time (mostly inexperienced devs, sales people, and tech companies looking to make a quick buck). Anything plug-in based was already on the chopping block by the time it came out. Blazor WASM is, at least, as safe a bet as any popular JS framework. If .NET was still a Windows only thing, I'd stick with the JS frameworks, but now that it's cross platform, I've got no problem choosing Blazor over any other UI framework that just as easily might need a full rewrite in a few years.