Live data from Hacker News

Microsoft Dependency Has Risks

blog.miloslavhomer.cz

221–230 of 238 posts

Re: Microsoft Dependency Has Risks

#221
post #146

Earlier quoted context omitted.

> OpenGL OpenGL is legacy tech, just as DirectX Vulkan is the new shader thing, and has been for at least a decade by now.

DirectX12 is still much better to use than Vulkan. Natively supports Xbox and PC. Can run on Linux with Proton. The Playstation API functionally resembles DX12. Vulkan is extension management hell (but has gotten much better, I concede)

Forgive me for being an idiot but i was under the impression dx12 was closer to vulkan architecturally which makes it easier to port to Linux display drivers (and thus why it has)

Re: Microsoft Dependency Has Risks

#222

I still find it hard to believe that so many people and companies are prepared to use Microsoft's online/cloud services. Not ony is this a single point of failure but it's one they've no control over whatsoever. Same goes for Google/Youtube etc. It's as risky as flying a passenger jet with only one engine. What are they thinking, why are they prepared to risk everything? It boggles my mind.

But isn't that how civilization literally works?

people live paycheck to paycheck, they have limited ability to create food, they rarely have enough safety equipment nearby to survive a heart attack or a fire, and afaict this is all accelerating.

Re: Microsoft Dependency Has Risks

#223
post #132

Earlier quoted context omitted.

> How do you separate the good from the bad? Developer tools and enterprise stuff good (mostly). Consumer products bad.

For whom? Microsoft? I don't know which of their developer tools I would consider good. Or less worse than the competition

Only from personal experience: people in the Microsoft ecosystem absolutely love visual studio, and hate the idea of migrating

Re: Microsoft Dependency Has Risks

#224
post #132

Earlier quoted context omitted.

For whom? Microsoft? I don't know which of their developer tools I would consider good. Or less worse than the competition

I consider C# / .NET to be one of the best options for application development. Many would consider both VSCode and Visual Code pretty good. There might be better alternatives, but generally I'd say they are more good then bad. Github is also a good product. Maybe not exactly a develop tool, but Power BI is also fairly good. Borderline developer / enterprise solution: SQLServer is great to work with. Maybe not the be…

Github was a great service well before Microsoft bought it.

The best thing about Microsoft’s stewardship has been that they haven’t fucked that up.

Re: Microsoft Dependency Has Risks

#225
post #119

Earlier quoted context omitted.

Ironically appropriate example. Many of the most famous restaurants in the world, like Noma [1], are famous precisely for sourcing ingredients that bypass mega-farming. At Noma many of the dishes are based on the produce provided from local foraging. And contrary to what you might expect from its presentation/reputation, the place itself is just a building surrounded by green houses and a guy growing and harvesting m…

Yeah, and many of these best restaurants in the world barely make a profit, compared to Olive Garden or McDonald's. But yes, I'm with you here. I also like Noma way more than Olive Garden.

I like your argument, but McDonald's gets their ingredients from multiple suppliers, all selected for their specific specialism.

They also don't run the cash registers on software provided by their meat supplier.

In Dutch government (especially local), for example, almost everything runs on Microsoft. From e-mail to web sites to chat to internal software. And with AI coming up, Microsoft is effortlessly capturing that market too by including Copilot in existing contracts.

Re: Microsoft Dependency Has Risks

#226
post #224

Earlier quoted context omitted.

I consider C# / .NET to be one of the best options for application development. Many would consider both VSCode and Visual Code pretty good. There might be better alternatives, but generally I'd say they are more good then bad. Github is also a good product. Maybe not exactly a develop tool, but Power BI is also fairly good. Borderline developer / enterprise solution: SQLServer is great to work with. Maybe not the be…

Github was a great service well before Microsoft bought it. The best thing about Microsoft’s stewardship has been that they haven’t fucked that up.

Before Microsoft bought it you could still search it / codesbases without making an account. Alone for that additional pain I would argue they instantly made it worse.

Re: Microsoft Dependency Has Risks

#227
post #176

Earlier quoted context omitted.

ASP.NET Just Works and has Batteries Included. As an example, just over the last few days, I hit all of these common issues with Node.js apps (that don't happen with ASP.NET): 1) Node apps are typically a "transpiled language on a language" because JavaScript is unusable for large-scale software development so everyone uses TypeScript compiled to JavaScript instead. But this is a hack! A clever, useful hack, but a ha…

That's really an insightful answer I enjoyed reading. Really brings me back! I dislike nodejs for the same reasons. But do get the feeling that rust and go, maybe even something more exotic like elixir would be good alternatives as well for your use case. I have barely anything to compare to your requirements tho. I personally would get panic attacks and couldn't sleep anymore if my dependencies aren't open source an…

> I personally would get panic attacks and couldn't sleep anymore if my dependencies aren't open source and I would depend on a company for any reason. But that's just me, it definitely sounds very mature

.NET is open source.

Re: Microsoft Dependency Has Risks

#228
post #88

Earlier quoted context omitted.

> There aren't many things like .NET, MSSQL and Visual Studio out there. The debugger experience in VS is the holy grail if you have super nasty real world technology situations. There's a reason every AAA game engine depends on it in some way. The reason all the AAA games are on it is because they're on the Windows platform, and more importantly their customers are on the Windows platform. If 95% of gamers ran MacOS…

Game customers are on Windows because DirectX has been superior to OpenGL - development wise - for what, 30 years?

No

1) OpenGL is a (now legacy spec) and DirectX is an API on Windows. OpenGL spec is implemented by your GPU driver.

