Is Java the new COBOL?
If it's ubiquitous and running mission critical stuff like payroll systems, then perhaps.
>>54914339
It's COBOL all the way down.
>>54914041
Java will never be ran by government databases, no
>>54914041
COBOL is still used. Java will never replace it.
>>54914041
how can language that is so simple have so many books??
>>54916011
how can a game as simple as chess have so many different possible states?
>>54916020
Chess has exactly 2 states.
>>54916035
explains why computers are so damn good at it then
>>54916011
Java is not simple at all.
It encourages all kinds on needless complexity.
>>54915570
>>54915682
The company I work for is actually in the process of phasing out their COBOL (and have been for almost 20 years...), but like >>54914339 said, COBOL runs mission critical things that are basically impossible to replace because it means downtime.
I've been rewriting non-essential programs in Java for the last few years, and we're almost entirely off of COBOL now.
>>54914041
java is so dogshit
javapublic class Pet {
private PetName name;
private Person owner;
public Pet(PetName name, Person owner) {
this.name = name;
this.owner = owner;
}
public PetName getName() {
return name;
}
public void setName(PetName name) {
this.name = name;
}
public Person getOwner() {
return owner;
}
public void setOwner(Person owner) {
this.owner = owner;
}
}
scalaclass Pet(var name: PetName, var owner: Person)
both JVM
>>54917668
Every decent IDE can build setters and getters. Only a moron would type that out.
>>54917723
>>54917668
>Getters and Setters
>OOP
Cargo-cult programming at its worst.
>>54917756
GET ready Get SET. OOP!
I'm sorry.
>>54917668struct Pet {
PetName name;
Person owner;
}
OOP is a disgrace
>>54917668
What if I want to verify my input?
>>54918873
not as big a disgrace as you are to your parents though.
>>54920850
>this is pajeet
>hello
>>54920889
your parents are talking about how to get you out of the house right now.
>>54917756
You add getters and setters for all attributes just with POJOs. I always thought it was a better idea to just make attributes public because in 99.999% of the cases you are not going to add extra checks in getters + setters for them.
But then again, some ORM frameworks require you to do this.
Hell, when it comes to ORM I just generate POJOs from a given schema. No way in hell am I going to write 50 objects with 20 attributes for all tables in a SQL database.
>>54916035
For each arrangement of pieces on the board you have one state.
Some quick look at google told me there are 1.58e55 different possible states in chess.
>>54920772
I had one of these back when I pentium 166mhz pc. so fucking boss.
>>54920813
Have fun wrestling against the type system!
>>54920995
>implying java is the only way to get a job