Live data from Hacker News

HTTP/3 is everywhere but nowhere

httptoolkit.com

471–480 of 504 posts

Re: HTTP/3 is everywhere but nowhere

#471
post #468

Earlier quoted context omitted.

Because in the relevant distros it is included in the first-party feeds. Only Debian acts like a special snowflake making it needlessly complex for everyone (including Rust). I believe there is an ongoing work to modify .NET's full source build (i.e. https://github.com/dotnet/source-build ) to satisfy Debian's admission requirements, but really it's a problem inflicted by Debian on themselves, not the other way aroun…

Rust is in debian. Why do you do FUD?

My comment says

> making it needlessly complex for everyone (including Rust)

have I missed something?

Re: HTTP/3 is everywhere but nowhere

#472
post #468

Earlier quoted context omitted.

Rust is in debian. Why do you do FUD?

My comment says > making it needlessly complex for everyone (including Rust) have I missed something?

Rust isn't a person, just FYI. If you had a point, please make it.

Re: HTTP/3 is everywhere but nowhere

#473
post #231

Earlier 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.

Can you name some examples of popular .Net applications on GNU/Linux or *BSD operating systems?

osu is a fairly popular rhythm game that is written in .net

https://github.com/ppy/osu

Re: HTTP/3 is everywhere but nowhere

#474
post #466

Earlier quoted context omitted.

I'm not sure why you are reading the docs sideways but just in case - C# has method overloading. Process API, while dated, simply offers multiple overloads suitable for different scenarios. Launching a new process can be as easy as `Process.Start(path, args)`. Although if you are doing this, I can recommend using CliWrap package instead which provides nicer UX. Anything is possible the second you stop looking for a s…

> Took you long enough. Yeah I do have a life. I advice you to get one as well. > Launching a new process can be as easy as `Process.Start(path, args);`. -_-' Same exact problem. Letting every single process do their own escaping of the arguments. A proper portable API would have an array of strings for the arguments, to map execve(). That's how on windows every program does its own escaping and there's lots of progr…

Look, it is very difficult to hold a conversation with someone who responds with "you're just a fanboy, it's 5!" to "2 + 2 equals 4".

On the off chance you are making an intentionally inflammatory reply - you could also ask normally.

Let me try one last time (and now I vaguely remember having similar conversation here before).

On Ubuntu:

  sudo apt install dotnet9
On RHEL (8 or 9):

  sudo dnf install dotnet-sdk-9.0
On Alpine:

  sudo apk add dotnet9-sdk
Then, you can get a simple cross-platform application template like this:

  dotnet new install Avalonia.Templates      && \
  dotnet new avalonia.app -o AvaloniaExample && \
  cd AvaloniaExample                         && \
  dotnet publish -o build -p:PublishAot=true && \
  ./build/AvaloniaExample
The above can target: Linux, macOS, Windows, WASM and with some caveats Android and iOS (although I would not recommend using Avalonia for mobile devices over e.g. Flutter).

The build folder will contain the native application itself and the Skia dynamically linked dependency alongside it (and possibly some symbols you can delete). This is very similar to the way Qt applications are shipped.

This is just one GUI framework. There are other: Uno Platform, Gir.Core (GTK4 + GObject libraries), SDL2 via Silk.NET, Eto. I'm sure there's more.

What is bewildering is you could argue about "first-class" or "subpar", etc. But "does not work at all" is just ridiculous and indefensible. What kind of thought process leads to this conclusion?

In any case, I doubt you're going to read this since your replies seem to indicate interest in tilting at any windmill with ".NET" label on it instead, but at least my conscience is clear that I tried to explain this to the best of my ability.

Re: HTTP/3 is everywhere but nowhere

#475
post #447

Earlier quoted context omitted.

I'm pretty it's just: sudo apt-get install dotnet-sdk-9.0 No?

That comes after adding an untrusted 3rd party repository no? Why are you omitting that part? Which means that nothing written in .net will enter the real repository until that changes.

> Why are you omitting that part?

Because I didn't have to do that. Have you considered your distro might be special for reasons that have nothing to do with .NET?

Re: HTTP/3 is everywhere but nowhere

