Author of this content has low reputation.
RE: RE: daily report 20191001
You are viewing a single comment's thread from:

RE: daily report 20191001

Words
255
Reading
2 min
Listen
Play
7y
if($hit){always();}

actually got a few minor things done this week omg ... so this is where something really bad happens then before i get any kind of drive on i suppose?
well no ... shit kept always happening because i didnt check if hit ... more like ... explain that to 100 people in the street and see how long it takes before you end up in a straightjacket, right ... heh

and yet i feel like todays programming is always the easy way out : production > understanding, i think it stifles creativity, not having to build from scratch ?

like here :

https://arxiv.org/ftp/arxiv/papers/1811/1811.02035.pdf

ProgrammingtheAtari2600
In order to fully appreciate the constraints under which Atari 2600 programmers hadto work, and to understand how Entombed was shaped by those constraints, we needto take a close look at the Atari 2600 platform from the programmer’s point of view.We frame this discussion by beginning with a summary list of the 2600’s programmingconstraints:
Limited ROM (i.e., program) space.
Very little RAM.No interrupts – polling only for I/O and timer.
No video framebuffer.
Real-time requirements, necessitating cycle counting.
No operating system, BIOS, or pre-existing ROM routines.

"no operating system (=lol)" ... i was like six or seven then, a few years before i wrote hello world "cycle-counting ... " :D ... does anyone actually still know what a cycle is ? Von Neumann has died a while ago ... and they killed Turing with dumbfuck-pills ... tschhaahh

you can find me

in the comment section

or mostly simply
not at all

@yapcat: if($hit){always();} | Ecency