I got curious and searched up your examples. While the StarBook looks like the most compelling alternative to the Framework laptop with coreboot and good repairability they don't seem to feature any modular ports, which is arguably what sells the Framework laptop for some people. Even for me, the thought of being able to swap out a USB-C charge port for a SD card reader is very appealing.
The other one, the PrimeBook Circular, doesn't appear to be on sale anymore? Their website is gone and an empty parking page loads.
Define "easily"? Non-tech-savvy users will never even touch an install USB or know what regedit is. They'll just see the dialog saying "your computer doesn't support Windows 11", chuck it in the bin, and buy a new one.
The comment is arguing that if Meta were to change the rules, they could easily block such sideloading of APKs by pushing out a simple system update. I don't think they will given the backlash, but the possibility is there.
By capable, the hardware is, but the software isn't. IIRC macOS removed the libraries required to run 32-bit applications back in Mojave or Catalina. So it's not really lying. While it is annoying that we can't use legacy software without resorting to workarounds like VMs, it does move the industry forward to 64-bit apps, on macOS at least.
That is terrible. I have a number of issue reports open with immich but didn't know about this particular snag. Has this been reported to their GitHub?
That only mitigates the problem of the official launcher not existing for Linux. Games are still installed with Proton.
For example, I was trying to install Into The Breach, which is available on both Steam and Epic. Steam has builds for all platforms, while Epic only has the Windows build. If I install the game using Heroic, it installs it with Proton, resulting in worse battery life and performance compared to the native build. Which is what you want to avoid with handhelds like the Steam Deck.
The one advantage that air fryers have over standard convection ovens (IMHO) is that you can make smaller portions, and because these products are designed to cook small portions they can direct a ton of heat at the food, cooking it very quickly. Prepackaged meals' instructions usually mirror my experience as well, saying that cooking in an air fryer will require less cook time compared to an oven, and a drastically lower temperature as the heating element is literally right next to the food as the air circulates the heat.
Otherwise, if you already have a convection oven and don't mind waiting a bit longer, I don't see a good reason for purchasing an air fryer (other than the aforementioned advantage).
Twitter (or X or Y or whatever the heck they're calling it nowadays) doesn't show replies if you're not signed in, which breaks all tweet threads. Amazing hostile UX right there.
It's a remote that charges via the USB-C port. If it doesn't follow USB 2.0 spec, or the USB-PD spec, or any spec associated with the type-C port, how is it supposed to get power from the host device/charger?
Author here; I don't think my blog post is in support of the USB-IF (unless I missed a sentence I wrote somewhere that insinuates otherwise...) I just think selling defective products that don't charge with certain cables shouldn't be allowed.
Hi, author here. The quote you mentioned from Wikipedia indeed says that devices don't have to implement all the capabilities of the connector. However, further down, it says the following:
> USB-C devices may optionally provide or consume bus power currents of 1.5 A and 3.0 A (at 5 V) in addition to baseline bus power provision; power sources can either advertise increased USB current through the configuration channel, or they can implement the full USB Power Delivery specification using both BMC-coded configuration line and legacy BFSK-coded VBUS line.
And further down:
> However, to connect a USB 2.0/1.1 device to a USB-C host, use of Rd[57] on the CC pins is required, as the source (host) will not supply VBUS until a connection is detected through the CC pins.
As the device doesn't implement the full USB PD specs, it must advertise that it wants power through the CC (configuration channel) pins. This is part of the specifications and it must be properly implemented.