News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Web Builder Zone:
What we don't need in object-oriented programming
October 04, 2010 @ 10:53:08

On the Web Builder Zone, Giorgio Sironi has a few suggestions about things that aren't really needed in object-oriented development but seem to have found their way in none the less (most of them are in PHP too).

It is in general true that you should strive for writing code as simple as possible (in length but in complexity too) to obtain an end result specified by a requirement or a user story. If there are two designs for a feature, almost always we would choose the simplest. This article takes a broader view on object-oriented programming, and ask the following question: What are the constructs we don't need in an object-oriented language? What we can take away without hampering our capabilities of building software?

He has a whole list of things that he thinks could be removed - "extra features" that wouldn't cause heartache if dropped including:

  • instanceof
  • break/continue
  • protected subclassing scope
  • if (conditional)
  • switch (conditional chain)
  • public (for fields)
0 comments voice your opinion now!
oop opinion remove feature functionality


blog comments powered by Disqus

Similar Posts

Community News: PHP Sadness - "Things in PHP that Make Me Sad"

Derick Rethans' Blog: PHP Look Back 2006

Mike Purcell's Blog: Symfony - PHP - Possibly Forking 1.x so Invested Companies donít Lose Millions

PlentyofCode.com: J2EE vs ASP.NET vs PHP

Marco Tabini: Duck blinds


Community Events

Don't see your event here?
Let us know!


unittest api voicesoftheelephpant interview podcast extension library install xdebug introduction laravel framework php7 example language version series opinion release community

All content copyright, 2015 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework