Comment Where the evangelicals lead... (Score 1) 1319
The others will shurely follow... (typo was deliberate)
Comment LAMP (Score 1) 99
Linux - Good
Apache HTTP - Not so good
MySQL - Currently doing no evil
PHP - For the love of god, why?
Comment Re:I'm a self-taught programmer (Score 1) 523
Some of greatest dullards I've ever worked with - have been: house in the suburbs, car-driving, college guys. Having had life handed to them on a plate; many display a noteworthy lack of initiative, extending themselves, only as far as is necessary to support their social-climbing goals.
I've worked as a consultant/contractor. Mostly, providing them with the information they were too lazy themselves to learn.
Who wouldn't rather have, a clued-up, hacker working on the team, and not an indolent, middle class jock.
And, seriously, the information is all on the Internet, or in books. Lots of people don't even want to go to college, and be forced to deal with priapic chasers of young skirt, egomaniacs, bullies, weasel-worded bigots, manic leftists, hangers-on, liars and all who plague academia.
It's the 21st Century, get the information yourself. Commerce is pure. Fuck University.
Comment Re:Why should we trust openssl? (Score 1) 53
Unless it's made of cheese, and stamped with 'Oude Kass', the wheel is never round enough for the typical Dutch developer.
Comment Re:RMS was right (Score 1) 447
He is always right - it's just that he's a little weird as well.
Comment Re:Serious issues with this (Score 1) 248
Now, without getting into how much i dislike Pulseaudio (maybe because i'm an old UNIX fart, thank you very much), I think there are really serious issues with "The Journal", which I can summarize as such:
1. the problem it's trying to fix is already fixed 2. the problem isn't fixed by the solution 2. it makes everything more opaque 3. it makes the problem worse
The first issue is that it is trying to fix a problem that is already easily solved with existing tools: just send your darn logs to an external machine already. Syslog has supported networked logging forever.
Second, if you log on a machine and that machine gets compromised, I don't see how having checksums and a chained log will keep anyone from just running trashing the whole 'journal'.
rm -rf
Third, this implements yet another obscure and opaque system that keeps the users away from how their system works, making everything available only through a special tool (the journal), which depends on another special tool (systemd), both of which are already controversial. I like grepping my logs. I understand http://logcheck.org and similar tools are not working very well, but that's because there isn't a common format for logging, which makes parsing hard and application dependent. From what I understand, this is not something The Journal is trying to address either. To take an example from their document: MESSAGE=User harald logged in MESSAGE_ID=422bc3d271414bc8bc9570f222f24a9 _EXE=/lib/systemd/systemd-logind [... 14 lines of more stuff snipped] (Nevermind for a second the fact that to carry the same amount of information, syslog only needs one line (not 14), which makes things actually readable by humans.)
The actual important bit here is "User harald logged in". But the thing we want to know is: is that a good thing or a bad thing? If it was "User harald login failed", would it be flagged as such? It's not in the current objectives, it seems, to improve the system in that direction. I would rather see a common agreement on syntax and keywords to use, and respect for the syslog levels (e.g. EMERG, ALERT,
Fourth, what happens when our happy cracker destroys those tools? This is a big problem for what they are actually trying to solve, especially since they do not intend to make the format standard, according to the design document (published on you-know-who, unfortunately). So you could end up in a situation where you can't parse those logs because the machine that generated them is gone, and you would need to track down exactly which version of the software generated it. Good luck with that.
I'll pass. Again.
Hear, hear. The biggest problem anyway is that people don't read their log-files. This Journal thing just seems to make them harder to parse.
Comment pension funds crisis (Score 1) 433
solved
Comment HTML version renders pretty well though.. (Score 1) 507
Went to the site but NoScript had disabled Flash by default. The HTML stuff looks pretty good though.
Comment Re:10 years ago (Score 1) 187
MaraDNS is a great little server
Comment Forget about Technology (Score 1) 235
Forget the technology angle. Be it a lace curtain, or a telephone or the Internet or a camera in the back of the taxi. This is British nature. They used to be really important in the world and controlled lots of dark skinned (and a couple of white skinned) races. Now that is all gone. There is nobody to boss around or control, colonial governors jobs go to Americans these days. So their neurosis grows.... They must manage and control something, so they do it to themselves. It's a nation of shopkeepers, curtain twitchers, and middle management. It will always be shit. Unless you have the money to buy space and privacy. The end.
Comment Re:The Cloud, obviously. (Score 1) 320
Wait a minute. I'm a manager, and I've been reading a lot of case studies and watching a lot of webcasts about The Cloud. Based on all of this glorious marketing literature, I, as a manager, have absolutely no reason to doubt the safety of any data put in The Cloud.
The case studies all use words like "secure", "MD5", "RSS feeds" and "encryption" to describe the security of The Cloud. I don't know about you, but that sounds damn secure to me! Some Clouds even use SSL and HTTP. That's rock solid in my book.
And don't forget that you have to use Web Services to access The Cloud. Nothing is more secure than SOA and Web Services, with the exception of perhaps SaaS. But I think that Cloud Services 2.0 will combine the tiers into an MVC-compliant stack that uses SaaS to increase the security and partitioning of the data.
My main concern isn't with the security of The Cloud, but rather with getting my Indian team to learn all about it so we can deploy some first-generation The Cloud applications and Web Services to provide the ultimate platform upon which we can layer our business intelligence and reporting, because there are still a few verticals that we need to leverage before we can move to The Cloud 2.0.
Bullshit bingo!! Bingo!!
Comment Do like Linux... (Score 1) 798
XFCE, or Awesome - if you're feeling particularly adventurous..
Comment Re:What if I don't mind? (Score 2) 222
I think you really bought the maltodextrin to cut drugs, dealer. Especially with your nerdy background, perhaps you're somehow involved in the manufacture of controlled substances, whoever heard of 'edible oil sands'. Lock m' up.
Submission + - Ask Slashdot: Dot Matrix Code Reviews 1
sentimental.bryan writes: "Are any Slashdotters using Dot Matrix Technology, and if so — do they have any recommendations?
When I was a child, I took a summer school class in computer programming. At one end of the lab stood one of those big old line printers complete with the ubiquitous continuous stack of folded green and white stripped paper. A computer user could print out an entire 10000 line computer program on that device, perusing it later at his or her convenience — on the bus, at the dinner table, at a meeting or even in the bath.
I recently tried something similar, a colleague (born physiologically incapable of the simple act of documentation) — was about to leave the company. A core part of his code-base remained non-functioning and undocumented. I printed out the five most important classes and taped them together forming a single sheet of paper, approx 20ft long.
We had our meeting, using highlighting pens to mark sections of code for review and comment. It was a resounding success, we cut out about 30% of the code, discovered 6 or 7 problems, clarified the DB schema, and much, much, more. I returned to my desk, scroll in hand, and set about correcting the code.
It was so easy to do! The code was corrected with about an hour of typing and it really felt like the job was finished. But it was tedious to tape the A4 pages together. Now I want one of those printers from the golden days. Do programmers still use them? Do you need to format all your code for 80 characters or can they print wider lines?"
When I was a child, I took a summer school class in computer programming. At one end of the lab stood one of those big old line printers complete with the ubiquitous continuous stack of folded green and white stripped paper. A computer user could print out an entire 10000 line computer program on that device, perusing it later at his or her convenience — on the bus, at the dinner table, at a meeting or even in the bath.
I recently tried something similar, a colleague (born physiologically incapable of the simple act of documentation) — was about to leave the company. A core part of his code-base remained non-functioning and undocumented. I printed out the five most important classes and taped them together forming a single sheet of paper, approx 20ft long.
We had our meeting, using highlighting pens to mark sections of code for review and comment. It was a resounding success, we cut out about 30% of the code, discovered 6 or 7 problems, clarified the DB schema, and much, much, more. I returned to my desk, scroll in hand, and set about correcting the code.
It was so easy to do! The code was corrected with about an hour of typing and it really felt like the job was finished. But it was tedious to tape the A4 pages together. Now I want one of those printers from the golden days. Do programmers still use them? Do you need to format all your code for 80 characters or can they print wider lines?"
Comment Re:OCZ (Score 1) 128
Supposedly the fixed one BSOD bug a few days ago. That wouldn't be with this controller anyway, but their record isn't spotless. Then again, Intel managed a SSD blemish too so... you're seeing an industry moving at breakneck speed, just make sure yours isn't on the line.
Using OCZ 8 months now. I tend not to get BSOD's on Linux anyhow.
