riskable

joined 3 years ago
[–] riskable@programming.dev 2 points 1 month ago* (last edited 1 month ago)

As time goes on I feel like the concept of DRY has more applicability to compiled languages like C/C++ and Rust than interpreted ones.

From a concise coding standpoint, it's a great idea most of the time. However—having worked with some long-term projects—I've found that it can create "code smells" if it's taken a little too seriously.

For example, I'll often see loads of tiny (Python) functions that do simple things like applying a regex. Then I'll search the code and see that a single regex function gets called in just two places.

If that was the only time it happened, it wouldn't be a big deal. Except I'll see dozens of tiny functions like this at the top of many modules and be scratching my head wondering why they went to such an extreme. It makes my job as a reviewer harder because now I have to scroll all the way to the top of the script and back constantly to figure out WTF it's doing.

Not only that, but Python doesn't have a JIT that would optimize away those extra functions calls. Every function call in Python carries some overhead (both CPU and memory), so by dividing up your functions into dozens of little ones you're actually slowing it down.

Normally such slowdowns are so trivial it doesn't matter. But when someone is following DRY like some kind of religious extremist, those extra calls really can and do add up. Especially when you find them being called inside of deeply nested loops!

[–] riskable@programming.dev 13 points 1 month ago

If Meta can’t distinguish feminist literature from prohibited content,

You misunderstand... Feminist literature is the prohibited content. I'm not making a joke here. That's literally their policy!

[–] riskable@programming.dev 4 points 1 month ago

I read once that the tale of the three little pigs was modified from its original form to preach the Protestant work ethic and also as a form of Victorian-style propaganda, where the rich, educated landowner was the reasonable one.

[–] riskable@programming.dev 22 points 1 month ago (1 children)

Back in the day, rich people would fund hospitals and schools in hopes of getting to heaven.

Actually, they did that to avoid peasant revolts. Attaching it to religion was just a convenient way to keep the church on their side so the pastors and priests would continue to preach the traditional message: "don't be violent against your oppressors, let God handle them and you'll be rewarded after you're dead."

Without that regular, Sunday propaganda, revolts would've been much more common.

[–] riskable@programming.dev 13 points 1 month ago (1 children)

Yeah, this is super SUS. It's right there on the card!

[–] riskable@programming.dev 0 points 1 month ago (1 children)

Your argument boils down to this:

  • This technology exists because you've worked with it.
  • You want to ban it because it could be used by bad people to invade others privacy.
  • The technology doesn't actually exist.

You're not making any sense.

The technology does exist and the software to do repair work with AR also exists: https://aidarsolutions.com/maintenance-augmented-reality/ (Just an example, there's more companies that do it)

People are using AR for equipment repair every day. It would be fucking nice if every day people could take advantage of that using cheap glasses that include a camera and a display of some kind.

The only reason why there's not open source projects for this is because the hardware is too expensive.

[–] riskable@programming.dev 1 points 1 month ago (1 children)

So you don't trust individuals with cameras but you trust the government and businesses with them. Got it.

[–] riskable@programming.dev 0 points 1 month ago (3 children)

Get your mind out of the gutter!

Have you ever seen AR glasses demos where someone is inspecting an engine or repairing something? Imagine open source hardware projects being able to offer similar capabilities for any common household appliance. It would be amazing!

There's infinite amazing and non-creepy uses for tech like this but it'll never happen with unimaginative luddites everywhere!

[–] riskable@programming.dev 0 points 1 month ago (3 children)

WTF? Local models run on your local hardware without an Internet connection. Hence, they're not giving any data to anyone except you.

[–] riskable@programming.dev 6 points 1 month ago (1 children)

Bill Gates tracking chip. You can tell it's the Australian version because it's a five-pointed star, designating your climate and local fauna.

Remove the RAM successfully and you could make some money 🤌

[–] riskable@programming.dev 3 points 1 month ago

I'm not going to let them eat me! Probably.

I'm still faster, thanks to exercise. For now.

[–] riskable@programming.dev 0 points 1 month ago (1 children)

Always assume you're being recorded in public because you are. You're not even talking about that: You're talking about preventing normal citizens from being able to record in public. Yet government will still have that power. That's exactly what's going on with Flock cameras.

You can regulate sales of hidden cameras in your country, but you can't stop their manufacture or general availability because they're literally designed to be undetectable. Anyone can buy them online and they always will be able to.

I could design my own PCB with a tiny CCD and put together a case with whatever lens I want. In your scenario, would I require a license to order such a PCB? Like it's a gun or something?

How would you even know that it's meant to be a camera for recording people? It could just be an environment monitoring sensor or a security device that sounds an alarm whenever it detects motion.

You brought up the practicality of things... What you propose is highly impractical.

view more: ‹ prev next ›