61–70 of 242 posts
k/q really doesn't have to be this unreadable, that's just Arthurs style. Here's some code in C by him for comparison: http://kx.com/q/cs107/a.c
Q isn't unreadable. Its implemented in standard English words. http://code.kx.com/wiki/Reference K is considered unreadable by many.
Earlier quoted context omitted.
It does not matter. This is not a programming language; languages are designed for human comprehension. Human comprehension is an irreducible part of the whole paradigm of programming, being necessary to understand the nearly always complex logic required to describe anything of value. This is gibberish. It fails at the one task of a programming language: to translate something a human can understand into something a…
[deleted]
If you have a sudoku solver that's entirely commented by the phrase 'sudoku', that's generally an indicator of code that is optimized for the computer rather than the reader--regardless of the language used.
Here'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)
> kOS is coming. Nothing will be the same afterwards. There seems to be this strange idea going around that if we just get the right tool, everything else is going to change forever. I see this a lot with people trying to create IDEs that let non-programmers create programs without really knowing how to code. But the thing is, most people just don't have anything worth coding. The problem isn't that the tools don't e…
If I am from another planet, and say I don't know why programs are so big and slow and buggy, and the most complicated program you see I've produced is a glorified calculator, it's too easy to be patronising and say well, that's because you haven't done anything complicated . However if I then show you a programming language, a database engine (similar in capability to SQL but around 1000x faster), a graphical deskto…
Right, and I'm not saying programming won't improve. It obviously has. No one wants to write a web app in C++ or assembly. What I'm specifically taking issue with is the idea that there is some sort of monumental change out there that is going to enable us to do... what exactly?... well no one can really answer that, but the claim is that it is big and exciting and will change everything.
Earlier quoted context omitted.
Ridiculous comment. Have you at least tried q? K? Kdb+?
I've worked with and later run the kdb/q stack for a couple of years at a financial services firm. I certainly enjoyed it but I've also seen the downsides of it, and according to my experience it does not worth the investment, and the biggest reason behind its adoption is A.W.'s relations with the financial industry. By the way, I really don't want to go into anything personal but your comments represent the attitude…
Earlier quoted context omitted.
That's an understatement. If we are allowed code like this, I can write an editor in ONE line of JavaScript. :)
Note that his lines are Can you write this editor in one line of less than 6000 chars of javascript (without a "textarea")?
I'm interested in a kOS with a "god says ..." program built in ...
k/q really doesn't have to be this unreadable, that's just Arthurs style. Here's some code in C by him for comparison: http://kx.com/q/cs107/a.c
The last line of TFA reads like the beginning of some sort of movie in the drama/thriller category. "kOS is coming. Nothing will be the same afterwards." That's what irritated me most. What I'd like to understand is - what led the author to this particular conclusion? Is it the fact that this language is super expressive and concise? Is it that it routinely [1] outperforms its C counterparts even if it ultimately tra…
What you're actually seeing is testimony: people saying they are seeing something amazing, and they aren't very good at explaining what they saw. Btw: k doesn't translate to C. It's actually a quite simple interpreter. The fact that it outperforms other languages so easily should be saying more about those languages than it should be saying anything about k.
> “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