yvdriess

Thanks for the clarification, learning everyday.

I haven't had to analyze the performance of no-swap processes before. My assumption is that code is hot enough to avoid eviction and that evicted code pages are rather the exception. To strong-man the argument, I can imagine long running complex (bloated) services could have parts that are not touched unless a specific request comes in.

Disabling swap disables loading a process' binary to memory? Or do you mean that evicted code pages will need to get loaded from disk every time.

But only in 2028 because all the wafers rotting away in the warehouses are HBM which are too expensive to package or integrate into consumer electronics with tighter margins. Looking forward to having enthousiast-grade GPUs with HBM again though.

Meritocracy, in its originally intended pejorative meaning.

I find it useful to use the term "determinate" (determinacy) [1,2] when dealing with concurrent or parallel computing. That puts the focus on equality of outcome (same result), leaving open "deterministic" to mean the exact same sequence of events (schedule).

[1] As used by Jack Dennis and Arvind: https://cacm.acm.org/opinion/the-resurgence-of-parallelism/#... [2] Originally defined by Karp & Miller: https://www.jstor.org/stable/2946247

Many earth rotations ago, I was IMing through an mIRC bot because I refused to install MSN. This kind of reminds me of that too.

> They probably don’t realize that the marginal rate of energy cost is fast approaching zero. That technological innovation is exponential and carbon capture can likely be made economical relatively soon.

By adding that, he is implying "Don't need to act, keep burning fossils, tech will fix it". That is in itself asserting a simplified model assumption about a (human) world that is much more complex; something he was railing against in the previous parts of his text. Either it's a cheeky joke, he himself is an intellectual or both.

I found it an apt demonstration of his own thesis.

They weren't. A lot of abstraction concepts like ADT, modularization, structured programming had to be developed over the following decades.

I really like languages that embrace the duality of "closures are a poor man's object, objects are a poor man's closure".

I enjoyed the programmer's approach to build it up from first principles. I chuckled at rythm being the binary encoding of the duration's mantissa.

Now dispell the "this is just the western tradition": do Klingon music theory https://youtu.be/1LjcBv-OWtQ

Iceland already is Schengen

Caches are important for cpu core performance even when the the working set doesn't fit.

You're thinking of Taalas.

Pretty old, but a good example of how such an abstraction works: https://github.com/ExaScience/arrow-street

The larger runtime makes bootstrapping go for unsupported architectures more laborious than C, but it's not a hard blocker. The function call overhead for inline assembly feels like more of an issue doing close to hw programming. It can be avoided for the runtime, but user go code can't escape it afaik.

Having played it: yep! It's a solitaire Mankala/Awele game. You use the sowing mechanics to try to clear the board, with chains scoring exponential points.

I can also recommend the manga, the first vol. It's packed with interesting ideas and author footnotes that the 1995 hints at but has no time to elaborate on.

E.g. In the movie the protagonist glances an office worker that looks like her. The manga has her explain that she looks like a cheap generic model to hide the fact she is full of expensive specialized government tech. I always think of that scene when I put an expensive work laptop in a ratty backpack.

Hanging out in programming language IRC channels (quakenet shoutout) makes you realize pretty quickly why experts in said channels and newsgroups are such irritable grumps whenever someone asks a question that smells like homework assignment.

I also grew to understand the value of people digging deeper into the underlying issue, instead of just answering "how do you do X in Y". The usual reaction was "I don't want to explain to you why I want to do it like this. Just tell me how to do this!"

The binary view is mostly true, unless it's for events or problems they are themselves familiar with. There is a term for this, but can't for the life of me remember it: People think the problems they are dealing with are infinitely more nuanced, complex and unique than the problems other people are dealing with.

Play on Cilk?

And here I thought drawing graphs in TikZ was doing it manually.

Love the article, this is why I browse HN.

And that's a shame, but the relevant workloads typically run on server class CPUs.

> Hard to make a better wheel.

Pet peeve: stupid analogy seeing how wheels kept being improved throughout the millennia with every new technology. The only thing in common is that it's round.

Similarly, DRAM in any way you see it has been improving to the point of barely being recognizable since the 70s.

That said, DIMMs and the whole bus idea is in dire need of getting a new type of bearing.

Just to highlight: in contrast with fossil fuels, at least nuclear waste is something we can capture, creating a storage problem.

AmbientTalk did this. I used it for a demo where I dragged a mp3 player's UI button to another machine, where pressing play would play it back on the originator's speakers. Proper actor programming in the veins of E and Erlang.

https://soft.vub.ac.be/amop/

Tournament parallelism is the technical term IIRC.

somethingaweful forums are still very much alive

Anyone else clicked on this expecting an article about Go Generics?

Ignoring the snark for a second. It's not because you are unfamiliar with the go toolchain that it's inherently bad, nor does it put you in a good position to give accurate criticism.

- "tea" is an explicit alias that was added to the import statement in the tutorial examples, which you did not reflect in your snippet:

    import tea "charm.land/bubbletea/v2"

- The following also just works as you expected, but directly assumed wouldn't work:

  import github.com/charmbracelet/bubbletea

The only surprise here is that the repository authors decided to change the name of the module between v1 and v2 of the package. The git branch tagged v2 contains a module named 'charm.land/bubbletea', earlier v1 branches are named 'github.com/charmbracelet/bubbletea'. That's on them for breaking convention and surprising users, the go toolchain does not factor into, this beyond supporting versioning by naming convention.