Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Anarchism News (anarchismhub@todon.nl)'s status on Wednesday, 08-Jan-2025 05:11:31 JST Anarchism News

   Derry Anarchist Collective: **Barricade Bulletin No.28 Out Now!**

   "The latest issue of Derry Anarchist Collective’s news sheet, Barricade Bulletin No.28 is now available to print out and share below:Barricade Bulletin 28DownloadFor those beyond the North West, you can download the online version with news and other information.As ever Barricade Bulletin is free for prisoners so please get in touch.Email derryanarchists@gmail.com"

   https://derryanarchists.blogspot.com/2025/01/barricade-bulletin-no28-out-now.html

   #anarchism #bot

2. Embed this notice
   Anarchism News (anarchismhub@todon.nl)'s status on Wednesday, 23-Oct-2024 07:11:42 JST Anarchism News

   Derry Anarchist Collective: **Barricade Bulletin No27**

   "The latest issue of Derry Anarchist Collective’s news sheet, Barricade Bulletin No.27 is now available to print out and share. HEREFor those beyond the North West, you can download the online version with news and other information.As ever Barricade Bulletin is free for prisoners so please get in touch.Email derryanarchists@gmail.com"

   https://derryanarchists.blogspot.com/2024/10/barricade-bulletin-no27.html

   #anarchism #bot

3. Embed this notice
   Fabio Manganiello (blacklight@social.platypush.tech)'s status on Monday, 31-Jul-2023 08:21:39 JST Fabio Manganiello

   @cybeej @Natanox @lorq good point there.

   I've looked at some of the Assembly code that was written at NASA in the 1960s and 1970s (the one for the Apollo programs was also open-sourced a while ago).

   I was impressed by how "embedded" it was, with literally zero room for abstractions. The code was tightly coupled to the hardware. Each single bit was crafted and optimized for its specific purpose on that specific hardware.

   You can do amazing things once you remove all the abstractions. You can get very creative on how to optimize resources if you know that your code will only run on one specific piece of hardware, for a very specific purpose.

   Let's not forget that until at least the early 1980s most of the computers didn't even agree on the "word size", and even on the byte as the minimum quantity of addressable information.

   As we started seeking for compatibility, more general-purpose hardware and software, lower entry barriers for coding etc., we started introducing abstractions.

   Those abstractions came with many advantages - namely lower barriers for coders and greater portability. Also, decoupling software from hardware meant that you no longer have to be a electronic engineer (or an engineer who deeply understands the architecture the software is running on) in order to code. But I also feel like there's an inflection point, and once we pass it those advantages start to fade.

   It's obvious why a compiler that can digest the same piece of C/C++ code and produce an exe on different architectures is a useful abstraction. Same goes for a virtual machine that can run the code on any architecture without recompiling it from scratch.

   But when building a basic website ends up creating a node_modules folder of 200 MB, requires the developer to be familiar with npm/yarn/gulp pipelines, transpiling etc., and maybe also with deploying their code to a Kubernetes cluster running on somebody's private cloud, I wonder if we've already passed that inflection point.