1. The world is full of fascinating problems waiting to be solved.
2. No problem should ever have to be solved twice.
3. Boredom and drudgery are evil.
4. Freedom is good.
5. Attitude is no substitute for competence.
That seems to capture the hacker spirit pretty well.
I do agree with jwise0, though, in that the phrasing and some details are way too specific to the author's own experience.
While "Unix" is perhaps not a requirement, but he does give a convincing argument why it should be an open source operating system - which significantly reduces the number of options.
Sure, you can be a hacker who uses Windows, but you're locked out of half of what your computer can do. That is a restriction.
Yes, you can work only on the userspace but to me, the essence of being a hacker is having a keen interest in the whole stack. While you're still locked out of your CPU internals, an avid hacker should also have an interest in hardware hacking.
Feel free to disagree, but I'm on ESR's side on this one.
I'm a pretty big Unix guy, I run Linux desktops and FreeBSD servers, but you're going to need to clarify what you mean by that.
What exactly is the restriction? Assuming you're willing to install some drivers and patch some system dlls, you can generally achieve the same things.
You can very easily disable driver signature enforcement in Windows, as I have and as does anyone who writes drivers for Windows platforms or does low-level reverse engineering work on it. I think the balance of "force signing by default but allow it to be turned off" is a pretty good one, works well for Windows drivers and for Android at least.
All of the below (and the parent post) is my opinion. You can disagree with me, and I'm fine with that.
You're unable to study what your computer actually does. You don't have access to the source of anything that happens in kernel space. You can take university OS courses and tinker with the educational toy operating systems, read about Windows internals but to see what you're actually running is different not only at a philosophical level but also practically.
Yes, you can get into kernel space in Windows by doing a driver DLL, so you can make your computer "do" anything, but what you, as a person, will do is a lot different when dealing with a black box rather than a white box. When doing Windows kernel space driver development, you're reading the documentation (and hope that your computer does what it says), when doing that with an open source OS, you can read the source too (and know that the computer does exactly that).
To me (you don't have to agree), the essence of being a computer is that you don't only use your computer to get work done or use it for entertainment. Computers are the entertainment (and perhaps the work too, like in my case in the semiconductor industry).
Uhm, or I can fire up windbg and trace through my kernel... not sure what you're getting at (though I do miss the days of softice where I could just hit ctrl+d).
Same goes for pretty much everything else you stated too. We have kernel level debuggers, don't blame me if you can't be bothered to learn a little assembly and trace out the knowledge you need.
Sure, it may not be as easy as C, but it's _very_ possible. It just requires some reverse engineering skill too.
If what you were saying was true, I would absolutely agree with you, but as long as ring0 debuggers exist, it won't be. I find reverse engineering just as exciting if not more so than forward engineering most of the time.
As I tried to say, it's more of a philosophical and psychological (and practical) thing than actually being impossible.
Reverse engineering is a valuable skill but it's not too fun when you could just look at the source, with variable names, comments and nice formatting. In some cases it might be a nice "puzzle" to solve but that's not how you want to learn how things work.
Speak for yourself. Some of us appreciate clandestine knowledge all the more.
I made it clear from the first comment on that it's my opinion and you don't have to agree.
You shouldn't take these as rules but as a guide which the title is indicative of. Sure you can become a hacker while not knowing english but the immense amount of information available on the internet (mostly in english) is just too big to avoid (not impossible as you've indicated with your examples) for beginners.
EDIT: Please write an article!
That seems like quite the coincidence given that Eric S. Raymond is the author of the article itself. Maybe there's something to that.
> For instance, he gives the monoculture that all hackers speak English
No. He doesn't give anything. He suggests that learning English is useful because the internet and hacker culture are dominated by it.
> But this essay is not that.
The scope of the document is clearly stated under the "Why This Document?" header.
The general aspect that I dislike is the idea that there is only one kind of hacker -- the kind that fits into Eric S. Raymond's "the hacker culture". For instance, he gives the monoculture that all hackers speak English; but just a few weeks ago, we saw an article on HN about the old microcomputers of the Soviet Bloc (I wish I could find the link now). And, perhaps, maybe my all-time favorite hacks were executed by demosceners who spoke little-to-no English. Are these people not hackers? I don't think you'd find anyone who could argue that, but they are not part of Eric S. Raymond's monoculture.
The great essay that I have always wanted to read about How to Become a Hacker would be answering the question of how to find joy in the minutiae, and how to put all the little pieces together to make the most interesting things. But this essay is not that.