Well, who could?
On the off chance, we are now going to be screwed for huge amounts of tax to save the planet.
Even if you believe in global warming, you'd have to be as stupid as, er, the average Guardian reader, to think that handing over countless extra bilions is going to make the slightest bit of difference to the problem, given we apparently only contribute 2% to the greenhouse gases.
So we get to lower our standard of living just to make a point to the rest of the world.
Brilliant idea, why don't do something really clever like invade a foriegn country as well. Oh, we already did.
Of course, the reality is it's just a cool way for the nice Mr. Brown to raise even more money to prop up his ill conceived squandering of billions of pounds to achieve a short term increase in the number of labour voters.
Want to save the planet - stop buying new cars and drive something old and interesting. Yes, it probably pollutes more but nowhere near as much as the environmental cost of building a new one or disposing of all these lead acid batteries in your bloody Prius.
Most of all, please, just start to use your brain to think for yourself instead of just believing everything you are told.
Tuesday, October 31, 2006
Monday, October 23, 2006
Sage Line 50 2007 - the Quick and the Dead
I'd like to say I'm surprised that version 13 appears to be full of bugs, but I'd be lying.
You can develop software quickly OR you can have something that works ; you can't have both.
Sage have followed the strategy adopted by many other companies in the past of having a release a year in order to drive sales. Witness Windows 98 and Windows 2000 etc. However most of these companies have dropped this concept because it makes a rod for your own back having to come up with new features every year and a constant unrealistic development cycle. It also means having to support an increasingly large number of versions.
Best advice for users is to stick to a version that works until you actually need the features offered in a new version or Sage threaten to remove the upgrade path. Then make sure you wait for the bugs to be found in the new version before you commit to the upgrade.
You can develop software quickly OR you can have something that works ; you can't have both.
Sage have followed the strategy adopted by many other companies in the past of having a release a year in order to drive sales. Witness Windows 98 and Windows 2000 etc. However most of these companies have dropped this concept because it makes a rod for your own back having to come up with new features every year and a constant unrealistic development cycle. It also means having to support an increasingly large number of versions.
Best advice for users is to stick to a version that works until you actually need the features offered in a new version or Sage threaten to remove the upgrade path. Then make sure you wait for the bugs to be found in the new version before you commit to the upgrade.
Tuesday, October 03, 2006
Sage Line 50 gets go faster stripes
Performance issues with Sage Line 50 may be about to become a thing of the past.
While converting our packages to Sage line 50 2007 it certainly seems that certain aspects are much improved in terms of accessing data across the network.
Initial testing suggests that reading through Sales Accounts across the network is at least 30% faster than version 12. There also seems to be more caching going on as consecutive read tests were again quicker than the same tests in version 12.
Watch this space.
While converting our packages to Sage line 50 2007 it certainly seems that certain aspects are much improved in terms of accessing data across the network.
Initial testing suggests that reading through Sales Accounts across the network is at least 30% faster than version 12. There also seems to be more caching going on as consecutive read tests were again quicker than the same tests in version 12.
Watch this space.
Subscribe to:
Posts (Atom)