I understand the subjunctive now; it's easy and I'll tell you about it. The problem is that we have been taught to think of it almost literally backwards
For the last couple of weeks I've been studying the uses of the subjunctive intensively for a couple of weeks, wading through inane comments like "it's just something only natives know for sure; to everyone else it is invisible magic" (a very unfortunately common and reductive opinion I've seen around), scouring forums to study how people use it, reading guides and books and the whole thing. Not much seemed to be working; the whole thing still seemed arbitrary, impossible to predict, and totally random. But last night I had a breakthrough, and damn near everything fell into place. I read a few things; I read a great write up on how in spirit English uses the "idea" of the subjunctive mood in various auxiliary verbs from "I think..." to "could", etc, and how it often parallels things in Spanish. I then read through a whole chain of spanishdict questions and answers on the topic, and someone made a comment talking to a new learner who used the indicative in the context of questioning whether or not she had popped a ball when she should have used the subjunctive. His comment was "if you're uncertain that the ball was popped...then why is your next sentence TELLING ME that the ball was popped?" I frowned. "Why would that say that?" I asked myself. "It wasn't as if she was literally telling him that the ball was popped from her perspective, instead she was just...she was...just..." Finally it all hit me; the subjunctive mood makes NO SENSE... on its own. The fatal flaw -- one that comes down to a critical misunderstanding between how english's and Spanish's primary moods operate -- isn't that I didn't understand the subjunctive per se It was that I had no real idea what the hell the indicative mood really was, nor how well-learned Spanish people interpret it to their ears. How could I? Nobody had explained it well to me. EVERYONE only talks about the subjunctive but never the indicative. Because it's obvious, right? It's the same in English as it is in Spanish, right? Let's barely even touch on it when discussing the subjunctive, how could they be related? It's like English, the subjunctive is just a weird thing dangling from under it. No it's not. Guys, the indicative mood is far stronger than english's. It isn't about an implication of rules, it isn't about an implication of concrete reality. It is ABOUT reality, truths, and our perceptions of that truth, directly. There is no implication, it's the outright direct meaning. ANY time we use the indicative, we communicate that what we are saying is a FACT to our perception, and everyone else will hear us like that's what we're saying even if the sentence would imply otherwise; it doesn't act subordinate to the sentence context, so if you use it in the wrong context they crash into each other. This is the key. The subjunctive isn't about being emotional, it isn't about possibilities, it isn't about hypotheticals per se. It is about NOT being the indicative, and literally the only real "rule" to the subjunctive is "do I want to give my sentences a strong meaning of truth, factual declaration, and concrete reality here? Or would that focus hurt my sentence?" The subjunctive is a mood of avoidance. It's used to AVOID the implications of the indicative. It can only properly be understood by contrast to spanish's usage of the indicative mood, and once you properly grasp that it's the easiest thing in the world to see. I was up till 5 am checking all the examples I could find, reading Spanish forums online and all their usages. I couldn't find one that didn't make sense to me anymore, not a single damn one. All those weird irregularities? Sensible. The reasons for why it seems to spread over so many theoretical topics? Sensible. I had done it, I'd cracked the meaning behind things. And regardless of what some people on forums had claimed, it's absolutely not magic or something you can only get by speaking for 10+ years. What it is is simply misexplained by means of being talked about in a vacuum. And with it came a LOT of sudden, cascading realizations about Spanish and how it truly differs from English. I will explain all of this below to help my fellow English-to-spanish people. First off: "Nice catch", you probably think, "but it's so abstract. How does realizing the implications of the indicative mood help me?" Allow me to demonstrate. First off, it must be said that the indicative is way simpler than the subjunctive in terms of its scope. In fact the entire reason why the subjunctive seems to cover so many things in theory is just that it is nothing more and nothing less than a reflection of everything the indicative is not, so covers more topics on paper (even if it's used far less frequently in reality) Like I said, literally all of it makes sense when you just flip things around and denote subjunctive as "that thing that gets called when the STRONG indicative mood would ruin things with its overwhelming presence." We can interrogate sentences in Spanish, piece by piece, and I'll show you exactly how it lines up. Let's take the classical example. "Estoy feliz que estés aqui!" Let's NOT ask ourselves why the subjunctive is here...instead, let's ask ourselves why the indicative ISN'T here. Indicative comes off as -- again, not merely implies like equivalent statements in English but outright states a purpose of -- declaring facts, discussing concrete reality of the here and now, our declarative plans, etc. Can you see why this would be "wrong"? It is in fact not wrong, at all -- it's just incongruous in context. If you said "estas aqui" with the mood that declares facts...well, at best you just announced to them that they are here, carrying the meaning of you wanting to let them know this fact. Rather bizarre under most circumstances, seeing as how they damn well know that they are already here and don't need us to declare this for them! So, normally we won't do it unless in context we really do want to declare this to them for some reason. "Es posible que él es aqui"Let's apply the same process! "Why wouldn't the indicative be good here?" Well let's look at the first half. "Es posible que..." alright so what we say next is possible! And next we say "es aquí". As in, we used the declarative, factual, concrete reality mood. In other words if we used "es" here, we would be outright saying that we firmly believe -- that it is a fact to us -- that this man is here Well if we firmly believed that already, then why the hell did we lead with "it's possible?" This is just an incongruous statement! Therefore, we don't use it like this (unless we really do want to make such an incongruous statement). Talking about an object that doesn't or may exist? Well when you refer to it with the indicative, you DIRECTLY STATE that to you that object might as well be reality. Poetic, but also rather delusional. Therefore, we don't use the indicative. Making conditional plans, like "we will go to the mall once grandma arrives?" If you use the indicative on the latter half, you directly state that her arriving is your reality...even if she hasn't arrived yet. See what I said above about being delusional. And so on and so on. Whenever you are confused about why a subjunctive is used, the proper question is not "why is it here". The proper question is "why is the indicative not here?" It's a subtle difference -- but an important one. What we have to understand is that Spanish is not a neutral-statement language. It is binary. You ARE asserting reality. Or you are not; those are the only options, and to speak in the indicative is to presume to be asserting your interpretation of facts for others to hear. It is not a subtle effect or theory, this is how the spanish-trained brain will unconsciously view your sentences and why it will tell them that 'something' is off about what you said. You indicated to them that you wish to discuss something factual that is in fact not, and their / our-future-brains aren't really sure how to interpret that. In fact, if you aren't already thinking of the indicative in this manner or interpreting sentences with that subtext, it's time to start; that's how the spanish speaking mind will interpret its usage, and if we want to learn this language well we need to interpret it as that as well. Those are the examples off the top of my head. I will now explain why, in terms of the structure of english and spanish, this idea is so hard to get across to native english speakers. This entire effect is a direct contrast to English, which is why it's alien to use until properly explain, and why to native Spanish speakers our confusion is foreign. To both of you -- english-to-spanish students and people who speak spanish first, i will note the following lingual truth that most people don't realize by virtue of not thinking about it: english is a flexible, and often neutral language. Let me repeat that; english is NEUTRAL by default. We DON'T communicate this kind of meaning with our basic sentences, ever. English is like a buffet rather than a binary. Its base forms are almost always implicationless by design specifically so that we can choose to insert auxiliary words to enchant it with such meanings as English speakers please. This is likely also why most of its true subjunctive mood has faded into niche forms; English genuinely has no real need of it with so many ways of putting a sentence together. Spanish, by and large, has 2, and you will not escape from them nor their implications. (Well and imperative, but I'm not talking about it because both of our languages share that one nearly identically in concept). A statement is a statement, indicative is your reality and your attempts to declare facts for others to hear and discuss, and subjunctive is the only way to indicate that what you speak of isn't that. That's it. That's all there is to it. Also, I'll tell all spanish-first readers who happen to read this the same thing i told my Spanish friends irl: you have no idea how confusing the subjunctive is when you are coming from a place where the "primary" prose can imply anything due to a) that being what we think of thanks to English b) most people not going out of their way to firmly correct this misconception. It would be damn near useless and indeed extremely random to perceive in usage if not for its reflections on the indicative, which is different from what we think at first. THIS is why your English speaking friends who are trying to learn Spanish struggle so hard with the concept, while you just know it. (And on the flip, why none of my Spanish-first friends realized the neutrality underlining English until i directly pointed it out to them. A lot of us aren't aware of the underlying mechanics; this is fine going from Spanish to English since English is flexible as hell, but not so much the other way around, unfortunately for us.) Now, after all of this, can I make a request to the general community: can we PLEASE not presume that the subjunctive is magic and that the indicative is so obvious? That kind of common notion is at least in part why a lot of English-to-spanish students wrestle with the concept. For some reason we're often taught (I sure was) that the indicative in Spanish is synonymous with English and to not think more on it in comparison to its bizarre cousin, when in reality the differences between English normal prose and Spanish's indicative are both easy enough to explain and also EXACTLY why the subjunctive exists. Trying to explain how and where to use the subjunctive is like trying to put a car together with a wrench and a few bolts; good luck figuring it out easily with so much essential context missing. Maybe my teachers just didn't think about it? Do people in general not just realize this crucial difference between English's loose neutral structure and Spanish's much stricter and meaning-laden structure? Who knows. And no, realizing this doesn't mean we don't have to practice. I'll forget use cases, not be able to realize when I needed to switch moods until hindsight, etc. I recommend "demystifying the subjunctive" for a book, it helped me out immensely. But at least now we understand it. Learning, as Spanishdude on YouTube says, is just an act of giving context to things we already know, and now we can do that without being lost. It IS a simple and easy to grasp concept at its heart, it's just not usually explained well and requires explaining what precisely is the difference between how english approaches delivering information and how Spanish does. Former is neutral, latter always communicates a meaning. The indicative in particular always imparts a sense of speaking of concrete reality no matter what sentence it happened to be in, and the subjunctive is nothing more than its replacement for when the indicative's strong statements on reality simply don't work with the matters being discussed. Of the two, the indicative is both more strict and also more narrow, and thus the clause of 'use indicative until its determinate attitude of only being used to address factual reality shits the sentence up' reigns best for the quickest and easiest way to conceptually grasp the subjunctive. It is all about the indicative; always has been. Anyway that's all I got. I'm finally going to bed, work will suck tomorrow but oh well, I'm too happy to care. After that I'll...maybe finally learn some decent vocabulary. I'm a heavily grammar based learner, so this was actually one of the first stops on my way through my new language, so I've still got a lot of learning to do. Still, now that i get this, I am much more confident of the rest of the way onward. ---------- Couple of more fun tidbits, if anyone is still reading. I also realized the English conditional is WAY wider than Spanish's, and that this is in part because in English it has come close to replacing separated subjunctive grammar in a lot of cases. If you ever notice how often we through "can" and "could" around, it is in part because of this. I also realized that in a theoretical sense, the "true" purpose of future tense in Spanish is to discuss plans for the future, not to indicate that it will happen. Technically a small detail and probably obvious to most, but for some reason I needed this realization to realize why the subjunctive isn't triggered by its speculation; merely declaring plans is a concrete thing, after all. For some reason in English I get the subtle sense of trying to will over the future when I use it. Might be a slight language difference in intent, or maybe I'm just presumptuous about the future in English. Finally, just a piece of trivia I liked; I realized "to think" and "creer / pensar" aren't really good translations for each other in implication. You ever wondered why it doesn't trigger the subjunctive in a positive usage? This helps to reinforce one last bit; for such things when it comes to certainty vs uncertainty, it's likely just a concept being used slightly differently in Spanish. While they mean literally the same thing, their connotations are nearly inverted. Spanish uses it to affirm that you believe something to be true (hence why it's also translated as to believe), while English uses it to instead imply subjectivity and impart doubt to a clause. It would absolutely be a subjunctive trigger in Spanish if it were transplanted directly since our usage of it in spirit is completely synonymous with Spanish's own usual triggers, but well it isn't. My Spanish speaking colleagues thought that one was interesting in particular for some reason, maybe they didn't really know how i had meant it this whole time?
It's that time of year again, and we've got a new version of macOS on our hands! This year we've finally jumped off the 10.xx naming scheme and now going to 11! And with that, a lot has changed under the hood in macOS. As with previous years, we'll be going over what's changed in macOS and what you should be aware of as a macOS and Hackintosh enthusiast.
Has Nvidia Support finally arrived?
What has changed on the surface
A whole new iOS-like UI
Broken Kexts in Big Sur
What has changed under the hood
New Kernel cache system: KernelCollections!
New Kernel Requirements
Secure Boot Changes
No more symbols required
Broken Kexts in Big Sur
MSI Navi installer Bug Resolved
New AMD OS X Kernel Patches
Other notable Hackintosh issues
Several SMBIOS have been dropped
Extra long install process
X79 and X99 Boot issues
New RTC requirements
Legacy GPU Patches currently unavailable
What’s new in the Hackintosh scene?
Dortania: a new organization has appeared
Dortania's Build Repo
True legacy macOS Support!
Intel Wireless: More native than ever!
Clover's revival? A frankenstein of a bootloader
Death of x86 and the future of Hackintoshing
Getting ready for macOS 11, Big Sur
Has Nvidia Support finally arrived?
Sadly every year I have to answer the obligatory question, no there is no new Nvidia support. Currently Nvidia's Kepler line is the only natively supported gen. However macOS 11 makes some interesting changes to the boot process, specifically moving GPU drivers into stage 2 of booting. Why this is relevant is due to Apple's initial reason for killing off Web Drivers: Secure boot. What I mean is that secure boot cannot work with Nvidia's Web Drivers due to how early Nvidia's drivers have to initialize at, and thus Apple refused to sign the binaries. With Big Sur, there could be 3rd party GPUs however the chances are still super slim but slightly higher than with 10.14 and 10.15.
What has changed on the surface
A whole new iOS-like UI
Love it or hate it, we've got a new UI more reminiscent of iOS 14 with hints of skeuomorphism(A somewhat subtle call back to previous mac UIs which have neat details in the icons) You can check out Apple's site to get a better idea:
A feature initially baked into APFS back in 2017 with the release of macOS 10.13, High Sierra, now macOS's main System volume has become both read-only and snapshotted. What this means is:
3rd parties have a much more difficult time modifying the system volume, allowing for greater security
OS updates can now be installed while you're using the OS, similar to how iOS handles updates
Time Machine can now more easily perform backups, without file inconsistencies with HFS Plus while you were using the machines
However there are a few things to note with this new enforcement of snapshotting:
OS snapshots are not calculated as used space, instead being labeled as purgeable space
Disabling macOS snapshots for the root volume with break software updates, and can corrupt data if one is applied
What has changed under the hood
Quite a few things actually! Both in good and bad ways unfortunately.
New Kernel Cache system: KernelCollections!
So for the past 15 years, macOS has been using the Prelinked Kernel as a form of Kernel and Kext caching. And with macOS Big Sur's new Read-only, snapshot based system volume, a new version of caching has be developed: KernelCollections! How this differs to previous OSes:
Kexts can no longer be hot-loaded, instead requiring a reboot to load with kmutil
OS Snapshots are now verified on each boot to ensure no system volume modifications occurred
apfs.kext and AppleImage4.kext verify the integrity of these snapshots
While technically these security features are optional and can be disabled after installation, many features including OS updates will no longer work reliably once disabled. This is due to the heavy reliance of snapshots for OS updates, as mentioned above and so we highly encourage all users to ensure at minimum SecureBootModel is set to Default or higher.
Note: ApECID is not required for functionality, and can be skipped if so desired.
Note 2: OpenCore 0.6.3 or newer is required for Secure Boot in Big Sur.
No more symbols required
This point is the most important part, as this is what we use for kext injection in OpenCore. Currently Apple has left symbols in place seemingly for debugging purposes however this is a bit worrying as Apple could outright remove symbols in later versions of macOS. But for Big Sur's cycle, we'll be good on that end however we'll be keeping an eye on future releases of macOS.
New Kernel Requirements
With this update, the AvoidRuntimeDefrag Booter quirk in OpenCore broke. Because of this, the macOS kernel will fall flat when trying to boot. Reason for this is due to cpu_count_enabled_logical_processors requiring the MADT (APIC) table, and so OpenCore will now ensure this table is made accessible to the kernel. Users will however need a build of OpenCore 0.6.0 with commit bb12f5for newer to resolve this issue. Additionally, both Kernel Allocation requirements and Secure Boot have also broken with Big Sur due to the new caching system discussed above. Thankfully these have also been resolved in OpenCore 0.6.3. To check your OpenCore version, run the following in terminal: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version If you're not up-to-date and running OpenCore 0.6.3+, see here on how to upgrade OpenCore: Updating OpenCore, Kexts and macOS
Broken Kexts in Big Sur
Unfortunately with the aforementioned KernelCollections, some kexts have unfortunately broken or have been hindered in some way. The main kexts that currently have issues are anything relying on Lilu's userspace patching functionality:
Big Sur dropped a few Ivy Bridge and Haswell based SMBIOS from macOS, so see below that yours wasn't dropped:
iMac14,3 and older
Note iMac14,4 is still supported
MacPro5,1 and older
MacMini6,x and older
MacBook7,1 and older
MacBookAir5,x and older
MacBookPro10,x and older
If your SMBIOS was supported in Catalina and isn't included above, you're good to go! We also have a more in-depth page here: Choosing the right SMBIOS For those wanting a simple translation for their Ivy and Haswell Machines:
iMac13,1 should transition over to using iMac14,4
iMac13,2 should transition over to using iMac15,1
iMac14,2 and iMac14,3 should transition over to using iMac15,1
Note: AMD CPUs users should transition over to MacPro7,1
iMac14,1 should transition over to iMac14,4
Currently only certain hardware has been officially dropped:
"Official" Consumer Ivy Bridge Support(U, H and S series)
These CPUs will still boot without much issue, but note that no Macs are supported with consumer Ivy Bridge in Big Sur.
Ivy Bridge-E CPUs are still supported thanks to being in MacPro6,1
Ivy Bridge iGPUs slated for removal
HD 4000 and HD 2500, however currently these drivers are still present in 11.0.1
Similar to Mojave and Nvidia's Tesla drivers, we expect Apple to forget about them and only remove them in the next major OS update next year
Due to the new snapshot-based OS, installation now takes some extra time with sealing. If you get stuck at Forcing CS_RUNTIME for entitlement, do not shutdown. This will corrupt your install and break the sealing process, so please be patient.
X79 and X99 Boot issues
With Big Sur, IOPCIFamily went through a decent rewriting causing many X79 and X99 boards to fail to boot as well as panic on IOPCIFamily. To resolve this issue, you'll need to disable the unused uncore bridge:
With macOS Big Sur, AppleRTC has become much more picky on making sure your OEM correctly mapped the RTC regions in your ACPI tables. This is mainly relevant on Intel's HEDT series boards, I documented how to patch said RTC regions in OpenCorePkg:
For those having boot issues on X99 and X299, this section is super important; you'll likely get stuck at PCI Configuration Begin. You can also find prebuilts here for those who do not wish to compile the file themselves:
For some reason, Apple removed the AppleIntelPchSeriesAHCI class from AppleAHCIPort.kext. Due to the outright removal of the class, trying to spoof to another ID (generally done by SATA-unsupported.kext) can fail for many and create instability for others. * A partial fix is to block Big Sur's AppleAHCIPort.kext and inject Catalina's version with any conflicting symbols being patched. You can find a sample kext here: Catalina's patched AppleAHCIPort.kext * This will work in both Catalina and Big Sur so you can remove SATA-unsupported if you want. However we recommend setting the MinKernel value to 20.0.0 to avoid any potential issues.
Legacy GPU Patches currently unavailable
Due to major changes in many frameworks around GPUs, those using ASentientBot's legacy GPU patches are currently out of luck. We either recommend users with these older GPUs stay on Catalina until further developments arise or buy an officially supported GPU
What’s new in the Hackintosh scene?
Dortania: a new organization has appeared
As many of you have probably noticed, a new organization focusing on documenting the hackintoshing process has appeared. Originally under my alias, Khronokernel, I started to transition my guides over to this new family as a way to concentrate the vast amount of information around Hackintoshes to both ease users and give a single trusted source for information. We work quite closely with the community and developers to ensure information's correct, up-to-date and of the best standards. While not perfect in every way, we hope to be the go-to resource for reliable Hackintosh information. And for the times our information is either outdated, missing context or generally needs improving, we have our bug tracker to allow the community to more easily bring attention to issues and speak directly with the authors:
Kexts here are built right after commit, and currently supports most of Acidanthera's kexts and some 3rd party devs as well. If you'd like to add support for more kexts, feel free to PR: Build Repo source
True legacy macOS Support!
As of OpenCore's latest versioning, 0.6.2, you can now boot every version of x86-based builds of OS X/macOS! A huge achievement on @Goldfish64's part, we now support every major version of kernel cache both 32 and 64-bit wise. This means machines like Yonah and newer should work great with OpenCore and you can even relive the old days of OS X like OS X 10.4! And Dortania guides have been updated accordingly to accommodate for builds of those eras, we hope you get as much enjoyment going back as we did working on this project!
Intel Wireless: More native than ever!
Another amazing step forward in the Hackintosh community, near-native Intel Wifi support! Thanks to the endless work on many contributors of the OpenIntelWireless project, we can now use Apple's built-in IO80211 framework to have near identical support to those of Broadcom wireless cards including features like network access in recovery and control center support. For more info on the developments, please see the itlwm project on GitHub: itlwm
Note, native support requires the AirportItlwm.kext and SecureBootModel enabled on OpenCore. Alternatively you can force IO80211Family.kext to ensure AirportItlwm works correctly.
Airdrop support currently is also not implemented, however is actively being worked on.
Clover's revival? A frankestien of a bootloader
As many in the community have seen, a new bootloader popped up back in April of 2019 called OpenCore. This bootloader was made by the same people behind projects such as Lilu, WhateverGreen, AppleALC and many other extremely important utilities for both the Mac and Hackintosh community. OpenCore's design had been properly thought out with security auditing and proper road mapping laid down, it was clear that this was to be the next stage of hackintoshing for the years we have left with x86. And now lets bring this back to the old crowd favorite, Clover. Clover has been having a rough time of recent both with the community and stability wise, with many devs jumping ship to OpenCore and Clover's stability breaking more and more with C++ rewrites, it was clear Clover was on its last legs. Interestingly enough, the community didn't want Clover to die, similarly to how Chameleon lived on through Enoch. And thus, we now have the Clover OpenCore integration project(Now merged into Master with r5123+). The goal is to combine OpenCore into Clover allowing the project to live a bit longer, as Clover's current state can no longer boot macOS Big Sur or older versions of OS X such as 10.6. As of writing, this project seems to be a bit confusing as there seems to be little reason to actually support Clover. Many of Clover's properties have feature-parity in OpenCore and trying to combine both C++ and C ruins many of the features and benefits either languages provide. The main feature OpenCore does not support is macOS-only ACPI injection, however the reasoning is covered here: Does OpenCore always inject SMBIOS and ACPI data into other OSes?
Death of x86 and the future of Hackintoshing
With macOS Big Sur, a big turning point is about to happen with Apple and their Macs. As we know it, Apple will be shifting to in-house designed Apple Silicon Macs(Really just ARM) and thus x86 machines will slowly be phased out of their lineup within 2 years. What does this mean for both x86 based Macs and Hackintoshing in general? Well we can expect about 5 years of proper OS support for the iMac20,x series which released earlier this year with an extra 2 years of security updates. After this, Apple will most likely stop shipping x86 builds of macOS and hackintoshing as we know it will have passed away. For those still in denial and hope something like ARM Hackintoshes will arrive, please consider the following:
We have yet to see a true iPhone "Hackintosh" and thus the likely hood of an ARM Hackintosh is unlikely as well
There have been successful attempts to get the iOS kernel running in virtual machines, however much work is still to be done
Apple's use of "Apple Silicon" hints that ARM is not actually what future Macs will be running, instead we'll see highly customized chips based off ARM
For example, Apple will be heavily relying on hardware features such as WX, kernel memory protection, Pointer Auth, etc for security and thus both macOS and Applications will be dependant on it. This means hackintoshing on bare-metal(without a VM) will become extremely difficult without copious amounts of work
Also keep in mind Apple Silicon will no longer be UEFI-based like Intel Macs currently are, meaning a huge amount of work would also be required on this end as well
So while we may be heart broken the journey is coming to a stop in the somewhat near future, hackintoshing will still be a time piece in Apple's history. So enjoy it now while we still can, and we here at Dortania will still continue supporting the community with our guides till the very end!
Getting ready for macOS 11, Big Sur
This will be your short run down if you skipped the above:
Lilu's userspace patcher is broken
Due to this many kexts will break:
WhateverGreen's DRM and -cdfon patches
Many Ivy Bridge and Haswell SMBIOS were dropped
See above for what SMBIOS to choose
Ivy Bridge iGPUs are to be dropped
Currently in 11.0.1, these drivers are still present
For the last 2, see here on how to update: Updating OpenCore, Kexts and macOS In regards to downloading Big Sur, currently gibMacOS in macOS or Apple's own software updater are the most reliable methods for grabbing the installer. Windows and Linux support is still unknown so please stand by as we continue to look into this situation, macrecovery.py may be more reliable if you require the recovery package. And as with every year, the first few weeks to months of a new OS release are painful in the community. We highly advise users to stay away from Big Sur for first time installers. The reason is that we cannot determine whether issues are Apple related or with your specific machine, so it's best to install and debug a machine on a known working OS before testing out the new and shiny. For more in-depth troubleshooting with Big Sur, see here: OpenCore and macOS 11: Big Sur
A non-D&D game you *need* to play: Ironsworn (FREE)
Why you need to play Ironsworn:
Ironsworn is a Viking themed low fantasy game it's completely FREE and you can play it in a group, with or without a GM or completely solo.
It has a highly customizable, modular setting.
It has a streamlined and elegant system that focuses on the narrative whilst still being deep and robust.
There are no classes, characters are created freely by mixing and matching modular thematic abilities.
The combat system is fast, dramatic and full of tension.
The game requires absolutely 0 prep, the rules and random tables how you make a satisfying game with no prior prep
It can be played completely alone or in a group with or without a GM. The games rules and random tables ensure that even without a GM it still goes in interesting directions you could never anticipate.
And it's COMPLETELY FREE.
I give the game a glowing recommendation and if that's enough for you here is the link. For those of you who need more details, I go into them below...
SETTING Ironsworn is set in the Ironlands, a gritty low fantasy wild frontier. The Ironlanders settled here a few generations ago after a cataclysm drove them out of the Old World. The Ironlander live in small settlements and villages or nomad and are constantly threatened by the things that lurk in the dark. You are an Ironsworn, one of the few people brave enough to venture wild for glory and adventure. The setting is fully customizable. There is a setting book that comes with pages on major setting elements like "communities" "religion" or "magic". These pages have 3 different options for what to do with the set element as well as a plot hook to go with it. You can choose one of these options or create your own using the setting elements as guidance. Creating a setting is quick, easy and engaging. PLAYER CHARACTERS You are an Ironsworn, a badass adventurer that travels the land fulfilling oaths called "Iron Vows." The game is human-centric, it assumes you are human but you can choose to flavour your character as a different race. Character creation is freeform, characters are made out of stats and assets. Stats: There are 5 stats: Iron (stcon), Edge (dex), Wits (wis/int), Shadow (stealth/deception), Heart (cha). Assets: PC's start with 3 assets. Assets are cards with 3 abilities tied to a specific theme, you start with one of these abilities marked and can spend XP to gain more of an asset's abilities or get new entirely (there are 70+ assets to choose from). These abilities generally aren't just number bonuses they are meant to give your more gameplay options or make you feel more like your character. A few example assets: Alchemist, Infiltrator, Archer, Swordmaster, Cave lion companion, Raven Companion, Divination ritual, Awakening ritual. CORE MECHANICS The game revolves around the action roll when you do something risky you roll 1d6 +stat vs 2d10s.There are 3 different results to a roll, unlike D&D binary system. If the d6 is higher than both d10s then you succeed, if it's only higher than 1d10 you succeed but at a cost or consequence, if it isn't higher than either then you fail and something bad happens. If you roll the same number on both d10's then its a critical success or failure. Only the PC's roll, how NPC's react depends on the result of your roll. The game gives you specific guidance on what to do through a system called moves. Moves are a chunk of rules that tell you how to resolve a specific part of the game, like fighting or compelling people to do what you want. Moves give you specific guidance on how to resolve the situation in an interesting way based on the result of your roll and often give you choices on how you would like to move the story forward. SOLO / GMLESS PLAY EXPLAINED You can play Ironsworn with a GM, with multiple players and no GM or completely alone. Playing without a GM just works, everything about the game's rules facilitate GMless play. The moves substitute for a GM by pushing the story in interesting and unexpected directions, and the game features many random tables to roll on if you get stuck. You won't even feel the GM's absence. COMBAT Combat is fast fluid and dramatic and it places a heavy emphasis on tension. It is nothing like D&D wargame-like combat system. There no, turn order or action economy or complex rules. Combat flows like a movie scene, you describe your action, you trigger a move and roll dice then depending on your role the enemies react appropriately. The combat system is designed to create quick, adrenaline and dynamic fights. A fight that could take an hour or more in D&D could take 10-15 minutes in Ironsworn and be just as compelling if not more. Ironworn's combat is nothing like D&D's slow tactical combat, but It is still filled with depth and meaningful decisions. You also don't have to have to worry about NPC stat blocks, an entire encounter can be designed on the fly. SEEING THE GAME IN ACTION Ironsworn is likely, unlike any game you've played before, so you may need to see it in action before you fully understand it. If you want an in-depth reading of the rules I recommend Adam Koebel's "Ironsworn First Look." If you want to an actual play of the game I recommend "Ask the Oracle," it's an actual play podcast made by the game's designer Shawn Tomkin and I also recommend the youtube series "Me Myself and Die" season 2 by Trevor Devall, (you don't need to watch season 1 first.) Thanks for reading those post I really hope you give my favourite game a try :)
Is nice to see that we have users from all around the world, even if nearly 50% are from English speaking countries. Image 1.
How old are you?
The average age of a /OnePiece user is 23.62 years old. We have roughtly 10% of users that are underaged, and 10% that are 30 years old or more. Image 2.
There is no surprise there. For the others, we have some Gender Fluids, transgenders, Bigenders, quite a lot of Non-binary, a Loli, a Furry, and nearly a 100 Oden (You wish), as well as some rude people, but I won't put up what they said.
Manga or Anime?
No real surprise here either. Considering the subreddit has a lot of spoilers and is focussed around the chapter release, it's obvious there are only a few Anime Only people here. So thank you for Sticking Around, even if it the best place to avoid spoilers.
For approximately how long have you been following One Piece?
1 Year or less
10 years or more
Nearly 40% of our users have followed the series for 10 years or more. (To give an idea, this mean they followed the series since Before the timeskip, as chapter 597 was released at the end of August 2010). For the rest, we have roughly the same number of new readers that stays with the series. So it's quite good to bring new blood and not have a decrease of new readers.
Where does One Piece rank on your list of favorite manga?
Bellow Top 10
Well, you are in /OnePiece after all. So it's kinda obvious the manga is either your favorite or in your top 3. If it isn't your number 1, what series are better than One Piece for you?
Do you own One Piece Merchandise?
Those are some good numbers I would say, 55.8% of users have some merchandise and are probably supporting the series (depending on where you bought those) For the OTHERS answers given, some good ones are : autograph from dub VA of brook, Alvida pre devilfruit bodypillow, Chopper teddy bear, Sountracks, Custom made and 3D printed Keychain, Databook.
Subreddit Section :
Do you visit OnePiece mostly on mobile or on desktop?
Mobile or Apps
If you are using desktop, are you using the old version of reddit? Or the redesign?
It seems like most users are using Mobile and Apps, as well as the redesign on desktop, so it's probably time to pay more attention to that than to the old version, this way we can get banners/flair for users that are on the new version of reddit.
How often do you make : a submission on OnePiece?/Comment?/read the rules?
Very often (Daily)
Very often (Daily)
Check the rules :
Very often (Daily)
This really shows that there are a lot of lurkers on the subreddit. Most of you won't ever post or comment on the subreddit. With 8% of users creating submission and 25% commenting. As for the rules, there isn't any surprise since nearly every post respect the rules. (Only 1/5 of the post needs to be removed), so thank you to all of those that read them.
Content you enjoy the MOST/the LEAST.
Content you enjoy the most :
Media (Photo and Video)
So without surprise, people in this subreddit enjoy the Theories/discussions the most out of every type of post, it's then followed by the Fanarts. Which is good since like 75% of posts made are Discussion (50% total)/Fanarts (25% total). Content you enjoy the least:
Here there aren't any content that most users enjoy the least, but it still seems like users don't want to see that much Merchandise or Cosplay post. (Youtuber video are very rare) Also, a quick reminder, Discussion/Theories are mostly found by sorting by New. This is where you will see all of them, as it's hard for them to show up on the front page of the subreddit (but if it shows up on Hot, then it's a very good one).
Do you only use the subreddit for the Spoiler and Chapter Discussion thread?
It's nice to see that roughly 2/3 of the users are here for more than just the Spoilers and Chapter discussion. But there is still a huge part that only use the subreddit for that.
Do you want the spoilers gone from this subreddit?
As it was expected, Luffy is the Favorite Straw Hat for a lot of peopel, he's also the Straw Hat with the fewest "Least Favorite". After him Zoro is second favorite, followed by Sanji, Robin, Usopp, Brook, with the other Straw Hat having very few votes (and Nami having the Least "Favorite" Straw Hat.) After that, it seems like Chopper, Usopp, and Franky are the one people like the least out of the Straw Hat. I know it was a hard question for some of you, but the result are still interesting to know.
Which Strawhat has the saddest backstory?
The Straw Hats with the saddest backstory is Robin! Followed by Brook, then Sanji, Chopper and Nami.
What is your favorite Yonko crew?
So the favorite Emperor's crew are the Red Hair Pirate! Which is very impressive since we haven't seen much of them. I guess Oda better delivers when it come to see them in action after Wano.
Who is your favorite Admiral?
While Garp was only a Vice Admiral, he was put in the poll, and he won it! Whitout him, it's Aokiji that is the favorite, followed by Fujitora. Image 4
Who is your favorite Supernova (outside the Straw Hat)
Who else than the character that nearly managed to defeat Luffy in the 5 popularity poll? Law is the Favorite Supernova outside of the Straw Hat!
Which is your favourite canon arc in One Piece?
The Favorite Canon Story arc are (You could vote for more than 1) :
Which is your least favourite canon arc in One Piece?
The Least Favorite Canon Story arc are (You could vote for more than 1) :
Long Ring Long Land Arc
Favorite Cover Story?
Enel's Great Space Operations
From the Decks of the World : "The 500.000.000 Man Arc"
The Stories of the Self-Proclaimed Straw Hat Grand Fleet
Ace's Great Blackbeard Search
Straw Hat's Separation Seria
Character Design in One Piece :
Do you like the female character designs in One Piece?
I have no opinion.
Do you like the male character designs in One Piece?
I have no opinion.
It's true that Oda isn't the best when it comes to Female character design. However it seems like the majority of users don't have a problem with that.
Are fight a determining factor for your enjoyment of the series/arc?
Now this is rather surprising I must say. What do ou thing about this?
What is/are your (absolute) favourite aspect(s) of One Piece?
From the result we have, it seems like the World-Building is the favorite part of One Piece (With 88.6% of voters choosing this). It's followed by The Adventure (69%), The characterization (54.4%), the Inter-character relationship (49.4%), the Action (36%) and the Art Style (26.2%). And those result are obvious. Some of the most upvoted chapters of this subreddit are when we have huge world building moment, like 907 (Shanks talks to the Elders), or 957 (ULTIMATE).
On Par with Pre-TS
Better than Pre-TS
Worse than Pre-TS
This question is one of the most asked. With a lot of vocal voices saying that post TS is worse than Pre-TS. It's different for sure, but now we know how the community feels about that.
If you could eat a Devil Fruit, what type would you want?
Most people could choose to eat a Logia, and it seems like becoming a Furry is the lesser choice in this subreddit.
The Final Antagonist of One Piece will be :
With 48.5% it's Blackbeard! Really? That is surprising for me since it's obvious that Oda will make the SH fight against the World Government after they find the One Piece. And I honestly don't see Blackbeard being the final Antagonist because of that. So people who voted for this, what was your reasoning for it?
What is One Piece Biggest Flaw?
Some of the biggest flaws mentionned are :
The Lack of characters' death outside of Flashback
Which are all fair flaws to the series.
Random Questions about the Series :
As of Wano, is Jimbei stronger than Zoro?
Yes but Zoro will be stronger soon
I guess people really want Zoro to always be the second strongest no matter what... I expected this result, but I was still disappointed...
Was Zoro as strong as Luffy just after the timeskip?
I... Really? 31.5% said yes?
Will Sanji get laid by the end of the story?
Nearly the perfect split, and it's easy to see why it's very divisive. (Also shows that every vote counts).
Will Usopp be part of the 1 Billion Club by the end of the story?
The Straw Hats will go to Laugh Tales :
Before fighting the WG
After Fighting the WG
It's been hinted at a lot that the SH will go to Laugh Tales before taking on the WG. So for me it feels rather strange to have more than 1/4 voting for them reaching the final island after.
Who will be the one to defeat Kaido? (So give the last hit)
With 66.3% of the votes the one who will give the last hit to Kaido is : Luffy! Followed by 11.5% with someone else (that isn't Law/Kid/Zoro/Big Mom/Scabbard/Admiral) and 11% by one of the Scabbard. Zoro received 6.4% of the votes.
Who will be the first SH to realize their dream?
Most users believe that Usopp will be the first one to realize his dream! I also think the same as it's the easiest Dream to realize really. I could bet you it will happen in Elbaf. After that, we have Luffy and Robin, and it make sense since their dreams are linked. Both can be done once they reach Laugh Tales.
How many members will the crew have at the end? (With Luffy)
And most people want 11 members total in the crew! (With 28.6%), 27.5% wants 12 members, wile 19.8% want the crew to be complete right now with Jinbe.
Who do you think wins in a 1v1 : An Emperor or an Admiral?
If you are active on the subreddit, you know it's one of the question that creates the most discussion/arguments about. So it's nice to know the overall opinion of the subreddit on this question (Doesn't mean it's always correct mind you).
Is Mihawk emperor's level?
Also a very divisive question on this subreddit.
Is Aokiji emperor's level?
Is Akainu emperor's level?
So they fight for 10 days in a very close battle. With Akainu winning in the end, but after a long and hard fight. And one is Emperor's level while the other isn't? Really? I find that hard to understand.
If Oden was alive would he be stronger than Mihawk
How strong was Oden at the time of his death?
< Top 20
I like Oden, but sometimes I feel like people are overestimating him.
Who is stronger between Shanks and Mihawk?
This is also one of the question creating the most arguments on this subreddit, after all Mihawk is the World Strongest Swordman. But Shanks is an Emperor and became one after losing his arm.
Is Kaido stronger now that 20 years ago?
Yes, he's stronger
Had Ace survived, would Wano be liberated by now?
Could the Marines take on ALL the Yonko at the same time ?
Yes in Marineford only
2 at the same time
3 at the same time
This question is also linked to how you see the Emperor vs Admiral. So depending on which side you are on, you are more likely to pick Yes or No.
Which character do you want focus on next?
All very good choices, and all of them are character we have known for a long time without really knowing.
Will Blackbeard find the One Piece before Luffy?
How strong is Monkey D. Dragon?
< Top 10
Here, most people seems to think that Luffy's father, Garp's son is part of the strongest characters of the series. Oda better respond to our expectations then. As for his Bounty : Well, 31.6% think it will be more than 6 Billions and 28.1% think it will be between 5-6 billions. That remind me, I once made a poll asking people what Sabo's bounty would be (since we knew it was getting revealed in a magazine soon). So maybe I will do the same for Dragon? That could be nice.
Who is currently the strongest Emperor?
I wonder if the recent chapters made people change their perception on this...
What are the fights you would want to see?
Blackbeard vs Shanks
Garp vs Rocks
Garp vs Roger
Mihawk vs Shanks
Akainu vs Aokiji
How long do you think One Piece has left? (At a rate of 40 chapters a year)
Image 5. As you can see, most people think One Piece has at least 5 years left to go on. We will know Oda is terrible with respecting his own objectives. And this is good. The more One Piece the better.
On a scale from Spandam to Whitebeard/Roger, How strong is Im?
For this question, it seems like most people put Im at the same level as Whitebeard/Roger with 28.6% voting Im being there. I honestly don't know how strong I want Im to be.
What arcs, after Wano, do you want?
The arcs people want the most are :
The Final War
Red Hair Pirates
So arcs teased for years (Elbaf/Laugh Tales/Final War) and about character that people want to see (Vegapunk/Red Hair pirates).
How is Blackbeard able to use multiples Devil Fruits?
More than 1 soul
It's one of those question were people have very different opinion about. And right now there isn't really a major concensus in the fandom, even if the theory about it being related to the Yami Yami is more popular. In the Other catergory, there was the Cerberus Devil Fruit option, Blackbeard being a Triplet, him being actually 2+ kids in a trenchcoat, him being a failed Vegapunk experiment, having several stomachs him being pregnant (Stop reading fanfiction), him putting the power inside his rings, being a great guy and him being a cunt.
Haki is :
Image 6 Overall, People like Haki in the series, with a 4.38 out of 5!
How many arcs are left after Wano?
Image 7 Here, it seems like the answer for the community would be 4-5 arcs left. Which would then make (base don the How long One Piece has left), like a year per arc on average.
The final war of One Piece will be :
SH+RA vs WG+Marines vs BB
SH+RA vs WG+Marines
SH vs RA vs WG
I just don't see Blackbeard being in the final war, as my opinion is that he will be dealt with before it. For the other answers, there was Straw Hats vs Blackbeard Pirates, Family of D vs vs im sama, Total civil war in marines, Straw Hat vs Shanks, Straw hat vs Pound, Zoro vs World Goverment, Dugongs vs buggy.
Will Luffy die at the end of One Piece?
Will Luffy die?
An ending were Luffy died wouldn't be a good ending for me. He needs to survive and go on more adventures.
Are Shakky and Rayleigh Mihawk's parent?
Will the crew still be together at the end of the series?
Yes, they will keep going on adventure together.| 57.6% o, they will move on, like the Roger Pirates| 42.4% Like with Luffy living, I want the Crew to stay together, and sail together for many more adventures. I could see them taking breaks from time to time, but them staying together would be the best ending for me.
Can the Red Line be destroyed with Ancient Weapons?
What is the biggest mystery left to be revealed?
The most common answers were : The Void Century, the Will of D, Im, The One Piece, Joy Boy, Luffy's mother and Who is Pandaman?
What is the One Piece?
Here, there was plenty of : "No idea", The friends we made along the way, a Devil Fruit, Knowledge, Uranus, History, a book, my mom.
What sort of Devil Fruit do you want to see in the story?
The most common answer was : Water Logia! Followed by Wind Logia and people wanting more mythical Zoans.
What is the craziest theory you believe?
Here are a few of them :
Shanks is a Celestial Dragon
That Vegapunk is going to flip a switch in the Pacifista programming to fight the marines at the end.
Luffy's mom was a celestial dragon
Devil fruits are all artificial from the void century
That Finland doesn't exist
Zoro is going to get Rodger's disease
D's were the original Celestial Dragons
Weevil was made by Vegapunk using Whitebeard's cells and then was discarded until Bakkin picked him up
One of the Roger Pirates (probably Scopper Gaban) is on Laugh Tale waiting for whoever finds it, sort of like how Crocus and Rayleigh seem to be positioned to monitor rookie pirates
Onigashima is an Oarz like skeleton and Big Mom is gonna bring it to life.
The different races came from other planets/moons
Tama is a Kurozomi
Ussop is a descendant of Mont Blanc Nolan
Luffy hatched from an egg.
The fish that bit Shanks's arm off was Joyboy's pet
Bon chan is Kin'emon's son
Oda no longer draws the manga
bonney and ace having a child
That Perospero is going to help kill Big Mom.
Dragon being former Admiral
What are your favorites? And here it is, the 500K survey! Took me far too long to make, as I underestimated the time needed to sort the answer and create this post. Like damn. I hope you enjoyed it. The anwers for the Survey Saga will be up next in some time.
I wanted to share this post I found in this subreddit from around 4 years ago. I have tried at least 10 different videos, 2 books, and 2 Udemy courses and IPv4 Subnetting made no f***ing sense to me. I didn't want to memorise a table, especially as I only have an option to take my CCNA test at home and Pearson doesn't allow writing on paper when testing at home. This is simple enough to do in a matter of seconds, as long as you can memorise the powers of 2 up to a power of 8. (2, 4, 8, 16, 32, etc.) (I copied and pasted the comment as the embedding didn't work. Credit goes to u/dalgeek) -------------------------------------------------------------------------------------------------------------------------- "No idea, but it looks overly complicated. The most important thing to remember about subnetting is that networks always fall on binary boundaries, so multiples of 1, 2, 4, 8, etc. If someone gives you CIDR notation it makes things really easy: 10.10.10.57/28. 32 - 28 = 4 bits for hosts, 24 = 16 What multiple of 16 is closest to 57 without going over? 48, so the network address is 10.10.10.48 and the broadcast is 10.10.10.63 (48 + 16 - 1) It gets a little more tricky when you cross octets, like 10.10.57.10/21. As as shortcut you can just ignore the last octet and pretend you're only dealing with 3 bits (the last octet is all 0s). 23 = 8, the multiple of 8 closest to 57 without going over is 56, so your network is 10.10.56.0 and broadcast is 10.10.63.255 (56 + 8 - 1 = 63) Now let's reverse it. You need a network in 192.168.10.0/24 that contains 17 hosts. The smallest binary boundary that is larger than 17 is 32, which is 25 , 32-5 = 27, so 192.168.10.0/27 can be a network, and if you keep adding 32 you can use 192.168.10.32/27, 192.168.10.64/27, etc. As for translating between network mask and CIDR, that is pretty easy. For a CIDR of /26, you do
32 - 26 = 6 2^6 = 64 255 - 64 + 1 = 192
So your network mask is 255.255.255.192. You add the 1 here because when you're counting boundaries you include the number you start on. For a CIDR of /17, you do the same as above where you ignore the last octet because they're all 0s.
24-17 = 7 2^7 = 128 255 - 128 + 1 = 128
The last octet is all zeros so the network mask is 255.255.128.0 Hope that's not too confusing!" -------------------------------------------------------------------------------------------------------------------------- If you're having as much an issue with IPv4 subnetting as I was, I recommend this method and practising along with this link: https://subnetipv4.com/ I hope this helps everyone, and happy testing!
There's been some discussion on Mikasa in the sub lately, both positive and negative, and it's led me to think a bit more about her character. In particular, I've been thinking about her character flaw, what it is exactly, and whether or not she's developed past it – and if she has, what that means for her in the final arc. Isayama once said that Mikasa is a character who 'expresses herself via actions and facial expressions quite a lot'. I sometimes feel that that's why a lot of her personal story gets overlooked – because she's not loud about it, and nor is anyone else. She's one of the most reticent characters in the manga and, more importantly, deliberately written that way. It's intentional on Isayama's part for Mikasa to mostly 'express herself via actions and facial expressions', and so, as difficult as it might be to follow, that's mostly how her personal journey is told. Because she doesn't say much, talks a lot with her fists, and is the team's natural and aggressive protector, it's easy to assume that there's nothing more happening there. Isayama clearly doesn't mean for readers to overlook her, but some inevitably do because she's not as obvious and outspoken as other characters. She's not like Eren, whose dissatisfaction with the world drives him to continuously push back, or like Armin, whose self-doubt and fear of responsibility constantly battle with his natural intelligence and sense of duty. She doesn't outwardly appear to suffer from the neuroses that afflict a lot of the others in the main cast. As a result, her development as a character isn't easy to track. Where does it start? Where does it end? What even is it? It's fair to ask, in Mikasa's case, whether she even has a character arc to begin with. What changes about her? Does she actually react in any way to her experiences and evolve as a result of them, or does she remain the same from beginning to end?
Fans' opinions on Mikasa's character are often based on her feelings for Eren and the actions she undertakes to protect him. It irks some readers that Eren is Mikasa's priority, and that her life seems to revolve around him. Because they consider this her character flaw, they expect that her character development is going to rectify this flaw; that she'll move away from Eren, whether physically, emotionally, or mentally, and find something else to live for. In a 2016 interview, Isayama said: 'Mikasa's growth probably involves separation from Eren'. People generally stop at that and go from there – they either believe that Mikasa can't grow as a person unless Eren stops being important to her, or that a Mikasa who isn't separated from Eren (emotionally, mentally, or physically) is inherently a flawed character. Isayama's explanation of the 'separation' he means is never usually discussed, even though he actually does go on to clarify it: 'Mikasa's growth probably involves separation from Eren. By separation, I mean she might be able to return to that ordinary girl that she used to be in childhood'. If the all-important 'separation' for her growth is about Mikasa returning to the 'ordinary girl' she used to be, it's worth asking what isn't ordinary about the girl Mikasa became, and when that change happened. And once that 'non-ordinary' quality about Mikasa becomes apparent, it can be identified as Mikasa's flaw; the deficiency in her character that we can expect her to overcome. Mikasa loving someone or wanting to protect them isn't in itself a flaw. It's a fairly ordinary, reasonable thing, and it's something plenty of other characters already display in the story: Franz wants to protect Hanna; Ymir, Historia; Eren, Mikasa; Kenny, Uri; Levi, Erwin, and so on ad infinitum. There's a reason that Mikasa's love for and general protectiveness towards Eren never changes. It's because it's not something she was ever meant to 'grow past' or 'get over'. It was never her flaw. Her flaw is fear. Mikasa's overprotectiveness of Eren is what isn't 'ordinary', because it's connected to her deep, abiding fear of loss. Her desire to constantly stay by him is pitiful because, above all else, it represents her fear and her mistrust of the world. And it's why her 'separation' from him is about more than just 'Mikasa finds something else to do apart from care about Eren'; it's a return to her being 'the ordinary girl of her childhood': a normal girl who isn't constantly fixated on how the people she loves can die at any moment: https://preview.redd.it/gpraaqxt1sq51.jpg?width=750&format=pjpg&auto=webp&s=dbcb1a366ae0b26f287143aa4d7e916d1c7b3c49
When Levi says they'll focus on one objective and that won't include outright killing Annie, Mikasa's one objection is: 'How many of our comrades has she murdered?' Mikasa has no problem being straightforward with Levi. If her first and only consideration was Eren, she'd voice it. She'd even get away with it, because they all need Eren at this point. But instead, she reveals that she has a separate, personal desire: avenging their dead. Mikasa wants to kill Annie for her own reasons.
Levi states that their goal is to retrieve Eren. He gives himself the main role of 'slash[ing] away' at the titan, meaning that he will be the one to actually save Eren, who is in the titan's mouth. And he gives Mikasa the job of distracting Annie. Mikasa accepts asecondary role in a planthat isspecificallyto rescue Eren.
And when she does break from the plan, it's not so she can go and get Eren herself. Mikasa risks the objective of the mission – and Levi, and Eren – by going in for the kill. Mikasa risks the plan to save Eren by acting on her own desire to kill Annie.
Two important shifts take place here for Mikasa. One, she entrusts Eren to someone else, as demonstrated by her action of allowing Levi to take the lead. Two, her focus stops being, even for a short while, Eren – as confirmed by her facial expression when Levi challenges her on it, because she doesn't seem to immediately realise she's even capable of that: The objective was: Forget killing the Titan. Rescue Eren. And Mikasa, for no matter how short a time, lost sight of that. The fearful, overprotective aspect of Mikasa's relationship with Eren is beginning to change, because her relationship with the rest of her world is beginning to change. With his rescue of Eren in the forest, Levi proves to Mikasa that other people are just as capable of protecting Eren as she is. And if she happens to take her mind off Eren for a bit, it doesn't mean he'll die. This is where the 'separation' begins. Mikasa starts to accept distance between herself and Eren; the distance of being able to trust others with him, of not needing to constantly be with him and personally oversee his safety. And it leads to this watershed moment in the Uprising arc: Mikasa. Whilst Eren has been kidnapped. And all they know is that he's inside a coffin with some random undertaker at some random inn. Maybe. In Chapter 4, Mikasa couldn't handle Eren being in a different part of the city from her during a mission because of how afraid she was that he'd die without her. In Chapter 30, she let Levi take the lead on getting Eren back, and was shocked when she realised that, even for an instant, she'd prioritised something else over him. In Chapter 57, Eren's been kidnapped, no one's been certain for two days about where he is or what's happening to him, and Mikasa is, well, as pictured above. The debilitating fear that used to tie Mikasa to Eren is gone for good. She's finally let Eren go, and discovered that it doesn't mean she'll lose him.
Post-timeskip Mikasa is in a good place, and long past the fear with which she faced the world as a young girl. She's with Eren, working with the Volunteers, and she and Armin are excited about the possibilities of the widening world. Then Eren effectively betrays the SC for reasons they can't fully understand, and, once again, Mikasa's world begins to change in alarming, unpredictable ways. https://preview.redd.it/y4f97ksi2sq51.png?width=346&format=png&auto=webp&s=a17a0410c8f25e97ee450b57d9636e5fc147b874 For the first time in a long time, she loses someone she loves. Eren's in jail and Mikasa remains by Sasha's grave, pondering the old words that bind her and Eren together: 'If we don't win, we die. If we win, we live. If we don't fight, we can't win.' Ironically enough, Sasha is the only character in the entire manga to have said those words apart from Eren and Mikasa themselves. And she's now dead as a result of Eren's fight. So what exactly is Eren fighting for, and what does winning that fight entail? This is the first time in the manga that Mikasa begins to doubt Eren, and the first time their bond has ever really been threatened. And not by the world, titans, or murderous kidnappers, but by Eren himself. The idea that there is beauty where cruelty also exists has informed Mikasa's perspective on the world since Eren wrapped his scarf around her. He showed her that it is possible for the two things to co-exist; for there to be human cruelty as well as human kindness, cold as well as warmth, life as well as death. But Eren is now showcasing the exact cruelty that Mikasa used him as a beacon against. What he's done is undoing what she believes in; it's not just that it's shaken her view of Eren – it threatens to undo Mikasa's whole world-view. In that same 2016 interview, Isayama spoke of Eren and Mikasa's eventual separation being ideological: 'If I were to draw the separation of Eren and Mikasa . . . Mikasa would have to endure the strain of being stuck between Eren and Armin. Even though she can sympathise with Armin, who considers things from a ''globalism'' perspective, it’s possible that she can't just let the more self-focused Eren go'. This ideological separation begins the moment Eren defects from the SC. It's from this point onwards that EMA's paths truly begin to diverge, and Mikasa in particular is presented with a choice that she's never had to face before. Of the two people she loves most in the world, does she choose the 'self-focused' Eren or the 'globalist' Armin? The choice she makes will most likely conclude Mikasa's character arc once and for all, and it's a choice that's been building since before the time-skip, represented by her interactions with two characters in particular: 1. Mikasa and Floch At the award ceremony in Chapter 90, Floch points out something interesting about Mikasa in what is otherwise an easily overlooked moment in the manga. Although multiple people were present on the rooftop during Serumbowl, he is the only one to explicitly draw attention to the fact that Mikasalet go. She resigned herself to losing Armin because Hanji convinced her that Erwin was more important to humanity and Mikasa's grief at losing him was something that would pass. https://preview.redd.it/oqjfh2gk2sq51.png?width=584&format=png&auto=webp&s=f13d8f9a80608e4ac8a85c30d3ddc79b751ad1dd Floch sees this as maturity, but the realisation that she was willing to let Armin go for the sake of humanity is something that Mikasa is shocked by. It makes her falter, and let go of Eren. Mikasa has always defined herself as Armin and Eren's protector; she's presented in the story as such, and she styles herself as such. She's the one who keeps Eren and Armin safe. But Floch's words make her realise that, on the rooftop, she was able to step away from that role – because her world has expanded beyond Armin and Eren. It has expanded to include Hanji and Levi and the other Scouts – and humanity. Mikasa is capable of making choices that hurt her deeply for the sake of a greater cause. 2. Louise and Mikasa Louise meets Mikasa on three occasions. The first time, Louise tells Mikasa she likes her because Mikasa saved her, and gave her something to strive for: 'You can't save anyone without power. It's okay for us to fight against unjust violence. That's what I learned' (109). In the same way Eren 'gave' Mikasa a motto to live by, Mikasa gave one to Louise. The second time, Louise tells Mikasa that she's happy to be by her side again, fighting for the same goal. Mikasa is ambivalent towards her. And she leaves her scarf behind, choosing to go and fight the titans without it. In between the second and third meetings, Mikasa talks to Armin. She asks him if he's really going to tell Connie to give up on his mother and let her remain a titan; Armin says yes, he is. When Mikasa asks what should be done about Eren, Armin replies that there's nothing to be done; he's a lost cause. After Armin leaves, Mikasa notices that the scarf is missing, and goes to retrieve it. The third and last time they meet, Louise is dying. She tells Mikasa that Eren wanted her to throw the scarf away, but she thought that she could take it to be close to Mikasa. Though she appears to sympathise with Louise's plight, Mikasa demands the scarf back from her. She walks away from Louise even as Louise tells her that she had no regrets, because she chased after Mikasa, devoting her heart. Each meeting between Louise and Mikasa mirrors, in an abbreviated way, the different stages Eren and Mikasa's relationship has gone through. 1: Louise's initial love and gratitude, and her taking Mikasa as an inspiration; 2: their fighting side by side as equals; and, finally, 3: their literal separation as Mikasa chooses to walk away. Louise reminds Mikasa of what Eren means to her. Mikasa never seeks to stop Louise from talking about her feelings; instead, she listens. She might not reciprocate, but she does understand. And her understanding Louise's love reminds her of her own. She walks away, but she takes the scarf with her. Despite what Armin said, and what Louise told her about Eren and the scarf, Mikasa chooses to keep a hold of it in the way she keeps a hold of the hope that Eren can still be brought back. Mikasa is capable of holding on to the person she loves even when he's gone too far. Mikasa Chooses . . . Mikasa Despite the apparently binary choice, Mikasa doesn't have to choose to side with Eren (allow the Rumbling to go ahead) or with Armin (kill Eren to stop him). She said it herself: there's a third option. Her way. Eren's wandered so far down his path that he's lost sight of Mikasa and of Armin; of what connects him to the world. Mikasa chooses, not to support him or to believe that he's a lost cause, but to remind him that walking away from his humanity doesn't mean that he can't turn around and walk back. Kruger said 'Anyone can become a god or a devil. All it takes is for someone to claim it for it to be true' (88). But if there's someone to challenge that belief, then the possibility remains of breaking the facade and setting the story straight – thereby freeing that person from the role they've either taken on out of necessity, or been assigned. It's something we've already seen happen. All it takes is for one person to question it, and the goddess falls apart to reveal an empty, unloved young girl, or the devil's mask cracks open to show the boy still grieving for the world he's lost. Ymir knows that Historia's faking it; Mikasa knows that Eren is kind. Each of them challenges the story that their loved one is telling in order to keep going: Historia to survive, Eren to achieve his dream. It took Mikasa years to truly overcome the cruelty she had seen as a child. Despite everything, she did, in the end, go back to being that 'ordinary girl'. She came to acknowledge that cruelty exists, as does death – but life must nevertheless be lived, people loved, experiences had, and faith kept. Seeing the beauty in a world that is inherently cruel is, and always has been, Mikasa's greatest strength. It's something she is capable of offering Eren, who no longer seems to believe in that duality, or in his own humanity. She can show him what he showed her; that the world isn't black or white, cruel or beautiful, dark or light. It's both. And it's possible to live with that.
Mikasa is no longer fighting to protect Eren from the world; she's fighting to protect the world from Eren. She's the person best suited to do that not only because she's his family, but because Eren's despair and anger at the world is what she might have ended up with herself. If any character was dealt a crueller hand by the world than Eren, or could have become as bitter about the world as him, it was Mikasa. But he stopped that from happening because his kindness showed her that the world, as bad as it was, had good in it. Little by little, Eren's abandoned that view of the world himself. He no longer sees both its beauty and its cruelty, but has confined himself to seeing - and acting on - only one. When they fought Annie in Stohess, Mikasa had to remind Eren that the world was cruel, because Eren had lost sight of that truth. Now, Eren's lost sight of another, equally valid truth; that the world, as cruel as it is, is also beautiful. That he, as inhuman as he thinks he is, is also kind. If Mikasa manages to 'bring Eren back', she'll have come full circle. She started off as a little girl who was seeking something, anything, to hold on to. She needed a saviour, and she got one in the form of Eren. In this scenario, she'll end as a saviour herself, someone who is now able to pass on the light that she once received. Her fear of the world and of losing her loved ones subsided; she managed to find the warmth she needed to carry on. She doesn't need Eren's scarf anymore – but he might need hers.
My perspective on Mikasa is that she's not a very obvious character when it comes to development, and so she sometimes appears static. And because so much of her drive is Eren, a lot of fans look to her relationship with Eren to change for proof that she's somehow developed. But Mikasa's obstacle, her personal flaw, isn't Eren himself, and never has been. Her flaw has always been her deep and debilitating fear about losing the people she loves – Eren and Armin – and her inability to really trust or love anyone apart from them. Mikasa's separation from Eren = her beginning to trust the rest of the world not to stab him in the chest, almost behead him, or eat him alive whilst she's not there. It's good for her because it means she stops being so terrified that she'll lose Eren, not because it means she'll stop loving him or wanting him to be safe. And she reached that point of separation a long time ago in the manga. It was fully realised the moment she decided to trust Levi during the Uprising arc, despite the fact that Eren was literally gone from her side and she had no way of knowing whether he was dead or alive. The final confrontation is where Eren and Mikasa's ideological separation, the one discussed by Isayama in the interview, will/won't occur. It – and its finer details – can unfold in a number of ways, and each one could mean something different for Mikasa's character. But her choosing to face Eren in this way is a natural culmination of her development until now. I've no concrete theories on what will actually happen once the Alliance reaches Eren, but I'm fairly certain that Mikasa is central to the resolution of this arc. And what with the way she's been written by Isayama so far, that's no bad thing. So, to finally end this ramble, I hope that this post at least offers people a different perspective on Mikasa's character and how it's changed over the course of the story. I look forward to reading any other observations/thoughts on Mikasa's development that people might have. Many thanks for giving mine a read!
After the excellent Wasteland 2, we were excited to get our hands on the new installment, and we can say without fear that it has met expectations. Wasteland 3 is a sign of the love that InXile has for his work and Brian Fargo for the genre that has created a name for him. If you are a lover of the saga or the genre, do not hesitate to enjoy it.
Wasteland 3 doesn’t pull any punches with its subject matter in sexuality, violence, and language. But if you are fine with that, I would highly recommend you give Wasteland 3 a shot, especially if you were (or still are) a Fallout fan.
On Paper Wasteland 3 sounds like the perfect RPG-Dream but the execution leaves much to be desired. Bugs, Glitches and graphics that doesn't really represent a game that releases and the end of this console generation are a bit of a letdown. Everything else from the great story, entertaining NPCs, solid battle system, clever leveldesign over to the love for details is amazing, besides some flaws that should soon be fixed, as inXile and Brian Fargo promise. Everyone that wasn't happy with the latest Fallout Games will surely love Wasteland 3.
Wasteland 3 is a old-school role-playing game, with a compelling story, a combat system that promises but is not groundbreaking and some funny moments and black mood, which always remind us that we are in a post apocalyptic world, but with a smile. Don't forget the powerful character editor, rhythm voices, and the beautiful scenery that puts you in that atmosphere of cold and snowy Colorado.
Wasteland 3 can be a bit of slog if you're gunning for marathon gaming sessions with it at the helm. Combat, whilst exciting initially can fall into the traps of repetition. A little more variety could have negated some of the repeated player actions. That said, the story is compelling and the characters an interesting assortment of misfit survivors, although perhaps fitting post-apocalyptic stereotypes. It's a fun, easy to play game overall though that should well-please fans of the series and keep players entertained for quite some time with its high replay-value. However, aside from some bugs here and there, the impressive amount of voice-work on offer, the character building is the best part of the experience where you can really nurture your ranger squad in this snowy post-apocalyptic world.
At least in my time with it, Wasteland 3 has been a fascinating experience. I’ve come to appreciate its depth of gameplay, character, building, and exploration, even if some of its pieces and parts still feel very foreign to me.
I will be even happier with Wasteland 3 once it’s patched and most of the bugs that bit me end up getting squashed. Even in its current state I’m having a grand ol’ time bringing some justice to the cold depths where no Ranger has dared to before. But for as much of a blast as I’m having out northeast in the cold, I hope I can make it back to sunny Arizona in time to save my fellow lawmen!
Wasteland 3 is a throwback to the old School RPGs of yesteryear, while providing a new combat experience and a bigger world. Players that liked previous Fallout Games, or games like Wasteland 2 or Baldur's Gate will feel right at home with this title, and will have the opportunity to try X-Com like combat. For the amount of content provided, 60 USD is a very good price, and fans of the genre should get more than their money's worth.
Wasteland 3 doesn't bring much new to the table, both as a CRPG and as a piece of post-apocalyptic fiction. But, it's a terrifically executed role-playing game that rewards player investment from beginning to end.
Wasteland 3 is a heady crescendo of post-apocalyptic story-telling. Its combat is compelling and fun while its characters and overall plot are engrossing, even when it goes to some dark places. A must-play for tactical RPG fans.
We’ll update this review if the game is fixed, and the issues outlined are fixed or at least addressed; and then I’ll pick it back up. As it stands now, I’ll be playing something else that isn’t as apt to crash. Buyer beware.
There are a few misgivings related to Wasteland 3's technical aspects, mechanics, and overall challenge. However, its cast of characters (both old and new), the switch to a traditional turn-based combat system, and branching paths filled with decisions and dire consequences make for a superb journey with the Desert Rangers.
With a focus on freedom of choice that is second-to-none, Wasteland 3 has set the benchmark for CRPG narratives, all the while being supported by wonderfully engaging gameplay and roleplaying mechanics.
It took me a while to realize how much these interactions, whether it be the interpersonal conversation or combat encounters themselves, stuck with me. Wasteland 3 has rules, but they only exist for you to bend them. With limitless character creation combinations, branching dialogue choices that affect what quests you do or don’t experience, and multiple endings, Wasteland 3 is an expanse of content and opportunity. The change in locale does wonders, no longer relying on a tired post-apocalyptic biome. Wasteland 3 has a wonderful backdrop in Colorado’s frozen wastes, making it the perfect place to spend a nuclear winter.
Wasteland 3 takes players to a new location and presents them with equally unfamiliar challenges, yet still perfectly demonstrates all of the reasons why this series has had die-hard fans for over three decades, and is absolutely worth playing for anyone looking for their next post-apocalyptic fix.
Wasteland 3 doesn't change its predecessor's successful formula but, outside of certain design limitations, it perfects and modernizes it. It's easily the best game in the franchise, in terms of pure technique, and one that clearly gives you an idea of what inXile is able to achieve.
Wasteland 3 is a good role-playing game, technically passable but enriched by a dense network of intriguing subplots that will push the most dedicated to play it several times. Watch out for the ever-present release bugs, though – best to wait a couple patches if you want to avoid unnecessary hurdles.
Wasteland 3 features everything only the best role-playing games do: an engaging story powered by excellent writing, compelling characters, tons of customization options, and a deep tactical combat system that feels fresh even after dozens of hours. But, most of all, it features a living world that reacts to what the player does, and changes depending on how the player decides to deal with the troubles ahead, providing a role-playing experience of the highest degree, one that very few games can boast of.
Wasteland 3 is a testament to the power of the branching narrative, taking it far beyond binary choices and into a grand canopy of cause and effect. It gives the wintry climbs of Colorado a lifelike quality that must have been painstaking to build. The most impressive RPG in years, Wasteland 3 is a masterpiece.
Wasteland 3 shines with clear dedication to crafting the best game its genre has ever seen. Excellent visuals are matched by top notch voice work and some of the best and most natural writing I have seen in a video game not made by Naughty Dog. The combat is a brutal dance where one wrong move can spell disaster, but victory is an exhilarating rush that never becomes old. Wasteland 3 cements inXile as one of the best in the business in the RPG genre and affirms that Xbox has something truly special on their hands.
Recently on the csharp subreddit, the post C# 9.0 records: immutable classes linked to a surprisingly controversial article discussing how C# 9.0's records are, underneath it all, immutable classes. The comments are full of back-&-forth over whether one should use records for ease or structs for performance. The pro-struct argument revolved around the belief that performance should always be a developer's #1 priority, and anything less was the realm of the laggard. Here is a real-world example that shows with stark clarity why that kind of thinking is wrong. Consider the following scenario:
You're working on a game with dozens, maybe hundreds of people on the team; you don't know because when you were cross with facilities about them removing all the fluorescents, you got accused of being against the new energy saving initiative. Now you swim in a malevolent ocean of darkness that on some very late nights alone in the office, you swear is actively trying to consume you.
The team that preceded you inherited an engine that is older than OOP, when source repositories were stacks of 8-inch floppies, and it looked as if Jefferson Starship was going to take over the world. One year ago they bequeathed upon the company this nightmare of broken, undocumented GOTO spaghetti & anti-patterns. You're convinced this was their sadistic revenge for all getting fired post-acquisition.
Management denied your request to get headcount for an additional technical artist, but helpfully supplied you with an overly nervous intern. After several weeks working alongside them, you're beginning to suspect they're pursuing something other than a liberal arts degree.
Despite the many getting started guides you spent countless evenings writing, the endless brownbags nobody attended, and the daily dozen emails you forward to oppressively inquisitive artists comprised of a single passive-aggressive sentence suggesting they scroll down to the part that begins FW: FW: FW: FW: FW: FW: RE: WE BROKE TOOL NEED WORKAROUND ASAP ...
...yes, despite all of that, the engineering team still spent days tracking down why the game kept crashing with Error 107221: У вас ошибка after re-re-re-re-re-throwing an ex_exception when it couldn't (and should never even try to) load a 16K-textured floor mat.
Despite your many attempts to politely excuse yourself, one blissfully unaware artist exhausts 48 minutes of your lunch break explaining how the Pitchfork review for the latest "dope slab" of this TikTok-Instagram-naphouse artist you never heard of was just sooooo unfair.
And then in their hurry to finish up & catch the 2:30 PM bus home, they forget to toggle Compress To CXIFF (Custom Extended Interchange File Format), set the Compression slider 5/6ths of the way between -3 & -2, look to their left, look to their right, click Export As .MA 0.9.3alpha7, and make absolutely, positively, 100% SURE not to be working in prod. And THAT is how the game explodicated.
You know better than anyone the intermediate file format the main game loop passes to Game.dll, memory mapping it as a reverse top-middle Endian binary structure.
You know for 381 of the parameter fields what their 2-7 character names probably mean.
YOU know which 147 fields always have to be included, but with a null value, and that the field ah_xlut must ALWAYS be set to 0 unless it's Thursday, in which case that blackbox from hell requires its internal string equivalent: TRUE.
YOU know that the two tech artists & one rapidly aging intern that report to you would totally overhaul tooling so artists would never "happen" again, but there just aren't enough winters, springs, summers, falls, July 4ths, Christmas breaks, Presidents Days, and wedding anniversaries in a year to properly do so.
And so somehow you do. A blurry evening or two here. A 3:00 AM there. Sometimes just a solitary lunch hour.
Your dog no longer recognizes you.
You miss your wife calling to say she's finally cleaning out the hall closet and if you want to keep this box of old cards & something in plastic that says Underground Sea Beta 9.8 Grade, you better call her back immediately.
And your Aunt Midge, who doesn't understand how SMS works, bombards you one evening: your father is... no longer with us... they found him... 1 week ago... in an abandoned Piggly Wiggly... by an old culvert... split up... he was then... laid down to rest... sent to St. Peter's... and your father... he's in a better place now... don't worry... it's totally okay... we decided we will all go... up to the mountain
You call your sister in a panic and, after a tidal wave of confusion & soul-rending anxiety, learn it was just Hoboken Wireless sending the messages out of order. This causes you to rapidly cycle.
On your bipolar's upswing, you find yourself more productive than you've ever been. Your mind is aglow with whirling, transient nodes of thought careening through a cosmic vapor of invention. It's like your brain is on 200mg of pure grade Adderall.
Your fingers ablaze with records, clean inheritance, beautiful pattern matching, bountiful expression syntax, aircraft carriers of green text that generate the most outstanding CHM for an internal tool the world has ever seen. Readable. PERFECTLY SOLID.
After much effort, you gaze upon the completed GUI of your magnum opus with the kind of pride you imagine one would feel if they hadn't missed the birth of their son. Clean, customer-grade WPF; tooltips for every control; sanity checks left & right; support for plugins & light scripting. It's even integrated with source control!
THOSE GODDAMNED ARTISTS CAN'T FAIL. YOUR PIPELINE TOOL WON'T LET THEM.
All they have to do is drag content into the application window, select an options template or use the one your tool suggests after content analysis, change a few options, click Export, and wait for 3-5 minutes to generate Game.dll-compatible binary.
Your optimism shines through the commit summary, your test plan giddy & carefree. With great anticipation, you await code review.
A week goes by. Then two. Then three. Nothing. The repeated pinging of engineers, unanswered.
Two months in you've begun to lose hope. Three months, the pangs of defeat. Four months, you write a blog post about how fatalism isn't an emotion or outlook, but the TRANSCENDENCE of their sum. Two years pass by. You are become apathy, destroyer of wills.
December 23rd, 2022: the annual Winter Holidays 2-hour work event. The bar is open, the Kokanee & Schmidt's flowing (max: 2 drink tickets). The mood a year-high ambivalent; the social distancing: acceptable. They even have Pabst Blue Ribbon, a beer so good it won an award once.
Standing beside you are your direct reports, Dave "Macroman" Thorgletop and wide-eyed The Intern, the 3 of you forming a triumvirate of who gives a shit. Dave is droning on & on about a recent family trip to Myrtle Beach. You pick up something something "can you believe that's when my daughter Beth scooped up a dead jellyfish? Ain't that something? A dead jellyfish," and "they even had a Ron Jons!"
You barely hear him, lost as you are in thought: "I wishIhad 2 days of vacation." You stare down ruefully at your tallboy.
From the corner of your eye you spot Milbert, index finger pointed upward, face a look of pure excitement.
"Did I tell you about my OpenWinamp project? It's up on SourceForge", he says as he strides over. It's unsettling how fast this man is.
Dave snickers. The Intern keeps staring wide-eyed. You position yourself somewhat close to the studio's 3 young receptionists, hoping they serve as a kind of ritual circle of protection.
It works... kind of. Milbert is now standing uncomfortably close to The Intern, Dave nowhere to be seen.
From across the room you distinctly hear "Think about it, the 1st-person UI could be Lua-driven Electron."
The Intern clearly understands that words are being spoken to them, but does not comprehend their meaning.
You briefly feel sorry for the sacrificial lamb.
You slide across the wall, putting even more distance between you & boredom made man. That's when you spot him, arrogantly aloof in the corner: Glen Glengerry. Core engineering's most senior developer.
Working his way up from a 16-year old game tester making $4.35 an hour plus free Dr. Shasta, to pulling in a cool $120K just 27-years later, plus benefits & Topo Chicos. His coding style guides catechism, his Slack pronouncements ex cathedra; he might as well be CTO.
You feel lucky your team is embedded with the artists. You may have sat through their meetings wondering why the hell you should care about color theory, artistic consistency, & debates about whether HSL or CMYK was the superior color space (spoiler: it's HSL), you were independent and to them, a fucking code wizard, man.
And there he stands, this pseudo-legend, so close you could throw a stapler at him. Thinning grey-blonde tendrils hanging down from his CodeWarrior hat, white tee with This Guy VIMs on the back, tucked into light blue jeans. He's staring out into the lobby at everything and yet... nothing all at.
Maybe it's the 4.8% ABV. Maybe it's the years of crushing down anger into a singularity, waiting for it to undergo rapid fiery expansion, a Big Bang of righteous fury. Maybe it's those sandals with white socks. Maybe it's all three. But whatever it is, it's as if God himself compels you to march over & give him a piece of your mind, seniority be damned.
"Listen, you big dumb bastard..."
That... is maybe a little too aggressive. But Glen Glengerry barely reacts. Pulling a flask out of his back pocket, he doesn't look over as he passes it to you.
Ugh. Apple Pucker.
"I thought bringing in your own alcohol was against company policy", wiping sticky green sludge from your lips. He turns with a look of pure disdain & snorts.
"You think they're going to tell ME what I can & can't bring in?" He grabs the flask back, taking a big swig.
For what feels like an eternity, you both stand in silence. You swallow, speaking softly. "None of you even looked at my code. I worked very, very hard on that. My performance review for that year simply read 'recommend performance improvement plan." The words need no further context.
"I know", Glen² replies. "That was me."
Now you're not a weak man, and maybe in some other circumstance you would have punched him in the goddamn lip. But you feel nothing, just a hollowness inside. "Why?", you ask, wondering if the answer would even matter.
"Because you don't use Bulgarian notation. Because your method names aren't lower camel case. Because good code doesn't require comments. Because you use classes & records over more performant structs, pointlessly burdening the heapstack. BECAUSE. YOUR CODE. IS. SHIT."
You clinch your fists so tightly the knuckles whiten.
He looks away from you, taking another sip of green goo. "You're not a coder. You're an artist masquerading as one" he speaks, as if it were fact.
The only thing artistic about you is the ability to create user-friendly internal tooling using nothing but a UI framework, broken down garbage nobody wants to touch, & sheer willpower. If your son's life depended on you getting accepted into art instruction school, you couldn't even draw a turtle.
He doesn't pause. "I'll champion ruthless micro-optimization until the day I die. But buddy, I'm going to let you in on a little secret: you aren't here to improve workflow. You're here to LOOK like you're doing something NOBODY else can."
He goes on. "What do you think those artists are going to do when they have to stare at a progress bar for 4, 5 minutes? They're going to complain your tool is slow."
"Sure, it may take them 20, 30 minutes to do it the old way, there'll be an error, and either they'll stare at it for 30 minutes before adding that missing semi-colon or they'll come get you. And you'll fix it. And 1 week later, they won't remember how. And you'll stay employed. And every. Body. Wins."
A little bit of the pride, the caring, wells back up inside from somewhere long forgotten.
"You don't think we should care about rapid application development & KISS, quickly getting things out that help our team, instead devoting ourselves to shaving off ticks here & there? What do you think artists are going to do with those 4 minutes you talk about?
You don't stop. "I'll tell you what they'll do. They'll 9GAG for 20 minutes straight. They'll listen to podcasts about dialectical materialism vis-a-vis the neo-feudalism that is a natural extension of the modern world's capitalist prison. They'll Reddit."
His silence gives you the bravery to push the limits.
"Christ, man. Are you only in it for the $120K..."
He corrects you: "...$123K."
"...only in it for the $123K/year? The free snacks from the microkitchen? The adulation? Have you no sense of comraderie?? No desire to push us to something better?! No integrity?!!!"
His eyes sharply narrow, face creases in anger. You clearly have overstepped your bounds.
"You thinkIdon't have integrity? No sense of teamwork? I'm only in it for the cold cash? You think I don't care about you all?", he roars.
A light volley of small green flecks land on your face.
"Why do you think they made a 16-year old tester the lead developer of a 1993 Doom clone?! Because my code was clean & painless to work with?! Because I made coding look easy?! No! IT WAS BECAUSE I WAS A GOD TO THEM.
And from a God, a PANTHEON. We built monuments to over-engineering! We crafted that of 7 weeks onboarding, that of immortal bugs, demonic hosts spawned by legion from the very loins of a fix. It took 2 years before a developer could BEGIN to feel confident they knew what they were doing. And by that time, they were one of US!
You think the team we laid off November '19 was fired because they were bad at their jobs? NO! It was because they worked themselves out of one. They didn't leave us a broken pipeline. They left an internal Wiki, a wealth of tools & example projects, and a completely transparent code base.
We couldn't have THAT, now could we? No, we couldn't. So we got rid of it. ALL OF IT. Poof. Gone. Just like that. Before anyone even knew a THING."
He leans forward, so close his psoriasis almost touches yours. With an intensity that borders on frightening, he whispers "You think they left us Game.dll? I fucking *MADE** Game.dll."*
The words hit hard like a freight train.
And without another word, he turns & leaves. You're left there, alone, coworkers milling about, with only one thought.
Were one to get a hobby, should it be cocaine?
It's these kinds of situations that make me believe there are far more important considerations than a ruthless dedication to performance, even in the game industry as my real-world scenario so clearly demonstrates.
Well! Here we are again. Everyone is sitting around this internet campfire, anxiously awaiting another Hawk story. Some of you are making S'mores. Others have crammed a stick into a hotdog and are now roasting it. I "Cope" with life and have a fat dip in. The only person I don't see is Hawk. Wait. There he is, and he keeps sticking his fingers into the fire to, "make sure it's still hot." I wonder if there is still a need to detail how mentally deficient or completely oblivious Hawk is? I strongly encourage you to read my previous stories if you have not been formally introduced to Hawk. I suspect you will continue to read anyways, so I offer you this: Hawk is the type of guy that gets into a spelling argument with his tattoo artist and walks out proud of his two-inch sized font forehead tattoo that reads "No Regerts." We were in beautiful Iraq, a charming vacation destination for thousands of Americans. The vacation was all inclusive. The local women dressed like Pac-Man ghosts or ninjas, and countryside smelled like raw sewage and regret. Most of the locals were very hospitable, but some of the locals had a very strong desire to shout, "Praise Allah" while simultaneously trying to kill us. I am not bothered by much. Every human is entitled to their beliefs. We are also entitled to our own opinions. For example, I don't personally feel "man-dresses" and flip-flops are suitable combat attire, but who am I too judge? The only time I have an issue with people is when they are actively trying to kill me. I don't know why, but it really pisses me off. That and grape jelly. We worked out of two different locations during this deployment. The majority of my Battalion worked out of a medium-sized Forward Operating Base (FOB), but we also operated out of a smaller FOB. We typically stayed at this other location for about ten days, and would rotate with another Platoon. The location was not horrible, but I personally hated the transient lifestyle. We lived out of our ruck-sacks, and had to find ways to occupy our time when we were not conducting raids or other missions. We didn't have the luxuries we had at "home." There were no gaming systems or large televisions. We simply had find ways to occupy ourselves. Football was the game of choice for a couple weeks, then it got blacklisted. It had nothing to do with the ball being pigskin either. It was mostly due to poor mission analysis. Football was one of the few things we could all do and actually enjoyed, until it was too dark to play. We had a brilliant and genius idea. We fucking "own the night" with our Night Vision Goggle (NVGs), so why don't we rent it for a couple hours to finish the game? Game on Garth! We thought of everything. We drenched that infidel ball in Infrared (IR) chemlight (Glow Stick) juice. The depth perception problem was immediately evident. House took a fucking laser beam pass to the to the face. Two black eyes builds character though. We can work through it though. His NVGs were still Fully Mission Capable (FMC), and we all realized that we needed to be a bit quicker. The fourth play from scrimmage was undoubtedly the best, and worst football play in the history of Iraq football. Fuck punting. We were going for it. It would have been easy to confuse Tony, our quarterback for Michael Vick from the shotgun. Tony was a Michael Vick with NVGs, and without the dog fighting felony. Tony evaded numerous rushers and then superbly delivered a fifty yard completion to Ryan. It was beautiful to watch, until it wasn't. NVG's are great, but they don't offer the same Field of View (FOV) your eye-nuggets offer. Ryan thought he was all alone and started a leisurely stroll to the end-zone. The he got fucking nuked from the top and bottom, in fucking reverse directions. Sure, Ryan broke a finger and required "some" stitches. Oh and they broke three sets of NVGs in one play, but damn that was a glorious fucking hit. It was first-and-ten, but our Platoon Sergeant was less than happy. Game off Wayne! We were now bored again. There was another unit on the FOB with us, but they were not fans of us. The only real interaction we had was when their full-bird Colonel told us to, "stay the fuck away from his Soldiers." I don't know if one of the other Platoons ruined it for us, but the guy was just a complete prick to us. We did our best to keep our reverse schedule, but it was just so boring during the evenings we were not working. The majority of us resorted to playing Spades or Echure, and others read. Hawk and a handful of others would take nightly showers and then seemed to vanish. "Knowledge is power" and I knew Hawk was utterly powerless. I knew better than to ever let that retarded bird spread his wings and fly solo. I didn't see any reason to worry though. The other people Hawk was with were far smarter than Hawk woud ever be. Furthermore, with football now off the table, there was really no way for anyone to get in trouble at this FOB. Imagine Hawk in a cattle chute. If I put a box labeled "commonsense" on the opposite end, Hawk would never fucking find it. In a place he literally has no option but to find it, he would NOT FIND IT. EVER. However, if I had a box labeled "worst decision ever" and dropped it in the ocean, Hawk would fucking somehow stumble upon the lost city of Atlantis. I had never really got my ass chewed before I became Hawk's leader, but that trend went out the window when I inherited him. We lived on the second floor, and my bunk was closest to the door that rotation. Thankfully too. I was woken up when I heard, "I want to talk to one of your leaders." I didn't know "who" was in trouble, but I had Hawk so I knew it was best to simply put my shoes on and assume I was in trouble by proxy. I didn't even wait to see if I would get to sit on the Green Army Weenie, I just spit in my hand and readied my o-ring for maximal insertion. It was too early for the sun to even be out, and I was already willingly walking to my execution. My how things had changed so quickly. I walk outside and I see five Soldiers, one Hawk, and a fucking pissed of Colonel (COL). COL: Are you their leader? OP: I am one of them. How can I help you Sir? COL: Do you know where I caught them? This is where I would typically say something stupid, but this guy didn't look happy, and I didn't want to give him a reason to wake up someone who "may" have gave a shit as to why he was irate. OP: No Sir. I don't. COL: Above MY SHOWER? I was now pissed. There was a large shower tent in the middle of large open courtyard. One half was male and the other was female. These fucking morons were spying on naked females? I want to kill them for listening to Hawk. Well, I assumed it was a Hawk idea. Like Hawk's brain, I was putting the cart before the horse. I assume it was Hawk, but I had questions. OP: How in the fuck did you guys get on top the shower tent? I was working myself into a frenzy. My brain does not operate like normal people brains. I was pretty pissed considering they violated the privacy of the beautiful ladies at the FOB, but I was actually more pissed they got on top of a fucking tent. They seemingly forgot everything about military tactics and got caught; that was the foremost reason for my anger. The spying on deployment 1's (binary thingy) was second. Considerably a far worse offense, but second at the point in time. COL: NO. Not the shower tent. On my personal shower. What? This guy was so special, he had a personal shower. What, he was too good to use the pallet floored showers like the rest of us? So maybe the Romanians (We think anyways) occasionally shit on the pallets and waffle-stomped the poop through the pallets, but the water pressure was phenomenal. OP: You have a personal shower Sir, and they were on top? COL: YES. I caught them in my water tank. Well, back to being puzzled. I don't judge. I personally don't care if penis gazing is your hobby, but there are five of you? Why don't you just unleash your hogs and stare at each others? Anyways, how in the fuck did they all fit into the water tank? What the fuck did they do when they got inside? My god, my brain was running wild with unsightly pictures. OP: My apologies Sir, but how did they all fit into your water tank? COL: Come with my Sergeant; so you understand what I am talking about. OP: You mother fuckers can wait for me in, the front-leaning-rest (Push-up position). I still wasn't certain I entirely cared, but I thought this would may demonstrate that I showed concern about his fucking one-person shower. COL Prick then lead me around the side of the building and showed me his water tank. It was fucking huge. It was one of the typical hard plastic tanks, but the entire top had been cut off. God knows why, not like it was ever dusty in Iraq, but the top was no-more. It all made sense now. They weren't gay; they were chilling in a makeshift hot tub! Well, the gayness thing is up in the air, but I guess they were too loud while he was showering!?! I apologized profusely, but COL Prick had me locked up at the position of attention for at least ten minutes just dressing me down. I was a "really poor leader, and you're not going to go anywhere in the Army." Jokes on him, they haven't kicked me out yet. COL: This is why nobody likes "cool guys." Words, words, words. You'd better do something about this, words, words, words. My penis is too small to shower with the big boys, words, words, words. NOW GET THE FUCK OUT OF MY SIGHT. I returned to the Soldiers, whom were still all in the front-leaning-rest. I screamed, "GET ON THE OTHER SIDE OF THE BUILDING. I DON'T WANT TO GO TO JAIL AFTER PEOPLE SEE ME SMOKE THE FUCKING LIFE FROM YOUR BODY. NOW FUCKING RUN." They fucking scurry, and I stroll to the other side of the building. Out of sight and out of mind. (I will use "Group" unless Hawk is the person talking. Too many useless names otherwise.) OP: That fucking dickhead has his own fucking shower! What the fuck? GROUP: I know right? OP: What the fuck were you guys thinking? I would expect this from at least one of you, but I won't point elbows. (I then just fucking stare at Hawk.) GROUP: We didn't think anyone used it. We had never seen anyone go into the room, and the room looked empty. We saw the water tank on top, and just figured we would check it out. OP: How the fuck did you even get up there? GROUP: You can walk to it if you exit any second floor window on our building. Well, the courtyard side. OP: So you guys just sneak out and hang out in this guys shower water? GROUP: Yes, but we seriously thought nobody used it. We would not have used it otherwise. OP:You fucking dip-shits think this was just a randomly placed unused water tank? You fucking idiots just stand in this guys shower water for hours? HAWK: No. We are not dumb Sergeant. We sit on MRE (Meal Ready to Eat) boxes. OP: HOW LONG HAS THIS BEEN GOING ON? GROUP: (LaughteGiggles) Every night!?! OP: We have been here for five days now! NO FUCKING MORE! I will fucking kill you if I get yelled at again over this. The only thing that makes me smile is the fact that he is showering with your ball funk. Hawk: I have some excellent news then Sergeant OP: Really? Whats Hawk? Hawk: (Smirk) We made a promise that, "nobody pisses in the hot tub"... OP: This is why your mother should have swallowed you Hawk. Why the fuck would that make me happy? Hawk: (Laughing) Because I broke that rule every night. Most nights more than once! GROUP: What the fuck Hawk! We have been lounging in your piss? What the fuck dude! Hawk: I know. (Smiles.) I lied to you though! Cheer up Sergeant. I peed on him for you! For the record, Hawk did not find the hot tub. He just peed in it, a lot. I don't think any of us paid attention because they came back from wet and with towels. I merely assumed they went to the showers. I suppose I should have kept better track of time. Also, I apologize if this was not as funny as the other Hawk tales. I realized it when I reread it, but it was certainly funny being on-the-ground and witnessing it. Can't laugh at them all I suppose. Remember, next week, "Hawk Walks Home: In Iraq." I don't think it is feasibly possible to not make that one funny. Lastly, some of my stories are a result of me being in the military, but not military. Those stories and others will/are posted at FuckeryUniveristy. I am not ever going to compete with this page, but I do need a place to post other stories and have little fear they will be taken down. The mod may be a huge prick, but at least I know the guy. Man...huge prick! Cheers!
Does this Key fit the Binary Options Door? Maybe this strategy is not a money making machine, maybe it’s not the best in the world but it’s very easy to trade and I believe that its simplicity will attract people. That’s good because once you start trading – even a simple strategy – you start seeing things and I don’t mean ... Binary options basics are helpful to understand how they work. You do not need any binary trading for dummies pdf to understand it. Beginners guide to binary options trading. This is a short and simple binary options tutorial.They are easy to understand.This is why they are growing fast.They are easy for the beginners. What are binary options? They’re called ‘binary’ because there can be ... However, binary options has much lower entry requirements, as some brokers allow people to start trading with as low as $10. Disadvantages of Binary Trading Reduced Trading Odds for Sure-Banker Trades. The payouts for binary options trades are drastically reduced when the odds for that trade succeeding are very high. While it is true that some ... Make Money with Binary Options Trading. To start, let’s be clear: you can make money binary options trading.It’s definitely possible to generate a consistent profit. Smart traders do it every day, executing binaries in everything from oil and gold to stocks and currency pairs.. The question is, is it as easy to make money as a lot of websites claim? Binary Options Making Money the Easy Way View Course. Paul Trades4us $497.00 Charts Made Easy View Course. Paul Trades4us $297.00 ... BINARY OPTIONS MADE EASY. TRADING BINARY OPTIONS CAN BE VERY DIFFICULT FOR THOSE WHO DO NOT KNOW WHAT TO LOOK FOR. ESPECIALLY WHEN THERE SHOWN HOW TO COVER THERE SCREENS IN INDICATORS BY SOME FAKE GURU SO THE ACTUAL MARKET IS BARLEY VISIBLE. IT REALLY DOESN’T HAVE TO BE THAT WAY. When I observe the market without indicators I see structure, I see rules. Predictable movement that can be ... Binary options trading is relatively easy. You can purchase a contract in just three steps: 1. Define your position. Choose the market, trade type, duration, barrier, and payout. 2. Get your price . Receive instant prices based on your position. 3. Make your trade. Buy the contract or re-define your position. Step 1: Define your position. The first step is to set the parameters of your trade ...
EASY BINARY OPTIONS STRATEGY TO MAKE MONEY IN 2021 - YouTube
💲💹Pocket Option: http://www.cryptobinarylivingway.com/PocketOption 💰💲FULL BEGINNER? Join My PERSONAL TRAINING!💴💵 BLW Trading Academy: http://www ... day trading binary options, binary trading education, binary trading example, easy binary trading, trading en binary, binary trading full course, binary trading for beginners 2020, binary trading ... How Binary Options Work. To get the transcript and MP3, go to: https://www.rockwelltrading.com/coffee-with-markus/how-binary-options-work/ Try it for yoursel... Want to copy Winning TRADES?🔙💲💹Join My Official BLW Signals Website: https://blwtradingroom.com/ 💲💹My Broker, IC Markets FREE DEMO ACCOUNT HERE: https ... 💰💲FULL BEGINNER? Join My PERSONAL TRAINING!💴💵 BLW Trading Academy: http://www.blwtradingacademy.com/ 💲💹Official FREE Telegram Group: https://t.me ... Binary Options Made EasySimple Strategy http://earnwithsherry.com Learn how to trade binary options using our easy strategy Binary options made easy Binary ...