275 replies to this topic

[kujaku]

acabo de ver esto en meneame:
http://www.codinghor...ves/000517.html

xD

Que raro, donde esta el Cobol?

[kebrantador]

NO ES DIGNO DE MENCIONAR KUJAKU!!!!!!!! xDDDDDDDDDDDDDDDD

[kujaku]

NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO! xDDDDDDDDDDDDD

Lo que pasa es que consumira tan poco que ni se dibuja en la tabla xDDDDDDDDDDDDDDD

[rokutanda]

O que picar 200 lineas de codigo para mostrar una les daba pereza..

[vimora]

O que picar 200 lineas de codigo para mostrar una les daba pereza..

http://en.wikipedia...._programs#COBOL

Yo solo pasaba por aqui... T4|u3

[rokutanda]

Seh seh, claro..

Yo estaba pensando en algo de este pelo


******************************************************************
* HOLAMUNDO *
* ---------------------------------------------------------------------------------------- *
* *
******************************************************************
* PROGRAM ID: *
* *
* OBJECTIVE: HACE UN DISPLAY DE HOLA MUNDO *
* *
* *
* *
* TYPE: *
* *
* INPUTS: FICHERO NOSECUAL *
* *
* OUTPUTS: FICHERO OTRO *
* *
******************************************************************

******************************************************************
* IDENTIFICATION DIVISION *
******************************************************************
IDENTIFICATION DIVISION.

PROGRAM-ID. HOLAMUNDO.
AUTHOR. ROKU.
DATE-WRITTEN. OCTUBRE, 2006.
DATE-COMPILED.

******************************************************************
* ENVIRONMENT DIVISION *
******************************************************************
ENVIRONMENT DIVISION.

CONFIGURATION SECTION.
SOURCE-COMPUTER. IBM-PC.
OBJECT-COMPUTER. IBM-PC.
...
..
.

Este tema ha sido editado por rokutanda: 21 October 2006 - 09:02 AM

[dee]

El cobol sin alineación en columnas no tiene gracia

[kujaku]

Roku, de todo el programa que has escrito te sobra el 90%. Vimora tiene razon, casi todos los tags que has puesto son opcionales. Por ejemplo, los inputs y los otputs no te hacen falta, ni los environments ni leches xDDDDD

Dee, no se por que, pero en este foro creo que poner los espacios los condensa en uno solo y se descuadra todo (mientras no ponga algo como [pongo espacios][soy gilipollas][porque no se escribir...]) xDDDD

[rokutanda]

Seh, opcionales pero te hacen ponerlos por standares de su puta madre, asi que pal caso...

y si, cuando puse el codigo estaba todo chulo pero el foro este se jama los espacios xD

[Hideyoshi]

pa eso teneis el code

me cawen to
	eres una puta
			tu madre es una zorra
					   alonsito es gilipollas
								  ¿sueñan los kujakus con mainframes?

Este tema ha sido editado por Hideyoshi: 23 October 2006 - 04:19 PM

[rokutanda]

Un haiku cojonudo tio xD

[Maeghith]

Un haiku cojonudo tio xD

más que un haiku... un haikujaku ;)

[dee]

Humor ácido.

A few years back, David Shideler worked at a company that built car dealership systems and was a bit reluctant to jump on the new technology bandwagon. In fact, to say that this company moved slowly is not just an understatement, it's an affront to the word "slow". 1200 baud: that's slow. Mail-in-rebates: really slow. Glacier movement: really, really slow. This company: about as fast as fossilization.

The company built the first version of their product in 1973 using COBOL and a specially-manufactured IBM System/3. It was an overnight success: hundreds of dealerships across the country bought their product and tens of millions of dollars in sales poured into the company. They discovered a formula that worked and didn't want to change it.

Despite numerous technological advancements over the following decade, they stayed the course and continued to improve and optimize their product for the System/3 platform. It got the point where buying an antiquated System/3 was significantly more expensive than buying a brand-new, much-faster computer. But that didn't matter; their system worked and there was no need to change it.

And then it happened: IBM announced that the System/3 would be discontinued. The company was outraged and begged and pleaded for IBM to continue supporting it. Being that they were one of the last System/3 customers, IBM offered to send a team of consultants to help them transition and compile their code on the new x86 platform.

The company refused. Instead, they hired a small team of computer-science whizzes to develop a low-level emulator that would allow them to run System/3 binaries on the x86. After all, their application ran perfectly on the System/3 and there was no need to change it.

The emulation worked fairly well for the next several years and they continued to develop their product in COBOL for the System/3 and run it on an x86. That is, until the manufacturer of their COBOL compiler went out of business.

