This is exactly what Australia is trying to do with the National Broadband Network; Telstra - the incumbent last mile monopoly for cable and copper DSL - will eventually phase out their copper network to be replaced with the the government-funded mostly fibre based Nbnco last mile network.
Of course, the project is political dynamite, the rollout is massively delayed, has run over budget, and the current government is trying to change the fibre to the premises network to fibre to the node, but the intention is to provide common "wholesale" last mile connectivity that any ISP can resell to consumers.
I'm no sucker. I only buy coins named after celebrities.
Like 50 Cent?
I've maintained legacy payroll software (Oracle RPT, predates PL/SQL) and have been marginally involved in migrating clients to the new shiny payroll system. Generally it fails where the client wants the new system to behave exactly like the old system.
The new system usually can handle the required business rules (or it's not too much work to make this happen) but all the processes around those rules are different. eg the new system needs to generate report RW200 to lineprinter 6, daily at 6PM and must be formatted just so (no one reads the first 1000 pages, but the summary page is critical to some obscure business process.)
So, the new system has to print unformatted ASCII to a serial line printer, in an obscure way, on nonstandard paper, that's hard to replicate in a modern report writer. Never mind the already written, laser printed, on-demand reports (or emailed, or exported to excel or whatever) have the same information - it's NOT THE SAME - our users will be confused so it MUST BE CHANGED!.
Rinse and repeat for basically everything else in your system and you've heavily modified your new system to behave just like your old payroll system (and killed any performance improvements, worked out all the bugs etc again). because it's so heavily modified you're basically on a unique version of the new system that only certain programmers really understand. Ant they're going to retire / leave because the project was so shit to work on.
Add the usual government oversight/waste and you've blown a billion dollars. (that's impressive though, I have to say.)
We moved from Open-xchange (maildir, cyrus imap) to exchange 2010 a while back mostly for political reasons.
Our email backups have become a nightmare.
We can't backup exchange mailboxes while they're being replicated to our DR site - the exchange server blue-screens BY DESIGN to provent the mailstore from being corrupted. Thanks, Microsoft! After shutting dowen replication we have to backup the entire 200GB database as one blob, every time - this takes at least a couple of hours over the network to our backup server.
The mailbox DAG loses sync fairly regularly, which means you have to dump a replication copy and start again (ie copy the whole thing over the network again.) This kills mailbox performance dramatically.
In comparison we used rsync to replicate our maildir directories to our DR site previously (along with openldap slapd replication) - it worked great. Rsync backup took minutes to complete as it only backs up the changes.individual email deach and recovery from backup is easy, too, just put the emailback int he user's mailbox and re-index the mailbox, compared to recovering the entire mailbox database.
Finally - Postfix appears to crap all over Exchange's MTA in terms of performance and logging/problem resolution. We use postfix in front of our exchange servers and it's regularly waiting for exchange to catch up.
Sure, exchange has lots of end user features but i'm not impressed with the backend storage solution at all.
Give me postfix/IMAP/maildir over Exchange any day.
I don't know about the rest of the world but last year, Lenovo Australia changed their support arrangements. Previously Lenovo support was excellent - now it's abysmal. We had a small form factor desktop power supply fail. Our "onsite next business day" support contract ended up being to a three week wait for parts, along with the engineer coming onsite before the part had arrived, twice. It was a joke.
We couldn't get a firm answer from Lenovo support - eg "the part is on route" or "we're out of stock" or "it's been ordered" were all provided as excuses at various times. A 3 week wait for "next business day" support is inexcusable. We also have HP and Dell desktops with NBD support. They also occasionally fail. They get replaced the next day.
We're not buying anything from Lenovo again.
Definitely need another web framework option
Between infinite and short there is a big difference. -- G.H. Gonnet