@aral that's a fine distinction. As a developer, you're in a better position than I am to know. But you'll need to convince me. Because it seems to me that outsourcing processing work to the user's PC - via JS black boxes - is exactly how #SurveillanceCapitalism achieves massive scale, while claiming that #ThereIsNoAlternative to centralized server infrastructure. A myth they've propagated so effectively that even many developers have started believing it:
@danjones fair points. But privacy is only a subset of a much larger concern, which is about *control*. Putting aside the argument we could have over the "black box" part of my post, the fact remains that:
> outsourcing processing work to the user's PC - via JS - is exactly how #SurveillanceCapitalism achieves massive scale, while claiming that #ThereIsNoAlternative to centralized server infrastructure.
@danjones There are many possible strategies for redecentralizing, and resolving the *many* problems with JS, some of which are described here:
@strypey @danjones @alcinnz Maybe the FSF should worry more about its logo appearing next to Google’s as they sponsor the same events than some ridiculous and ill-informed stance against a programming language that spreads FUD about potential alternatives. Remember that an AGPLv3 licensed app specifically built for drones to send hellfire missiles to little children would get the FSF seal of approval. Free Software is just a component of ethical tech but doesn’t care about ethics of use cases.
@aral I share your concerns about open source events being sponsored by Google, as do FSF, but they can't control this. As for approving of child-killing drone software, that's FUD worthy of Microsoft. FSF have often spoken out about the use of freely-licensed code to do much less anti-social things than that:
> ridiculous and ill-informed stance against a programming language
I note that they're far from alone in seeing JS as a problem. Plenty of experienced engineers have serious problems with it too. A quick selection off the top of my head:
> let's not forget it killed off better alternatives at the behest of Google
To what alternatives are you referring?
Also, Google didn't exist yet.
Because of that limitation, I wouldn't consider them as serious contenders.
And Java applets were an awful user experience.
And Google certainly didn't have the clout to kill any of those off at the time.
@walruslifestyle @aral @alcinnz
@strypey @danjones @aral @alcinnz agree, and it's also dangerous because all it takes is a monopoly or duopoly among browser makers for the entire industry to consolidate around a technology that benefits their business interests. instead of having a healthy ecosystem of alternatives so that developer's can choose what works best for them
As a general instance, we are not centered on a specific theme, or a specific language. Everyone is welcome as long as they follow the few rules we have.
We always run the latest stable version of Mastodon, providing you a stock experience, with the following modifications:
Although we are a medium+ sized instance, we'd like to keep the feeling that you are at home and safe here.