Now, some might have seen that as a sign to switch to a new language and a new hardware platform. Not these guys. Their solution was, again, to hire a small team of computer-science whizzes to develop a COBOL "compiler" that would translate all of their System/3 COBOL code to C and then compile it as an x86 binary. Their application ran perfectly in COBOL and there was no need to change it.

Of course, one of the big problems with their COBOL-to-C translation program was that it produced completely unreadable C code that none of the COBOL programmers could understand, let alone debug. The computer-science whizzes were brought back in to create a COBOL development environment that allowed for the COBOL developers to step-through and debug their code. Amazingly, it worked and they were able to continue developing in System/3 COBOL for the next decade or so.

Fast forward to 2001 and the company is in need of yet another team of computer-science whizzes. And this is where David comes into the story. You see, the company wanted to extend their reach into Europe, but the European market was all into this fancy new technology called "Windows." Since the terminal emulator on top of Windows just wouldn't cut it, they brought in David and several others to help them embrace the "new" Windows technology.

Obviously, their advice to switch to C/C++ or an actual Windows development environment fell on deaf ears. David and the rest of his team needed to figure out a way to bring their System/3-COBOL-translated-into-C application into the world of Windows.

One of David's first challenges was COBOL's event model, or, more accurately, its lack of one. In standard Windows programming, when the user clicks on a button or does just about anything else, Windows raises an event to tell the application what happened. In COBOL programming, the application periodically asks if the user did an action. They were able to work around this by creating an "action queue" that allowed COBOL to see what happened and respond accordingly.

The next challenge was in creating the Windows Forms themselves, or, more accurately, creating a form generator that would translate the terminal screens into Windows forms that don't look too "terminaly" but still maintained a terminal feel. They actually managed to do this, too.

Amazingly, once the "Windows conversion" project was over, their software actually worked in Windows. It looked terrible and ran incredibly slow, but it worked. The company was able to keep its entire floor of COBOL programmers working on the System/3-COBOL-translated-to-C-rendered-in-Windows application and things have remained the same ever since. After all, they found a formula that worked and there was no need to change it.

viene de the daily WTF

[phenrir]

juas, esto es verídico?

Si aplicásemos la misma filosofía que esta compañía, hoy en día estaríamos haciendo fuego con dos piedras xD

[kujaku]

Jo-der. Ni tanto, ni tan calvo. De todas formas, una cosa es ser cerrado de mente pero lo que es ser aldeano-aldeano, y otra ir evolucionando poco a poco segun la tecnologia. Una cosa es que tengan su COBOL para System/3 (que luego el System/3 evoluciono al System/34, de ahi al System/36 y de ahi a AS/400) y otra es que crean que tengan que cambiar toda la programación por cambiar de arquitectura. Ademas, no veo que tiene que ver que tengan que irse a x86 para programar, pueden seguir haciendolo en AS/400 o mainframe sin problemas. Para mas detalles, podeis consultar uno de mis articulos sobre la evolución y la compatibilidad hacia atras. Toooma SPAM xDDD

[thexsam]

Kujaku, ¿un articulo tuyo es asi como un tochopost pero a lo bestia?
Es que solo tengo 2 gigas de ram y me da miedo abrirlo por si se me cuelga el ordenata

[dee]

Lo que es cierto es que es un nombre de web "difícil de olvidar"

[Yentin]

más que un haiku... un haikujaku ;)

you must die

[kujaku]

Kujaku, ¿un articulo tuyo es asi como un tochopost pero a lo bestia?
Es que solo tengo 2 gigas de ram y me da miedo abrirlo por si se me cuelga el ordenata

Nada que no hayas digerido por aqui, es un tochopost pero los he escrito mas bestias por aqui, asi que no tienes nada que temer

Lo que es cierto es que es un nombre de web "difícil de olvidar"

Como olvidar el nombre del mainframe mas famoso del anime, que gestiona los contratos de las Diosas con los mortales, y que tiene una administradora de sistemas sexy-sexy?? Hereje! xDDDDDDDD

[Maeghith]

uno de mis articulos

Me suena, me suena...

¿copypasteas en sigt.net o hay un sistema automático para cojerte del feed los artículos en la categoría documentación de yggdrasil?

[kujaku]

Me suena, me suena...

¿copypasteas en sigt.net o hay un sistema automático para cojerte del feed los artículos en la categoría documentación de yggdrasil?

No, colaboro en sigt.net escribiendo esos tochos. Lo curioso es que a alguien le ha gustado esos articulos y los ha publicado en barrapunto y todo. Me estoy haciendo famoooso