Impending kOS
archive.vector.org.uk
Impending kOS
1–10 of 242 posts
Re: Impending kOS
#2Um, so what happened?
Re: Impending kOS
#3Here's the text editor they're talking about: http://www.kparc.com/edit.k
The code is, well, not the easiest to understand.
Re: Impending kOS
#4Here's the text editor they're talking about: http://www.kparc.com/edit.k The code is, well, not the easiest to understand.
That's an understatement. If we are allowed code like this, I can write an editor in ONE line of JavaScript. :)
Re: Impending kOS
#5Googled around, Kuro5hin (that's a name I haven't seen for some time) has a tutorial for K from 2002: http://www.kuro5hin.org/story/2002/11/14/22741/791
The download link at http://www.kparc.com/ asks for password, so I'm not sure whats going on with that.
Re: Impending kOS
#6Re: Impending kOS
#7Here's the text editor they're talking about: http://www.kparc.com/edit.k The code is, well, not the easiest to understand.
Here is the four line version: http://www.kparc.com/$/edit.k (lines beginning with / are comments)
Re: Impending kOS
#8Re: Impending kOS
#9> “It is a lot easier to find your errors in four lines of code than in four hundred.”
Looking at his code on http://www.kparc.com/edit.k I'd like to disagree with that statement
Re: Impending kOS
#10> “It is a lot easier to find your errors in four lines of code than in four hundred.” Looking at his code on http://www.kparc.com/edit.k I'd like to disagree with that statement
If I posted four lines of Chinese or Sanskrit, it's likely that native English speakers would disagree that they had much meaning either. However, this doesn't mean that those lines are inherently devoid of meaning or difficult to parse.