3,974 karma · joined February 21, 2007
See this thread on my site, the story of how I kicked the Mathematica habit:
I dislike Clojure because it is a cheap knock-off of Common Lisp, with no upsides that I'm aware of - besides trendiness. The article mentions one serious flaw - Clojure barfs Java stack traces, instead of serious debug information (the way Common Lisp does - with restarts, etc.) Another flaw is the lack of reader macros. But what is the point of listing said flaws? I could go on and on, and no one will care a whit. Why? Because Clojure is a product of immature minds who piss on the past work of serious people (the Common Lisp community) simply for the sake of faux-novelty. In this, it resembles Newlisp and other backwards steps disguised as progress. It is, in fact, best understood as yet another product of the idiotic language-of-the-day mentality which gave us Dylan, Python, Ruby, and the many other shoddy "infix Lisps."
> hates all languages that aren't the Symbolics flavour of common lisp
This is patently untrue, as anyone who actually bothers to read my articles knows well. Symbolics (or rather, the MIT Lisp machine architecture their products were based on) was simply an example of a Lisp system done well. Clojure, a thin veneer on the Java cesspool, is not. To run with your analogy, I am a lover of steak, who is upset by tofu peddlers' success in passing off their cheap trash as real meat.
Without fuses, the electric grid as we know it would be quite impossible.
http://www.loper-os.org/wp-content/killed.png
Anyone who sets the sheeple a-bleating is labeled a "troll."
In all seriousness, compressed air is a simply dreadful way to store energy. The necessity of an adiabatic cycle (store the heat from compression to use during expansion), for one thing. Tank rupture, for another.
One trivial example: let's say that I want to emulate a machine with 100,000 CPUs. On a quad-core PC. There is a strong pressure to reduce the number of emulated CPUs if possible, to more closely correspond with the physical architecture. This in turn leads the user of the emulator to avoid the kind of programming that would take advantage of 100,000 CPUs. Already the notion that "you can emulate anything" productively falls out the window.
Likewise for type-tagged architectures. (The user always has an incentive to strip away the "unnecessary" tags.) Look at Common Lisp and its "optimize" directives. The result is inevitably that somewhere in the system, there will be "C-style," non-type-tagged code. This is a Bad Thing.
Probably not. At least one generation of children has already grown up without proper penmanship training, and for them, the experience of handwriting at any length ranges from awkward to excruciating.
If Jack the Ripper or Jeffrey Dahmer had left behind something like Kaczynski's manifesto (and later prison essays), some respectable intellectuals would pinch their noses and study them.
http://www.loper-os.org/?p=448
And the ground rules of computer system creation have changed. The reasonably-cheap, high-capacity FPGA now exists, as it did not in the age of the BeBox. It is no longer necessary for a hardware project to generate millions of sales (or any sales at all) in order to be "successful" (in the sense of actually remaining available to interested persons indefinitely.)
That being said, I am still working on a Linux-based emulator for the Loper architecture. In all likelihood, it will be unusably slow for any truly practical use, but will serve as a proof of concept (that is to say, agitprop.)
(Author of linked article speaking, in case no one noticed.)
Also: have you ever seen a court stenographer at work? You are simply wrong. (At least, with regards to the limits of what human hands are ultimately capable of.)
http://www.loper-os.org/?p=309
Transparently offload the "patent sin" to a system's users. (With plausible deniability.)
Implicit in almost all discussions of unfair discrimination in the programming labour market is the assumption that being a programmer is overall a glorious and pleasant thing, and that a great many people would be happier doing it than they are in their present lives.
Notice that no one is angry that >99% of all persons who have sizzled in the electric chair were male.
"Market demands"? What part of "non-monetizable calling" do you not understand? I'm not sure it even makes sense for me to talk to you at all. It is like trying to describe 15-dimensional geometry to a Flatlander.
> If you had to choose again, what would you've done that wasn't 'salt-mine labor' then?
I can say only:
"I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question." (Charles Babbage)
But if you must know: I'd be an inventor. In the 1880s.
Hey, you asked.
I have a life project. What is sometimes called a calling. (If you don't, you probably cannot process what I am saying and should disregard this post.)
So whenever I am doing some other work - anything at all - other than my calling - to pay for food and housing - I am acting under duress. Which isn't much fun. Of course, some kinds of forced labor suck more than others. I could be felling trees, or laying pipes, or something even more physically unpleasant. So overall, programming for money is far from the worst among possible fates.
And often, even persons who lack a calling and for whom all work is just work, "just switching professions" is not an option. For a different perspective on why many programmers stay in their line of work despite hating it, consider this book: "Desperate Journeys, Abandoned Souls: True Stories of Castaways and Other Survivors" (http://books.google.com/books/about/Desperate_Journeys_Aband...). It is largely about shipwrecked sailors. One of the more interesting facts about these is how many kept at their profession despite suffering wreck after wreck - witnessing murder, cannibalism, and various other unpleasant things. The explanation offered by the author is that sailors typically entered their trade during childhood, and were largely unfit (by their own estimate as well as that of others) for any other work.
I started programming when I was nine years old. And perhaps you did so, or know those who did, at an even earlier age. This is not necessarily true for all such people, but switching professions after having your whole development as a person wrapped around computing can be like being asked to switch to being left- (or right-, as the case may be) handed, late in life.
> The work is intellectually gratifying
Most likely, this is where we differ.
The only programming work that I find truly gratifying happens to be my 100%-non-monetizable life project. (http://www.loper-os.org) Everything else is just a way to pay the bills. That is to say, salt mine labor.
In order to eat and pay rent, I burn my prime waking hours working on things other than my life project. I understand that, given our present social structure, this is unavoidable. But I don't have to pretend to like it. I suppose this makes me a "bad prostitute," rather than a "good" one.
Programming sucks. So I am not particularly upset that there aren't more women doing the work, just as the lack of female coal miners is likewise not a cruel injustice.
Software developers are largely male for the same reason that construction crews and prisoners are - rather than the reason Nobel Prize winners in Physics are.
What, if anything, there is to be gained by encouraging women to join men in wasting their lives away in the IT salt mines, is another question entirely.
Really?
Well, if you're building a skyscraper, then sure, yes. But a computer program?
How much of that code really ought to have been written in the first place?
We could have a better-functioning civilization if most people who start to suffer delusions of programming were simply given Welfare.
These may be very different meanings of "use."
Using PHP, Java, etc. involves a fair bit of purely mechanical (think "human compiler") labor - cranking out boilerplate, and solving the same idiotic non-problems (all "patterns" spoken of by programmer types) again and again and again. Both of these are things that the average programmer can get quite good at. He will think of himself as a master craftsman. But what he really is: is a valve turner on a Newcomen steam engine. (http://www.loper-os.org/?p=388)
If Haskell were to be rid of all of the shortcomings you have described, the masses would still avoid it for the above reason. Most programming work - particularly paid work, that an ordinary person can reliably get hired to do - is of the idiotic makework variety. So a language which does not supply a steady stream of such makework (e.g. Common Lisp) will stay obscure.
If we were to banish the automatable makework, only the intrinsic complexity of intrinsically-complex problems would remain. And we would need about the same number of computer programmers as we need neurosurgeons. (Fewer, because there are many meat bags and they are always diseased. But engineering problems, once solved, stay solved - or they would, in a sane world.)
No interesting property of a computer system (vs. a single algorithm) can ever be provable in the mathematical sense - because said proof, if true, can be construed as a program in its own right - and where is the proof of its correctness - which is to say, its consistency and correspondence to actual human wants? A. Perlis put this concisely: "You cannot transition from the informal to the formal by formal means."
Switching between alternate mathematical models of computation will not give us better intelligence amplifiers (what the personal computer is really meant to become.) Instead, we need systems which cut the operator's OODA loop delay as close to zero as possible: http://www.loper-os.org/?p=202
Any idiot can use modelling clay. Or a child's set of blocks. These objects have no hidden state, allow for no inconsistent states, posses no "compile" switch. One can build a computer which behaves in the same way. And no mathematical wankery need be involved.
Lustrate the squiggly crowd! Half a century of stagnation in computing is enough:
“Throughout my life I have known people who were born with silver spoons in their mouths. You know the ones: grew up in a strong community, went to good public or private schools, were able to attend a top undergraduate school like Harvard or Caltech, and then were admitted to the best graduate schools. Their success was assured, and it seemed to come easy for them. These are the people— in many, but certainly not in all cases—who end up telling the rest of us how to go about our business in computing. They figure out the theories of computation and the semantics of our languages; they define the software methodologies we must use. It’s good to have their perspective, but it’s only a perspective, not one necessarily gained by working in the trenches or watching the struggles of people grappling with strange concepts. Worse, watching their careers can discourage the rest of us, because things don’t come easy for us, and we lose as often or more often than we win. And discouragement is the beginning of failure. Sometimes people who have not had to struggle are smug and infuriating. This is my attempt to fight back. Theirs is a proud story of privilege and success. Mine is a story of disappointment and failure; I ought to be ashamed of it, and I should try to hide it. But I learned from it, and maybe you can, too.”
- Richard P. Gabriel, “A Personal Narrative: Journey to Stanford (Patterns of Software)
But what about your neighbor Bob's place? You buy him dinner, and the next day a string of bits comes your way via Tor (or somesuch.) There is no need to utter the word "Bitcoin" during said dinner. A wink, a nudge, etc. will suffice. The next day, Bob does the same with his neighbor Charlie. And so on.
And, naturally, if Bob were a traitor, he could rat you out to the Gestapo. But he could just as easily rat you out for [insert extremely popular but highly-illegal-in-the-USA activity here.] No digital cocaine required - the analog kind will do. And if you haven't any under your bed, Bob will helpfully leave a kilo in your toilet tank.
Most people have already had plenty of practice exchanging highly-illegal strings of bits. Now they will just need to learn to give each other "free" stuff as well.
Bitcoin hasn't reached the critical mass needed for this kind of thing, but there is no reason why it could not.
Consider hawala (http://en.wikipedia.org/wiki/Hawala) which is doing quite well despite draconian bans. On which currencies do hawala transactions depend? All of them and none of them.
I saw it when you checked it in. Be careful what you post for public consumption, someone might actually read it.
> And why does a self-compiling compiler need an RSA implementation, anyway?
You gave this one away already on MoronLab, for anyone who wishes to see.
Any why has the Urbit Dukes list been so quiet? Make some noise, Moldbug.
Moldbug's system:
https://github.com/cgyarvin/urbit/
Its blog:
Paper is not the answer for a pauper with no room to call his own, nor for a factory hand living in a dormitory. There are many people alive right now for whom paper is already not the answer. But some of them could benefit from a Wikipedia "gameboy."
Yours or my paper library will carry knowledge into the ages quite well - until some vagrant burns it to warm himself in the wintertime. A piece of electronics, on the other hand - assuming we could make one that really lasts - could be passed down as an heirloom. And, should it begin to flicker out, the words could always be read off and set to paper.