• 18 Posts
  • 563 Comments
Joined 2 years ago
cake
Cake day: March 19th, 2024

help-circle
  • New tech isn’t socially neutral. Should we be excited about the possibilities of new missiles and warplanes? If you understand how that new technology can be bad, you can understand how other new technologies can also not be “exciting”. Capitalism produces for the sake of production. We have plenty of useless shit that exists for the ouroboros of profit and marketing rather than to fulfil some natural use case. I think modern LLMs fall into the former, not to mention the energy cost of the current demand. I think LLMs can be cool as toys/for demos/as academic projects/etc but the current prevalence is purely due to marketing and AI companies trying to make something that is quite expensive, profitable.





  • Having to replace perfectly functional Pixel phones because GOS stopped making updates for them. I don’t blame GOS as they’re a FOSS project and their end of support coincides with Google’s end of support, but it still feels bad replacing perfectly functional hardware. Wish release cycles were much slower so support for existing devices could be focused on, instead of having to spend time porting to every new phone dropped like every year or whatever.













  • The problem with Scratch is that you don’t learn very much about computers with it. When I expressed I wanted to learn programming as a kid, I was directed to Scratch, and the whole time I was like “ok this is fun and cool, but when do I get to the real programming. I want to make an ‘actual program’.” You’d learn about how programming works on a very high level but you don’t learn much about how things work “under the hood” which imo is the fun thing about learning to program.

    The best way I can articulate my goal is like how it feels to watch an edutainment video (think VSauce/Veritasium/Numberphile/etc)—you get a peek at some topic you didn’t know about before and feel you understand how the world works a bit better. It’s not the same thing as training someone up to be an expert, i.e. I’m not trying to turn these people into programmers (though if they’re interested enough they can of course go away and pursue that in their own time).





  • I mean someone pointing out a vulnerability in a piece of software should be a falsifiable claim, e.g. “they store their passwords in plaintext”—if it’s foss then just look at the source. You don’t need to read the entire source because you have been given a specific part of the code to look at. You need to only look at the process between the software receiving a password and its query to the database.

    And if it’s not foss I don’t use it, and the claim may be unfalsifiable for an outsider who isn’t bothered to try reverse engineering.