Java vs OOP (JavaDay Kyiv)

#lecture #programming #software #oop

[Martgician]

That guy who knocked over your camera is a procedural programmer..

[cs_student]

So from what recourses can we learn the idea behind OOP and it's principles

[LewisCowles]

I Love the passion. I Have a feeling you'd be mad at my code because I believe the problem with maintainability is actually that too many people are doing it wrong by keeping code alive for decades. If you can remove or reduce the time to develop code, and develop clever ways to test (like UI automation), then you can throw it in the bin in 3 years time because you have ways to check requirements and compatibility. The main problem for this is of course data and integration capability of connective technologies.

[jorgeolive]

It's simply easier for the average developer to get on pace on huge procedural codebases. At the end of the day the projects get delivered and start generating revenue without getting super orthodox on what pure OOP should be. New developers can start putting stuff out simply by understanding a few simple procedural patterns; No need to deal with the cognitive load of hundreds - if not thousands - of tiny objects to be organized in some IDE side explorer view. That, and that is also much cheaper for the hiring companies, as - IMO - the knowledge and the experience necessary to create good OOP code is an order of magnitude bigger than procedural's

[vamshikanisetty]

I initially made couple of mistakes discussing about the cons of OOP with others. I later realized that it is detrimental to the progress of my career. The world does not seem to tolerate any criticism of OOP techniques - the worst comment I got in a public forum when I asked a question (which can also be taken as a criticism of OOPs) was ' Oh! So you think all the people who are using OOP techniques are fools?'. Anyway, I like constructive criticism as the world seem to move away from Programming and Programmers; if you need any evidence look at the 'packaged solutions' like Sales Force or Pega Systems. Some of their training sessions make a scathing attack on the low productivity and complexity of programmers and their 'outdated' overly complicated architectures. One of my friend who implements Pega Systems told me 'If you are writing code then you are doing it wrong!'.

[Molamini]

Paul, intuitively I believe what you are saying but do you have evidence? Do you have numbers between code your way versus other ways to validate what you are saying?

[razvanandrei]

In general, I agree that JAVA beside OOP dev. style became a collection of workarounds dictated by real world needs and JAVA is not pure OOP, but should it be pure OOP only? Is it feasible to have pure OOP languages? I think the pragmatism should win not pure theoretical concepts, btw why do you think OOP is the nirvana of the programmers and the holy grail, why not functional programming or other paradigm? One more aspect that I didn't like it about the presentation is that it was presented to passional and with a bit too much hate about various tools, frameworks, if I had to resume it, "everything in the JAVA world is a mess and a mistake" - who says, are you any authority, can you show us some alternatives that from your POV is the way to go?