News for hackers. Stuff that matters.
Re:Silverlight Shouldn't Come Back to Life by PaulHoule on Friday March 13, 2020 @12:21PM (#22568533)
Your examples point out how hit-and-miss Microsoft is.

When it comes to TFS vs Git, even Microsoft will choose Git. (e.g. it is the only version control designed from the start to handle a major operating system kernel)

When it comes to Azure vs AWS I see them as evenly matched. If you make a decision based on your gut it won't hurt you. (If you picked IBM cloud because you liked IBM, however...)

Some Microsoft products are pretty good but often Microsoft drops the ball. For instance, the foundation of ASP.NET is absolutely great. However, they introduced some controls that looked a lot like "Web Components" that ran (mostly) on the server side. These dealt with all the usual annoyances about HTML forms, and could have been a real productivity booster.

The fatal trouble these had was that they used a state management mechanism that wasn't compatible with the "MVC" web framework approach which is mostly a matter that forms don't live in isolation. After processing the form, the server can decide to render any of a number of possible output pages: for instance you might render the same form if the form failed validation, but deliver one of several forms depending on what the user filled out (think tax paperwork)

Microsoft might have been able to make the existing system work in an MVC framework, or made something similar from the ground up to work with MVC, or other moderate decisions.

Instead they came up with ASP.NET MVC which wasn't trying to be a market leading product, but instead is a cut-rate version of Ruby-on-Rails that cut you off from much of what was cool about ASP.NET.

Microsoft had the chance to make a system that was really worth paying for, but they blew it.

Re:Silverlight Shouldn't Come Back to Life by jdsully on Friday March 13, 2020 @12:44PM (#22568740)
> When it comes to TFS vs Git, even Microsoft will choose Git. (e.g. it is the only version control designed from the start to handle a major operating system kernel)

Microsoft used an internal fork of perforce for most of Windows' history. Substantial changes were needed for git to handle the windows codebase. I don't know of any major project that used TFS internally, Source Depot was the primary source management.

Linux is quite small compared to many internal Microsoft code bases.

Re:Silverlight Shouldn't Come Back to Life by Ididntdothis on Friday March 13, 2020 @12:49PM (#22568791)
From what I understand MS never had a problem using tools that weren’t the ones they give to their developers. They used perforce while selling SourceSafe for example. I don’t think they used Winforms or WPF much either except in maybe a few projects. I always wondered what would have happened if they had made the UI libraries Office uses available to third party devs or beefed up MFC so Office could be written with it.
Re:Silverlight Shouldn't Come Back to Life by jdsully on Friday March 13, 2020 @12:55PM (#22568866)
TFS was never really that good and I won't defend it, but Winforms and WPF are more RAD tools not really appropriate to projects like Office. They are excellent for the tasks they were designed for.

Re the Office libraries you probably wouldn't want to use them anyways. They were designed for maximum flexibility and performance not with ease of use or fast development velocity.

Re:Silverlight Shouldn't Come Back to Life by Ididntdothis on Friday March 13, 2020 @01:15PM (#22569019)
I think it’s a big problem if a vendor of dev toolkits doesn’t use them themselves. WPF is a great example. The underlying concept is very interesting but it seems they stopped developing it before it had the chance to be really good.
Re:Silverlight Shouldn't Come Back to Life by jdsully on Friday March 13, 2020 @01:44PM (#22569249)
I don't think its fair to say it wasn't used. Just that it wasn't used on the big projects like Office. There were certainly a ton of internal tooling from that era that did indeed use it, which was also the primary use case in the wild: Internal line of business applications. With RAD you are making tradeoffs that aren't appropriate for massive code bases. Microsoft always took dogfooding very seriously.

It's a bit like complaining Ford doesn't use its pickup trucks to transport vehicles to the dealer. They just aren't designed for that purpose.

Re:Silverlight Shouldn't Come Back to Life by Ididntdothis on Friday March 13, 2020 @02:25PM (#22569635)
To some degree I understand what you are saying but it’s still a wrong strategy. It means there are easy to use tools for small apps and large apps have to deal with Win32 directly with nothing in between. No wonder the desktop is dying.

The propaganda MS has been putting out also contradicts this. I remember well how they were first telling us that WPF, then Silverlight, then WinRT is the future of windows. Got burned a few times and then refused to look at UWP which is now the future of Windows until it probably isn’t.

Re:Silverlight Shouldn't Come Back to Life by jdsully on Friday March 13, 2020 @03:26PM (#22570149)
.NET has a very good inter-op story for win32. If you started with MFC, WPF, or another framework and then needed to add win32 flourishes you can do so quite easily.

It's quite a different thing to try and retrofit a traditional win32 message pump application with one of these frameworks. Especially if it's in an entirely different language and runtime. Had Office been born in the early 2000s its quite likely they would have tried to use .NET and had the same issues as Longhorn. I think Microsoft did have broad ambitions for the framework, but reality was the tech couldn't handle large scale software at that time and Longhorn failed as a result.

I think your right it is a little unfortunate win32 is needed if you want to make a million LOC desktop application. I don't think there really was anything better for native code up until recently with modern C++. The ugliness of COM and MFC are really due to limitations of C and C++ at the time. Now I don't think there is enough demand to really justify something radical.

.NET Always did reasonably well for web backends, and I think they have the right strategy to keep pushing there.

Re:Silverlight Shouldn't Come Back to Life by JamesBarney on Friday March 13, 2020 @03:13PM (#22570060)
Most desktop projects I've seen have stuck with WPF and they've all been happy with that decision (except for a few who wish they'd gone web).
Re:Silverlight Shouldn't Come Back to Life by Ididntdothis on Friday March 13, 2020 @03:40PM (#22570253)
That’s pretty much how I feel. Go to web if possible. It’s also better for the resume :)
Re:Silverlight Shouldn't Come Back to Life by scarface74 on Friday March 13, 2020 @10:31PM (#22572684)
There was nothing cool about ASP.Net Web Forms.