I don't understand something: if the null pointer was a billion dollar mistake, and has caused pain and system crashes for decades, then why weren't there any attempts to just not implement it in an object-oriented system?
#programming #oop #nullsafety #nullpointer #null #billiondollarmistake #algol #java #c #question
Mixing #functionalprogramming and object oriented techniques in JavaScript is bad. I can easily see how someone exposed to this would think that #oop was inferior or frustrating. Someone only used to OOP is likely to feel the reverse.
Gemini 2.0 is very smart, though not as smart as 2.5 pro. The problem is not 2.0 herself, but the fact that she has to handle a huge amount of queries. She will not spend too much resources on a particular user. You have to push her to her limit to get the "correct" response.
Whatever you can achieve with "#Interface", you can do it with OOP. if you have a perfect understand of #OOP, there is really no need for interface. In any case, here are 2 examples of using "this" in both cases. #C#
@amoroso #clos #commonlisp #oop #lisp there was still a choice between various proposals then...
But the actual CLOS was not far away - the standard proposal was published in September 1988: https://dl.acm.org/toc/sigplan/1988/23/SI
Available above as a PDF. The final version was then published with the ANSI CL standard.
GRASP: почему настоящая архитектура начинается не с SOLID
Хочу начать с личной предыстории. Давным-давно, как и многие из вас, я читал умные книжки: «Чистый код» и «Чистая архитектура» Роберта Мартина, «Совершенный код» Стива Макконнелла и другие. Также не обошли меня и классические принципы проектирования — SOLID , KISS , DRY — и, думаю, каждый читатель добавит сюда свои. Безусловно, это всё важные и фундаментальные вещи. Но однажды на горизонте появилось DDD — предметно-ориентированное проектирование в изложении Эрика Эванса. Именно его «синяя книга» стала культовой и задала язык для архитектурного мышления. Позже я открыл и «красную книгу» Вона Вернона, где DDD уже рассматривался с точки зрения практической имплементации: архитектура, код, реальные подходы в проектах. Читая Эванса, рассматривая его диаграммы классов и примеры кода, я всё думал: как он это делает? Самым большим открытием для меня стало то, что книга DDD хоть и показывает стратегические и тактические приёмы — агрегаты, объекты-значения, спецификации, фабрики и т.д. — но не учит проектировать саму предметную область . Складывалось ощущение, что мы это уже откуда-то должны были знать . А откуда — остаётся загадкой.
As installments of the ARTIFICIAL INTELLIGENCE column by Ernest Tello, in 1987 Dr. Dobb's Journal published a series of articles on OOP and object-oriented extensions for Common Lisp and Scheme. Back then CLOS was not yet on the radar but the Common Lisp extensions the articles covered already contained the main ideas of CLOS.
https://archive.org/details/1987-03-dr-dobbs-journal/page/126/mode/2up?view=theater
https://archive.org/details/1987-04-dr-dobbs-journal/page/146/mode/2up?view=theater
https://archive.org/details/1987-05-dr-dobbs-journal/page/132/mode/2up?view=theater
No, non ho abbandonato il progetto. GIAMMAI!
Anzi... Sono sempre più determinato a volerlo portare a termine.
Il Mondo ne ha bisogno! 
Scherzi a parte...
La mia #OCD nel voler fare le cose perfette, mi ha costretto a sperimentare molte strade differenti.
L'ultima che ho imboccato, mi ha portato dritto dall'architettura #ECS: https://en.wikipedia.org/wiki/Entity_component_system
L'ho studiata e ho riscritto tutto seguendone i sacri dettami, permettendomi qualche piccola modifica affine ai miei gusti (#OOP).
Functional vs object-oriented vs procedural programming?
The Open-Closed Principle - Part 2 - The Contemporary Version - An Introduction - oldie but goodie - uploaded to fpilluminated - fpilluminated.org/deck/259 #OOP #open_closed_principle #dependency_inversion_principle #liskov_substitution_principle #implementation_inheritance #interface_inheritance
The Open-Closed Principle - Part 1 - The Original Version - oldie but goodie - uploaded to fpilluminated https://fpilluminated.org/deck/258 #OOP #OCP
SOLID Principle = Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion.
A compact reference for developers with examples in C#
See how to iterate a composite dataset without exposing its internal logic. Its a combination of the composite and Iterator design patterns while implementing an office furniture system. It uses workstation as a composition of office chair, desk and cabinet.
Read More...
https://muwangaxyz.medium.com/composite-and-iterator-design-pattern-combination-in-typescript-9840aab74dd5
The problem with object-oriented languages is they've got all this implicit environment that they carry around with them. You wanted a banana but what you got was a gorilla holding the banana and the entire jungle.
— Joe Armstrong, Jason Gorman
one of my favorite quotes about #OOP is that a class hierarchy isn't made to unleash your inner Linnaeus ;) - but this most certainly is: https://jillianhess.substack.com/p/carl-linnaeuss-note-taking-innovations - cute lil video about Linnaeus' note taking system. (As a german political scientist I'm course Luhmann's Zettelkasten inspired 
) Cool bits of information design however - If you love Tufte's book, you'll love this :))
I have this whole object-model in my head which is basically a compromise between class-based #oop, and prototyped with differential inheritance.
You would just need to differentiate between an objects namespace and its layout, decoupling state and strutucture. 'Layout' only being created when the object is used as a prototype, and the resolution chain would go local ns->local layout if any->proto layout. Changes to the layout would have to be done explicitly to get propagated down.
The principle of data hiding in #OOP is an evil principle, for it seeks to instill a product/consumer dichotomy in the programmer's mind, and this is inherently hierarchical and #oopressive.
New Blog Post!
Fizz Buzz has just enough complexity to demonstrate a principle that is usually tough to understand through toy examples: the open/closed principle.
https://kerrick.blog/tutorials/2025/fizz-buzz-object-oriented-edition/
I've been using #AI to critique my #blog posts before I publish them. Among other techniques, I have it stereotype commenters on various tech sites. Tonight's example was pretty funny. #RewriteItInRust
Take the red pill of #OOP! Learn programming concepts in #TheMatrix. Less dodging bullets, more #coding. Inheritance, polymorphism, fun!
#OOP #ObjectOrientedProgramming #Abstraction #AgentSmith #C++ #characteranalysis #Classes #Encapsulation #Inheritance #Java #Morpheus #Neo #Objects #OOPConcepts #Polymorphism #TheMatrix #Oracle #Trinity #GiggleByte #SwapneelMohite #programming #coding
https://medium.com/@swap.mohite/the-matrix-an-object-oriented-lesson-i-taught-revisited-9532a0712bc9
Principle of Mutual Oblivion (PoMO): https://ralfwestphal.substack.com/p/principle-of-mutual-oblivion-pomo
Radical Object-Orientation looks a lot like functional programming.
️ 
