141–150 of 226 posts
Earlier quoted context omitted.
Do you have a source for real world sites broken? It’s extremely rare for me and I exclusively use Safari and Firefox.
When I use porkbun in Firefox, it hangs and has to be kill -9'ed.
For a very long time, I was pissed at "the web" being abused by heavier and heavier "apps" instead of staying "websites" and keeping "desktop apps". Now I am starting to think that this is maybe just a super inefficient way to improve the technology for desktop apps: after years and a shit load of money put into running apps in the browser, maybe the end technology will just end up being used for desktop apps. And go…
The web had this before briefly. Back in the 90s and 00s, some people just wanted to use Flash. They treated the web browser like it was just a way to run executables in a window. Nothing worked right. Bookmarks, search engines, command-line tools, user preferences for font size, user scripts, view source, right-click menus, ad blockers, auto-translations, user stylesheets, assistive tools, bookmarklets, deep links……
> The web had this before briefly. Back in the 90s and 00s, some people just wanted to use Flash. WebAssembly is different. WebAssembly brings every language to the web. Flash didn't. WebAssembly can render to canvas and enable applications that compile to desktop, mobile, and the web. UI libraries like Avalonia do this: https://avaloniaui.net/ For example, here's C# implementation of Visual Basic 6 compiled to WebAs…
https://adobe-flash.github.io/crossbridge/
Before asm2js was even an idea, Unreal compiled to Flash via CrossBridge.
https://www.youtube.com/watch?v=xzyCTt5KLKU
https://www.youtube.com/watch?v=ZmZS7B1pLWg
To this day, with exception of maybe PlayCanvas, there are hardly any tools that can match the same developer experience for WebGL, almost 15 years later.
It was a rich, interactive, streaming vector file format with a gorgeous and tiny code execution engine. It was an incredible time of creative exploration with many thousands of people figuring out how to make beautiful and ugly and funny and sad things and share them with each other.
Steve took this from us 18 years ago because it clearly threatened his ability to enclose the entire application ecosystem, control who can and can't publish, and charge a 30% tax against every dollar spent on the internet.
Please note: Many of the very same people who shit all over Flash as some proprietary, ethical violation, happily tap away on their iOS devices, sending billions of dollars to Tim.
Of course I'm not talking about you, it's those other people over there.
Earlier quoted context omitted.
No, performance and fidelity are definitely better with the canvas renderers, especially skwasm. Flutter is very inspired by React, but instead of React which does tree diffing to minimize rebuilds, Flutter tries to make rebuilds as cheap as possible instead - for example through its single pass layout algorithm. The issue is that this doesn't map well to the DOM. You can't rebuild cheaply on the DOM because you'd be…
I went and loaded up the flutter web demo on my iPhone 15 Pro https://flutter.github.io/samples/web/material_3_demo/ In addition to the pitfalls mentioned like being unable to select text, every interaction including scrolling is noticeably laggy and dropping frames.
Because of this alone I would not use.
Funny to read this: > So there are only 2 web browser engines, and it seems likely there will soon only be 1, and making a whole new web browser from the ground up is effectively impossible because the browsers vendors have weaponized web standards complexity against any newcomers Ladybird seems to be thriving. Sure, they themselves only plan on releasing a beta version next year, but still. And it's even on the Hack…
What is ladybug's marketshare? Does it work flawlessly with "This webpage works better with Chrome" webpages? It is not even mentioned on https://caniuse.com/?search=web%20components
Chrome is the new Internet Explorer. It successfully replaced it. Only to start sharing most of the qualities that were the reason for Internet Explorer to fail in the market. And there was a web before Internet Explorer as well.
Chrome once started at 0% market share. Displacing the dominant browser has been done before. It can be done again.
Web pages that only worked with Internet Explorer did not age very well. Companies ended up spending a lot on needing to replace those. Making a webapp that only works with Chrome is at this point seriously misguided. If only for the simple reason that you can forget about IOS compatibility if you do (as long as Apple keeps a death grip on the app stores, there will be no chromium based HTML rendering on IOS).
Earlier quoted context omitted.
I went and loaded up the flutter web demo on my iPhone 15 Pro https://flutter.github.io/samples/web/material_3_demo/ In addition to the pitfalls mentioned like being unable to select text, every interaction including scrolling is noticeably laggy and dropping frames.
> unable to select text Because of this alone I would not use.
Uh, hm, I think this critical assertion requires some justification.
Earlier quoted context omitted.
> Nothing worked right. One thing worked right: the app looked the same and acted the same everywhere where it could run.
That’s a bug, not a feature. Apps should match the OS they’re running on.