this post was submitted on 19 Apr 2026
2 points (62.5% liked)

Programming

26579 readers
106 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
2
Language Design: Annotations Obsolete Modifiers (soc.me)
submitted 22 hours ago by soc@programming.dev to c/programming@programming.dev
13 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] soc@programming.dev 0 points 2 hours ago

The point I’m trying to make is that this is a very incomplete article, as it doesn’t seem that much thought was put on the downsides.

I could mentioned additional points in favor for the same reason you mentioned your points against, but at some point one has to stop and decide whether any minor, additional points made would sway the overall verdict.

Many of the most popular languages have both modifiers and annotations:

I have a separate blog post in which I consider when "popularity" or "familiarity" should be considered when it comes to language design.

People genuinely don’t believe this to be an issue. The closest is public static int main() for java.

If you look at Java-inspired languages like Scala or Kotlin, neither of them have public (made the default) nor static (replaced by companion objects).