Results 1 to 9 of 9
Thread: singleton object ...
- 06-19-2008, 01:20 PM #1
Member
- Join Date
- Jun 2008
- Posts
- 11
- Rep Power
- 0
- 06-19-2008, 01:25 PM #2
- Join Date
- Jul 2007
- Location
- Colombo, Sri Lanka
- Posts
- 11,374
- Blog Entries
- 1
- Rep Power
- 18
It's all about a design pattern. I think it's better to find a article and read. Just Google it, you have a large number of such.
- 06-19-2008, 01:56 PM #3
- 06-22-2008, 04:10 AM #4
Once you've read what it is, please search google for all the reasons you should not use it.
Such as "Singleton Considered Stupid "
And check into the JUnit groups and see how using Singletons makes proper unit testing much harder.
In general, a Singleton is just a wad of global stuff. Good OO design avoids global stuff, as it increases coupling.
- 06-23-2008, 05:02 AM #5
- Join Date
- Jul 2007
- Location
- Colombo, Sri Lanka
- Posts
- 11,374
- Blog Entries
- 1
- Rep Power
- 18
- 06-23-2008, 05:14 AM #6
Yes, good OO should be about abstractions and isolation. Coupling has been proven to make systems exponentially complex.
Sadly, a lot of Java, even professionally developed Java is not very good OO.
This bad Java will be the Year 2000 Cobol problem of the future, probably in five years or so.
- 06-23-2008, 06:29 AM #7
- Join Date
- Jul 2007
- Location
- Colombo, Sri Lanka
- Posts
- 11,374
- Blog Entries
- 1
- Rep Power
- 18
Lots of people working on Java(other languages too) without knowing any about OO. Some people don't want to use it either. I don't know why, but in later they found full wired with further maintainability and expandability of the application.
- 06-23-2008, 06:40 AM #8
I think part of it is that Java was cursed with a C-foundation, which greatly helped acceptance at first, but enables bad practices.
I did some professional Smalltalk, and while it wasn't long term useful (Smalltalk is dead) it forced you to think about OO seriously.
For a lot of applications, especially in the business domain, OO hasn't worked well. It works great for GUIs and other user interfaces, but gets hard to do with a payroll record.
Our continued use of Relational DBMS doesn't help.
This is probably moving a bit OT, probably should go into a less specific thread.
I'm not quite following this, perhaps its an idiom? or maybe typo? What is "fully wired" in this context? Thanks Pat
- 06-23-2008, 06:43 AM #9
- Join Date
- Jul 2007
- Location
- Colombo, Sri Lanka
- Posts
- 11,374
- Blog Entries
- 1
- Rep Power
- 18
Yes, seems now this is going out of the scope of this thread. Lets try is on different place...
Similar Threads
-
Whether to make Bean Singleton or non Singleton (prototype)
By Java Tip in forum Java TipReplies: 0Last Post: 03-29-2008, 12:41 PM -
Singleton Pattern
By Java Tip in forum Java TipReplies: 0Last Post: 01-24-2008, 03:21 PM -
Whether to make Bean Singleton or non Singleton (prototype)
By JavaBean in forum Java TipReplies: 0Last Post: 09-26-2007, 08:32 PM -
Google Singleton Detector 0.7.2
By levent in forum Java SoftwareReplies: 0Last Post: 07-26-2007, 08:12 PM -
singleton pattern
By Peter in forum Advanced JavaReplies: 1Last Post: 07-09-2007, 04:45 AM


LinkBack URL
About LinkBacks
Reply With Quote

Bookmarks