Form of Ready Player One Sequel?

I've just finished a re-read of "Ready Player One"; and I heard tell that Ernie had embarked on writing a sequel... Now before you all start I make the distinction between the film and the book, we are talking about the book.

In fact, those of you who haven't read the book... (Spoiler alert)... It starts out being written as the true story, to set the record straight... Straight up calling the movie out as wrong!  Oh yeah, love that preemptive strike on the Spielberg saga.

Anyway, the sequel eh?... Lets gather around the camp fire and think about this...

It can't be another hunt, we've had a hunt, Z is the man now, we may get a little friction between the members of the high-5 and Z maybe?... But it's going to be about what they find within the folds of the fabric of the Oasis.

Perhaps whether Halliday's Avatar was some form of personality transplant from his real-world body into the Oasis, some form of literal Ghost in the Machine?

I'd like to see some form of digital court, like a war-crimes tribunal, all accounts whom were Sixers being required to justify their existence?  Maybe some form of play on "The Odessa Files" in digital form, with IOI has the continuing evil?


Maybe there's some form of massive community lash back, everyone died on the release of the Cataclysm, Z resurrected the High-5 members, but everyone else was perma-death?



Comments

Post a Comment

Popular posts from this blog

C++ : Ignored qualifiers (-Wignored-qualifiers)

What is an ignored qualifier?  Well, in a class, lets have a student class: #include <string> class Student {     public:         const std::string Name;     private:         bool m_Present;     public:         Student(const std::string& p_Name)             :             Name(p_Name),             m_Present         {         }                 void SetPresent() { m_Present = true; }         void SetAbsent() { m_Present = false; } }; Now, we may want to access the present flag, therefore provide a function to do so:     bool Present() const { return m_Present } This function is telling the user of our class quite a bit, it tells them that the return type is boolean and that the calling of this function makes no changes to the class  contents (const trailing the parameter list). However, for me, this isn't quite right, I believe that we want to inform any user that the boolean returned is also constant, it does not change unless you alter the internal value with the "Set
Read more

C++: The Dilemma of using Exceptions

Image
As a C++ developer I've recently been in the midst of the Exceptions debate.  Exceptions as a feature of the C++ language have long divided the community, naively I've often put this down to their coming to the language from elsewhere (C perhaps) where exceptions were not the norm. This was a mistake, for in the projects I've previously worked upon the overhead of an exception compared to the ramifications of the error resulting in a crash have often totally outweighed the overhead, making deciding to employ an exception exceptionally easy (*bum bum*).  Exceptions were the norm, still are and should be to you too (according to the C++ Core Guidelines https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Ri-except ). The difficulty, the dilemma if you will, comes not from the feature, but the cost.  If you application domain demands high performance you can not risk using exceptions, the argument carries on therefore whether in not using them to avoid
Read more

Development : Anti-Hungarian Notation

Whilst cutting code I employ a coding style, which I enforce, whereby I output the scope of the variable being used with a prefix. "l_" for Local "m_" for Member "c_" for constant "e_" for enum And so forth, for static, parameter and a couple of others.  I also allow compounds of these, so a static constant would be: "sc_" This is useful in many languages, and imperative in those which are not type strict, such as Python. Some confuse this with "Hungarian Notation", it's not.  Hungarian notation is the practice of prefixing a type notification to the variable name, for example "an integer called count" might be "iCount". I have several problems with anyone using Hungarian Notation, and argue against it thus. With modern code completion and IDE lookup tools this is really not needed, with useful and meaningful naming of your variables the type is not needed and finally there are multiple types with the s
Read more