The company doesn't have to go away, the app just has to have issues. At least with web apps, you aren't depending on the manufacturer investing in nearly continuous upgrades to work in the rapidly changing phone environment
A web UI will continue to work for decades. And app will likely not last a year without updates.
They basically are. They just license their name out now, it’s like buying a Kodak router.
(That’s actually relatively common with various tech-adjacent companies, e.g. off the top of my head both Energizer and Philips license out their brand to third parties for random crap, even though they make actual products themselves too.)
Really. Because it looks less useful than its source.
If I search for Apple on food central, I get offered different types of Apple, like Fuji, honeycrisp, etc. with nutripedia I just get raw and cooked, which are within each type on food central.
In addition, nutripedia has a bunch of what looks like AI written text that is not particularly useful.
Writing an AI generated wrapper around something is not enough to be interesting. What do you see as your value add?
Like a time capsule. Last modified date at the bottom of the page says 2007.
Also:
> Saffron has been licensed to Adobe and is shipping in all Flash-based products, including Adobe Flash CS3. The Adobe Flash Player is the world's most pervasive software platform and reaches 99% of Internet-enabled desktops.
No, the problem is the software has an internal certificate that is about to expire.
This is exactly the sort of scenario where I do not feel bad at all tracking down an online crack that disables the certificate check.
That said, it is probably not in Microsoft's best interest for people to have a legitimate reason to discover how much easier life can be if you pirate software.
As described, the licensing system will fail you into readonly locally unless you subscribe Office Clippy 365, buy Office 2024, apply Office 2021 updates, or (not listed) apply third-party licensing cracks for Office 2019.
Presumably we’ll know soon if network firewalling the licensing server helps, but I expect it’ll just delay the intentional failure by a few months at best.
The odd thing is that this disguises as some bare metal, hackable device.
Their TUI[1] is planned to use react(!), to share logic with their BrowserUI[2]. In the repos you can see how they struggle to get anything gpu backed done (which is required by the browser). Then falling back to wayland to do it for them. (This all seems a mess that LLMs can't figure out.)
Anyway, it does seem to end up in a custom linux desktop environment, with lots of sharp edges that makes it less hackable.
> The 256×144 px screen requires pixel-level rendering, which standard TUI libraries (ncurses, etc.) cannot provide. The proposed solution is an HTML/CSS rendering engine running as a background daemon — a lightweight browser-based renderer that draws menus, popups, and UI components.
First time I've heard anyone call the Flipper Zero "simple" and "focused", most people seemed to have considered it a "swiss-knife" meant to just house a bunch of features and radios, meanwhile the One has less features but more connectivity and I/O.
But apparently you're not alone in feeling this, but I don't understand what from the submission makes you and others believe so, what exactly gave you this impression?
And this one is an 8-core Arm computer and the project has ambitions of some notoriously difficult things: no binary blobs, full mainline support (including a NPU), reinventing small-screen UI for more serious handheld computing, and supporting a ton of high-bandwidth interfaces.
Agreed. This will likely never ship with all the bloat. Custom AI model, custom OS, extremely custom architecture (2 "main" processors running independently...), barely reuses any of the previous work from Flipper Zero.
A combined MPU and MCU architecture isn't that exotic. ST microelectronics currently sells a single chip with that contains a two core Cortex A7 Microprocessor combined with a microcontroller. Admittedly more tightly integrated with ability to communicate via shared memory.
The "custom os" part could also be done easilly enough with the correct approach.
Specifically systemd has a less-known feature known as system extensions intended for basically exactly these sort of scenarios. These system-extensions are basically disk images containing files in /usr and/or /opt that can be dynamically overlaid on the existing filesystem (the intent is that these are purely additive). Systemd also intends that all os provided configuration live in /usr, with /etc existing only for machine specific or admin applied configuration. (And which should enabling overriding anything specified by the package or OS.)
System extensions when used default /opt and /usr to be read-only, but you can enable mutability if you having write routing directories or symlinks in the right spot.
So for userland this whole os profiles things could literally just be a set a of system-extensions, a distinct /etc folder, and distinct set of write redirect directories for each. An initramfs can simply bind mount the /etc directory, and add the correct write redirection symlnks before systemd starts. Rolling back a profile is simply wiping its write redirection and /etc folders. If you also want each to potentially have distinct device trees and/or customized kernels, that would need additional bootloader work on top, but nothing that feels too extreme.
Now in reality, since not everything support systemd style configuration, these OS profiles would probably need to construct an initial /etc by copying files from a base-os template, and then copying in anything included in the system extension images (which can have these as systemd will ignore such folders), but that is straightforward enough.
> A combined MPU and MCU architecture isn't that exotic. ST microelectronics currently sells a single chip with that contains a two core Cortex A7 Microprocessor combined with a microcontroller. Admittedly more tightly integrated with ability to communicate via shared memory.
Don't underestimate the value of that integration.
With the hybrid architecture chips you get the vendor controls for managing the MCU with supporting documentation. ST is good at this.
This isn't the same thing. It's two chips running side by side. It's possible to set it all up so that the Linux chip can control everything you need to manage the MCU, but it's not easy. There are a lot of edge cases to think about and things that need to be handled manually.
Absolutely every laptop uses this same architecture, you can even find the source code of the MCU firmware for Framework laptops and Chromebooks (chromium-ec).
> A combined MPU and MCU architecture isn't that exotic. ST microelectronics currently sells a single chip with that contains a two core Cortex A7 Microprocessor combined with a microcontroller. Admittedly more tightly integrated with ability to communicate via shared memory.
Going with an SoC is much simpler than trying to set up custom communications between two processors, I'm not sure why they didn't think of that.
On the other hand, this has been working pretty well for the first few Raspberry Pis! (Although they had the benefit of leveraging an existing smart TV based platform for that.)
Thats terrible marketing then. Trying to leverage an unrelated device because it was popular is almost guaranteed to spurn those expecting the next flipper to be an improved flipper, not a "not-a-flipper"
Open source software isn't meaningfully insulated from this. Anthropic purchased Bun's maintainers as well and are effectively killing it, using it as a sacrifice to their AGI hype marketing. Could people fork it, technically yeah. Will anybody? Probably not, the original vision of Bun will probably go unmaintained while the main repo is destroyed with an AI Rust rewrite with 1m loc that no human ever read. If you were using Bun in your stack you're almost certainly going to be forced to switch to an alternative.
"When exposed to a trigger -- such as a small amount of heat or a catalyst -- the molecule snaps back into its original form, releasing the stored energy as heat."
That's a bit concerning. Runaway waiting to happen.
One important difference is that costs are bounded on your own machine. Like with cloud providers, I'm always worried that cost may accidentally explode if I launch an agent swarm wrong.
Now, it looks like the providers I use have good limits. But I do worry about this.
Modern OCR is amazing. That image is full of noise and ChatGPT did it without any errors that a I can see.
I compared it to another OCR of the same image, using http://ocr.space, and ChatGPT was correct in all the small number of differences, even preserving misspellings in the source.
The company doesn't have to go away, the app just has to have issues. At least with web apps, you aren't depending on the manufacturer investing in nearly continuous upgrades to work in the rapidly changing phone environment
A web UI will continue to work for decades. And app will likely not last a year without updates.
reply