• 0 posts
  • 16 comments
Joined 3 years ago
Cake day: June 30th, 2023
  • I’ve never been able to successfully write a jq command without having to Google it. It is something so complex and I don’t do it often, so I just forget everything.

    I hope they figure out something with more I tuitive syntax, something SQL-like that people can write without having to look at a manual.

    Anyways, AI is here… pretty soon we’ll just translate natural text to whatever overly complex language there is.

    I’m sure I’ll get replies of people saying jq is easy. It isn’t for me, right now I can t even remember how to filter and create associations between objects. I think I’ll just start writing small python apps to process JSON. A bit longer but at least I can maintain it. The only issue is that Python is too heavy… I’ll figure something out.

    I’ve been thinking for a while that what we actually need is a modern shell language. Like a mix between python and shell. Imagine if you had native support to read a JSON using shell.

    Edit: oh shit. Said all of this and then saw the comment below talking about Nushell. Today is a good day.

  • 10 minutes after migrating from Maven to Gradle…

    “Wow, I can do the same I did with Maven with such a small configuration and a few lines of code”.

    2 months later…

    “Wtf is broken!!? Wtf is going on?”

    2 hours later…

    “Wtf is broken!!? Wtf is going on?”

  • Man, I honestly have no idea why they are downvoting you. Composition literally means taking common behavior and placing it in external objects behind interfaces using a has-a relationship.

    No idea why they are denying this. Inheritance vs composition is the same as “is-a” vs “has-a”. In composition re usability isn’t done via inheritance but code encapsulation.

    Saying that in Go objects can implement many interfaces is the Interface Segregation principle from SOLID. Basically having small interfaces instead of a big interface with methods that may not be implemented by all implementors.