So that's how it worked with MacOS and Windows? Color me surprised.
But bth, Google doesn't seem to care about Android either. Chrome supports it on Snapdragons and that's it. Do you have Xclipse GPU? Like, I don't know, Samsung's current flagship line Galaxy S24 does? Too bad, not good enough.
You can turn pretty much all of it off, disable SIP, boot Linux, whatever you like.
Good security is layered. For example, even with a sandbox escape, and app could not read your full Documents directory, modify the OS, or install a firmware-level rootkit.
What exactly is an old Intel mac and what is a casual work?
For example, I have 2015 macbook pro. The last macos release for it is Monterey. Even brew has problems with that, erroring out when installing packages like libpng and complaining, that I should upgrade xcode cli tools. Which I can't.
Not really; vintage macs turning obsolete are being dropped from the macOS support very reliably. I.e. the 2015 mbp was dropped from 2022 macos release like on the clock.
Never seen this; however, youtube prefers pushing VP9 over H.264. Maybe your computer cannot use hardware decode for VP9 and can for H.264? (Since you mentioned, it is an older one). Maybe the h264ify extension would help.
What firefox cannot do and chrome can is HDR playback.
> however, youtube prefers pushing VP9 over H.264. Maybe your computer cannot use hardware decode for VP9 and can for H.264?
No, even if I download the 4k 60fps file using yt-dlp with forced h264 codec settings locally to my harddrive, Firefox still can't play the mp4 file smoothly.
So it's not really a streaming issue or h264 vs VP9 codec issue. The Firefox core engine doesn't seem optimized to playback 4k and 8k high-frame-rate videos with low cpu utilization. Even VLC for 4k and 8k isn't as smooth as Chrome. I don't know what the Chrome team did but they really optimized that code path to play back hi-res videos.
Interesting, I recently had the opposite experience. Wanted to enable hw decode on an older Intel system and only got it to work on Firefox. Tried several different instructions from the web on how to force chrome to ignore any blacklists for drivers or anything, but still no luck.
Oh and a while ago I noticed (on a more modern system) that enabling hw decode makes chrome ignore the aspect ratio of the video and displays it like the pixels are square. Again Firefox handled it fine.
YouTube is routinely broken for Firefox, especially when navigating around in places like shorts. I actually find this to be a feature because it prevents me from continuing to mindlessly consume. But it is broken.
Do they? There's no lack of Electron UIs on Mac and Windows. What's even a native widget library on Mac and Windows today? Do Swift-UI and WinUI (v3 nowadays) count? It's not as clear cut as it was in 2000s.
Yes they do, that is why I clearly mentioned "still".
Native widget libraries is whatever the OS vendor puts on the SDK, and ships on the installers for their compilers.
The large majority of Electron apps that happen to land on Mac and Windows land, usually come from GNU/Linux shops, that also feel like targeting other operating systems, and since that is the solution for GNU/Linux, they dump it into everyone else.
In the process they help Google take over the browser ecosystem, and then talk about how M$ used to be all over the place with IE.
Native widgets libraries were historically those, who were only one that knew, how to talk to the display server. So if you wanted to write another widget library, you had to link to them anyway, to use them as a proxy. That's how Qt, for example, runs on Windows or Mac, using the old win32 api or Cocoa.
But meanwhile, the OS vendors got creative and pumped out a bunch of new, _more modern_ libraries, which have abilities that the old, "system" ones do not have. You want Acrylic design on Windows? Better be satisfied with WinUI -- which, in v3 is the recommended way to write native applications by the platform owner, and which is decoupled from system releases and from Windows SDK.
Electron apps are coming from any shop, that want to throw together some installable, locally running app and figured out, that paying HTML+CSS devs is cheaper, than paying C++ (or ObjC) ones. Having shorter development time is also something positive. It has nothing to do with Linux shops; there are Electron apps, that could be running on Linux if there was a will, but aren't (Whatsapp), or almost-electron-but-edge_webview-instead (Teams).
In 2024, the recomend ways to write GUIs in Windows are Win32 (your native widgets library), exposed by WinForms. WPF has parity with WinUI 3, in recomended way by the platform owner, officially communicated at BUILD 2024.
Doubled down at .NET Conf 2024 during the last week.
Regardless of the GUI framework from Apple, and Microsoft, those are managed bindings to the underlying native APIS (Win32 and Cocoa), which is why they also expose handles to do lowlevel stuff if one so desires, coding like 2000.
Webviews are a different matter, as they don't require shipping Chrome with the application.
It definelty has a lot to do with Linux shops, as they can't be bothered to support GNOME, KDE, Sway, XFCE, or whatever everyone else uses, so Electron it is.
And then they want Mac OS and Windows customers as well.
> In 2024, the recomend ways to write GUIs in Windows are Win32 (your native widgets library), exposed by WinForms. WPF has parity with WinUI 3, in recomended way by the platform owner, officially communicated at BUILD 2024.
| Many apps for Windows are written using Win32, Windows Forms, or UWP. Each of these frameworks is supported and will continue to receive bug, reliability, and security fixes, but varying levels of investment for new features and styles. For more information about these app types see the following tabs.
Yes, in Build 2024, there was backpedaling back to WPF, since WinUI is in terrible shape.
> Webviews are a different matter, as they don't require shipping Chrome with the application.
Electron also doesn't ship Chrome with application; it ships the rendering engine (blink) and javascript engine (v8). Which is exactly the same, as edge webview. Unlike edge webview, they are not dragged in by Microsoft Edge, the browser (so you get it whether you have an use for it or not).
> It definelty has a lot to do with Linux shops, as they can't be bothered to support GNOME, KDE, Sway, XFCE, or whatever everyone else uses, so Electron it is.
So how do you imagine such support would look like? I know a thing or two about development on linux, but I have no idea what would supporting XFCE or Sway explicitly in an app would involve. Unless you hyperbolize, right?
The only real decision would be choosing Gtk or Qt; the desktop environments have no real impact on your app and with Qt, you are getting the multiplatform support, that is supposedly behind the electron usage of those linux shops.
Also, what exactly are those linux shops, that target multiplatform by using electron? Is it like Cisco? Or Meta? Maybe Bitwarden? Discord? Figma? Microsoft (skype, vscode)?
5K displays are very limit set in the first place. There is Studio Display, LG Ultrafine 5K and Samsung ViewFinity 5K. Samsung seems to be better value than Studio Display.
It is, but on the other hand, I would prefer to have plastic display with two inputs (since I have two computers; desktop and laptop) than aluminum one with just one input.
It was a response to Youtube playing stupid games with demonetizing and changing thresholds for payouts; they thought, that they can push creators around. They were wrong.
So what gives you a right to download and use the software in the first place? The copyright law forbids that by default. What permission other than the license do you have?
I'm not sure what point you are trying to make but thankfully, given that they obviously can't be trusted to maintain security-critical software (despite what they imply on their website and marketing material), I haven't downloaded or used it or recommended it anywhere while consulting.
But bth, Google doesn't seem to care about Android either. Chrome supports it on Snapdragons and that's it. Do you have Xclipse GPU? Like, I don't know, Samsung's current flagship line Galaxy S24 does? Too bad, not good enough.