Architecture-of-consoles VS blog

Ah no worries! From my side I was only trying to explain more about the origins of the article, since I see it often mentioned/speculated in many forums.

By the way, I'm always open to criticism ! (https://github.com/flipacholas/Architecture-of-consoles/issu...)

Author here! Surprised to see it shared! This article was the first one where I studied how a cryptography-based system worked and how it was subsequently broken, back in late 2019. Lot of things in the website have changed since then.

For this reason I humbly ask, if you find any mistakes, please report them here:

https://github.com/flipacholas/Architecture-of-consoles/issu...

That will make sure I don’t miss them, thanks!

No nitpick is too small or too big :) I've just logged your comment on the repo (https://github.com/flipacholas/Architecture-of-consoles/issu...) so I remember to take a look at it after I get back home.

Yeah, if anyone spots other issues can you log it first on the repo please? (https://github.com/flipacholas/Architecture-of-consoles/issues). Hope I don't sound too bossy, it's just that I can organise it better considering other forums may also spot mistakes.

Alternative edition without styles: https://classic.copetti.org/writings/consoles/playstation-3/

(ideal if you use accessibility tools, like text to speech, or want to read from an eBook or legacy browser)

If you spot a mistake, please log an issue on the repo (https://github.com/flipacholas/Architecture-of-consoles). Thanks!

Oh what an amazing feeling seeing one of my articles here. Let me share you a bit of history about this one:

- A year ago, an old version of this article got shared in hn (https://news.ycombinator.com/item?id=22932134) and since then, google started positioning my site in their search results, and many forums started noticing the site. Yay!

- Fast forward, I graduated from uni, continued working on more articles in my free time, and with all the newly acquired knowledge, I decided to re-write the old PS1 article to make it much more informational and accurate - This is the one you are seeing right now.

- The rewrite wasn’t easy, though. Luckily, I found very kind and talented experts that lent me a hand, you can see them credited in the ‘Changelog’ at the end of the article. Curiously enough, we are still debating on Discord about some discrepancies regarding the main diagram shown in the article. LSI’s docs (the CPU manufacturer) and Sony’s docs contradict each other when they explain the layout of the CPU’s ‘main’ bus! But don’t worry about it, it doesn’t affect any statement in the article. It’s more of a need to have everything as accurate as possible.

Finally, I’m always open to comments, improvements, suggestions, anything really! I share the writings here (https://github.com/flipacholas/Architecture-of-consoles) to discuss improvements but you can also find my email in the site.

Originally published at https://github.com/vb-consulting/blog/discussions/1

A follow up on this article was written today

[Recursion with PostgreSQL, Follup 1, Perfomances](https://github.com/vb-consulting/blog/discussions/4)

In my previous article, I managed to get some really crazy performances in tree processing by using PostgreSQL recursive procedural-style function.

I wrote a follow-up on yesterday's article on tree processing and recursion with PostgreSQL. This one: https://github.com/vb-consulting/blog/discussions/1

SQL was never intended for this kind of stuff; I'm sure that Fabian Pascal will tell us all about it.

And indeed, recursive CTEs are awful, confusing, and severely limited ... but they look cool and smart, and smart people use them (I hate them).

In any case, I used a procedural approach to this problem and, with a few smart optimizations, managed to squeeze some really spectacular performances (757K tree records with 20K unique nodes in just 5 seconds without any indexes, so it probably can go even faster).