Curious if you saw any difference in far IR vs near IR on cameras with removed filters. When I tried camera without filter or camera with IR filter (one that only lets IR through and look redish black to naked eye) attached I had nice b/w images of trees on long exposures or better pictures of tv remote leds. But if I make a picture of an iron or pan they look the same when either cold or hot.
This is very different from thermal cameras I used where you can clearly see unevennes of the pan heat, dark image on tshirt being warmer on the sun, person at night etc.
I can speculate that thermal exhaust falls into the second category.
With the post's logic if you work on DB you likely have an SQL engine that is a CRUD on top of storage engine. And storage engine is a CRUD on top of some disk storage, which is CRUD over syscalls on files. Think Mysql using MyRocks using RocksDB.
And keep applying until there's no sense left.
If you are referring to my post, it's about web applications. I'm not in any way claiming that postgres is a crud app. I'm describing how to design a good web application that mostly revolves around a database. Which is what people mean when they say crud app. It's just any app that's mostly crud. Where the majority of the logic can be handled by the database like I described.
A lot of apps are just about putting data into a DB and then providing access to that data. Maybe using the data to draw some nice graphs and stuff. That's a crud app.
Not exactly what you want...
You can likely run Mopidy on a pi and lauch browser in kiosk mode to show its web interface.
If you don't want display and ok controlling from your phone then you can run mpd for local files and librespot as spotify speaker.
There's a pressure drag and skin friction drag. Friction drag is supposedly a majority component unless you sail a brick. But I don't have sources to prove that.
Apple uses functional organizational structure. Every product needs a cooperation of all functions to produce results. So engineer on os team working on drivers could be working on driver for the new hw part, but other team members including their manager are not necessarily disclosed on that hw.
In all fairness the highway code specifically says that you should not violate it to let ambulance pass.
Might be down to sketchy council, but they normally place signs "new layout ahead" and the like when limits, lanes change.
In US, it's not uncommon for small towns to have traffic fines be a significant part of their budget, which in turn incentivizes them to deliberately confuse motorists to fine them - this is especially true for towns located on busy routes where there's a lot of out-of-town traffic, since locals generally learn the where the traps are.
I might be this missing a point here. What is the reason to block screenshots? If we want to save space, blocking screenshots is irrelevant. If we want sender to have a guarantee that message is not preserved then we can't do that either because screen is visible.
I can only see that as a marketing trick for unsophisticated user.
The only reason you don't see "Torches of Freedom" now is because PR has become infinitely more sophisticated. To the extent that you create your own Torches of Freedom by your own volition.
Spotify has albeit unofficial headless client for linux. None of other services I know does. It implements the same interface as smart speakers so can be controlled remotely by any gui client.
You can try to virtualize generic ARM in qemu and see that it won't reach Raspberry Pi performance. Recent versions should have it available out of the box afaik.
Virtualizing Mn cpus would be even less useful.