The amount of sigils and occult jargon
math invents on the spot is very weird
in context of most sciences:
imagine creating entire fields/theories
and gaining followers, like a religious sect,
in a field like geometry?
The Template pack index is going to make
meta-template variadics much easier.
Usually this is prone to cludges like converting
parameters to structs or filtering them with functions holding the pack.
the one-to-many model of blog broadcasting
information has been outcompeted by
communities like facebook groups or subreddits,
where interaction is many-to-many,
typically much faster response and
more incentive to comment(likes, karma, scores).
Ethics, regulations, patient privacy.
Generally what is done is clinical trials and
research on model animals, that of course
is much cheaper to experiment as
first stage before human trials.
AppImage are perhaps that only thing working
OOTB like windows/Mac programs,
and other container formats don't come close.
Everything else is dependent on right configuration,
correct versioning and lots of
"magic" settings that need to be
set to make something functional.
Depending on correct glibc, dependencies
being installed with the right settings,
environment variables,makefiles
being compatible with what your system
has,having the right kernel version,
etc.
IIRC teenagers/children suffer greatly
from this at the morning,
with none of them being "morning people",
as this is likely some 'learned habit'
driven into people by force.
https://time.com/6206470/school-start-times-research/
I find it somewhat interesting and
providing European perspective.
Perhaps the text is hard to translate due
cultural frame of reference being
so obscure and distant:
more that Homer and enmeshed in society
was isolated from the West for millenia.
You can't pick and choose "Not a real scotsman"
since 99% of users will be on bigcorp 2FA
that does it in most ass-backwards way possible.
2FA as mobile apps locked to hardware is not
going to go away without 2FA being replaced by something else.
Old code does acquire new bugs by sitting in your hard drive,
since it interfaces with dozens of libraries and APIs that
don't care about how well test the code is: every path of code
is dependent on multiple components playing well and following
standards/APIs/formats that old code has no knowledge of.
Also, the mountain of patch-fixes and "workarounds" in the end
force the programmers into a corner, where development is hobbled
by constraints and quirks of "battle-tested" code, that will be thrown
away as soon as it couldn't support fancy new feature X or
cannot use fancy new library API without extra layers of indirection.
The constant factors could be optimized or
even accelerated with special-purpose hardware.
There could be a simplification or even something
like reuse/caching/memoization that in real world
will reduce the constant factor significantly.
Its random and default 23/3 rule always decays to
oscillators and static objects.
`Most initial patterns eventually "burn out", producing either stable figures or patterns that oscillate forever between two or more states (known as ash)`
https://conwaylife.com/wiki/Conway%27s_Game_of_Life
I can't name a good one, but i have strong
dislike for big project codebases where
even finding one file out of thousands where
the relevant code resides is a challenge:
its never something isolated but acts
like some "component".
The best i can think of is one-person projects
where organization is streamlined as its
actually has to be used by the author,
not like a cog in a giant project.