Feeds

The BBC Micro turns 30

The 8-bit 1980s dream machine

Build a business case: developing custom apps

Corporation Street

Before the Atom had even been launched, executives at the BBC's education programming department, enthused by rival broadcaster ITV's 1979 series The Mighty Micro, developed a plan to help encourage ordinary Britons to learn to use computer technology.

The Mighty Micro

Instigator: Christopher Evans' 'revolutionary' book

The Mighty Micro, presented by physicist Dr Christoper Evans and based on his book of the same name, had forecast how computer technology would utterly change working practices and the economy in the near future. He'd seen how the computing scene had exploded in the US on the back of kit from the likes of Apple and Commodore, and how it had not merely appealed to enthusiasts, but had also begun to transform business.

In 1979, the BBC produced a three-part series, The Silicon Factor, to explore the social impact of the microchip revolution. In November of that year, the Corporation began preliminary work on a ten-part series, provisionally titled Hands on Micros and scheduled to be broadcast in October 1981. It would introduce viewers to the computer and help get them using one. It would also form the launch of what would become known as the BBC Computer Literacy Project (CLP), steered by The Silicon Factor Producer David Allen.

In March 1980, the BBC began a consultation process to shape the Computer Literacy Project. It discussed the scheme with the UK government's Department of Industry, the Department of Education and Science, the Manpower Services Commission, and other organisations. By happy chance, it learned that the DoI was planning to name 1982 the 'Year of Information Technology'.

BBC Literacy Project original review

Internal review: in 1983 BBC detailed the progress made by the Computer Literacy Project

It was decided that the Computer Literacy Project and the TV series that would launch it needed a machine which the public could buy and use to gain hands-on experience of what was being discussed in each episode. Only that way would the audience truly engage with the new technology and the goals of the CLP be realised. Around it would be assembled a full array of guides, adult-learning courses and software packages.

However, the BBC quickly realised that, with no standard platform available, particularly when it came to Basic, the lingua franca of home micros and the language the show would be using to present examples of programming, it would have to specify one itself. With currently available machines all sporting different dialects of Basic, it was felt that choosing one of them would hinder viewers who had bought a different machine.

The only option, then, was to define a standard, to specify a machine that would incorporate a Basic that would have a great deal of commonality with other dialects, but would be well structured to foster good programming practice. It would specify all the features a computer ought to possesses, even if those features – such as floppy disk and hard drive support, extended I/O options, and the ability to download programs over the air through the Teletext system – were absent from many current machines.

The BBC's Computer Programme

Geek chic circa 1982: Ian McNaught-Davis on The Computer Programme
Source: BBC

It became clear that to give this 'standard' some weight, it would need the BBC's clear stamp of approval – to be, in fact, the BBC Microcomputer. That, in turn, would necessitate the close involvement of BBC Engineering, the department charged with handling all of the Corporation's technical endeavours.

Building a new machine from scratch was impossible – it would take at least two years, more than the Computer Literacy Project schedule allowed. So the CLP team decided to approach the likes of Acorn and Science of Cambridge – soon to be renamed Sinclair Research. In all, the BBC met seven computer companies in the UK, six of whom were keen enough to detail how they would work with the BBC and the machine they would produce.

The essential guide to IT transformation

Next page: NewBrain? Never

More from The Register

next story
Reg man looks through a Glass, darkly: Google's toy ploy or killer tech specs?
Tip: Put the shades on and you'll look less of a spanner
So, Apple won't sell cheap kit? Prepare the iOS garden wall WRECKING BALL
It can throw the low cost race if it looks to the cloud
Apple promises to lift Curse of the Drained iPhone 5 Battery
Have you tried turning it off and...? Never mind, here's a replacement
Now that's FIRE WIRE: HP recalls 6 MILLION burn-risk laptop cables
Right in the middle of Burning Mains Man week
One step closer to ROBOT BUTLERS: Dyson flashes vid of VACUUM SUCKER bot
Latest cleaner available for world+dog in September
Apple's iWatch? They cannae do it ... they don't have the POWER
Analyst predicts fanbois will have to wait until next year
HUGE iPAD? Maybe. HUGE ADVERTS? That's for SURE
Noo! Hand not big enough! Don't look at meee!
Samsung Gear S: Quick, LAUNCH IT – before Apple straps on iWatch
Full specs for wrist-mounted device here ... but who'll buy it?
AMD unveils 'single purpose' graphics card for PC gamers and NO ONE else
Chip maker claims the Radeon R9 285 is 'best in its class'
prev story

Whitepapers

Top 10 endpoint backup mistakes
Avoid the ten endpoint backup mistakes to ensure that your critical corporate data is protected and end user productivity is improved.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Backing up distributed data
Eliminating the redundant use of bandwidth and storage capacity and application consolidation in the modern data center.
The essential guide to IT transformation
ServiceNow discusses three IT transformations that can help CIOs automate IT services to transform IT and the enterprise
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.