Programming Languages

12 readers

1 users here now

Hello!

This is the current Lemmy equivalent of https://www.reddit.com/r/ProgrammingLanguages/.

The content and rules are the same here as they are over there. Taken directly from the /r/ProgrammingLanguages overview:

This community is dedicated to the theory, design and implementation of programming languages.

Be nice to each other. Flame wars and rants are not welcomed. Please also put some effort into your post.

This isn't the right place to ask questions such as "What language should I use for X", "what language should I learn", and "what's your favorite language". Such questions should be posted in /c/learn_programming or /c/programming.

This is the right place for posts like the following:

"Check out this new language I've been working on!"
"Here's a blog post on how I implemented static type checking into this compiler"
"I want to write a compiler, where do I start?"
"How does the Java compiler work? How does it handle forward declarations/imports/targeting multiple platforms/?"
"How should I test my compiler? How are other compilers and interpreters like gcc, Java, and python tested?"
"What are the pros/cons of ?"
"Compare and contrast vs. "
"Confused about the semantics of this language"
"Proceedings from PLDI / OOPSLA / ICFP / "

See /r/ProgrammingLanguages for specific examples

Related online communities

founded 1 year ago

MODERATORS

armchair_progamer@programming.dev

If Inheritance is so bad, why does everyone use it? (buttondown.email)

submitted 7 months ago by armchair_progamer@programming.dev to c/programming_languages@programming.dev

24 comments fedilink hide all child comments

This essay says that inheritance is harmful and if possible you should "ban inheritance completely". You see these arguments a lot, as well as things like "prefer composition to inheritance". A lot of these arguments argue that in practice inheritance has problems. But they don't preclude inheritance working in another context, maybe with a better language syntax. And it doesn't explain why inheritance became so popular in the first place. I want to explore what's fundamentally challenging about inheritance and why we all use it anyway.

you are viewing a single comment's thread
view the rest of the comments

[–] porgamrer@programming.dev 6 points 7 months ago (1 children)

It does frustrate me that people say "composition over inheritance" and then act like the problem is solved.

For a start, dependency injection is an abomination. Possibly the single worst programming paradigm in the history of software development.

The only codebases I've seen that deliver on some of the promises of composition have been entity-component systems, but this concept hasn't even matured to the point of being a first-class language construct yet, so the programming style is pretty janky and verbose.

[–] balder1993@programming.dev 5 points 7 months ago (1 children)

dependency injection is an abomination

I don’t think so, dependency injection has made testing easier in all static typed code bases I worked on.

[–] FunctionalOpossum@programming.dev 4 points 7 months ago* (last edited 7 months ago)

The general idea is to not test things that need to be mocked, keep all logic out of those and keep them at the edges of the application. Then you test the remaining 90% of your code which would ideally be pure functions that don't need mocks .

The remaining 5% can be integration tests which doesn't care about DI.

In reality this doesn't always work, because sometimes it's better to write a complex query with logic and let your database do the processing.