Readit NewsJell-o (gello?) is a good example, nothing tastes like it naturally. Why aren't there tasty food that are original in terms of taste and texture but good for health and the environment? I suppose part of the struggle is that food is entrenched into culture so much. burgers and bbq are inextricable from july 4th and memorial day for example.
Jell-O actually proves this rather than refuting it. It succeeds because it hits that hardwired sweet preference, not because it invented some novel taste dimension. A truly new taste that doesn’t map onto the existing five basics would likely register as “off” rather than delicious. Your brain wouldn’t know what to do with it, nutritionally speaking.
So you’d have to either work within those existing taste channels while creating novel combinations and textures, or somehow condition people to associate genuinely new sensations with safety and reward. The latter is slow going. We’re quite literally built to be suspicious of unfamiliar foods.
Historically the strength of Apple was that they didn't ship things until they actually worked. Meaning that the technology was there and ready to make an experience that was truly excellent.
People have been complaining for years that Apple isn't shipping fast enough in this area. But if anything I think that they have been shipping (or trying to ship) too fast. There are a lot of scenarios that AI is actually great at but the ones that move the needle for Apple just aren't there yet in terms of quality.
The stuff that is at a scale that it matters to them are integrations that just magically do what you want with iMessage/calendars/photos/etc. There are potentially interesting scenarios there but the fact is that any time you touch my intimate personal (and work) data and do something meaningful I want it to work pretty much all the time. And current models aren't really there yet in my view. There are lots of scenarios that do work incredibly well right now (coding most obviously). But I don't think the Apple mainline ones do yet.
A device trying to duplicate a part of smartphone/smartwatch functionality is doomed to fail, as those can easily just be an app on said devices.
So the computation part is likely out of the question. Input/output remains, and there is really not much you can innovate here.
Smartglasses? EarPod clones?
We're using a lot of WSL in CI - we're mostly Linux based, but for some stuff toolchains came up which didn't work nicely with wine (like MSVC). So for us we want a Linux system that seamlessly can execute Windows stuff in a Linux based build process. WSL1 can do that, WSL2 can be kicked into working somewhat, but needs quite a few ugly workaround as they're not sharing a process namespace or file descriptors. While the faster IO would be nice that's pretty much the only thing we'd care about - and wouldn't work here, as we need shared access to the files. And while we could access the WSL2 files from Windows side that's even slower than just using WSL1.