nah, one is never to old to learn stuff.

a tough, but hands-on start would be something like https://www.theodinproject.com/

it’s a free course for web development and their material is really good, so even if you don’t finish it you’ll aquire some good fundamentals about programming.

sadly that does not match your language preferences, but a lot of knowledge tends to transfer or helps to understand different approaches.

you could also try a course like Introduction to CS and Programming or other university/college courses. they are meant for people who start without programming experience.

sure, if the limitting factor in a case like this would be the speed of computation and not slow IO than implementing the computation in another language would be a viable way to increase performance.

Fyi: Libre Office is the actively developed Open Office fork.

Don’t know how it stacks up to MS Office though.

Access control and offering a sound interface.

You don’t need getters and setters if every attribute is public, but you might want to make sure attributes are accessed in a specific way or a change to an object has to trigger something, or the change has to wait until the object is done with something. Java just has tools to enforce a user of your objects to access its attributes through the methods you designed for that. It’s a safeguard against unintended side effects, to only open up inner workings of a class as littles as necessary.

In a language without something like private attributes you’d have to account for far more ways someone might mutate the state of objects created by your code, it opens you up to far more possible mistakes.

You let your ide generate simple getters and setters or utilize something that generates them during a compilation process.

Who ever writes them per hand needs to utilize their tooling better or needs better tooling.

Maybe it hurds in a good way.

Nah, it’s a kernel it does kernel stuff and does not offer anything a normal user notices compared to other kernels.

It might be interesting for people who work on kernels just to see different ways on how to solve common problems.

I guess the biggest difference for users is that nostr relays don’t federate with one another. So you’ll have to query multiple relays yourself if you want to see stuff outside of the relay(s) you post to. The other big difference is that your identity is a keypair. The relays you send to only know your public key and that’s it.

E: someone running a relay could still decide you need to create an account or something, but this account is only the permission to use this specific relay. Your identity would still be your keypair, so moving to another relay is easy.

If null is a valid value for the field there is no reason why a builder should not construct an object where the field is null.

The only thing i dislike about the pattern is that a class utilizing the builder to retrieve the object has to know a lot about how the object has to be constructed, however it makes for very readable code imho.

Eh, if i wanted to i could scrape various instances and do whatever i want. The question is would i be able to pin information to identities without the accompanying meta data or would i only get a big text corpus.

The benefit of the fediverse is that no instance can sell the whole package, because most instances only have the posts of most users and nothing more. Reddit has way more additional data that can be used to track and identify someone.

No, the right to be forgotten is about data that can be used to identify you stored by a service provider. It’s not a right to have every record on the internet purged.

I guess you could force Instances one by one to forget you, but a single provider only has to make sure they deleted the data they stored.