77
Callum
77313c523694bfccaa05034010f6714604098380e77e13deeda40dc91427ef53
~~~

My not setting up a wallet here is deliberate; I think zapping is a gimmick and a bad incentive on social media platforms.

And finally, I largely enjoy your account and will continue to follow it. None of what I have written was an attack on you, just on certain LLM posts. (But I do make attacks on others here, it's true.)

Maybe. You're free, of course, to post whatever you want on yr account. But yes, I think the term #brainwank is apropos and while they may be useful to play around with personal ideas privately, I don't think they make for good public postings, because they're not 'authentic' opinions /analyses.

States work on the basis of a class of power sharing 'middle men's. See for example the feudal system with its earls and barons and knights under a king. When a class of middle men are thrown out, as is happening now under Trump, that is a point of change and potential fragility in a state, even if the moment of fragility passes and a new set of middlemen are established.

To relate what is happening in the USA now to a *technological* system, like Bitcoin, is erroneous. They are 2 different things, one technological, the other political. Bitcoin is apolitical .

I've found some of your other LLM posts useful (and bookmarked them) but the ones that are responses to a leading question, like this one, fairly weak.

(And no, of course I don't work for the government)

This mediocre 'analysis' illustrates the inherent problem with asking an LLM a leading question

The chances that it does, or from some other similar foreign source, are exceedingly high

I respect Brian but I think he's wrong here. The blob & the political establishment had obvious deep antipathy for Trump and went to extreme ends to prevent him from becoming President again. Precisely because he's unpredictable in what he might do and we're already seeing this unpredictability play out.

The exposure of USAID activities has done real damage to the Blob; it wasn't just a limited hangout. Sure they will try to regrow this 'tentacle' and reestablish control in areas that they have lost it. But it will be hard work for them and something they would have very much wanted to avoid having to do.

This isn't to say that it's over for the Blob, not at all. They'll fight back. But there is a real fight going on, it's not just theatre.

Replying to Avatar Peter Todd

Apartheid is coming back, and Trump is taking action:

https://www.whitehouse.gov/presidential-actions/2025/02/addressing-egregious-actions-of-the-republic-of-south-africa/

“In shocking disregard of its citizens’ rights, the Republic of South Africa (South Africa) recently enacted Expropriation Act 13 of 2024 (Act), to enable the government of South Africa to seize ethnic minority Afrikaners’ agricultural property without compensation.”

It'll be darkly hilarious if this leads to sanctions...

Why not link to the actual Act itself Peter, rather than a foreign and hostile government's take ?

Replying to Avatar asyncmind

Why modern languages will never be able to replicate the elegance of Erlang because of fundamental organisational rot?

https://cdn.nostrcheck.me/16d114303d8203115918ca34a220e925c022c09168175a5ace5e9f3b61640947/d98862fb31baa8ef870135fee432ac6d69f102f36c24b62ea7fb25db31f626b1.webp

Modern programming languages will never replicate the elegance of Erlang due to fundamental organizational rot in the software industry. This rot manifests in several ways:

1. Short-Term Thinking and Market-Driven Development

Modern languages are often designed to capture market share rather than solve fundamental problems elegantly.

Features are added for popularity and hype, not for long-term maintainability or correctness.

Example: JavaScript’s evolution is often dictated by trends (e.g., async/await, promises, transpilation layers) rather than principled concurrency models.

2. OOP and Accidental Complexity

Many modern languages are burdened with Object-Oriented Programming (OOP) paradigms, which introduce unnecessary complexity.

Erlang’s functional purity and message-passing concurrency eliminate entire classes of bugs that OOP languages struggle with (e.g., race conditions, shared-state complexity).

3. Corporate Bureaucracy and Design by Committee

Languages like Java, Rust, and Go are often designed by committees with conflicting interests, leading to bloated abstractions and unnecessary complexity.

Erlang was created by a small, focused team (Joe Armstrong, Robert Virding, Mike Williams) with a clear goal: build a fault-tolerant, highly concurrent system.

4. Misunderstanding of Concurrency and Fault Tolerance

Modern languages treat concurrency as an afterthought, leading to frameworks and workarounds (e.g., Java’s thread pool, Python’s asyncio).

Erlang was built for concurrency from the ground up, making it naturally resilient to failure.

Modern systems attempt to bolt on microservices and Kubernetes to achieve what Erlang does natively.

5. Memory Safety Fetishism Without Understanding Fault Tolerance

Rust, for example, prioritizes memory safety at the cost of developer cognitive load.

Erlang’s philosophy is “let it crash”—failures are expected, so the system recovers instead of preventing crashes at all costs.

The obsession with memory safety in modern languages ignores the real-world need for uptime and self-healing systems.

6. Tooling and Framework Bloat

Modern ecosystems rely on massive build systems, dependency managers, and layers of abstraction.

Erlang’s lightweight OTP framework provides battle-tested primitives for concurrency, supervision, and fault tolerance without unnecessary dependencies.

7. Lack of Simplicity and Readability

Modern languages (e.g., Python, Rust, TypeScript) have complex syntax, macros, and excessive abstractions.

Erlang’s simplicity and pattern matching lead to readable and maintainable code, even for highly complex distributed systems.

8. Cloud Capitalism and the Overengineering of Infrastructure

Modern languages are designed to fit into corporate cloud ecosystems (AWS, Kubernetes, microservices).

Erlang was designed for distributed, self-healing systems that don't need cloud bloat to be resilient.

9. The Culture of Over-Engineering

Engineers today are incentivized to write overly complex, resume-driven code.

Erlang’s philosophy is the opposite: write simple, correct, scalable code and let the system do the heavy lifting.

10. People No Longer Build Systems to Last

Erlang was built with telecom-grade reliability in mind—systems that need to run for decades without downtime.

Modern software is designed with planned obsolescence—every 5 years, a new language, framework, or paradigm takes over.

Conclusion

Modern programming languages will never replicate Erlang’s elegance because software development today is broken at an organizational level. The focus is on short-term trends, bureaucratic decision-making, accidental complexity, and corporate profit motives, rather than simplicity, resilience, and correctness.

Erlang’s functional purity, lightweight concurrency, and self-healing philosophy make it fundamentally superior for building fault-tolerant, high-performance systems. Modern software development, burdened by hype and corporate-driven over-engineering, will never achieve this level of elegance.

#Erlang #C #Programming #SoftwareIndustry #TechDecay #LegacyCode #FunctionalProgramming #Concurrency #SoftwareEngineering #TechCulture #Coding #OpenSource #TechInnovation #HackerMindset #DistributedSystems

Generated by an LLM ?

The only thing I have to say to you is don't use your child for yr profile pic. It's creepy.

I'm amused by the person who 'stepped up' to zap you (nostr:npub1h50pnxqw9jg7dhr906fvy4mze2yzawf895jhnc3p7qmljdugm6gsrurqev). Clearly you're a hit with the narcissistic, politically ignorant wine-moms of the USA. Now I know the target audience of your cringey profile pic.

I don't care about yr book. Your position with the HRF says everything that I (or anybody else) needs to know about you.

False (and moronic) dichotomomy. What we want is for the USA to stop sending weapons & funds to Israel and to stop blocking international actions against its crimes in the UN. Then the evil colonizing state can collapse on its own and Palestine can be restored to full independence.

The nostr:npub17xvf49kht23cddxgw92rvfktkd3vqvjgkgsdexh9847wl0927tqsrhc9as that nostr:npub1trr5r2nrpsk6xkjk5a7p6pfcryyt6yzsflwjmz6r7uj7lfkjxxtq78hdpu is CSO for, is a shadowy intelligence agency cutout, dedicated to fomenting regime change in states that the North Atlantic oligarchy identify as obstacles to their extractive neo-colonialism. Same as USAID (and probably partially funded by them).