2) DirectX is a collection of multimedia APIs on Windows. OpenGL is just graphics. Direct3D is one of those APIs.

3) Thirdly OpenGL and Direct3D (before version 12) are pretty much the same in they can do. The code is pretty similar IIRC (though it been some time since I've done Direct3D programming).

4) Devs use DirectX because there is a full set of APIs for the target platform. Linux and Mac aren't typically targeted when making a game. Mac and Linux sales have been a very small percentage historically.

Re: Microsoft Dependency Has Risks

#229

Earlier quoted context omitted.

dotnet build https://tonybaloney.github.io/CSnakes/getting-started/#build... What's with the "just copy it" thing? Nobody does that, we use NuGet packages, GitHub Actions, SDK supported containers, reproducible cross-platform builds from command line, etc. edit: I'm sure some people use file/copy, but you sure don't have to. That stopped being a common thing 10+ years ago with cross-platform .NET.

Nope. Try again. > Nobody does that Read the parent post. > we use NuGet packages, GitHub Actions, SDK supported containers, reproducible cross-platform builds from command line, etc. So basically, "NPM but different". Got it.

My point was that "copy" is sufficient and works much more robustly than with NPM/Node, for example.

At $dayjob I use DevOps agents or App Service with pipelines. I'm not a savage.

Re: Microsoft Dependency Has Risks

#230

Earlier quoted context omitted.

> the ribbon is fully customizable so was the one in office 95 > with greater functionality than traditional menu you click a button and something happens? except now the button isn't in a consistent place a usability regression

Wrong about "inconsistent", the ribbon follows predictable patterns. Home tab always has basic formatting, Insert always has objects/media, etc. What changed is intelligent positioning based on context. Office 95's menus were consistent in the worst way - consistently buried everything under nested submenus. Finding mail merge meant File→Tools→Mail Merge→Options→Setup. Now it's Mailings tab, right there.

Word is a word processor.

It is a tool for people who write words. That is its prime purpose.

People write words for people to read the words. That is the prime purpose.

It is a tool for readers and writers.

I am both.

I can read a menu, and scan through submenus, about 10-20x faster than I can page through buttons on a tabbed bar. The replacement is dramatically inferior in legibility and so in efficiency.

That is 1 way it is worse.

A menu bar takes a single line of text. It works perfectly in a text-only display. A ribbon bar takes many lines of small intricate graphics. It is dramatically and measurably and demonstrably inferior in its use of screen space, its use of pixels, its adaptability to other displays, its functionality for those with restricted vision or restricted computer display abilities.

This is a 2nd way it is worse.

It is not re-orientable; I can't move it to one side to use a widescreen more efficiently. Because of its poor and fixed layout I can see less of my document, meaning it hinders the primary purpose of the tool.

This is a 3rd way it is worse.

It does not interoperate with other UI paradigms. Right now I am typing on an old Mac with macOS. Word is the only Office app on it. The oldest 64-bit version of Word I can find. It has to duplicate the entire UI both in the Mac's mandatory global menu bar and in the clumsy bolted-on Windows-centric ribbon. This demonstrates the inefficiency and poor design.

This is a 4th way it's worse, although for me, it means I can ignore the ribbon and use the menus.

I read fast. I cannot squint at tiny icons and try to guess their functions quickly. It's slow. The ribbon defeats muscle memory and defeats fast reading.

This is a 5th way it's worse.

The ribbon is context-sensitive. I can't just remember what is where under where relative to the first menu, because it changes depending on where the cursor is, what is selected, what tab I left it on last time. In a menu tree, if it's left open, I tap ESC once and I am at a known place and can start over. Not with the ribbon.

This is a 6th way it's worse.

I speedread and I have good colour vision. Some people can't see colours. Some can't see fine details. Some can't see at all. A screenreader can just read all of a menu, but it can't describe icons and it can't say "then there's a vertical line and in the next section, it starts..."

The ribbon fails at accessibility.

This is a 7th way it's worse.

Menus can be accessed and manipulated in a consistent way with keyboard controls. Up/down/left/right/enter. 5 keys and you have total control. You can use this with a mouth control if you have no use of any limbs. This is good for people with motor disabilities but it is also good for keyboard-centric users with no disabilities. This is good design: it's adaptable and it's flexible and it fits different needs. But also, you can use letters to leap faster through the menu bar, so power users and touch-typists can navigate faster. All blind people who can type are touch typists; they have no other option. So this feature that aids accessibility also aids power users.

None of this applies to the state-sensitive context-sensitive ribbon. That is an 8th way it's worse.

You are wrong, and what's more, you are wrong on multiple levels, some of which I have itemised. I could get to 10, I suspect, but I have a job to do and this is not it.

Stop defending bad design. Learn to look deeper at good design that lasted decades and learn to ask why things you don't like so much survive and are widespread and have not been replaced by novelties you like.

Post reply on HN