But isn't that's what popular music is reported to be already? If only a formula can win, then an AI should be able to do it.

FWIW, my tastes are "folk music" and sometimes "filk music". That's much less a formula, but possibly only because the sample size is small.

I've been using a TCL NXTPAPER for reading for a couple of years, and haven't used my kindles since. The screen has no glare at all, none. It's night right now, can't tell you about reading in bright sunlight. I haven't found a phone yet which is any fun in bright sun, so this NXTPAPER is probably not great either. But none of my house lights drown it out.

I have one, #11 I believe, which I use instead of Kindles. Zero glare, zero lag while paging. Works OK for general use too, but it beats the pants off Kindles and all other tablets I've tried for readability. Had it for a couple of years now.

Hedge funds and private equity firms demurred on investing in NTP, reportedly claiming that the foundation didn't have a credible plan for improving engagement.

GPU are retargetable (to their original use as graphic processors), but I'm not sure the same is true of TPUs and the other more specialized varieties.

Don't expect AI to ever use only a small amount of compute. You can do a lot by pre-training, but there are limits.

OTOH, I'm rather sure that the current algorithms are a lot more wasteful than a later version will be. A factor of 100 wouldn't surprise me. Personally I think the way to handle it is with a raft of Small Language Models, each one tuned to a specific context, and a higher system that switches context as appropriate. (I've seen signs in the news that we're already headed that way.)

Moore's law may be over, but the 3D version of it is just getting started. The real problem is moving the heat away from the chip. I think we're in the early part of the ramp up of 3D chips.

N.B.: That it's actually do-able was proven decades ago, but only for custom sculpted 1-off chips in a lab setting. (I believe it was the Tennessee Valley Authority...but I'm more sure about the Tennessee than about the rest.)

AFAIKT, China is 4-5 years away from "breaking into this market", if they market is the upper end of the chips. Possibly even a bit longer. OTOH, for many purposes their chips are already good enough, so they'll break into it at the lower end as soon as they have enough chips for export. (Aren't they already doing that?)

I may have a "smart phone", but I refuse to set up internet connections on it.

That smells a LOT like BS. I'm just going to eat all this food in your pantry to make sure you don't get food poisoning, and such.

Compare, instead of the nobleman charging rent, the herdsmen do get together and own the commons in common, working out a fair deal between them for sustainability.

As for the NYC situation, if there's a glut, why don't prices fall? Where are the buildings for sale cheap to someone who wants to do a residential conversion?

...This is my embarrassed face.

I had previously assumed you were speaking of allocating $1M across all projects used by Google. In fact, you were speaking of giving $1M to each such project.

One would wonder what sorts of strings would be attached to such largesse. Still, that would indeed be game-changing and amazing.

Google could create a new corporate policy to provide a minimum of $1M/year to any open source project it uses.

That would be real innovation.

While acknowledging your noble intentions, no, it wouldn't be innovation. It would be cheaping out.

In the San Francisco bay area, $1.0E+06/year gets you maybe five skilled engineers. Set against the quantity of Open Source projects used by such organizations -- FFmpeg, GStreamer, OpenSSL, ssh, rsync, gcc, gdb, coreutils, nanopb, Samba, Lua, Python, Perl, Git, Vim/Neovim, Yocto, ImageMagick, Blender, the Pipewire framework, the Linux kernel, the Debian packaging system, etc. etc. etc. etc. etc... -- five engineers is miserly.

So why wait at all just release the bugs you found. So if you find a vulnerability in Chrome don't even bother sending an email to Google. Eventually Google will find out and fix the bug. /s

Google appears to have understaken the expense of spinning up an ocean-boiling slop machine to automagically generate plausible bug reports, and then casually fire off an email to the maintainers.

Note that Google has not undertaken the expense of assigning an engineer to also write a fix.

That they are not doing that is a conscious, management-approved choice.

...Y'know how Google relishes in closing bug reports with "WONTFIX - Working as designed?" I think FFmpeg should close slop reports from Google with, "WONTFIX - Unfunded."