Object Oriented Programming really an Advantage

I played a little with node.js
I don't know coding or OOP, but don't like the complexity I've seen with Node packaging and npm stuff. If OOP means or encourages packaging like that then nah :p
C is good, but Java doesn't need to be recompiled by the distributor, is even more portable, and will work between OSes easily, and our modern computers are powerful enough that the performance hit from the JVM doesn't matter as much as it used to.
That's why I like Java :D An old version of Runescape with JOGL built on Java 17-24 various Linux, Windows, and even FreeBSD with Java 8; no visible differences and full 3D OpenGL cross-OS!

Meanwhile a different RS version using Node/npm/Bun.js had various incompatibilities on FreeBSD because of modules used (still not sure what swc's deal was even after specifying a native FreeBSD version). Prior to the filesystem watcher switch, Node/npm modules worked from Wine on FreeBSD before native; I'm not sure on the module or why it was OS-specific, but the scenario's odd with it working sooner from a Windows compatibility layer than native with a distribution platform designed for cross-OS.
 
but don't like the complexity I've seen with Node packaging and npm stuff. I
My opinion, this is not a problem unique to Node.
Seems like lots of languages (perl, node, python) have their own packaging systems. We've had lots of discussions about pkgbase vs freebsd-update, but all these other package things outside of base?
 
My opinion, this is not a problem unique to Node.
Seems like lots of languages (perl, node, python) have their own packaging systems. We've had lots of discussions about pkgbase vs freebsd-update, but all these other package things outside of base?
I wonder if those languages do or encourage something to warrant their packaging systems; I'm not a fan of pip with Python either :p

Does Rust have a packaging system? I haven't done anything with a Rust program, but heard of crates that might be similar to Node and npm?
 
Library/package installation (pip for Python, crates for Rust ...) and package deployment systems (npm, docker ...) are orthogonal to the question of procedural, object-oriented, functional, ... coding style. Except that certain languages are correlated with these systems and coding styles.
 
I don't know coding or OOP, but don't like the complexity I've seen with Node packaging and npm stuff. If OOP means or encourages packaging like that then nah :p
For me, the only reason to look at node.js is that it contains a web server, programmable in javascript.

To learn some javascript was since long due, but I do not like it
 
For me, a "fun" part of OOP is DO-332 (a supplement to DO-178C).

I feel it gets hung up with stuff such as setWidth of a Square object potentially violating the fact that width and height should be equal but seems to overlook the fact that this problem exists in non OOP code too.

It has a "related technologies" section which also touches on dynamic memory which has little to do with OOP. I feel more focus on lifespan of data could be more useful, expecially since OOP encapsulation also implies nested lifetimes.
 
For me, a "fun" part of OOP is DO-332 (a supplement to DO-178C).

I feel it gets hung up with stuff such as setWidth of a Square object potentially violating the fact that width and height should be equal but seems to overlook the fact that this problem exists in non OOP code too.

It has a "related technologies" section which also touches on dynamic memory which has little to do with OOP. I feel more focus on lifespan of data could be more useful, expecially since OOP encapsulation also implies nested lifetimes.
Granted, I have not read the DO- standards but to be clear, I do NOT like style standards or ones that dictate "process". They hinder creativity. Verification of function is fine and expected but it goes to my disdain for folks who not only feel the need to tell me what they want me to do, but somehow feel they must also dictate "how I do it".

Been coding to MISRA/AUTOSAR standards since 2018ish and there are many useful/ beneficial rules for safety criticallity but those documents have also started to delve into "stylistic rules"...Grrr!

re - dynamic memory...I think the inference is that OOP heavily leverages dynamic memory as an implementation detail, but there are heavy rules aobut dynamic memory use in safety critical systems because your memory management becomes non-deterministic.
 
Verification of function is fine and expected but it goes to my disdain for folks who not only feel the need to tell me what they want me to do, but somehow feel they must also dictate "how I do it".
Y'know, that's kind of normal and expected. The project you're doing is not for your pleasure. You're merely renting your expertise out to get somebody else's project going. If you're setting up stuff for yourself, then yeah, you control the outcome. There are limits, of course - asking to run a Windows binary on a UNIX is pretty much technically impossible. An expert is supposed to think the whole project through, and negotiate beforehand where the limits are. Some things are easier to resolve and commit to beforehand.
 
astyle
Seven Red Lines...<
View: https://www.youtube.com/watch?v=BKorP55Aqvg
>
A great analogy as to why no sane person would ever advise their kid to get into computer technology as a career.
I do disagree with the assessment.

I'm looking at consequences of Zoomer-style education, this video is a great demo of the Dunning-Kruger effect.

Basic math is something that nobody in the room (except for the expert) has a grasp of. And the gap is so big that it's just impossible to bridge it without blood, sweat and tears from BOTH sides. If one side doesn't realize that, they're the uninformed losers.

Basic computer literacy is still needed to navigate the digital organizational morass and make sure that silly problems don't trip people up.

This is sometimes referred to as 'wolf, goat, cabbage' situation. A solution will be reached. No, not the most elegant one around.

But seriously, try getting one of those managers/designers to walk into an auditorium full of experts who actually know something about the topic, and select someone from that pool to attend the meeting. Simply because the pool of people who actually have the knowledge is kinda small. Then again, it takes a LOT to get into that kind of pool. Yeah, it will give some leverage over morons.

This video is actually not a bad conversation starter if you wanna motivate your kid to study hard and aim for the top. Because that's what gives you leverage over morons.
 
Basic computer literacy is still needed to navigate the digital organizational morass and make sure that silly problems don't trip people up.
...
But seriously, try getting one of those managers/designers to walk into an auditorium full of experts who actually know something about the topic,
...
I'm only glad that most "designers" moved from print to web. They are your problem now, thank you very much 🤪
 
I have just learned a little of Javascript, some principles, what objects are, prototypes, inheritance, constructors.
I played a little with node.js

I also read once about the tcl extension tclOO for object oriented programming, but forgot everything.

Sure, the theory looks nice. I do understand that it may have advantages, encapsulating code, making some order,
but I have the feeling it is an exaggeration. If I have to program, I have no idea how to begin using that.

Are eventually pointers to structures in C not enough?

What is your opinion / experience?
I believe OOP is a necessity where you need to build on/for a foreign, complex and modular but unified structure i.e. GUI.
Paradigm shift in GUIs is probably comming, tho. LLM controlled interfaces. No need for unified GUI then. Maybe OOP will take a hit.
 
Back
Top