codelobe

Holo Display: generate the refractive voxel via ultrasonic convergent propagation fringe pattern, and light the voxel with IR that becomes higher frequency visible light color at point of interfearance/intersection.

PrHoteph: hyperplanes are your friends, may they guide your long distance acoustic whisper / ultrasonic voxel intersections.

Distinguished seekers also searched: "NOFORN" "EYES ONLY"

Ooin called; Wants the Yggdrasil equation back... TREE_LIFE=FILE_TREE

The meaning of life is what life is and does. Life experiences reality and message-passes thee grokked data to the future.

Thanks for your suggestion!

I tried cats.youtube.com also, but it's just like my IRL cat.

>a certain number of plants will form a rough line as seen from the earth

Ah, a fellow galactic hitchhicker. I too am a fan of dead-reaconeering in favor of astrolabian navigation.

[x] Strongly Agree.

Also, the focus on how these devices are increasingly consumer only instead of me being able to use my device to create

Disclaimer: one of my goals is to build apps for my machine on the machine itself. I had this working on the now defunct Firefox phone OS (Its apps were deployed as Zipped HTML/JS and related resources -- I cobbled together a dev environ out of a few browser based tools).

TL;DR: I'm a tool-using creator-type species, The modern "CONSUME ONLY" device craze makes my eye twitch; Ads that reinforce destruction of tools make me want to join fight club.

Indie Gamedevs can do their own Voice Acting? See also indie film, same use case. Actor dies / hit by buss before a work is finished - Create a few more lines posthumously (it'll be in the fine print of the contract that you allow voice & image fakes in the event not able to do them). Satire, Pranks, and alleged pranks (stuff that makes folk laugh).

Maybe the Sumerian or (blue-skinned) Vedic Gods saw some giant sentient machine life, and went out of their way to honor these "Angels" with many eyes and huge wings by creating what we call insects (in addition to Humans [Hanuman's ilk]).

When you transcend the physical form into a body of energy (hint: OR=constructive, XOR=deconstructive, NOT=XOR(k,1), NOT( OR(j,k) )=NOR(j,k), NOR=Functionally Complete, ergo EMF or even sound can be Turing Complete), then as an energy body you may want to interact with physical forms again w/o ionizing them; So you'll create (sentient) machinations that can do tasks. Because your design parameters include survivability across large thermal and pressure gradients you'll [re]discover giant robotic beetle design.

If you'll excuse me, I've got to tend a Kephri (beetle of remanifestation) who is eagerly attempting to choose an Odin to ride this 6-legged "Steed" next Ragnorok.

The upstream who manages their name::location mapping?

Usually I would agree. I typically make a "Crash-Course in $PLATFORM" document while keeping notes. These I very commonly reference in order to externalize my memory since it seems to be approaching capacity. I don't care about Ruby on Rails, but once I did, and I can reference my notes if I ever need to touch that platform again.

I never refactor for the purpose of refactoring.

If I can do things better, and I usually can, it's because I have a more performant higher level algorithm or set of low level optimization strategies to apply.

I agree, Those API organizers are just creating future crap for others. However, objective benchmarks showing my changes yield 10 to 100 thousand times quicker execution than the old method mean the legacy code was crap...

Legacy being crap is not always the fault of devs. Back on Z80 and similar, before execution caches were expansive and expensive to invalidate, the short circuiting && and || bool operators made sense. Now that invalidating the CPU instruction cache with a jump is far more expensive than just running the ops these short circuits are trying to avoid, it is better to just use bitwise | or & instead of boolean || or && unless there are needed side-effects (really should make the conditional evaluations into proper branches [if statements] anyway, if only for clarity). Benchmark it and see. C is stuck doing LOTS of old and busted style logic, and coders imagine their compiler is doing a lot of magic voodoo under the hood that simply isn't happening. There's loads of compiler optimization hype.

Sometimes the hardware or platform just shifts underneath Good Code and turns it into Crap Code.

Join the trust graph...

Remember when .PNG included a gamma correction to try and make a more accurate image -- Appearing as the creator viewed the image...

And then WE ALL REJECTED THIS INSANITY because it made .PNG images a pain in the butt to work with since the gamma corrected image wouldn't match the RGB values of the surrounding document (see: CSS color codes). Then Ye ol' .GIF enjoyed being the pixel perfectionist's choice of image format for the web for quite a while longer. I once was forced to write a script that chopped up a 24bit images into a bunch of 16px by 16px .GIFs (one palette entry per pixel, 256 total).

Digital doesn't usually need to be restored as long as it is replicated often enough (before bit-rot sets in). However, I've got a large number of tools for restoring spinning disks (migration to new hardware isn't easy for the average end-user).

Let's say a modern game came out that had a capability to demand of a GPU more polygons/paritcles than capable today... but in the future those capabilities might exist. Digital media could be improved by adding more/better compute resources (if originally designed to scale, that is). Then there will be curmudgeons (like me) that think things were better before the edge users' hardware became a giant supercompute cluster / distributed storage...

My "solution", to the example config error: delete everything after the first close curly brace.

Works on my machine... Ship it!