Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Dependency Has Risks

blog.miloslavhomer.cz

Post reply on HN
Print view View original

191–200 of 238 posts

Re: Microsoft Dependency Has Risks

#191

Post by Arch-TK »

jofzar wrote: post #123
kookamamie wrote: post #115

Earlier quoted context omitted.

Yes, that's the essential reason. Even though that barrier has been lifted with Vulkan matching DX12 in many ways, the accumulated mass moves slowly.

Has there been a game where vulkan performance has been better then dx12? Whenever they are side by side vulkan always performs worse in my experience.

If games run faster on linux with DX12 translated to Vulkan than they do on identical hardware running on Windows 11 then I can't imagine a particularly big performance difference.

Re: Microsoft Dependency Has Risks

#192

Post by metaltyphoon »

guappa wrote: post #167
metaltyphoon wrote: post #93

Earlier quoted context omitted.

When it starts with the phrase “FIP-S compliant”, hardly anyone is wants to do that on Linux.

You live in a parallel universe where wolfssl doesn't exist?

Oh I know about this, but tell what’s simpler: Embed wolfssl per app / make it work with openssl as a module (for system wide usage) or turn a registry key to true?

Re: Microsoft Dependency Has Risks

#193

Post by firesteelrain »

smaudet wrote: post #186
firesteelrain wrote: post #40

Earlier quoted context omitted.

Samba4 is the closest you can get. It is not as nice as ActiveDirectory.

> Samba is an important component to seamlessly integrate Linux/Unix Servers and Desktops into Active Directory environments. It can function either as an Active Directory Domain Controller or as a member server. What's something that AD provides that this does not? It certainly sounds like an (almost) drop-in replacement.

Samba4 covers core AD features like Kerberos, LDAP, and can act as a DC, but it’s not a full drop-in. GPO support is limited, management tools aren’t as robust (no full RSAT equivalent), and some advanced AD features (like DAC or ADCS) aren’t supported. Fine for smaller setups, but not 1:1 with enterprise AD.

Re: Microsoft Dependency Has Risks

#194

Post by xigoi »

duped wrote: post #60
bob1029 wrote: post #18

The trick with Microsoft is to very carefully separate the good parts from the bad ones. Labeling all of Microsoft as banned is really constraining your technology options. This is a gigantic organization with a very diverse set of people in it. 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 situation…

Microsoft, for all their warts, has the absolute best documentation for every public API in Windows. I'd go so far as to say it's better on average than manpages in Linux and BSD and light years better than the actively hostile bullshit from Apple. Submitting a bug report though, you gotta know people or know where to ask.

This is peak documentation:

https://learn.microsoft.com/en-us/dotnet/api/microsoft.offic...

Re: Microsoft Dependency Has Risks

#195

Post by cyberax »

jiggawatts wrote: post #39
cyberax wrote: post #34

Earlier quoted context omitted.

I tried developing an MS .NET app and it's indescribably bad. The deployment story is non-existent, monitoring, tracing, alarming is barely there. You have to work with MS libraries that are on life-support with glaring bugs still present.

Unless you found yourself in some bizarre dark corner of a huge ecosystem of products, that's just not true. Deployments are just "file copy". You don't even need Docker, because Windows isn't Linux, it has stable user-land APIs so apps are portable . Not to mention that the dotnet sdk can create container images directly without even needing Docker installed: https://learn.microsoft.com/en-us/dotnet/core/containers/…

> with C code blended in randomly

And now add a small Python neural network to a .NET app. Just to do some mild AI stuff. Go on, I'll wait.

Oh, and I forgot: don't forget about data migrations. It's a freaking disaster in .NET deployments. Apparently, the best practice is to apply them manually?

Re: Microsoft Dependency Has Risks

#196

Post by cyberax »

mrcsharp wrote: post #141
cyberax wrote: post #34

Earlier quoted context omitted.

I tried developing an MS .NET app and it's indescribably bad. The deployment story is non-existent, monitoring, tracing, alarming is barely there. You have to work with MS libraries that are on life-support with glaring bugs still present.

> The deployment story is non-existent Wrong! it is as simple as executing `dotnet publish`, zipping up the output folder and sending that package somewhere using whichever protocol and shell utility you like. > monitoring, tracing, alarming is barely there Also wrong. OpenTelemetry is fully supported by first-class packages and the dotnet runtime itself exposes a lot of counters. There are a lot of tools to monitor…

> Wrong! it is as simple as executing `dotnet publish`

Yeah. And now add a C/C++ component there. Or maybe a neural network in Python?

In my case, it was a ray tracer that used a GPU.

"Just zip it", yea sure.

Re: Microsoft Dependency Has Risks

#197

Post by esperent »

graemep wrote: post #170
esperent wrote: post #126

