#oop — Public Fediverse posts

Learn how to write dynamic programs for #Web pages! Take CS22A "JavaScript for Programmers" online for those who have already learned programming in some other object oriented language (like Python, Java, or C++).
#JavaScript #ECMA262 #WebDev #OOP
https://foothill.edu/cs/schedule.html

Guarded Methods in OCaml

https://xvw.lol/en/articles/oop-refl.html

Comments: https://news.ycombinator.com/item?id=49157770

#HackerNews #OCaml #GuardedMethods #OOP #ProgrammingLanguages #FunctionalProgramming

Guarded Methods in OCaml

https://xvw.lol/en/articles/oop-refl.html

Comments: https://news.ycombinator.com/item?id=49157770

#HackerNews #OCaml #GuardedMethods #OOP #ProgrammingLanguages #FunctionalProgramming

The basics of Java you need to know: Encapsulation, Polymorphism, Abstract classes, Generics, Exceptions, etc.

Although AI already programmes very well, even better than many developers, it is important not to forget these concepts.

https://www.byandrev.dev/posts/the-basics-of-java-you-need-to-know

#java #ai #vibecoding #oop

The basics of Java you need to know: Encapsulation, Polymorphism, Abstract classes, Generics, Exceptions, etc.

Although AI already programmes very well, even better than many developers, it is important not to forget these concepts.

https://www.byandrev.dev/posts/the-basics-of-java-you-need-to-know

#java #ai #vibecoding #oop

"The Debate of Mockist v Classicist TDD Is Like OOP v FP."

"The testing debate is actually a paradigm debate people don’t realize they’re having"
https://fagnerbrack.com/the-debate-of-mockist-classicist-tdd-is-like-oop-fp-c9124185f3d2 #tdd #mocking #oop #Testing #fp

"The Debate of Mockist v Classicist TDD Is Like OOP v FP."

"The testing debate is actually a paradigm debate people don’t realize they’re having"
https://fagnerbrack.com/the-debate-of-mockist-classicist-tdd-is-like-oop-fp-c9124185f3d2 #tdd #mocking #oop #Testing #fp

Figure that fedi would be good to answer this.

I'm working on a music library manager (and eventual player) in C# and while I can program, designing how objects should be structured has been more difficult than I'd like, and while an LLM can help I find that I learn in reverse or basically don't understand it at all (obviously). Such things include custom tags, and how to map fields to track tags. (This has been an issue pre-LLM, given I was very "linear"? with code I published in the past)

I guess the question I'm asking is, how do I (learn how to) make a properly good and informed design decisions with these? I know of the KISS principle, but that's only part of it lol. Any good resources will help.

This isn't specifically a .NET thing, more so OOP generally. I know the basics, and I properly learned some of how .NET works (such as events). It's more like, "when do I need a service?" or "how can I encapsulate different types (and when)". A lot of when to do xyz thing.

#programming #oop #dotnet #csharp

Figure that fedi would be good to answer this.

I'm working on a music library manager (and eventual player) in C# and while I can program, designing how objects should be structured has been more difficult than I'd like, and while an LLM can help I find that I learn in reverse or basically don't understand it at all (obviously). Such things include custom tags, and how to map fields to track tags. (This has been an issue pre-LLM, given I was very "linear"? with code I published in the past)

I guess the question I'm asking is, how do I (learn how to) make a properly good and informed design decisions with these? I know of the KISS principle, but that's only part of it lol. Any good resources will help.

This isn't specifically a .NET thing, more so OOP generally. I know the basics, and I properly learned some of how .NET works (such as events). It's more like, "when do I need a service?" or "how can I encapsulate different types (and when)". A lot of when to do xyz thing.

#programming #oop #dotnet #csharp

Cooperative Vectors Introduction https://www.evolvebenchmark.com/blog-posts/cooperative-vectors-introduction

#indiedev #oop #gamedev #gamedevelopment

I am looking for archives of early #pattern/ #OOP mailinglists, like the University of Illinois ones linked on https://hillside.net/patterns/mailing-lists
Aside of general interest in the history of #agile methods, I would also be curious about discussions about @k9ox ’s C2 wiki.

