opencl

There aren't a whole lot of power management features available in the hardware, the SoC just wasn't designed for mobile/battery use. About all you can do is disable USB/ethernet/HDMI if not needed for your use case, or drop the CPU/GPU clocks.

Seems like it includes owner operator pay without deducting the (quite large) expenses.

No, the category is a performance specification (higher category is faster), the band is the frequency of the radio signal.

I think the performance loss for a higher resolution screen would not be worthwhile here. The GPU in the Pinephone Pro is a lot faster than the original but it's a 6 year old design that is not exactly great by modern standards. And a lot of the existing software stack is not even GPU accelerated yet. 1080p would probably give quite noticably worse performance.

There are 31" and 42" e-ink displays available, but they cost a few thousand dollars. The 42" is pretty close to 2ft by 3ft, 25" x 33".

There are a few devices around that size with 300PPI screens. Kobo Forma, Boox Nova2, Likebook P78, etc.

It's quite simple, the market for paid end user applications on Linux is tiny. Canonical was saying years ago that they were going to add paid applications to the Snap Store but seemingly never got around to it. Elementary's App Center has integrated payments but they are optional and ~99% of users do not pay anything.

You can certainly make a living selling a cross platform application that supports Linux, but it's probably quite difficult to make much of a living selling Linux-only applications.

Drawing video took up a very large fraction of the CPU cycles on the ZX81 so there was a 'fast mode' and 'slow mode'. Fast mode cut out video output when programs were running, slow mode left it on and ran at something like 1/4 the speed.

They've done a little bit of that with DirectX for WSL2.

https://devblogs.microsoft.com/directx/directx-heart-linux/

There are some a few public docs.

https://estradajke.github.io/k9-simples/

https://code.kx.com/q/learn/

It's CPU specific in the sense that the CPU needs IOMMU instructions (almost everything made in the past 10 years) and OS version specific in that Windows and Linux have both supported it for about 3 years.

The problematic part is that the UEFI needs to support it, it seems most systems with Thunderbolt have enabled it since 2018 and systems without Thunderbolt still don't bother.

It's Electron, the Mac and Linux versions will look exactly the same.

AMD has been doing custom x86 SoCs for a long time, mostly for game consoles. It hasn't had any real impact on the laptop/desktop/server market so far.

The software could be pretty simple. Hook a button up to GPIO, write a bash wrapper around one of the command line VoIP clients, write a little program to call the script when the button gets pressed, autorun that one on boot.

The current Ranger model is not just larger than an 80s Ranger, it's larger than an 80s F150!

There are a couple of 10 bit IPS 4096x2560 monitors these days. They are ludicrously expensive, but they are out there.

144Hz monitors are definitely a noticeable improvement over 60. GSync/Freesync are nice in games, not really relevant elsewhere.

If you want to avoid microstutters associated with power savings you can adjust the minimum clock the CPU governor will set.

The DRM on blurays has been broken for over a decade now. The newer 4K blurays are a pain though, there are only a few drives that work and you will probably need to reflash the drive firmware.

That's what it costs buying the parts from them.

$750 laptop, $360 RAM, $1000 SSD. The RAM is pretty reasonably priced, but you can get your own 4TB SSD for about $500 less. $150 less if you want the exact same model they're selling.

It's a much more reasonable level of markup than RAM/SSD upgrades from other manufacturers, though of course being able to bring your own is a major selling point.

A lot of e-ink devices just run Android so it's relatively easy to run whatever you want on them.

Refresh rate depends on how much of the screen is updating at once. Scrolling a whole page is pretty bad, updating a small region is reasonably quick. Some devices have an 'A2 mode' that makes it somewhat faster by just doing black/white instead of grayscale.

Not as cool but if you really want to run System 7.5 on an e-ink display you can already run a Mac emulator on an ebook reader today.

https://imgur.com/a/kJRCR

Firefox has had WASM SIMD for a few months now, it was enabled by default in FF89.

https://bugzilla.mozilla.org/show_bug.cgi?id=1695585

My understanding is that the licencing of the console SDKs and their associated NDAs is so restrictive that you're not allowed to publish source code using their APIs. Depending on the GPL version you may be able to get away with publishing the source minus the console-specific parts.

The Android version seems abandoned, it hasn't been updated in several years and there are several reviews complaining that paid features no longer work. Are there any plans to update it?

When I worked at one of these warehouses, anything over 30 minutes per day of 'time off task' out of a 10 hour shift was supposed to get you written up. Time off task being defined as any period greater than 5 minutes without doing work that the computer tracked.

It's certainly possible, there's already a company[1] that sells cameras with this modification performed. And a few cameras that come from the factory with no Bayer filter, like the Leica Monochrom, but all the ones I know of are very expensive.

[1] https://maxmax.com/shopper/category/9241-monochrome-cameras

Intel is not even manufacturing these, they are TSMC 7nm so they are competing for the same fab capacity that everyone else is using.

Avantek also sells a few workstations that are basically Ampere ARM server boards stuffed into desktop cases. Very powerful CPUs with up the 80 Neoverse N1 cores, lots of PCIe and RAM slots, very expensive.

https://store.avantek.co.uk/arm-desktops.html

What makes all of the other ARM hardware available unsuitable?

Neat project. I wonder how hard this would be to adapt to an ESP8266/ESP32 target (or other micros with onboard radios) and sending the code wirelessly.