0bfusct3

5 ms·

1.
by 0bfusct3 16y ago
Professional Linux Kernel Architecture has a good introduction into the Linux/os nomenclature.
2.
by 0bfusct3 16y ago
People that have all this "talent" is nothing more than a drive for something - the talent in x, y, z is a side effect. My drive is for a distributed, vm based operating system and a language to go with it, subsequently I'm versed in mathem
3.
by 0bfusct3 16y ago
Tivo releases what they see as either not a competitive advantage or a burden to maintain. Just like Nvidia releases the shim but nothing relating the how the hardware works - it's a business they aren't here to plant daisies in the FOSS fi
4.
by 0bfusct3 16y ago
My example may have been flawed (it was meant for exaggeration ) but the point still remains that API use is fine under GPL v2.
5.
by 0bfusct3 16y ago
Then taking it all the way down to the hardware, every user of x86 should be required to agree to a license agreement to use an x86 processor since it 'interprets' opcodes on-the-fly thus everything that uses x86 is under an intel license Q
6.
by 0bfusct3 16y ago
Overhead of the operating system and more likely a massive amount of packets per second will easily peg a single core.. I did some tests with nginx (comparable to node.js) and it easily pegged a xenon 2 cpu quad core 8GB ram (all 8 cpu's we
7.
by 0bfusct3 16y ago
Maybe it's just me but I think this is incredibly stupid - He's abstracting the issue that Unix isn't distributed into a single application. It's like putting $5000 rims and mufflers on a $100 van.
8.
by 0bfusct3 16y ago
Configuration files need to be static key value or a relational algebra - you cannot have mutations and branches based on logic within a configuration or else you introduce issues you wouldn't want to even dream of.
9.
by 0bfusct3 16y ago
c, capabilties (or lack there of), self healing, runtime based optimizations, concurrency, locking, threading and just generally the way it's structured it's not meant to be a distributed operating system the applications developed for it s
10.
by 0bfusct3 16y ago
Sure they do but they use extremely specialized software that probably took years to apply to the platform let alone developing the software. Linux is the top in distributed computing because it filled a niche (free) and has momentum if BSD
11.
by 0bfusct3 16y ago
That's like saying language y is fine because I can just search and copy and paste... no you cannot. If you do anything beyond a simple [[ -f somefile ]] && do something sh turns into a nightmare.. case in point autotools.
12.
by 0bfusct3 16y ago
Simple interfaces tying into a vm for complete distribution of software on any architecture. Concurrent, functional and slightly object orientated low level languages allowing automatic formal provability and easier formal provability. Th
13.
by 0bfusct3 16y ago
The same can be said for *nixes, in order to create something in sh using programs you need literally days of reading man pages for switches, etc or use perl, python, etc.. but even then many tools don't have bindings so you're back to use
14.
by 0bfusct3 16y ago
Unix is bad, crusty and getting less relevant due to how computers are becoming more distributed and less as a single system. Linux may be the top of the herd right now but sooner rather than later there is going to be a huge paradigm shift
15.
by 0bfusct3 16y ago
Get a hardware book and read up on how computers actually work. This will help an immeasurable amount to understanding why C is the way it is.
16.
by 0bfusct3 16y ago
I recently ditched rails for sinatra / padrino (mostly sinatra) due to the fact that if you want to do something off the beaten path, even in rails 3 it's a complete crap shoot of trying to tie together different pieces since it seems peopl
17.
by 0bfusct3 16y ago
Not to crap on the parade or anything but new languages are a dime a dozen and most all offer the same exact paradigms rehashed over and over and over. What I want is a low level easy to verify OOP/chaining functional concurrent language ba
18.
by 0bfusct3 16y ago
This shows nothing more than a badly implemented api. POSIX is a bad api for anything modern (distributed).
19.
by 0bfusct3 16y ago
This 6k vs 6M LoC comparison is pretty dubious. If your disk driver has a bug and overwrites some data you're just as screwed up, be it running in userspace or kernel space. The argument these bugs are less powerful because they are now in
20.
by 0bfusct3 16y ago
Linux has exploitable bugs about once a week, read lwn and scan over the security page for kernel cve's.
21.
by 0bfusct3 16y ago
The problem with opscode is that it still does take work to scale due to applications needing to be reconfigured in order to allow multiple servers (and this is the main issue with scaling: work). Currently I'm working on a very very simila
22.
by 0bfusct3 16y ago
Can we just call it what it's been known as in computer science since oh 1960's distributed operating systems?