I am looking for archives of early #pattern/ #OOP mailinglists, like the University of Illinois ones linked on https://hillside.net/patterns/mailing-lists
Aside of general interest in the history of #agile methods, I would also be curious about discussions about @k9ox ’s C2 wiki.

From the archives:

Object-Oriented HTML, and OOCSS:

https://meiert.com/blog/object-oriented-html-and-oocss/

#html #css #oocss #oop

From the archives:

Object-Oriented HTML, and OOCSS:

https://meiert.com/blog/object-oriented-html-and-oocss/

#html #css #oocss #oop

After more work on GravityLoops, my gravity simulator in Interlisp and LOOPS, I have something to show for.

https://journal.paoloamoroso.com/paoloamoroso/early-simulations-with-gravityloops

#interlisp #oop #lisp

After more work on GravityLoops, my gravity simulator in Interlisp and LOOPS, I have something to show for.

https://journal.paoloamoroso.com/paoloamoroso/early-simulations-with-gravityloops

#interlisp #oop #lisp

A snapshot of my work on GravityLoops, a gravity similator in Interlisp and LOOPS. I'm debugging an issue with the newly written simulation output code.

#interlisp #lisp #oop

A snapshot of my work on GravityLoops, a gravity similator in Interlisp and LOOPS. I'm debugging an issue with the newly written simulation output code.

#interlisp #lisp #oop

Last Call: Der CFP endet heute.‼️

Ich verantworte bei der nächsten #oop wieder einen Track. Diesmal zum Thema digitale Souveränität.

Ich freue mich auf zahlreiche Einreichungen:

https://www.oop-konferenz.de/de/oop-2027-in-muenchen/vortrag-einreichen

#digitaleSouveränität #digitalsovereignty #opensource

Last Call: Der CFP endet heute.‼️

Ich verantworte bei der nächsten #oop wieder einen Track. Diesmal zum Thema digitale Souveränität.

Ich freue mich auf zahlreiche Einreichungen:

https://www.oop-konferenz.de/de/oop-2027-in-muenchen/vortrag-einreichen

#digitaleSouveränität #digitalsovereignty #opensource

In LOOPS, classes, class variables, and instance variables can have property lists of name/value pairs along with a value. It's useful for documentation, units, or other metadata. For example, this is the declaration of an instance variable "mass":

