Java

Created: Apr 25, 2025 | Stub quality | Low importance

The problem with Java is that everything has to be a class. Period point blank. This distorts all design of programs, because you start thinking "Well I can't have a function that just takes an object, so I better add it as a method of the object". Then you think, "Well my Object needs to be able to construct other Objects that it needs, but I don't want to tightly couple them" so you end up with a Factory pattern. Also, you end up trying to map classes to "real world-ish" things, like Databases and Business Models and such, even though some functionality cuts across class boundaries and would be better in just a simple funcion. Don't worry, we have the Singleton pattern for that, for basically just a loose colletion of random code. :facepalm:.

Backlinks

Ruby (on Rails)

Ruby on Rails is probably the first frontend framework I ever used. I think I dabbled in Perl a bit in a college course, cgi-bin style. But even in college, I worked on a project for a digital choral music library, where I created a R
Programming languages (meta)
I realize that I've written a lot about different programming languages that I'm familiar with in this digital garden. This node is sort of a meta node that serves to tie those pages together a bit.

Here is a list:
- Python - my curre

Comments

With an account on the Fediverse or Mastodon, you can respond to this post. Simply visit the post on its original server and leave your comment. It and other known non-private replies will be displayed below. Learn how this is implemented here and here.

Loading comments relies on JavaScript. Try enabling JavaScript and reloading, or visit the original post on Mastodon.