As the creator of the C programming language and one of the main developers of Unix, he impacted the life of me and other developers a lot.
Even today, 30 years after their initial creation, many people work on Unix like systems (like Linux or Mac OS) and develop in (Objective) C(++).
For me C was one of my starting languages for my real programming work and even today I analyze the whole day software written in C for embedded systems that control our modern world, be it the flight control of airplanes or engine control of cars.
Without his initial ideas and work, today there would be no Linux kernel, no Mac OS, …
We all owe him a lot. He changed the world.
Thanks for your great inventions! You won’t be forgotten.
Just two impressive Ritchie cites:
“Unix is simple and coherent, but it takes a genius – or at any rate a programmer – to understand and appreciate the simplicity.”
“The greatest danger to good computer science research today may be excessive relevance. If we can keep alive enough openess to new ideas, enough freedom of communication, enough patience to allow the novel to prosper, it will remain possible for a future Ken Thompson to find a little-used Cray/1 computer and fashion a system as creative, and as influential, as Unix.”
Christoph and me cleaned up the visualization of the code folding for KDE 4.8 a bit. In the snapshot, the left image shows the old behavior, and the right one shows the new behavior. The background highlighting appears as soon as you hover over the code folding bar. We hope you like it Mockups of how to make it even better are welcome, of course! You can try it by building Kate yourself, if you want.
Some days ago, Dominik implemented a line modification system in the KatePart.
For all who don’t know what that means at all (like me before the DS 2011), here some screenshots.
First, starting with a fresh loaded file:
Now, lets write some lines:
Next, after saving:
Now, lets change some stuff again:
First I thought: Why to hell do I need such a feature? But after using it some days now, I think it is really VERY useful.
Yesterday I worked in parallel on code that generates integer linear programs as CPLEX files and read the output files (which are > 100000 lines) to find regressions.
I had to manually tweak the ILP files a bit to reveal the reason of my issues and it was just cool to exactly know even after save, which lines in the ILP I touched.
Normally I would have written some comments like \changed… above my modified lines in the output files, but yeah, KatePart does track such stuff now automatically 😉
Even for the much less big source files, it was nice to see:
Oh, I just tweaked that few C++ lines and it did remove the issue, maybe I should look at the lines below/above of that lines, too, for more possible problems?
Therefor: Thanks to Dominik for this nifty feature, I hope others appreciate it, too!
If you want this feature now: Use the guide at kate-editor.org’s Get It!.