Especially on mobile.

Mumble is another strong, open source, self-hosted option.

you really shouldn’t be using variables with the same name but different capitalization in the same sections of code anyway.

It’s a standard convention. Notice step #3 here: https://scottlilly.com/learn-c-by-building-a-simple-rpg-index/lesson-08-1-setting-properties-with-a-class-constructor/

Edit: Step #4 is a different standard convention that also applies here.

It turns out that the easiest thing to program isn’t always the best application design.

Nope. Completely different.

Case is often used to distinguish scope. Lowercase is local while uppercase is public. “Name = name” is a pretty standard convention, especially in constructors.

There is a ubiquitous use case in programming. There is not in the file system.

Done! You should see about 4 reports in !linux . Take a peek and see what that looks like from whatever client(s) you normally use. Note that you’re not always obligated to take action on things that are reported. You know where the reports come from and have a good idea of how reliable they are.

We have a completely optional moderator discord here https://discord.gg/wKg6bhkM if you’re interested.

Thanks for helping out. If you have questions or need help at any point, let us know. You can PM me, there’s the discord, or there’s the info@lemmy.world email that goes to the instance admins.

Just blame the users. Easy.

For what? To keep track of who’s drinking coffee? Are you charging for coffee?

I didn’t understand the downvote I’m the first half… and then I read the rest.

I think it asks “Are you sure?” now first.

And it can be in any language, but typically comes from someone who started with Java.

Okay, here we go. I’m going to spit out some bullshit and home someone corrects me if I’m wrong. I’ve looked for some explanations and this is what I’ve gotten.

Are you ready?

The Factory Pattern.

My understanding is that the purpose is a function to return any of several types of objects, but a specific type, not just an interface or whatever they might all inherit from.

I think most languages now have something like a “dynamic” keyword to solve this issue by allowing determination of the type only at runtime. (To be used with extreme caution.)

But most of the time I see the Factory pattern, it’s used unnecessarily and can only return one specific type. Why they would use a Factory pattern here and not just a plain old constructor confounds me.

Am I off base?

Seems like he’s worried you’ll Java everything up, which can be valid.

I think a good, easy example is whether your application should allow a selection of databases or be tied to one database.

You can make arguments for either, often (but not always) regardless of your use case.

I don’t know. Doesn’t look nearly as cool as my XP desktop with custom themes did.

Oh yeah? How about SMS? Or you can install this proprietary Symantec bullshit!

Fewer people will get into unraid. Natural churn will happen. The OS will slowly die, and as it dies usability will get worse.

Not many people are going to choose the subscription Linux over a free Linux.

Pick a language. Keep it simple. Make something.

Bonus points if it’s something very simple that you’ll use.

Tic tac toe. Fizzbuzz. A score pad for a game. Something that can theoretically be done in an hour (if you were an expert).

between the android phone and the macbook.

Apple intentionally doesn’t play well with others in order to trap you into their ecosystem.

Agreed. I may not want to mix my discord identity with whatever project I’m looking at. I especially don’t want to mix my personal online identity with my professional identity. I post too much politics for that.

IRC at least you have text logs, but I agree.