I don't see why not. All the Apple II line were all very well constructed, and mine have withstood tremendous abuse over the years. The battery may be dead though, so watch out for that.

Forgive me, but I think I don't understand what you mean. Would you care to elaborate, or provide an example?

You could develop C programs by layering DSLs written in preproc macros. But why would you go to that much effort?

If I'm already working in C, I wouldn't. If I'm working in a Lisp, that changes everything.

The author's criticism of lisp is complete nonsense.

The author admits as much in their followup article. I think it is still interesting to look at the experience as they describe it and through their eyes. Lisp is amazing, but it is not so easy for a new Lisp-er to know when one technique is more appropriate than another. I've been there. I'm still there, more often than not. The amount remaining for me to learn is very daunting. The community, though they have the opportunity to be helpful, may then choose to be elitist. The author didn't find a helpful community. I've been there, too.

If you are already comfortable with Python, then there are a few reasons you might want to learn Lisp. I'll cite a few practical reasons, but avoid the most commonly given ones:

• You enjoy learning new programming languages, especially if they are very different from the ones you already know. You aren't afraid of learning entirely new programming paradigms, disciplines, and idioms. (This is me FWIW.)
• You want to participate in or use an existing project in Lisp, such as the one linked in the OP, or Emacs, or many others.
• You know of specific career opportunities which require Lisp experience.

Those are the compelling practical reasons I can think of off the top of my head. If you have other reasons ... I dunno ... maybe share them?

As I read that, it is more like an example of how what one philosophy deems a strength doesn't even make sense in a different philosophy. Really, why would C++ programmers ever want the ability to redefine their language on the fly? It would lead to utter madness! Well, it really would ... for C++ programmers.

I recommend this book and an Apple IIe emulator. The Apple IIe has a program in ROM called "Monitor", which is pretty much a REPL for 6502 development. It makes practicing much more fun because you can debug your code in realtime.

The Edit Menu

You can modify the search and replace behavior by selecting different options at the bottom of the bar. Selecting will limit finds to entries that match the case (upper or lower) of each of the characters in the search pattern. will search and replace within the current selection only. The Find All button highlights all matches in the document and shows the number of found matches in a small popup.

If that's not enough, then open a konsole window inside kate to grep your document. Or just use Emacs' occur mode. Or use Ed, which has supported global regular expressions since forever.

for(i = 0; i < nrows; i++){

Fix your fucking HTML, assholes!

How is this good for Java?

Don't compile from source then? Pre-built binaries are not that hard to get. If you really need all the flexibility of compiling from source, then you ought to appreciate why makefiles are needed. As @supercunt alluded, if not for makefiles you'd have to replace the configuration with something else that does the same things but looks different.

Usenet definitely gets far less attention by enforcement agencies. If you buy a subscription retention is good enough.

most laptops have at least two interfaces, as do some desktop motherboards.

document anything non-obvious from the code itself. document non-idiomatic constructions. document uncommon dependencies. don't over-document.

http://www.dailyinfographic.com/wp-content/uploads/2015/06/OBHEr1J.png

It doesn't cover everything, so if there's a better one please link.

http://wiki.c2.com/?FunnyThingsSeenInSourceCodeAndDocumentation

http://repo.or.cz/

Edit: more here

Can you write and execute the example programs? Do you understand how they work? If so, then you should be gaining the knowledge you need to write your own programs. For example:

>>> print('hello world')
hello world

Can you see how to make it say your own name instead of "world"?

I abandon alts too frequently to care for this sort of application. OTOH if you love your alt and want to be associated with it for all eternity, maybe it is a good idea.

But the authenticity of the digital signature depends on the same cryptography which could be used to encrypt the message, but in this case is used to encrypt a token which can only be decrypted by the sender's public key. Or have your done something different that I missed?

I was wondering what the comic was trying to say. I've been programming in Lisp long enough that languages without fully parenthesized prefix notation seem harder to read.