4) Already got 'em. A Brainfuck iterator is just a bracket loop with an ascend command before the closer.
5) !!!
6) I am but a mere mortal, sir.
231 karma · joined January 31, 2013
5) !!!
6) I am but a mere mortal, sir.
Also, we will actually be breaking 30,000 cells. Just not with a single tape :).
a) I'm going to be doing this "work" (which, okay yeah it is) full-time or even constantly, when I'm probably just going to hack on it for the next few months or years; whenever I've got a coding itch. I doubt I'll ever go into crunch mode on this or get "burned out". I'll just put it aside for a while and do something else.
b) That I can't just say "Whelp, it was fun but I'm done" at some point during the project and find something else to do. There's no hardcore commitment here; like all projects, everything beyond the first step is a pipe dream.
I get what you're saying though and it could definitely be a shitton of work that's probably not usable IRL. But it's still a fun plaything.
2) Integers! Strings are integers, arrays are tapes of integers, etc... I guess this means it's dynamic, but at the bottom levels I'm not (yet) concerned with typing.
To me, coding is like painting or cooking. It's a fun activity done for leisure and self-improvement. I do silly things like code Brainfuck environments because I mostly do these things for me.
I'm not in a startup or building a company because I don't want to give my leisure activity a work stigma. I don't want to code for money because it'll strip away everything I like about programming: the fun of untangling a problem, the casual pace of piecing together a solution and the independence of being able to code whatever I want whenever I want.
In the future I can see myself doing open source projects or writing professionally but I can't see myself coding for 9 to 5 or swapping out my silly activities for a dayjob where I build someone else's thing.
Beyond that, it's far too young for me to decide.
But I'm doing it.