Earlier quoted context omitted.
it kinda of already begun
Has there been a big ipv6 worm? I thought that the defense against worms was that scanning the address space was impractical due to the large size.
Direct Sockets API in Chrome 131
91–100 of 171 posts
Re: Direct Sockets API in Chrome 131
#92Earlier quoted context omitted.
with so many multiplatform gui toolkits today, tauri and electron are really bad choices
What's your recommendation? I've tried so many multiplatform toolkits (including GTK, Qt, wxWidgets, Iced, egui, imgui, and investigated slint and sciter) and nothing has come close to the speed of dev and small final app size of something like Tauri+Svelte.
but for us an inhouse egui pile of helpers allow for fast applications that are closer to native speeds. and flutter for mobile (using neither Cupertino or material)
Re: Direct Sockets API in Chrome 131
#93Earlier quoted context omitted.
That doesn't really make it any better, if you ask me. The entire Isolated Web Apps proposal is a massive breakdown of the well-established boundaries provided by browsers. Every user understands two things about the internet: 1) check the URL before entering any sensitive data, and 2) don't run random stuff you download. The latter is heavily enforced by both Chrome and Windows complaining quite a bit if you're tryi…
Unfortunately this is the future. Handing the world wide webs future to Google was a mistake, and the only remedy is likely to come from an (unlikely) antitrust breakup or divestment.
Nobody handed anything to anyone. They go with the flow. The flow is driven by people who use their products. The browser is how Google delivers their products so it’s kinda difficult to blame them for trying to push the envelope but there are alternatives to Chrome.
Re: Direct Sockets API in Chrome 131
#94Re: Direct Sockets API in Chrome 131
#95Earlier quoted context omitted.
Which part of "is not a w3c standard and not any standards track" do you not understand? I am not surprised sites like that include Chrome-only non-standards, they've done this for years claiming impartiality
Cry me a river. Apple doesn't need you to defend their strategic and intentional PWA boycott.
Do you understand that for something to become a standard, it needs two independent implementations? And a consensus on API?
Do you understand that "not on any standards track" means it's Chrome and only Chrome pushing this? That Firefox isn't interested in this either?
Do you understand that blaming Apple for everything is borderline psychotic? And that Chrome implementing something at neck-breaking pace doesn't make it a standard?
Here's Mozilla's extensive analysis and conclusion "harmful" that Google sycophants and Apple haters couldn't care less about: https://github.com/mozilla/standards-positions/issues/431#is...
Re: Direct Sockets API in Chrome 131
#96Earlier quoted context omitted.
IPv6 isn't going to happen. Most people's needs are met by NAT for clients and SNI routing for servers. We ran out of IPv4 addresses years ago. If it was actually a problem it would have happened then. It makes me said for the p2p internet but it's true.
What do you mean not going to happen? It's already happening. It's about 45% of internet packets.
Try to connect to github.com over IPv6.
Re: Direct Sockets API in Chrome 131
#97Earlier quoted context omitted.
Unfortunately this is the future. Handing the world wide webs future to Google was a mistake, and the only remedy is likely to come from an (unlikely) antitrust breakup or divestment.
> Handing the world wide webs future to Google Nobody handed anything to anyone. They go with the flow. The flow is driven by people who use their products. The browser is how Google delivers their products so it’s kinda difficult to blame them for trying to push the envelope but there are alternatives to Chrome.
The ancient history of just 10-15 years ago shows Google aggressively marketing Chrome across all of its not inconsiderable properties like search and Youtube, and sabotaging other browsers while they were at it: https://archive.is/2019.04.15-165942/https://twitter.com/joh...
Re: Direct Sockets API in Chrome 131
#98When reading https://github.com/WICG/direct-sockets/blob/main/docs%2Fexpl... , it's noted this is part of the "isolated web apps" proposal: https://github.com/WICG/isolated-web-apps/blob/main/README.m... , which is important context because the obvious reaction to this is the security nightmare
I did a search, and most stuff come from a few years ago.
Re: Direct Sockets API in Chrome 131
#99Re: Direct Sockets API in Chrome 131
#100Earlier quoted context omitted.
The cross platform desktop gui toolkits all have some very big downsides and tend to result in bad looking UIs too.
I've built my app[1] using Qt (C++ and QML), and I think the UI looks decent. There's still a long way for it to feel truly native, but I've got some cool ideas. [1] https://get-notes.com/
Many such applications are accessible on the web, often with the exact UI. They may even have a mobile/iPad version. They may be big enough that they have a design system that needs to be applied to in every UI (including company website). Building C++ code on all platforms and running all the tests may be too expensive. The list goes on.