The last post or so sounded stressed. I hope they feel better.
But in general, going to read a little n-gate was a relief when some HN comment thread went off the rails. Someone else could rant about the dumbness, and a burden was lifted.
I think they mean to refute the article's suggestion that tiktok and misinformation are the cause by highlighting that they received accommodations at a young age.
>You seem to imply your conditions have not really improved and you need same/similar accommodations
They didn't share the nature of their current accommodations.
The article frames being smart and promising (to a university) as at odds with having a learning disability, which is not necessarily true. It also frames depression and anxiety as learning disabilities, which they are not.
Amazon claimed their energy usage was "matched with 100% renewable energy" in 2023, while Google's goal is to actually "run on 24/7 carbon-free energy".
Google already claims to have matched 100% of their energy with renewables since 2017.
I appreciate how the author highlighted the python domain-specific tricks like dropping imports and rewriting tabs/spaces. It's good to be reminded that even with "large" language models you can get better results with quality over quantity.
This article could use a disambiguation. Distributed systems are systems "whose components are located on different networked computers, which communicate and coordinate their actions by passing messages to one another"[0].
This article appears to be focused on running many components on a single computer under the same process tree. Perhaps a better title would be "No more DSLs: Implement and deploy microservices as a monolith".
No, this is distributed; see this line in the introduction:
>Functionality for distributed execution and monitoring is shared through libraries rather than by delegating to external orchestration systems, making a single-program system completely self-contained.
The quote you pulled out mentions "distributed execution" being completely contained in a "single-program system" - isn't a single-program system, by definition, not a distributed system?
With the emphasis on distributed systems, I was waiting to see how the approach would help synchronization, replication, network dependencies, etc. But all the examples show calling other services as functions or spawning new processes. At the end orderd starts listening for requests, but I don't see any example in the article where the example program talks to another computer in the system. Perhaps I am missing something?
>The quote you pulled out mentions "distributed execution" being completely contained in a "single-program system" - isn't a single-program system, by definition, not a distributed system?
Nope. As the second paragraph talks about, there are other tools too (distributed languages) which also let you write a single program which is distributed. It's very common really - if you've ever written a shell script which performed some operations on another host with ssh, you've written a distributed program.
This is just another way to write a program which performs distributed operations, like using a distributed language or using ssh. (Well, rsyscall is the way to do that, this article is about an application of doing that, actually...)
That section is about threads. This is not a distributed system (running on different machines), it's a concurrent system (running in one machine.)
Anyway there is overlap between the two terms so strictly speaking the author is not wrong. But is anything with threads a distributed system? If so I built many of them, even with Python .
>An rsyscall.Thread may operate on a local or remote host, or inside a container or VM, or on other kinds of nodes, depending on how the rsyscall.Thread was produced...
>All distributed operations are performed by method calls on rsyscall.Thread objects.