#476

Earlier quoted context omitted.

Huh, I have one for my personal home network :-) Granted, that is in RIPE. As long as you're multihomed, how can they turn it down?

Multihoming is broken for most people in IPv6 space. It's stupid easy in IPv4. https://blog.ipspace.net/2010/12/small-site-multihoming-in-i...

You lost me at “multiple per-interface NAT rules […] with some load balancing trick” being “stupid easy”…

But BGP+PI is indeed how multihoming is supposed to work, both in IPv4 and IPv6. (Well, in IPv6, you can put two prefixes on-link and do poor man's multihoming that way, which you cannot reliably in IPv4.) Of course, if you define “it cannot be BGP+PI”, then indeed it's probably harder, but if you exclude the intended solution, obviously there's no intended solution.

Re: HTTP/3 is everywhere but nowhere

#477
post #125

Earlier quoted context omitted.

Only Typescript is in-house. Others are acquisitions. Do you remember Embrace, extend, and extinguish times? https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

VS code is mostly in house too. Sure, they don’t own Electron, but I was at MSFT when project Monaco (which became the basis for VS Code) was started and remember being very impressed by it back then

They acquired Electron alongside with Atom with GitHub. It is hard not to make parallels between Atom and VS Code

Re: HTTP/3 is everywhere but nowhere

#478

Earlier quoted context omitted.

For a long time all my internet connections were bad (slow, unstable or both). Compressing HTML/CSS/JS, avoiding JS unless absolutely needed, being careful with image sizes and formats, etc, helped a lot... so I guess this makes me biased. Today I have fibre at home, but mobile networks are still patchy. I'm talking sub 1Mbps and high ping/jitter sometimes. So you can see why I think an "irrelevant" optimisation that…

That was my point: 300ms sounds like a lot until, like me too, you're on a slow connection and those 300ms on the entire 10 second page load are utterly irrelevant. You were already expecting a several second load time, that 300ms is not something that even registers: the HTTP negotiation on a modern page is _not_ what you're noticing on a slow connection. You're noticing literally everything else taking forever inst…

3% speedup is still pretty good. (especially because with some of the awfulness, it's possible to get bottle-necked by multiple of these in which case it could be 6 or 9%)

Re: HTTP/3 is everywhere but nowhere

#479
post #459
post #356

Earlier quoted context omitted.

GitHub is behind ADO in multiple areas. Boards is the one they're furthest from ADO on; leaving that for last is letting them get the others to a state where ADO users can successfully migrate some of their work to GitHub now, even if the boards need to stay in ADO. That said, Microsoft is never going to be able to completely kill Azure DevOps. If nothing else, they'll have to keep it alive for enterprise customers'…

> TFVC source control history Surely there's a migration path to git from TFVC? Many large projects successfully moved from CVS and SVN into git. I'm just surprised that, after 7 years of owning Github, Microsoft hasn't plowed their resources into Github's Projects. It's literally the number one complaint I see regarding project management inside Github - and would likely be an easy way to scale subscriptions for Tea…

The different branching approaches makes migrating history difficult. Microsoft's recommendation is to migrate just the tip, but will allow you to migrate up to 180 days of history for the trunk (no branches).

If you need branch history, or more than 180 days worth of history, the only option is third-party tooling (git-tfs). It seems to work good enough for development purposes (i.e. git blame)... but I'm not sure if it's good enough if we need the history for legal purposes.

Re: HTTP/3 is everywhere but nowhere

#480

Earlier quoted context omitted.

It's horrible that the Internet is slowly becoming a locked-down ecosystem. Everyone should turn off HTTP/3 in protest of this. https://news.ycombinator.com/item?id=43329320

What exactly are sites supposed to do to prevent being the targets of DDoS, spam, fraud, aggressive bots, and other abuse? And it's not "locked down", it's usually just a CAPTCHA as long as you're not coming from an abusive IP range like might happen with a VPN. Also there are a thousand other signals besides HTTP/3. It's not going to make a difference.

It's not "just a CAPTCHA", it's a monstrosity involving tons of invasive JS that requires the latest Big Browser and attempts to identify you.
Post reply on HN