Timeline for Is coupling a good thing or bad thing when I'm developing standalone modules in a framework?
Current License: CC BY-SA 3.0
28 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2016 at 10:20 | vote | accept | Josip Ivic | ||
| Oct 26, 2016 at 19:09 | answer | added | Bradley Thomas | timeline score: 2 | |
| Oct 26, 2016 at 19:08 | comment | added | candied_orange | @RobertHarvey good point, I've tried to deal with that a little better. | |
| Oct 26, 2016 at 18:03 | history | edited | Robert Harvey | CC BY-SA 3.0 |
deleted 637 characters in body; edited title
|
| Oct 26, 2016 at 18:02 | history | rollback | Robert Harvey |
Rollback to Revision 1
|
|
| Oct 26, 2016 at 18:02 | history | edited | Robert Harvey | CC BY-SA 3.0 |
deleted 1516 characters in body
|
| Oct 26, 2016 at 17:55 | history | edited | Robert Harvey | CC BY-SA 3.0 |
edited title
|
| Oct 26, 2016 at 17:55 | comment | added | Robert Harvey | Yes, the actual question is in the last paragraph: "what do you do to avoid coupling when there's a bunch of inheritance?" Incidentally, the de facto answer is probably some combination of "use composition instead," "inherit from interfaces instead," or "use composition with dependency injection." | |
| Oct 26, 2016 at 17:34 | comment | added | Caleb | This question would be much improved if you deleted everything but the last paragraph. I'm sure the first 85% deals with some sort of concerns that you have, but it has little to do with the question you're asking and it just muddies the water. | |
| Oct 26, 2016 at 17:10 | comment | added | gnat | @RobertHarvey you got to read it differently than I then, what I see here is far beyond just coupling, there's inheritance and encapsulation. To me that makes it about general OO principles | |
| Oct 26, 2016 at 17:08 | comment | added | Robert Harvey | @gnat: This question appears to be specifically about coupling, not general OO principles; we can't ask folks to wade through a mountain of information to find a nugget that you happen to know exists in some other post, unless that post happens to be the same question. | |
| Oct 26, 2016 at 17:05 | comment | added | gnat | @RobertHarvey if the one I referred isn't canonical (answer / meta) then I don't know what is | |
| Oct 26, 2016 at 17:01 | comment | added | Robert Harvey | @gnat: The general principle is "but only for canonical questions," and that Javascript question seems too specific to act as a canonical here (this question mentions Javascript, but only in passing). | |
| Oct 26, 2016 at 16:59 | comment | added | gnat | @RobertHarvey per my reading this answer at MSE you accepted a while ago suggests otherwise | |
| Oct 26, 2016 at 16:38 | comment | added | Robert Harvey | @gnat: Strictly speaking, answers don't make a post a duplicate target... Questions do. | |
| Oct 26, 2016 at 16:18 | answer | added | candied_orange | timeline score: 9 | |
| Oct 26, 2016 at 15:47 | comment | added | Erik Eidt | Encapsulation does not require inheritance or imply class hierarchy. Whereas inheritance involves class hierarchy, and implies encapsulation. | |
| Oct 26, 2016 at 15:39 | comment | added | Tulains Córdova | How is inheritance opposed to encapsulation in a way that you have to decide to go with one or the other? | |
| Oct 26, 2016 at 15:12 | review | Close votes | |||
| Nov 3, 2016 at 3:01 | |||||
| Oct 26, 2016 at 15:05 | comment | added | LindaJeanne | Maybe the conflict between "inheritance" and "encapsulation" that you are asking about is specific to Javascript? Because otherwise, I got nothin'. | |
| Oct 26, 2016 at 15:04 | comment | added | LindaJeanne | Also, the problem isn't with "coupling" generally, it's with "tight coupling". Obviously the parts of the program are all connected together somehow, it's just a matter of how easy any individual part is to change or maintain without breaking the rest. | |
| Oct 26, 2016 at 15:01 | comment | added | Josip Ivic | @LindaJeanne, don't know, that's why I asked, because there's a bunch of experts on this SE. :) | |
| Oct 26, 2016 at 15:00 | comment | added | Josip Ivic | @gnat, Cool. Because, I'm only seeing bennadel.com/blog/recent-blog-entries.htm this link that is talking about encapsulation. | |
| Oct 26, 2016 at 15:00 | comment | added | LindaJeanne | Maybe it's my relative unfamiliarity with Javasript, but I'm having a hard time seeing how encapsulation and inheritance would be mutually exclusive? (Also, curious as to if and why you eschew composition?) | |
| Oct 26, 2016 at 14:58 | comment | added | gnat | sure I did. Answer in duplicate target is a definitive guiding reference on how to address concerns like you expressed in your question | |
| Oct 26, 2016 at 14:55 | comment | added | Josip Ivic | did you actually read my question and read that question? | |
| Oct 26, 2016 at 14:55 | comment | added | gnat | Possible duplicate of Are there any OO-principles that are practically applicable for Javascript? | |
| Oct 26, 2016 at 14:53 | history | asked | Josip Ivic | CC BY-SA 3.0 |