(mass 2.0 unit 'kg doc "Mass of a body")

unit, doc are property names followed by values.

LOOPS (Lisp Object-Oriented Programming System) is the object extension of Interlisp.

#interlisp #oop #lisp

In LOOPS, classes, class variables, and instance variables can have property lists of name/value pairs along with a value. It's useful for documentation, units, or other metadata. For example, this is the declaration of an instance variable "mass":

(mass 2.0 unit 'kg doc "Mass of a body")

unit, doc are property names followed by values.

LOOPS (Lisp Object-Oriented Programming System) is the object extension of Interlisp.

#interlisp #oop #lisp

The difference in Python OOP between:
- instance method
- class method
- static method
visually explained using 𝗺𝗲𝗺𝗼𝗿𝘆_𝗴𝗿𝗮𝗽𝗵: https://memory-graph.com/#codeurl=https://raw.githubusercontent.com/bterwijn/memory_graph/refs/heads/main/src/different_methods.py&play
#Python #memory_graph #oop

A wonderful conversation to have with proponents of #OOP is whether or not the compiler of their programming language and the CPU that carries out their instructions care about the immutability (finality) of their memory placeholders. Oh, you can't change to which memory location your variable points because you declared it as constant or final? Guess what? The CPU doesn't care. And that's why memory leaks happen.

A wonderful conversation to have with proponents of #OOP is whether or not the compiler of their programming language and the CPU that carries out their instructions care about the immutability (finality) of their memory placeholders. Oh, you can't change to which memory location your variable points because you declared it as constant or final? Guess what? The CPU doesn't care. And that's why memory leaks happen.

There's nothing to see yet in my GravityLoops simulator in Interlisp and LOOPS, but for good reason. I worked on the foundations that will make the program actually show something on the screen.

https://journal.paoloamoroso.com/preparing-gravityloops-for-simulation

#interlisp #lisp #oop

There's nothing to see yet in my GravityLoops simulator in Interlisp and LOOPS, but for good reason. I worked on the foundations that will make the program actually show something on the screen.

https://journal.paoloamoroso.com/preparing-gravityloops-for-simulation

#interlisp #lisp #oop

Ich verantworte bei der nächsten #oop wieder einen Track. Diesmal zum Thema Digitale Soveränität.

Ich freue mich auf zahlreiche Einreichungen:

https://www.oop-konferenz.de/de/oop-2027-in-muenchen/vortrag-einreichen

#digitaleSoveränität #digitalsovereignty #opensource

Ich verantworte bei der nächsten #oop wieder einen Track. Diesmal zum Thema Digitale Soveränität.

Ich freue mich auf zahlreiche Einreichungen:

https://www.oop-konferenz.de/de/oop-2027-in-muenchen/vortrag-einreichen

#digitaleSoveränität #digitalsovereignty #opensource

Exam Object-Oriented Programming #OOP graded! Lowest grade: 1.0; Highest grade: 9.8 (which will be a 10.0 on the grade list!) 66% passed the exam. Also, we graded this within less than 24 hours after the students did the exam!

Exam Object-Oriented Programming #OOP graded! Lowest grade: 1.0; Highest grade: 9.8 (which will be a 10.0 on the grade list!) 66% passed the exam. Also, we graded this within less than 24 hours after the students did the exam!

Don't mind me, I'm just using the Medley environment to work on my gravity simulator in Interlisp and LOOPS. It's 1986(+40) and this new OOP thing is a lot of fun.

https://journal.paoloamoroso.com/gravityloops-a-gravity-simulator-in-interlisp-and-loops

#interlisp #oop #lisp

Don't mind me, I'm just using the Medley environment to work on my gravity simulator in Interlisp and LOOPS. It's 1986(+40) and this new OOP thing is a lot of fun.

https://journal.paoloamoroso.com/gravityloops-a-gravity-simulator-in-interlisp-and-loops

#interlisp #oop #lisp

The December, 1983 edition of the LOOPS manual listed the intellectual precursors of the Lisp Object-Oriented Programming System, the object extension of Interlisp:

- Smalltalk
- Flavors
- PIE
- KRL
- UNITS
- EMYCIN

#oop #interlisp #lisp #retrocomputing

The December, 1983 edition of the LOOPS manual listed the intellectual precursors of the Lisp Object-Oriented Programming System, the object extension of Interlisp:

- Smalltalk
- Flavors
- PIE
- KRL
- UNITS
- EMYCIN

#oop #interlisp #lisp #retrocomputing

I wrote a short note on defining a core class of GravityLoops, my gravity simulator in Interlisp and LOOPS.

https://journal.paoloamoroso.com/representing-the-universe-of-gravityloops

#interlisp #lisp #oop

I wrote a short note on defining a core class of GravityLoops, my gravity simulator in Interlisp and LOOPS.

https://journal.paoloamoroso.com/representing-the-universe-of-gravityloops

#interlisp #lisp #oop

#HiveMind: Is the opposite of an "abstract class" a "concrete class"?

When building code for a class, #CTRAN needs to be able to find the next ancestor that isn't abstract. I'm trying to think of a good name for the function, e.g. GetConcreteAncestor() or GetNonAbstractAncestor().

#OO #OOP #AskFedi

#HiveMind: Is the opposite of an "abstract class" a "concrete class"?

When building code for a class, #CTRAN needs to be able to find the next ancestor that isn't abstract. I'm trying to think of a good name for the function, e.g. GetConcreteAncestor() or GetNonAbstractAncestor().

#OO #OOP #AskFedi

Paolo Amoroso @amoroso is writing a gravity simulator using LOOPS (Lisp-Object Oriented Programming System), the object extension of Interlisp.

https://journal.paoloamoroso.com/gravityloops-a-gravity-simulator-in-interlisp-and-loops

#interlisp #lisp #oop

Object-oriented programming like it's 1986: I'm doing a fun project with LOOPS, the object extension of Interlisp.

https://journal.paoloamoroso.com/paoloamoroso/gravityloops-a-gravity-simulator-in-interlisp-and-loops

#interlisp #oop #lisp