Browse Source


Signed by: yogsototh GPG Key ID: 7B19A4C650D59646
  1. 6
  2. 25


@ -12,9 +12,9 @@ blue=4
# magenta=5
# cyan=6
# white=7
green() { printf "$(tput setaf $green)%s$(tput sgr0)" "$*" }
yellow() { printf "$(tput setaf $yellow)%s$(tput sgr0)" "$*" }
blue() { printf "$(tput setaf $blue)%s$(tput sgr0)" "$*" }
green() { printf "$(tput setaf $green)%s$(tput sgr0)\n" "$*" }
yellow() { printf "$(tput setaf $yellow)%s$(tput sgr0)\n" "$*" }
blue() { printf "$(tput setaf $blue)%s$(tput sgr0)\n" "$*" }
pipegreen() {while read line; do green $line; done}
pipeyellow() {while read line; do yellow $line; done}


@ -8,6 +8,31 @@
#+options: auto-id:t
#+startup: showeverything
The oldest code I ever wrote was probably in logo, then in Basic.
Then I learned Turbo Pascal, then C, but also awk, csh, bash, etc…
And for most of these programs, I am pretty confident, that taking the
source code and using it today will still work as I would expect.
Then during my PhD, I wrote a quite extensive C++ program.
And, this was probably one of the first time I used extensively a library.
But, a few years later, I couldn't make my code compile.
I updated my code to make it work again.
But today, I wouldn't be surprised to learn it doesn't work anymore.
Why? The compiler will not accept some of my code, the library might have a
few issues.
Whatever, it is difficult.
I think, most of my application code suffer from the same issue.
The ecosystem of the language evolve, but if I don't take care of my code,
it rots.
But really fast.
Wouldn't it be nice to be able to know that a code you write today will
still be usable in 10, 30 or 100 years?
Could this be possible looking at how our industry is going in the opposite
Have you remarked how difficult it is to have something now.
I mean, really have an object that you know, could be passed to your
children that they themselves pass to theirs for many generations.