badgersandjam

Unfortunately we live in an age of idiocy where anyone will sell their soul for a smaller fee and less privacy. There's no winning against that so you have to deal with this from the inside of the enemy via "legitimate sabotage"

a) get into hiring positions in the government and hire the stupidest, least qualified and incompetent people you can get then quit and leave the projects in the shit.

b) spend money galore so it cant be used on anything else

c) leak insider information on the sly.

d) use the tools you built against the people who paid for them.

e) manipulate and shame other staff out of positions of power.

f) play people off against each other and create new rivalry which consumes all money and time.

I worked for the defence industry. This is how to break it.

You'd make a good politician because you make a bad human now with all that word twisting.

Entirely agree!

But blaming everything on climate suddenly isn't the right answer. Perhaps someone lost a ship load of PCP in the sea and they just snuffed it. And they're trying to hide that.

Another hypothesis that could be tested rather than "fuck blame it on climate so we can get some funding and get some nice new Herman Miller chairs and a new MacBook each"

That's not what I'm saying. I can't make it much clearer than:

a) suddenly out of the blue, a Ford Transit mutates into a toaster.

b) someone is "pretty sure it is related to the impending comet impact".

c) Everyone goes YAY SCIENCE!!!

Sorry but derision is the only thing left. It's not science, it's religion.

a) suddenly out of the blue someone delivers a load of fish.

b) Some guy doesn't notice this and goes "pretty fucking sweet; I'm totally wasted on mushrooms and I reckon that bearded dude over there turned that loaf of bread into all those fish. Damn I've got the munchies."

c) HE'S THE FUCKING MESSIAH.

There is no causality chain established other than a hunch.

Problem is we have about 50% certainty...

There's a pretty big assumption in there. That the comet is approaching earth and not going to miss it by half a parsec or that the comet is infact a bit of dirt on the lens of the telescope...

All of which need testing first before you start waving your hands around and start saying "WE'RE GOING TO FUCKING DIE - RUN!"

This is exactly the problem. There should be no activism and no causes in science. Each of them implies bias and results in less than ethical practice and unreliable theories.

To ask for rationality and the application of the scientific method results in claims of denialism and instant burying of the opinion.

That's not acceptable.

None. However svn prevents them doing anything major unless they tell someone.

You never know with git. Which is one of my big problems with it. The picture on master doesn't necessarily represent what happens on other repos across your organisation.

Not sure why you're downvoted. That's bad science regardless of how you look at it. The use of the word "climate" in a quote is a big indicator of bad science as it happens to pay the bills and make a good quote in the press before all other concerns at the moment.

If it turns up in a paper at the end and is peer reviewed, then it has some credence but before that, nada.

Feynman is rolling in his grave again...

Edit: if you downvote, explain yourself or you're a coward and a hypocrite.

I disagree. The tools are awful and terribly slow to execute at best. Then you occasionally get shafted with a relabel.

Interesting approach and one I hadn't considered. Thanks for the heads up.

Actually I had a nice dedicated box until 2013 at a reputable host in the UK. Unfortunately I no longer wished to fish out for £95/month for it. Still had problems even though the thing was well maintained and there were no bad neighbours. It was less noisy than a VM at Linode however, so you're right there.

I'm not sure why you were downvoted - it's a valid solution.

To be honest, I'd rather see DCE/RPC (DCOM's ancestor) make an appearance without some of the pain points of DCOM.

Don't bother running a mail server. It's hell. I did from 1998 until about last week. I started running it on a cable modem with an old Compaq desktop, migrated to a dedicated server (which hosted a load of other stuff) and finally onto VMs.

I have spent hours getting myself of blacklists after entire IP ranges were reported. I've spent hours working out why the hell Postfix won't talk to dovecot on a local socket, upgrading Linux distributions, postfix and dovecot and being fucked over by config format changes and periodically losing entire mailboxes to IMAP bugs. Oh and SELinux - hours of it.

The thing that finally killed it for me was Yahoo. My landlord uses Yahoo mail for comms and Yahoo just decided to stop accepting delivery from my server. It took a phone call from me asking him why he hadn't sorted something for me and for him to tell me that he didn't get the email to discover this. So I dredged through the logs, found an error from yahoo's mail servers saying I need to hit a web form to prove I was a legitimate sender. So I did that, and nothing, not a sausage happened. Googling around says I need to wait 6 months before submitting the request again.

