GORUCO 2014

Las lecciones que podemos aprender del éxito de COBOL

Andrew Turley  · 

Transcripción

Extracto de la transcripción automática del vídeo realizada por YouTube.

hi my name is and eat early I'm a junior lead software senior engineer at the ladders cassia juarez on twitter and today I'm going to talk to you a bit about Cobalt first of all who here knows COBOL alright so this should be pretty easy to put one

past you guys so first of all I'd like to talk a little bit about what COBOL is and get into a little bit of the history of the language itself back in nineteen fifty-nine the landscape in computer programming was that you bought a computer from somebody

IBM Honeywell one of these other big companies and you got the programming language with it there really wasn't a cross-platform language for writing code and so you were kind of tied as a customer to whatever piece of hardware you bought and that made

it hard for you it also made it kind of hard for the people trying to sell the computers because one of the big problems was well we don't really like your language or you know maybe what if we decide we want to switch things up so in 1959 a woman named

Mary Hawes was at a conference and started cornering people in saying hey we've got this need on the business side to have some sort of common programming language that we can use to write business applications and she started kind of putting together

a team of people who were interested in doing this so by about the middle of 1959 they had started a organization to develop COBOL they had a long-range committee that was in charge of kind of strategic long-term planning a short-range committee in charge

of the medium range committee in charge of kind of figuring things out for the next few years and a short term committee that was in charge of actually designing the language short term committees the only one that actually ended up doing anything in 1959

the December they produced the first COBOL spec so the driving ideas this is according to gene samet who was on the short term committee the driving ideas behind COBOL were that they wanted a language that was natural so they wanted something that people could

[ ... ]

Nota: se han omitido las otras 1.027 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.