Anomandaris

Honestly I don't get why this is so surprising, humans have been drawing graffiti for thousands of years. There's plenty of Ancient Roman graffiti to attest to that.

While yes, we should discourage it where possible, we also need to acknowledge that it's just as big a part of human nature, and culture, as the colosseum itself.

Burning it would release too many fumes, sink the bastard and turn it in to a new coral reef for marine life.

But that's functionally no different than what's already there...

The reason the lines are so long isn't because of anything Java related, it's because of the field names themselves.

That is an interesting point, but it's not Java specific, you could do this exact thing in most other languages and it would look pretty much the same.

Considering the fact that in a lot of enterprise projects the data structures are not necessarily open to change, how would you prevent reaching through objects like this?

This just tells me you don't use Java. Factory classes are just used to create objects in a standardized way, but this code isn't creating anything, it's just getting nested fields from already instantiated objects.

Sure, but most of the lines in the screenshot break down to:

object1.setA(object2.getX().getY().getZ().getI().getJ().getK().getE().getF(i).getG().toString())

Aside from creating a method inside the class (which you should probably do here in Java too) how would another language do this in a cleaner way?

If you honestly believe the standard, sterile, grandma-friendly, value-brand emojis typically available to all devices convey tone and response in the same way then nothing I could say would convince you otherwise.

That's not to mention the fact that non-mobile devices typically have no emoji keyboard available.

We unironically need these Twitch/pepe emotes to spread further, they're great for quickly and easily conveying a tone or emotion.

There's a massive range of these emotes that we're all missing out on... Madge

-50% ad revenue says otherwise

One of the topics I've seen become more prevalent in recent years is the idea of limiting your use of privacy addons and softwares, with the aim of trying to prevent your fingerprint becoming too unique.

For example, there are probably a billion users with 21 inch monitors, running Windows 11, browsing on Google Chrome. Providing them with that information just makes you one more in the bunch, but if you stack up privacy addons you end up creating a more easily identifiable picture of yourself through the hole you created by hiding information.

Like most things, it's about balance. All changes to open source software must be approved by the community managing it, and if that community is lazy or poorly managed or simply too busy then there's an opportunity for new vulnerabilities to be created, either accidentally or maliciously.

But for well managed software, as other people have said you can get more changes more frequently, more security as many people are evaluating the code base, and greater attention to what users want rather than what's profitable. Whereas with closed source software there is a greater focus on profitability, and sometimes that leaves vulnerabilities open when development is rushed and/or vulnerabilities are not seen as important enough to justify the cost to fix, but sometimes that tendancy towards profitability can also ensure the product stays a market leader. Steam may be a good example of a good closed source product.

It would be interesting to see exactly how Meta is managing to block VPN users. Is it simply a matter of looking up instagram or facebook account related to email addresses used to sign up? Is it evaluating some sort of browser fingerprint? That's assuming VPN users are doing so via desktop, if it's an Android device for example is the OS itself providing information that's not getting obfuscated by the VPN?