The most popular internet protocols are 100% text. This fact is indisputable. I doubt that the guys at google even know this, or know why ....
HTTP/3 is everywhere but nowhere
271–280 of 504 posts
Re: HTTP/3 is everywhere but nowhere
#272Earlier quoted context omitted.
.NET suffers from the long lasting reputational taint of Microsoft. It was seen as the sworn enemy of open source and Linux, and for good reason. Today’s MS is not what it was back then. But long memories are not a bad thing, really. If .NET suffers a bit from some unfair perception, perhaps that can remind MS and others what happens when you take an aggressively adversarial approach.
They may be much less Linux-hostile today, but are still plenty user-hostile. Not to mention their lackadaisical security record.
Can you please highlight some examples of .NET’s lackadaisical security record? I’m curious for my own awareness.
Re: HTTP/3 is everywhere but nowhere
#273Earlier quoted context omitted.
More than just that it came from MS. For a long time, .NET was completely proprietary, and only ran on Windows. Now it is open source and cross platform, but it is still fighting the momentum of being seen as Windows-only.
except if you want to use for example system.windows.forms, then "oh well different teams maintain that, nobody made it for linux!!!" "the core is open!!!" they clearly WANT applications written in .net not to be cross platform
It's not about different teams, it's that System.Windows.Forms is exactly what the namespace says. It's Windows Forms. It's a fairly thin wrapper over the Windows API. It's never going to be adapted to be cross-platform and isn't really something they've put any development work into for many years at this point.
If you want a cross platform UI, use WPF with Avalonia. Or if you want something entirely from Microsoft themselves, there's MAUI as an option.
Re: HTTP/3 is everywhere but nowhere
#274Earlier quoted context omitted.
GitHub was purchased, which is a bit different. TypeScript though I had no idea about! Good for them!
> GitHub was purchased, which is a bit different. Why is that different? The purchase was 7 years ago (?) at this point. Do we make an exemption for SharePoint because it, too, is an extension of FrontPage acquired via Vermeer?[0] At what point does it lose its exemption from "Hate All Things Microsoft"? 10 years? 20 years? [0] https://en.wikipedia.org/wiki/Microsoft_FrontPage
Github looks and works mostly indistinguishable from how it was 7 years ago.
Re: HTTP/3 is everywhere but nowhere
#275Earlier quoted context omitted.
I'm not an expert on HTTP/3, but vehemently disagree about IPv6. It removes tons of overhead and cruft, making it delightful for datacenter work. That, and basically guaranteeing you don't have to deal with the company you just acquired having deployed their accounts with the same 10/16 subnet your own company uses.
The problem I keep running into is that IPv6 support in common infrastructure is somewhat lacking. It's always a headache to learn that some container orchestration system doesn't support IPv6. Or an http client. Or a DNS resolver. Or whatever. Not to mention the supreme annoyance I have that, to this day, my ISP still does not have IPv6 addressing available.
Yep, it's tragic because it all stems from unforced differences vs ipv4. The design was reasonable, but with perfect hindsight, it needed to be different. They needed to keep the existing /32s and just make the address field bigger, despite the disadvantages.
"Everywhere but nowhere" is sorta how I'd describe ipv6. Most hardware and lower-level software supports it, so obviously it wasn't impossible to support a new protocol, but it's not being used.
Re: HTTP/3 is everywhere but nowhere
#276Earlier quoted context omitted.
The ironic thing? GitHub, VS Code, and TypeScript are all Microsoft products.
You mean that Microsoft BOUGHT GitHub , like they did with Skype and many other things.
Skype that they ran into the ground despite it being their best messaging product, and are shutting it down in May.
Re: HTTP/3 is everywhere but nowhere
#277> Really it's hard to point to any popular open-source tools that fully support HTTP/3: rollout has barely even started. > This seems contradictory. What's going on? IT administrators and DevOps engineers such as myself typically terminate HTTP/3 connections at the load balancer, terminate SSL, then pass back HTTP 1.1 (_maybe_ 2 if the service is GRPC or GraphQL) to the backing service. This is way easier to administ…
Speaking of gRPC, it's unfortunate that they went all-in on HTTP/2. Should have made it work over HTTP/1.1. I know others made it work, but it wasn't first-party. Maybe it could've been more popular than JSON-over-HTTP by now.
Re: HTTP/3 is everywhere but nowhere
#278Earlier quoted context omitted.
These are handful of handpicked twitter posts that are almost 3 years old, including the page itself. https://github.com/ghuntley/isdotnetopen The website doesn't even explain what they mean by open. Nor they explain why they think .NET is not open source.
Isn't `vsdbg` still distributed with an incredibly restrictive license? Doesn't sound all too open to me. Further, the twitter posts themselves are still relevant I believe. If someone took over my repo, I'd remember it 3 years later.
VSCodium uses NetCoreDbg. There are community snippets to make the same work for Cursor, NeoVim, etc.
So far, there was little demand to write another debugger integration (because, really, the debugger core is implemented in the runtime itself - what vsdbg, NetCoreDbg and Rider all primarily do is consume the runtime API).
Re: HTTP/3 is everywhere but nowhere
#279Earlier quoted context omitted.
> GitHub was purchased, which is a bit different. Why is that different? The purchase was 7 years ago (?) at this point. Do we make an exemption for SharePoint because it, too, is an extension of FrontPage acquired via Vermeer?[0] At what point does it lose its exemption from "Hate All Things Microsoft"? 10 years? 20 years? [0] https://en.wikipedia.org/wiki/Microsoft_FrontPage
Github looks and works mostly indistinguishable from how it was 7 years ago.
So you are of the belief that Microsoft has not had any effect on GitHub over the last 7 years? Interesting.
Re: HTTP/3 is everywhere but nowhere
#280Earlier quoted context omitted.
I edited it because it's not just my own experience of dealing with this. On twitter, I follow a couple Japanese developers from mainly gamedev scene and even they complain they started hearing more about "but it only works on windows" and "it's not open-source". Don't you find it strange that it should be the other way around the more years pass since .NET went OSS? The link itself is also quite outdated and mainly…
I assumed .NET is Windows-only and proprietary, too, but it has to do with me not having done enough research, so if it is not the case anymore, the blame is on me.
Hey, I just want to commend you for amending your perspective (even if a little). There's a lot of intellectual hoop jumping in this thread with respect to Microsoft.