The thin client... The future of computing?

[morse86]

You've taken an extreme example in an attempt to prove your point, and I suspect you know that if writing say, an n-tier system with multiple interfaces that writing only procedural code would be nigh on impossible not to mention horrible to maintain and debug. In reality there's nothing to stop a programmer from writing those two lines of code of yours as opposed to the more verbose 7 lines. A good programmer isn't a slave to their methodology, but they know when to be pragmatic and employ different techniques when time or other priorities allow.

What?!?!? All of the programming problems was fixed in the 70s. OOP solves nothing, it just adds to the complexity.

You can take linux core as an example. Almost all of the CLI tools are written in pure C.

Those that don't know the history, repeat the same errors.

Example:

A young woman was preparing a ham by cutting of the protruding ham bone before putting it in the oven. Her friend asked her, “Why did you cut off the bone"?

And she replied, “I really don't know but my mother always did, so I thought you were supposed to."

Later when talking to her mother she asked her why she cut off the bone before baking it, and her mother replied, "I really don't know, but that's the way my mom always did it."

A few weeks later while visiting her grandmother, the young woman asked, "Grandma, why is it that you cut off the ham bone before you bake it?"

Her grandmother replied, "When I was first married, we lived in a small apartment with a tiny stove. The oven was so small you had to cut off the ham bone to get it to fit and cook it a long time."

 

[morse86]

The key thing to remember is that programming is not a one size fits all. I've seen some cases where OOP is helpful in it's full implementation, others where is my is helpful to use in moderation. Other programs, I can understand reasoning for not using OOP. That said, reusability is a must in my opinion across the board.

One example where I definitely would use OOP would be JAVA with Spring and Hibernate. The annotation capabilities in a large application greatly enhance the efficiency, as well as coding for the database through the POJOs in JAVA. Using the interfaces is extremely helpful. That said, I am selective for the extent of OOP concepts that I use. Also, it is very helpful for test driven development.

I've also developed for years with both procedural and OOP. The most important thing to remember is that programming is not one size fits all. Flexibility in the tools and concepts you use is critical. Many factors determine what is most efficient for the particular application being developed.

TDD? POJO?? wow. These were house of cards patches developed for bad coding/design from the 90's/20's. You know, when programmers used COUNTS to verify existance OR they had a client-side million record pagination OR they used 1000GB webforms viewstate.

99% of today's application issues are related to the database. All of the front-end languages are fast enough, it is really pointless to add complexity like OOP.

 

[morse86]

Better readability, maintainability and reusability straight off the top of my head.

The front-end is for displaying data only. Why make it unnecessarily complex? No most applications do not need a buisiness logic/service layer. It belongs in the database. With federated databases, partioning, stored procedures, replication, terabytes of memory and SSDs, we can scale the DBMS both horizontally and vertically.

It's like the time when I had to maintain a 3-tier MVC + Web API app. All of the tables had nullable columns except the primary key!

 

[All4Christ]

It's like the time when I had to maintain a 3-tier MVC + Web API app. All of the tables had nullable columns except the primary key!

Your experience with the MVC app was with programmers that were negligent in that area. The MVC apps I have worked with do not have nulls allowed for every field except the primary key. Bad programming can be done across the board, including the database.. One of the apps I work with has a lot of bad coding going on, and all of it is done via the database. There isn't any application logic in any programming language other than PL/SQL. Many coders in our team write applications that have everything in a single procedure start to finish, including the HTML, application logic, and database work. The code is a mess. Bad coders easily can make something good be something bad.

 

[WalksWithChrist]

I got a tech call on one of our very last thin clients.

It was dead.

 

[lesliedellow]

Thin clients used to be called smart terminals, attached to a mainframe computer.

Should that be the future, we will have come full circle.

 

[dysert]

Thin clients used to be called smart terminals, attached to a mainframe computer.

Should that be the future, we will have come full circle.

I think we about have come full circle. Just that now the mainframe is called the cloud.

 

[WalksWithChrist]

I think we about have come full circle. Just that now the mainframe is called the cloud.

Or "someone else's computer".

 

[dysert]

Or "someone else's computer".

Maybe Ken Olsen was right after all these years...

 

[WalksWithChrist]

Maybe Ken Olsen was right after all these years...View attachment 161401

Looks that way.