There is an even darker possible future: gamers WILL buy this AI generated crap. And the executives know it, since gamers have been buying their low effort budget cut pre-order alpha crap for years.
There is an even darker possible future: gamers WILL buy this AI generated crap. And the executives know it, since gamers have been buying their low effort budget cut pre-order alpha crap for years.
Can someone explain how this ensures security?
Because hackers always work in the dark? /s
It just means that visible or IR light (What are they using?) won't leak through walls the way Wi-Fi does. Depending on how wide the beam is and exactly how it all works, it _might_ still leak out of windows and under doors. But it's not like someone casually wardriving outside your house will get as much as they would from Wi-Fi, I would think.
It has the umami quality certain meats & cheeses have, you just need to have another bite, that I've not have had with other meat replacements.
I've eaten the most delicious vegetarian chicken made of Seitan over a decade ago in a monastery in Xiamen.
Still not sure why it hasn't made it's way to the West. Maybe because of the fact its basically pure gluten.
1. can you put a link to the running http file served by the example so we could see how the result looks?
2. Defining CGI would be helpful because I looked it up and found “computer generated imagery” which doesn’t seem like what you meant.
3. Might be good for this example to load the html from a file or SQLite to fully trivialize the whole stack, as this example doesn’t include the S in the acronym.
sometimes I think the Next.js examples folder at https://github.com/vercel/next.js/tree/canary/examples is just an amazing example of how best to market a software product to developers because it’s such a rich source of integrations, almost anyone can find a good starting point for a web app project in there, if BCHS had the 80:20 of examples ready to roll then maybe it could blow up, because BCHS a great idea to use the most battle tested solutions in existence! Keep it up! bravo!
The most primitive version is just launching one process per request, piping the HTTP request into stdin, and piping the response out of stdout.
It works, but you can imagine the startup latency is rough and it takes a lot of resources.
There are faster variations that try to reduce the overhead. Ironically FaaS is sort of a rebirth of CGI
It was only after I wrote a couple of games that I realized that extracting this OS component would be worth the effort and after that making new games went substantially quicker.
Stuff like static, film grain, particles like snow or rain, those all suck up bits from the same encoding budget.
"Why Snow and Confetti Ruin YouTube Video Quality" by Tom Scott probably explains it nicer than I can https://www.youtube.com/watch?v=r6Rp-uo6HmI&pp=ygUaYnJlYWtpb...
This could be a problem for video game streaming, and it could affect the artistic decisions a game studio makes - Drawing a billion tiny particles on a local GPU will look crisp and cool, but asking a hardware encoder to encode those for consumer Internet (or phone Internet) might be too much. I think streamers have run into this problem already.
then again, thinking about code with timestamps in float makes me scared
Of course when I search on DDG I only get "wow the fast inverse square root"