* CodeGeek!~codegeek@about/java/CodeGeek changed the topic to: Welcome! || Read Channel Rules at https://javachannel.org/ before participating. || Paste limit is two lines; ~pastebin lists options. || No applets, please. || Minecraft, Android, and Javascript all have their own channel. || You are being logged.
* kathadris joined #java
* fgarcia joined #java
* mindCrime joined #java
* mwnaylor joined #java
* xv8 joined #java
* vobar joined #java
* CodeGeek!~codegeek@about/java/CodeGeek changed the topic to: Welcome! || Read Channel Rules at https://javachannel.org/ before participating. || Paste limit is two lines; ~pastebin lists options. || No applets, please. || Minecraft, Android, and Javascript all have their own channel. || You are being logged.
NeXeNi think i've read some of the sources in the biblio
NeXeNdefinitely knr
* mwnaylor joined #java
jreicherElevator pitch might be something like abstract data types and objects are not the same thing, even though both can be used for data abstraction (which is defined as hiding the representation of the data). And if I understand the paper correctly, the main aim of it is to clarify exactly why the object-style is. Author seems to think that's the more misunderstood of the two.
jreicherI'm still getting a feel for the points in the paper, but it seems to me it explains why pattern matching and destructing came late to "OO" languages, and why data-oriented programming in an OO language "feels new"
jreicher^destructing^destructuring
* stfstfm joined #java
dreamrealI mean... on the first page he says ADTs and objects are not the same thing. And they're not. Okay?
* canton7 joined #java
* yaboishady joined #java
dreamrealThat essay isn't irrelevant but it feels a lot more like something people would care about in formal drawing rooms than in actual programming... and the way he presents it feels VERY 2009.
dreamreal"I have a secret... visibility is an attribute that ADTs have that objects don't necessarily present! Now discuss, noobs."
* kcomhnall joined #java
* MikeBux joined #java
* polyrob joined #java
* CodeGeek!~codegeek@about/java/CodeGeek changed the topic to: Welcome! || Read Channel Rules at https://javachannel.org/ before participating. || Paste limit is two lines; ~pastebin lists options. || No applets, please. || Minecraft, Android, and Javascript all have their own channel. || You are being logged.
* nevet joined #java
* geli joined #java
* GreenResponse joined #java
* CodeGeek!~codegeek@about/java/CodeGeek changed the topic to: Welcome! || Read Channel Rules at https://javachannel.org/ before participating. || Paste limit is two lines; ~pastebin lists options. || No applets, please. || Minecraft, Android, and Javascript all have their own channel. || You are being logged.
* nevet joined #java
* nevet joined #java
* CodeGeek!~codegeek@about/java/CodeGeek changed the topic to: Welcome! || Read Channel Rules at https://javachannel.org/ before participating. || Paste limit is two lines; ~pastebin lists options. || No applets, please. || Minecraft, Android, and Javascript all have their own channel. || You are being logged.
* magla joined #java
* MonsterAbyss joined #java
* ChaiTRex joined #java
* MonsterAbyss joined #java
* geli joined #java
* metalmaniac joined #java
* gas51627 joined #java
jreicherdreamreal: have you seen the difference between ADTs and objects discussed elsewhere? Because I haven't, and by his account (which is not necessarily correct) it's very easy to "confuse" the two in Java (which is one of the reasons I mentioned the paper here).
* Fiji joined #java
* Fiji joined #java
* emaczen joined #java
* ChaiTRex joined #java
* Fiji joined #java
dreamrealjreicher: I don't know that I've encountered it as a problem, but then again, I find most such discussions to be rather ivory-tower-driven. And I've used scala; this sort tneds to lead to discussions like "OMG your hierarchy is bounded in the wrong way in this one instance, OMG I hate you and wish you would literally die in a fire"
cheeserjust use a monad
dreamrealit's scala, so it's implicit
dreamrealdumbie
ParaAcademic Ivory is least favorite type of ivory.
Para+my
* kcomhnall joined #java
* kbmonk joined #java
* zoraj joined #java
* amosbird- joined #java
* Maxdamantus joined #java
* jetchisel joined #java
* zoraj joined #java
* sponkz joined #java
* sponkz joined #java
jreicherdreamreal: I agree that it's ivory-tower-driven, but when it's done well - and I think this paper is an example of that - it takes problems found in practice and explains why they happen, sometimes (but much less often) offering solutions. In the case of this paper I think it explains some of the pros and cons between protected vs (package) private.
jreicherAlso the differences between (IIRC) object-based encapsulation vs class-based.