kagenouta

5 ms·

1.
by kagenouta 6y ago
If we're nitpicking, it's Pascal case when it starts capitalized :-p
2.
by kagenouta 6y ago
> x264 and x265 are not hardware accelerated, either. Huh, TIL. Though I would also sort of want to know where x264 and x265 were a year in, tbf.
3.
by kagenouta 6y ago
Note that the encoders are slower largely because it's not hardware-accelerated yet. We can reasonably assume that will change, as basically every major player in the CPU/GPU spaces[1] has signed on to back this. Even Apple is a
4.
by kagenouta 6y ago
Brave and a couple of others are actually getting extension support in the near term because Kiwi recently went FOSS.
5.
by kagenouta 6y ago
Hard agree. I'd also argue that any meaningful antitrust action we may eventually impose on big tech companies should force this. If the one thing so far that's led the feds to threaten this is that they wanted to build a modern p
6.
by kagenouta 6y ago
Huh, TIL.
7.
by kagenouta 6y ago
> Qualcomm being closed source is the biggest issue with running good (user-respecting) software on phones, since basically every single Android has a Qualcomm processor/GPU. Actually there are kernel drivers for several Snapdragon
8.
by kagenouta 6y ago
Which just sort of loops back to how if Web-based chat had a spec with meaningful user traction we wouldn't have any real use for RCS in the first place. Also how XMPP could have been that spec, if Google hadn't decided when launc
9.
by kagenouta 6y ago
Tackling this point separately: the entire reason they do this is because they routinely experiment with side projects and then build the ideas that work well into the services that gain traction. As much as it comes with the drawback of be
10.
by kagenouta 6y ago
Not within the spec. Which was sort of the point I was (poorly) trying to make - that it's a huge caveat, but otherwise a decent fallback if and when that changes. Google is adding an implementation into Messages, and it's honestl
11.
by kagenouta 6y ago
I, for one, have a bigger problem with it forcing the use of phone numbers as a sign-in method. They're an arbitrary identifier from a legacy system that there's not really a point in continuing to extend, because if your device i
12.
by kagenouta 6y ago
Am I the only one thinking it's weird that this rolls out on ChromeOS first but other Linux platforms (including Android) last?
13.
by kagenouta 6y ago
Also worth noting that one of Google's long-term goals is to make Android bootable on mainline. They've been slowly upstreaming the patches they built into Android's base kernel, and their Treble roadmap involves further isol
14.
by kagenouta 6y ago
Or that you still call your OS "intuitive" after shuffling keyboard shortcuts around so hard that not only is your OS running a completely different set of hotkeys from everything else you use, but so is every app you used that wi
15.
by kagenouta 6y ago
11 is still early into its public testing phase -- developer previews are essentially pre-beta -- so it's hard to really make concrete guesses at what user-facing stuff will show up in the next version at this point.
16.
by kagenouta 7y ago
Tl;dr up front: For now. The UI absolutely isn't as fleshed out, but that's not the thing that makes this important. Yeah, it's built primarily as a test environment for apps that require free-form multiwindow, multi-resume
17.
by kagenouta 7y ago
Depends on your device state. If you've unlocked your bootloader already, you should only need to wipe system-level partitions (which would affect applications, but not user storage). But if you haven't, you need to do that first,
18.
by kagenouta 7y ago
This actually happened once before -- Cyanogen himself spent several years working as an engineer at Samsung. The project didn't actually start running into serious sustainability issues until the team tried to build it into a company.
19.
by kagenouta 7y ago
You might want to look into Pipewire - it's a next-gen A/V framework being developed by one of the creators of GStreamer. It isn't ready for prime time yet, but the long-term goal on the audio side is to replace both PulseAud
20.
by kagenouta 7y ago
So you're saying, then, that it's some sort of cowabunga lifestyle?
21.
by kagenouta 7y ago
> dx11 implemented in Vulkan Also 9 and 10, FYI. DXVK targeted 10/11 initially, and merged in D9VK (a separate but similar project covering DX9) about a month ago. Proton also has a branch that bundles in VKD3D (Vulkan layer for DX1
22.
by kagenouta 7y ago
If you expect to reliably be able to fix something -- especially at scale -- you need to understand how it works. Specifically, you need to understand how it should work, where it's deviating from that, and what you can do to address