• 0 Posts
  • 289 Comments
Joined 3 years ago
cake
Cake day: July 14th, 2023

help-circle
  • Beautifully put.

    I especially like that they called out the “it’s just a tool” BS:

    Yet technological artefacts cannot be separated from the conditions under which they are created, or from the realities of who controls and profits from them. Today, developing these technologies expands racial capitalism, intensifies imperialist extraction, and reinforces the divide between the global North and South. The technology is inseparable from the labour that produces it — the expropriation of work by writers, artists, programmers, and peer-production communities, as well as the highly exploitative crowdwork of data annotation.








  • Not to be confused with SOLID, SolidJS, or Solidity.

    It’s a neat idea. Because of the need to operate on data close to web servers and backend services for potentially long timeframes, I think we’ll need a widely-adopted CRDT solution in order for something like Solid to really take off from a technical standpoint.

    And from a business standpoint, there’s really no upside. Sure, you delegate some cost for storage, but compute tends to be the more expensive aspect, and if you’re spending more time to interact with these external data stores, it may be more expensive in the end.



  • Gamehub Lite is pretty wild. It does take some fiddling, but it’s amazing how well (and relatively easily) you can get x86 Windows games to run on a $200 ARM Android device.

    I’m 12/13 so far on getting games to work at an acceptable level.

    Inexplicably, Vampire Survivors causes the entire device to crash. I guess they pull some pretty silly memory tricks to keep that game responsive with potentially hundreds of thousands of projectiles, so maybe it’s not so surprising.






  • You can run Linux on ARM. I do. And let’s not act like x86 wasn’t full of Microsoft-led efforts to undermine Linux. Anyone who’s had to disembowel their BIOS settings to the tune of “Your PC will be unsafe! Are you sure you want to run a LEGACY OS???” is familiar.

    I’m not a huge fan of the idea of buying CPU+GPU+RAM+mobo all as one unit. But like… that’s what tends to happen. Audio cards, SATA drives, network cards, these things all used to be separated until motherboards offered features to streamline things.

    The real problem is not form factor, but lack of competition. If there were 10-15 Qualcomms out there, offering different combos and a la carte options, there’d be no problem. It’s only because there are a tiny number of dominant players in the space that technical consolidation automatically translates to abusing consumers.


  • Well… modularity is kinda coming to an end anyway, regardless of supply chain moves. Apple’s M series has shown that op decoders and unified memory are the low-hanging fruit for overall system performance improvements, and that means less modularity.

    I think Valve sees the writing on the wall and is trying to get ahead of the game via FEX and the Steam Frame. Intel and AMD are pretty much stuck playing Nvidia’s game at this point, and Qualcomm has an incredible opportunity here. I’m still rooting for RISC-V, and I think it may end up being the long-term winner in like 10-15 years time.

    But either way, x86-style modularity is not long for this world. From a purely technical standpoint, I think that’s good. Adding the political and economic situation into the mix… well… fuck, we’re mega-fucked. About the only thing we have going for us as consumers is the fact that this is already headed towards a reset. So if we do gain some leverage, we can make a big change all at once. If we don’t though… things will get much worse.




  • The seal looks like this:

    Code completion is probably a gray area.

    Those models generally have much smaller context windows, so the energy concern isn’t quite as extreme.

    You could also reasonably make a claim that the model is legally in the clear as far as licensing, if the training data was entirely open source (non-attribution, non-share-alike, and commercial-allowed) licensed code. (A big “if”)

    All of that to say: I don’t think I would label code-completion-using anti-AI devs as hypocrites. I think the general sentiment is less “what the technology does” and more “who it does it to”. Code completion, for the most part, isn’t deskilling labor, or turning experts into chatbot-wrangling accountability sinks.

    Like, I don’t think the Luddites would’ve had a problem with an artisan using a knitting frame in their own home. They were too busy fighting against factories locking children inside for 18-hour shifts, getting maimed by the machines or dying trapped in a fire. It was never the technology itself, but the social order that was imposed through the technology.