I think the trend of front-end projects not providing a compiled `dist` folder with the assets for web inclusion to be a bad idea. This requires me to NPM install this "front-end code" (no Bower) and then add this Gulp compilation to my build. What happened to adding a `dist/hack.min.css`? Why no Bower?
Please stop calling your project '<x> for hackers.' It's annoying, regardless of whether your project shows any of the concepts or ideals associated with hackers (either kind). Which most of these projects don't.
Besides, it's a trend that's really easy to satirize.
Here's a fun game: describe an "os for hackers." See how long it takes for the person you are talking to to realize you're describing ITS. You win if the person fails to realize this, and actually says they would want to use said system today. For bonus points, cart in a PDP-10: their new 'working environment'. :-D
ITS was good. For something a little more recognizable (and probably more achievable on current hardware), MS-DOS was actually pretty good from the hacker's point of view (and FreeDOS continues that legacy).
I say this because DOS was an OS that didn't get in your way. No, it didn't afford you any conveniences, really. It gave you a (shitty) file system, command line, program loader, a handful of utilities, and practically nothing else. Not exactly user-friendly. However, it also gave you completely unfettered access to the underlying hardware. The Intel reference manuals and a good assembler, and you could do literally anything. Since it was single-tasking, once your program was loaded, it had complete control and owned the entire physical address space. There was nothing to prevent you from calling into the BIOS, or doing I/O willy-nilly to ports, peeking/poking randomly into memory, etc. There's a reason why several OS's were bootstrapped on top of DOS, including Windows: it gave you just enough conveniences that you didn't have to start from total scratch, but it did so little that it never got in your way or otherwise prevented you from doing whatever you wanted.
I occasionally fire up FreeDOS on an old P2 or in a VM and just tinker. If I were to produce a real product, I'd obviously be better off writing something for Linux or BSD kernelspace, but for exploring the way hardware gets programmed on its lowest level, DOS is pretty indispensable. I'd liken the difference between low-level programming on DOS and the same on Linux/BSD to the difference between using an interactive interpreter and a batch compiler. It really can enable low-level experimentation in much the same way.
Some of this is nice, but I don't get why you would want your output to look like markdown _before processing_. Why can't the headings be headings, without the "##"s etc.
Because to some of us, including me, actually, that kind of markdown markup is quite pleasing to the eye, as well as providing addtional visual queues. You can never have too many of those, provided they are well designed.
That's pretty much what CSS frameworks are: a set of pre-built items you can use to build your site, so you don't have to do it all yourself. Don't ask me why, ask whoever wrote the first CSS framework.
[+] [-] mikegioia|9 years ago|reply
[+] [-] insin|9 years ago|reply
http://npmcdn.com/hack
[+] [-] jafingi|9 years ago|reply
[+] [-] the_duke|9 years ago|reply
Well... move along please, nothing to see here.
[+] [-] sanqui|9 years ago|reply
[+] [-] damptowel|9 years ago|reply
[+] [-] vortico|9 years ago|reply
[+] [-] qwertyuiop924|9 years ago|reply
Besides, it's a trend that's really easy to satirize.
Here's a fun game: describe an "os for hackers." See how long it takes for the person you are talking to to realize you're describing ITS. You win if the person fails to realize this, and actually says they would want to use said system today. For bonus points, cart in a PDP-10: their new 'working environment'. :-D
[+] [-] groovy2shoes|9 years ago|reply
I say this because DOS was an OS that didn't get in your way. No, it didn't afford you any conveniences, really. It gave you a (shitty) file system, command line, program loader, a handful of utilities, and practically nothing else. Not exactly user-friendly. However, it also gave you completely unfettered access to the underlying hardware. The Intel reference manuals and a good assembler, and you could do literally anything. Since it was single-tasking, once your program was loaded, it had complete control and owned the entire physical address space. There was nothing to prevent you from calling into the BIOS, or doing I/O willy-nilly to ports, peeking/poking randomly into memory, etc. There's a reason why several OS's were bootstrapped on top of DOS, including Windows: it gave you just enough conveniences that you didn't have to start from total scratch, but it did so little that it never got in your way or otherwise prevented you from doing whatever you wanted.
I occasionally fire up FreeDOS on an old P2 or in a VM and just tinker. If I were to produce a real product, I'd obviously be better off writing something for Linux or BSD kernelspace, but for exploring the way hardware gets programmed on its lowest level, DOS is pretty indispensable. I'd liken the difference between low-level programming on DOS and the same on Linux/BSD to the difference between using an interactive interpreter and a batch compiler. It really can enable low-level experimentation in much the same way.
Anyway, ITS was the bee's knees.
[+] [-] dikei|9 years ago|reply
[+] [-] qwertyuiop924|9 years ago|reply
[+] [-] allthetime|9 years ago|reply
[+] [-] kowdermeister|9 years ago|reply
http://m.imgur.com/3uzsU8p
[+] [-] joshka|9 years ago|reply
[+] [-] Illniyar|9 years ago|reply
[+] [-] dlsym|9 years ago|reply
[+] [-] zongitsrinzler|9 years ago|reply
[+] [-] kimshibal|9 years ago|reply
[+] [-] elsurudo|9 years ago|reply
[+] [-] qwertyuiop924|9 years ago|reply
[+] [-] bobwaycott|9 years ago|reply
[+] [-] Tobold|9 years ago|reply
I never used one and everyday there is another one on HN, confusing me with all its features xD
[+] [-] 0x142857|9 years ago|reply
[+] [-] component|9 years ago|reply
Or am I missing something?
[+] [-] qwertyuiop924|9 years ago|reply
[+] [-] dismal2|9 years ago|reply
[+] [-] 0x142857|9 years ago|reply
[+] [-] Kinnard|9 years ago|reply
[+] [-] oldboyFX|9 years ago|reply
It's kind of sad that it isn't.
[+] [-] c4pt0r|9 years ago|reply
[+] [-] dismal2|9 years ago|reply
[deleted]
[+] [-] shrugger2|9 years ago|reply
[deleted]