I have no power in this situation. I can't email my landlord. I need to do business, not piss around with politics.

So in a fit of anger, I blasted my VM on Linode, went to my local supermarket, bought a Moto G2 in cash to replace my Lumia 630 (which was doing IMAP) that I just smashed the screen on, signed up for Google Apps free trial and just moved the domain over to that.

Just can't be fucked with it any more. I run "inbox zero" (i.e. I delete religiously) so there is no cost for me to migrate.

I don't care if they read my email or shop me to the feds; I'm tired of herding servers and software these days. A decade ago I could quite happily spend all day doing it but I have better things to do now.

Spot on. I can't say enough good things about COM; it's enabled some quite amazing things for me over the years and really top notch distributed systems that are easy to manage.

Fantastic - thanks for the link.

I wonder what Andrews and Arnold's approach to this problem will be. They're the last bastion of common sense in the UK.

MVC is really easy to test. This example just completely ignores concepts as programming to interfaces, composition and single responsibility.

This. Plus its fucking miserable dying slowly over the space of 20 years. I've watched it happen to so many people. Avoid work, retire early, spend everything, eat everything, do what you must do as early as you can before probability becomes your worst enemy.

Edit: The people I've watched die had one regret only: Waiting until retirement to do what they wanted at which point they can't. Perfect cogs with pensions and private healthcare paid up through slavery for 40+ years. Nothing to show other than some bricks and a hip replacement and a nice plot in the graveyard.

Just want to mention that some of the internals of this aren't great. There's absolutely no decoupling which makes testing very difficult and the contextual stuff is horrid. The components folder is also a cleverly hidden static ball of mud. I hope this isn't what they're teaching new developers as we'll have to spend a long time getting them to unlearn this in the future...

That's not much. Our baseline config HP DL380s come with 64GiB RAM (!!)

Wasn't aware of the C65. I'd not have bought one myself. In 1990/1991 there were a lot better machines on the market.

Unfortunately my only Commodore experience was the Amiga 2000. That lasted a mere year before it was replaced by an Acorn A440/1 which was an 8MHz ARM2, 4Mb RAM and 40Mb hard disk'ed monster. That lasted until Windows NT3.51 came out for me to give you an idea how powerful it was.

Nice to see someone giving the C65 some headspace and time though. Especially when you think of the man hours that went into the original.

Ok perhaps the personal attack was uncalled for. Please accept my apologies.

That's exactly my point. It's not limited to the Linux core team. We divide into working groups of 2-3 people max to avoid this. Works quite well.

Not really odd. You just haven't poked the bits I have.

You're entirely right and I've upvoted you.

However, with one small caveat: servers don't generally have sound cards so the impact of this was relatively low. There aren't that many desktop Linux users out there. I mean I'm a Unix guy at heart and I'm typing this on a Windows laptop. I've never used Linux on the desktop and probably never will.

Now servers do have init processes and we don't really want to spend the next 3-4 years being guinea pigs. I'm quite happy for the vendors to do this behind the scenes or offer it as an alternative but we've got an RHEL+CentOS release with systemd in it already and a Debian with systemd in it just around the corner. A pulseaudio situation, even for 6 months, will result in no small amount of chaos.

I do indeed remember times before even ALSA when you had to pay OSS for drivers for your turtle beach card etc. But that's in the distant past, not right now and of little relevance. Windows was fine on the desktop then as well and the sound worked fine out of the box.

Known good HP DL380 G8 pulled from production, ECC RAM, monitoring, SAS disks, full hardware test and memtest86 pass.

Nope. Not that.

We don't buy crappy hardware or not test it.

Yes you're right.

When your system consists of functions "A, B, C, D", I'd expect to see test suites for "A, B, C, D". In this case there were test suites for "A, B, C". The client found D therefore the test suite was incomplete.

Now if a bit of A, B, C or D suites were missing that would be different and entirely expected.

You're 100% correct. In fact my own mail server/web machine uses it. Theo is not right at the centre; there's a large group of people who work together as equals from what I can see. I can't recommend it for our "enterprise use" though because we need some of the more friendly features that FreeBSD offers such as ZFS.