Earlier quoted context omitted.

Also, if you're a small business without a dedicated tech team, what are your options that don't involve relying on a single big company? Speaking for myself, running a bakery, I chose MS 365/Teams with regret but accepting that there's nothing else out there with the same value proposition except maybe Google workspace. They have regional pricing so we get everything for the equivalent of $3.50 per user. Basically n…

> The only thing I've found with a close value proposition (still slightly more expensive even if I limit to just a few gb of space per user) is self-hosted Nextcloud, which is about the same level of janky and requires a tech person or team to set up. I would not imagine storage to be a major cost with something like Nextcloud. They major cost is going to be the tech person to set it up, and you do not need that man…

I've already set it up and we're running a test with 4 users since about a month now. I'm hosting it on Hetzner VPS with storage on Wasabi, backups on Backblaze. You're correct that storage is cheap. Compute and ram are the main costs, and I'm not sure how to quantify that until/if we run with the full team of 30 people. My current setup of 4 dedicated vcpus, 16gb ram is massive overkill for 4 people, hopefully it's enough for 30.

It's currently at around the break even point compared to MS Teams. I think maybe $5 a month more expensive all in for the VPS, storage, and backup.

It would be cheaper if I could run on Arm but unfortunately Hetzner doesn't have that in their Asia region yet.

Re: Microsoft Dependency Has Risks

#198

Post by esperent »

dismalaf wrote: post #189
esperent wrote: post #126

Earlier quoted context omitted.

Also, if you're a small business without a dedicated tech team, what are your options that don't involve relying on a single big company? Speaking for myself, running a bakery, I chose MS 365/Teams with regret but accepting that there's nothing else out there with the same value proposition except maybe Google workspace. They have regional pricing so we get everything for the equivalent of $3.50 per user. Basically n…

I personally think Google workspace is better for small business. I think filesharing/permissions/synchronization is much easier and more intuitive across machines and employees and since everything runs in the cloud if you have say, iPads for the POS they can also use Google everything pretty easily. Google Sheets is IMO also much nicer than Excel and for small business you don't really need to deal with Excel lock…

Yeah, we were just starting out and really needing to keep every possible cost down when I chose MS. Looking back I definitely wish I'd paid a bit extra for Google Workspace though, it does look much better suited for a business at our size. Plus, I just cannot get people to use MS Office, they're constantly sharing Google sheets and docs around. Habits are hard to break!

Teams is much better suited for a company with 1000 staff and a tech department. Admin is massively overcomplicated. Oh well, hindsight is 20/20 I guess.

> That being said, the price you got seems unreal.

We're in Vietnam, and like I said, regional pricing. It is a good deal, but doesn't look quite as unreal from over here. Really wish more companies would do regional pricing, $8 a month for slack, $10 for notion and so on is basically a no go for a small business here.

Re: Microsoft Dependency Has Risks

#199

Post by throwaway48476 »

velcrovan wrote: post #5
throwaway48476 wrote: post #3

In the era of globalization businesses expected to only follow a set of harmonized global laws set through treaty. TPP etc. Now globalization is reversing and business is expected to follow the law of the nation they're from wherever they're operating. Such risks will have to be factored in now.

Businesses have never been exempt from the laws of the nation they're from.

The expectation was that international trade courts would be placed above and overrule national courts. That's why the reaction to TPP was so negative.

Re: Microsoft Dependency Has Risks

#200

Post by majkinetor »

mrcsharp wrote: post #181
majkinetor wrote: post #152

Earlier quoted context omitted.

Yeah, that is a new thing, but honestly it existed a way back, its just that it is now officially supported. But you are missing a point here. It's about the language, ecosystem and practicality. In shell, you need correct abstraction that lets you work in fast and efficient way and lets you interact fast when debug is needed. What is done using c# in 10 lines can be done in a single line in pwsh. In my book, lower a…

> What is done using c# in 10 lines can be done in a single line in pwsh Mostly, yes. The problem is that the moment I need something more than what a single cmdlet or bash utility can provide, now I have to use an awkward looking scripting language (bash is the worst offender here). Almost every time I found myself having to write a somewhat long script file, I wish I could just do it with a C like language instead.…

There are many simple tasks in a typical multiyear project. Most of my scripts are between 100 and 1000 lines of code.

Example: https://github.com/majkinetor/SSImport

That script made noticeable difference in speed, quality and pleasure on our recent project (production tests on payment gateway for half of the country) as before I wrote it, devs did it by hand which took 10s of minutes every day with awkward tools (if they made an error, even more) and they complained about the chore. The script literarry replaces entire feature of the Sql Server Management Studio and I did it during the weekend.

Regarding syntax, not sure why would you consider that awkward. IMO, it can't be easier to read in any language, both configuration and code.

Post reply on HN