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
This is the CLI & GUI v0.17.1.3 'Oxygen Orion' point release. This release predominantly features bug fixes and performance improvements. Users, however, are recommended to upgrade, as it includes mitigations for the issue where transactions occasionally fail.
We encourage users to check the integrity of the binaries and verify that they were signed by binaryFate's GPG key. A guide that walks you through this process can be found here for Windows and here for Linux and Mac OS X.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 # This GPG-signed message exists to confirm the SHA256 sums of Monero binaries. # # Please verify the signature against the key for binaryFate in the # source code repository (/utils/gpg_keys). # # ## CLI 38a04a7bd00733e9d943edba3004e44730c0848fe5e8a4fca4cb29c12d1e6b2f monero-android-armv7-v0.17.1.3.tar.bz2 0e94f58572646992ee21f01d291211ed3608e8a46ecb6612b378a2188390dba0 monero-android-armv8-v0.17.1.3.tar.bz2 ae1a1b61d7b4a06690cb22a3389bae5122c8581d47f3a02d303473498f405a1a monero-freebsd-x64-v0.17.1.3.tar.bz2 57d6f9c25bd1dbc9d6b39fcfb13260b21c5594b4334e8ed3b8922108730ee2f0 monero-linux-armv7-v0.17.1.3.tar.bz2 a0419993fbc6a5ca11bcd2e825acef13e429824f4d8c7ba4ec73ac446d2af2fb monero-linux-armv8-v0.17.1.3.tar.bz2 cf3fb693339caed43a935c890d71ecab5b89c430e778dc5ef0c3173c94e5bf64 monero-linux-x64-v0.17.1.3.tar.bz2 d107384ff7b1f77ee4db93940dbfda24d6045bf59c43169bc81a0118e3986bfa monero-linux-x86-v0.17.1.3.tar.bz2 79557c8bee30b229bda90bb9ee494097d639d60948fc2ad87a029359b56b1b48 monero-mac-x64-v0.17.1.3.tar.bz2 3eee0d0e896fb426ef92a141a95e36cb33ca7d1e1db3c1d4cb7383994af43a59 monero-win-x64-v0.17.1.3.zip c9e9dde61b33adccd7e794eba8ba29d820817213b40a2571282309d25e64e88a monero-win-x86-v0.17.1.3.zip # ## GUI 15ad80b2abb18ac2521398c4dad9b8bfea2e6fc535cf4ebcc60d99b8042d4fb2 monero-gui-install-win-x64-v0.17.1.3.exe 3bed02f9db5b7b2fe4115a636fecf0c6ec9079dd4e9284c8ce2c67d4996e2a4a monero-gui-linux-x64-v0.17.1.3.tar.bz2 23405534c7973a8d6908b76121b81894dc853039c942d7527d254dfde0bd2e8f monero-gui-mac-x64-v0.17.1.3.dmg 0a49ccccb561445f3d7ec0087ddc83a8b76f424fb7d5e0d725222f3639375ec4 monero-gui-win-x64-v0.17.1.3.zip # # # ~binaryFate -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEgaxZH+nEtlxYBq/D8K9NRioL35IFAl+oVkkACgkQ8K9NRioL 35Lmpw//Xs09T4917sbnRH/DW/ovpRyjF9dyN1ViuWQW91pJb+E3i9TY+wU3q85k LyTihDB5pV+3nYgKPL9TlLfaytJIQG0vYHykPWHVmYmvoIs9BLarGwaU3bjO0rh9 ST5GDMdvxmQ5Y1LTwVfKkmBJw26DAs0xAvjBX44oRQjjuUdH6JdLPsqa5Kb++NCM b453m5s8bT3Cw6w0eJB1FQEyQ5BoDrwYcFzzsS1ag/C4Ylq0l6CZfEambfOQvdUi 7D5Rywfhiz2t7cfn7LaoXb74KDA/B1bL+R1/KhCuFqxRTOQzq9IxRywh4VptAAMU UR7jFHFijOMoyggIbkD48JmAjlBnqIyQJt4D5gbHe+tSaSoKdgoTGBAmIvaCZIng jfn9pTNzIJbTptsQhhyZqQQIH87D8BctZfX7pREjJmMNGwN2jFxXqUNqYTso20E6 YLtC1mkZBBZ294xHqT1mQpfznc6uVJhhoJpta0eKxkr1ahrGvWBDGZeVhLswnBcq 9dafAkR14rdK1naiCsygb6hMvBqBohVu/bWuhycJcv6XRvlP7UHkR6R8+s6U4Tk2 zaJERQF+cHQpEak5aEJIvDlb/mxteGyvPkPyL7UmADEQh3C4nREwkDSdnitYnF+e HxJZkshoC98+YCkWUP4+JYOOT158jKao3u0laEOxVGOrPz1Nc64= =Ys4h -----END PGP SIGNATURE-----
Note that you should be able to utilize the automatic updater in the GUI that was recently added. A pop-up will appear shortly with the new binary. In case you want to update manually, you ought to perform the following steps:
Extract the new binaries (the .zip file (Windows) or the tar.bz2 file (Mac OS X and Linux) you just downloaded) to a new directory / folder of your liking.
Open monero-wallet-gui. It should automatically load your "old" wallet.
If, for some reason, the GUI doesn't automatically load your old wallet, you can open it as follows:  On the second page of the wizard (first page is language selection) choose Open a wallet from file  Now select your initial / original wallet. Note that, by default, the wallet files are located in Documents\Monero\ (Windows), Users//Monero/ (Mac OS X), or home//Monero/ (Linux). Lastly, note that a blockchain resync is not needed, i.e., it will simply pick up where it left off.
You ought to perform the following steps:
Download the new binaries (the .zip file (Windows) or the tar.bz2 file (Mac OS X and Linux)) from the official website, the direct download links in this thread, or Github.
Extract the new binaries to a new directory of your liking.
Copy over the wallet files from the old directory (i.e. the v0.15.x.x, v0.16.x.x, or v0.17.x.x directory).
Start monerod and monero-wallet-cli (in case you have to use your wallet).
Note that a blockchain resync is not needed. Thus, if you open monerod-v0.17.1.3, it will simply pick up where it left off.
In the wizard, you can either select Simple mode or Simple mode (bootstrap) to utilize this functionality. Note that the GUI developers / contributors recommend to use Simple mode (bootstrap) as this mode will eventually use your own (local) node, thereby contributing to the strength and decentralization of the network. Lastly, if you manually want to set a remote node, you ought to use Advanced mode. A guide can be found here: https://www.getmonero.org/resources/user-guides/remote_node_gui.html
Don't Be A Basic Bench: A Comprehensive Introductory Guide
Hello everyone! In an effort to keep the subreddit and its wiki filled with good and useful information, we are compiling guides for the main lifts (deadlift, squat, bench, potentially others). These guides will be added to the wiki and posted as posts as they are completed. The goal of these guides is to provide basic lift information, descriptions of some common variations, equipment considerations, related and complimentary exercises, additional resources for further reading, and to showcase incredible women (and non-binary folks) performing these lifts. This is the second entry in this lift series. Check out the first entry, The Deadlift Guide in the FAQ! If you have suggestions regarding things that should be added to these guides, or other subjects you'd like to see in the wiki, please message the mods!
The Bench Press
Bench Press Form and Variations
The main muscle group worked by the bench press is the pectoralis major, which is the largest muscle in the chest area. The pectoralis major muscle has two sections that are named for the bones they attach to – the sternal portion attaches to the breast bone and makes up the bulk of the muscle fibers, making up the middle and lower section; the clavicular portion attaches to the collarbone and is the more superior (upper) portion. The bench press also heavily involves the triceps (back of the upper arm), and recruits the deltoid muscles (shoulder), and pectoralis minor to lesser extents. I’ll first be discussing the form for a standard, flat, “neutral/wide” grip bench press. Variations on this will be discussed below it. This guide is written for barbell bench pressing, but all of these variations can be performed with dumbbells as well. Flat bench – the standard/”default” bench press Start out flat on the bench with bar directly over your eyes (with spotter) or over your nose/mouth (without spotter), feet flat, butt and upper back planted firmly on the bench. Arching of the lumbar spine is normal, fine, and absolutely legal in lifting competitions. Scapulas (shoulderblades) should be retracted or “pinched together” to provide both a stable flat surface for your upper back to settle on the bench, and to minimize undue tension on your shoulder joints. Retracting your scapulae will also puff your chest up and put your shoulders in a safer position for the lift. The bar should rest in the heel of your palm so that it is stacked above the wrist, forearm, and elbows through the lift. A slight internal rotation of the hands will help with this positioning and will angle your elbows out slightly. For a standard flat bench press, your hands will be a bit further apart than shoulder width – about 1.5-2x shoulder width is the average position – position your hands so that your forearms will be almost completely perpendicular to the floor at the bottom of the lift. Retract your scapulae (as if you’re trying to pick up a pencil off the bench between them), keep actively pushing your chest up, take in a big belly breath, and hold it before pushing the bar away from the rack and locking out at the elbows. Bring the bar down your torso so that it is directly over the line of your shoulders – this is likely going to be about the level of the middle of your sternum or your nipple line, but may vary depending on your individual anatomy and the degree of arching your back is doing. The bar should be directly above your elbows at all times during the movement of the lift. This not only increases stability during the lift, but also prevents undue stress on your triceps or your shoulders. It also is the most efficient configuration for using the majority of the muscle fibers within the pectoralis major. Speaking of efficiency in recruiting pectoral muscle fibers, let’s talk about arching your back during a bench press. This is a faux controversy like “sumo deadlifting is cheating” – the claim is that an arch will significantly decrease the range of motion for the bar, making the lift “easier”. While the purpose of the arch is to slightly decrease the range of motion, it also makes the lift safer at the bottom of the movement, which is the riskiest for your shoulder joints. It also serves to recruit more of your pectoral muscle fibers to the lift – this should increase the amount of weight one can lift and impact muscle growth when the goal is hypertrophy. Degree of arching is going to be up to personal preference and anatomy, but some degree of arch is natural and normal. Check out the natural position of the spine and you can see that the lumbar spine (lower back) has a natural forward curve (lordosis) which helps with loadbearing since we’re just hairless upright apes. An arch during bench press may be anywhere from your normal lumbar spine position to an exaggeration of your body’s natural lordosis. As you lower the bar, keep tension in your upper body by trying to “break the bar in half” or “rip the bar apart” until it touches your mid-to-lower sternum (depending on anatomy and degree of arch). After a touch (and brief pause, if you’re powerlifting), push the bar back upwards and slightly backwards towards your face to lockout. You can now exhale that big belly breath you’ve been holding for the duration of the rep.
Stronger by Science also has a very in depth How To Bench article. It is more in depth than this guide intends to be, and definitely worth a read. It also covers the anatomy and physics behind the bench press – things you should be interested in if your goal is to move weight safely (even if your goal does not necessarily involve moving a lot of weight).
Dumbbell bench: These are not only great when you aren’t yet able to use the barbell, but also for correcting muscle imbalances and general strength improvements that can translate into a barbell bench press. These also have more flexibility with grip positioning – if a barbell bench press irritates your shoulders, consider trying dumbbell bench press with a neutral grip (the dumbbells will be parallel to your body instead of perpendicular). Dumbbell bench press also allows for an increased range of motion, developing small stabilizer muscles in the upper body, and can be used to correct muscle imbalances.
Incline bench – performed with the bench angled about 15-30 degrees up from parallel to the floor. As you change the bench to a more upright position, the front shoulder muscle (anterior deltoids) will become more involved in the lift compared to lower degrees of incline and flat bench. The purpose of incline benching is to recruit more shoulder involvement and also more of the upper (clavicular) parts of the pectoralis major muscles. Bar will still track to be over your shoulders, about the nipple line/mid sternum. Grip width just wider than shoulder width so forearms will be completely perpendicular to the floor at the lowest point of the press.
Decline bench: There are benches and racks specifically for decline benching. If you only have access to a flat bench, you can potentially “make” your own decline by elevating the foot end of the bench. If you do this, make sure it’s very stable before trying the lift. The benefit of a decline bench is to utilize the lower portions of the sternal portion of the pecs more, and also decrease the amount of involvement of shoulder muscles. If you have a shoulder injury but are still cleared to lift, this can be a better option for you than a flat or incline bench press. In this position, the barbell will be over the lower part of your breast bone (sternum) and will touch the chest lower than in a flat or incline bench press.
Close grip bench: As the name suggests, this bench press variation has a more narrow grip width than standard or wide grip bench press. The purpose for this positioning is to increase the involvement of the triceps muscles during the lift. Proper grip width for this is over the shoulder joints – too narrow of a grip can internally rotate the shoulder joint which can lead to strain and injury. In this variation, the bar will touch your chest even lower than a decline or flat bench press – the bottom of the movement should still have your forearms perpendicular to the floor, with the wrists and bar stacked over the elbows.
Supinated/reverse grip bench: This variation can be very challenging, especially as weights increase. The benefit to supinating your hands so that the palm is facing your chin during the bench press is to reduce strain on the shoulders. It can be challenging to keep the bar in the fleshy part of your hands without dropping the bar on your face. Definitely practice with an empty bar or light dumbbells.
Floor press: Not just an exercise for when the benches are all occupied. Floor press is good in its own right or as an accessory for bench press. Set up is basically the same as a flat bench press, but you’re on the floor. Personally I prefer to have my knees bent and my feet flat, but one could also keep the legs flat out and completely remove lower body involvement/drive. These are especially great with dumbbells for folks with shoulder pain or issues, because you can use a neutral grip. These can help with lockout strength at the top of the bench press as well as if your sticking point on bench press is on the ascent.
Larsen press: The set up for the Larsen press is identical to a standard flat bench press. The biggest difference is that once you unrack the weight and have the bar over your chest, the feet are lifted off the ground, either straight out or resting on something else at the heel (toes up). “This forces athletes to really focus on maintaining their upper back tightness without the feet and legs compensating for poor bar path, set positioning, and inadequate force displacement.” The biggest benefit to this variation is to force the lifter to maintain a tight upper back during the bench press, though it also serves as a way to increase relative intensity/difficulty of the exercise without adding more weight to the bar.
Helpful Bench Press Cues
Try to “break the bar” while pushing it away from you. Imagine it is a big long dry spaghetti noodle and you are trying to turn it into two pieces of spaghetti by snapping it away from you. This will help engage your upper body muscles and ensure that your upper back is tight and flat, promoting a safer and more stable lift.
Grip the bar very hard, with special focus on gripping hard with your pinkies. This can help engage your latissimus dorsi for the lift!
Stack the bar over your wrists over your elbows. This means your forearm will be perpendicular to the floor and the barbell and increases stability, improves form, and reduces undue strain on your shoulders and elbows.
Push yourself away from the bar and push your body down into the bench during the actual press portion (from the bottom back up to the top) of the lift. This will help keep your upper body muscles engaged appropriately and keep you in place on the bench.
For leg drive, plant your feet and apply force down on the floor and towards your head. This will help keep your upper back planted so long as you aren't slick and sweaty and keep optimal form and tightness through the lift.
Push ups –Push ups are basically the body weight exercise version of the bench press – the movement and position is very similar and translate well into bench press gains. Succeeding in bench press will benefit your push ups, and succeeding in push ups will benefit your bench press. The bodyweightfitness subreddit guide for pushups is excellent and goes over a suggested progression program if you are not yet able to do full push ups on your toes. Note also that you can do a narrow width diamond pushup to increase involvement of your triceps.
MegSquats also recently posted a “3 tips for push ups” post that several of our users have already mentioned as being helpful.
Svend/pinch press - a great accessory exercise for pectoral muscle growth, especially right in the middle along the sternum. You’ll be squeezing a plate or other weight between your hands at mid chest level and pushing the weight straight out away from your body – make sure you’re squeezing the weight through the whole motion. This can be done either standing upright or lying flat on your back (supine). The supine version recruits your triceps more, and the standing version recruits your anterior deltoid more.
Chest flies - another favorite chest accessory. These also hit the pectoralis minor, along with pectoralis major. These can help your bench press by increasing the strength of the pectoral muscles, but are also great for changing the aesthetics of your chest muscles. Flys can be performed flat or at an incline – like incline bench press vs flat, increasing the angle away from the ground will increase the involvement of the upper aspect of the pectoral muscles as well as the anterior deltoid muscles.
Cable crossoveiron cross: Very similar to chest flies, but you’re using the cable tower and performing these upright. These engage the core and abdominal muscles more, but are still primarily for strengthening the chest, shoulders, and triceps. The best part about cable flyes or cable crossovers is that you can adjust the height of the cables to target different aspects of your chest muscles – higher cable anchors target the lower pectoral fibers, middle (shoulder-ish) height target the middle fibers, especially along the sternum, and low cable anchor points target the upper pectoral muscle fibers.
Dips are challenging body weight exercises that can have either a chest or triceps focus. Essentially, these are vertical pushups – you will be suspended from a rack or pull up/dip ‘machine’. Start with your arms fully extended while you’re holding onto the handles. Bend your arms to lower your body, leaning forward slightly, until your shoulders are just below your elbows. Lift yourself back up while straightening your arms until you lock out at the top. You can also do bench dips which may be easier on your shoulders. Surprisingly good wikihow guide on bench dips.
Around the Worlds - an exercise for pectoral and shoulder muscle strength and development. Can be done supine or standing – supine will be a chest focus, while upright will be a shoulder focused movement (but don’t worry – both groups are definitely involved in both versions). Hold dumbbells or small weight plates with your palms facing forward throughout the motion. Start with your hands at your sides and, keeping elbows slightly bent, slowly move your arms away from your body like you’re making a snow angel until they are side by side over your head. Do the reverse movement to return to the starting position with the weights by your side – this is one rep.
Triceps Pushdowns are one of many triceps extension exercises that can help you get that stylish horseshoe muscle appearance, and improve your bench press. You can do triceps pushdowns with a cable tower, pull down station, or even resistance bands.
Triceps extensions encompass a wide variety of exercises aimed at isolating the triceps for hypertrophy (size) and strength.
Equipment, Tools, and Other Considerations
These items are not required to be successful in bench pressing, but can be beneficial to lifters that bench press at any skill or weight level.
Wrist wraps can help keep your wrists straight and supported during bench press. They can help keep the weight safely and evenly distributed through your wrist and thus through the entire forearm and elbow.
Slingshot: A device invented by powerlifter Mark Bell who can bench 545lbs without special tools and 854lbs “equipped”. It wraps around your elbows and can allow you to overload your bench press by “10-15%” with the help of elastic tension from the Slingshot. It can also be helpful in taking some of the stress off shoulders and elbows during a bench press but is NOT a substitute for proper form and safe lifting.
Blocks or boards - board pressing uses wooden boards or something like benchblokz between the bar and your chest during a bench press. This decreases the range of motion for the lift and can help lifters work through sticking points (relative weak points in the range of motion), which can lead to improved bench without tools (“raw”). Here’s another article, from elitefts on board pressing and its uses.
GameMaker Studio 2.3.1 will allow you to build games for Raspberry Pi - here's how to get it all working!
GameMaker: Studio 2.3.1 will be introducing a significant amount of support for platforms running on ARM. For the most part, exporting to these platforms is a subset of the target platforms (specifically Mac OS and Ubuntu/Linux) that already are supported by GMS2, but the magic happens in the export! If the platform you’re targeting is running on an ARM processor, the build process will handle the heavy lifting. I’ve left a full guide below to getting your projects running on a Raspberry Pi - here are the important take-away’s if you’re familiar with the Ubuntu export process
When building for Linux normally, GMS2 builds a 64-bit binary. This is NOT the case with the ARM build process - it in fact DEPENDS on you running a ARMv7 architecture, which is great news for older hardware (Raspberry Pi 2 + 3).This also means that building your project with a Raspberry Pi 4 running Ubuntu Desktop is out of the question for now, as only 64-bit binaries exist officially.
You can build and run your project with Raspbian (the default Raspberry Pi linux distribution)
Warning: Depending on your project, performance will vary significantly - you should expect to overclock your Raspberry Pi CPU and GPU clock speeds to achieve best performance in graphically intense games. Most folks have their Pi’s overclocked, and it’s a very straight forward process that you can learn about here. I suggest getting a case for your Pi with heatsinks and fan, regardless of your configuration.
Known Supported Linux Distributions for building GMS2 projects on RPi
Ubuntu MATE (ARMhf version)
It’s important to note, while I haven’t tried it, the binaries generated should work fine on most distros running on ARMv8.
What you’ll need:
GameMaker: Studio 2.3.1 (beta currently available on the YYG website) with Desktop export running on either Windows or Mac OS
A Raspberry Pi (I have only done this with the Raspberry Pi 4 model B, but it should work with RPi 3’s as well at the very least).
A linux distribution that is for ARMhf or ARMv7 (The default Raspbian OS works perfectly)
Step 1: Setting up your Raspberry Pi
There are plenty of guides for how to do this online, so I’ll assume you can figure most of this out.Prepare your SD card with either Raspbian or Ubuntu MATE and boot into it on your Raspberry Pi. I suggest going with Raspbian, and most of my notes in here will be specific to it - it will be the most straight-forward option and likely the best performance on Pi. Once Raspbian has booted, let it update using the built-in update manager (it might take a little while) Find a way to entertain yourself... this might take a little bit.
Step 2: Install the dependencies
This is pretty much the same as it would be in any regular Linux setup to build your GMS2 projects, however, if you’re using Raspbian some of the regular dependencies will already be installed - so I’ve skipped the ones we won’t need right now in the list below. If you’re having an issue or using Ubuntu MATE, check out the full list here. > Open "Terminal" For each of these you’ll type “sudo apt install” followed by the listed name, so for the first one we’ll go:
Raspbian has the OpenSSH server dependency that GameMaker: Studio needs already installed, but it’s inactive by default. Browse to the Raspberry Pi Configuration window (located in the Raspberry Pi icon menu > Preferences > Raspberry Pi Configuration and over to the tab “Interfaces”. Enable SSH and press OK. Do not forget to enable SSH!
Step 4: Reboot
I can’t stress this enough - Reboot your Pi. Just do it, it may or may not do anything at this point, but it’s better than not doing it.
Step 5: Set up your connection in GameMaker
This is pretty straight-forward. In the upper right hand corner of your IDE window, change your target platform to Ubuntu.Add a Device for your Raspberry Pi. You can set the Display Name to anything you’d like to, Host Name should be the local ip address for the Raspberry Pi - an easy way to get this is by typing “hostname -I” into your terminal on the Raspberry Pi. By default, if using Raspbian, your username is “pi” and your password is what you set during the Raspbian setup. Here's what my device looks like - your hostname is most definitely different <3 Press “Test Connection” - you should see a message that the connection was successful! If not, double check that the IP address you dropped into Host Name is correct and that you followed step 3 to enable the SSH server. Press “OK” once you’ve gotten a Connection Successful message, and you’re off to the races!
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!
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.
I am not a top-100 player, as given the inevitable RNG of effects, matchups and draws in card games, and the lack of rewards for ranking up in LoR, I simply don't see the point in painstakingly grinding up to such a level. The highest I've climbed is low Diamond, but considering the above knowledge, I believe that at a certain skill level (perhaps at around Platinum), it's more about how much time one can put in than how skilled they are. HOWEVER, considering all this, I have the absolute conviction that this deck is a top-100 worthy deck.
This is the only deck that I've played since Day 1 of Call of the Mountain, with various modifications, and I believe that it is a completely undiscovered meta unicorn. I've never faced a similar deck on ladder, and my deckbuilding experiments with any other archtypes have left me completely unsatisfied with the lack of interaction and agency, as well as the sheer counterability of the vast majority of tools currently out there. A lot of people are frustrated with the current meta - a lot of points of which are covered by BruisedByGod in his recent video critique. To summarize his main points:
Most answers are completely outclassed by threats
Sheer lack of healing options locks out deckbuilding choices
Most top-tier strategies prey on lack of interactivity (Pirate Burn, Lee Sin OTK, Star Spring)
This is a Control deck which, while originally devised to prey on the inevitably popular Aurelion Sol and Troll Chant and abuse the broken, flexible toolbox of Invoke on Day 1, also manages to both answer all 3 of these problems efficiently.
Lunari Duskbringer x 3
Spacey Sketcher x 3
Lunari Shadestalker x1
Pale Cascade x 3
Unspeakable Horror x 2
Vile Feast x 3
Simply the best available early-game that an Invoke Targon deck could hope to muster - Diana functioning as both early game and late-game removal (we have just enough Nightfall Synergy) for practically no investment, Pale Cascade being legitimately one of the most broken cards currently in the game, and the ping cards also serving a modicum of uses at all stages of a match. Spacey Sketcher has been severely underrated so far - providing critical tools for certain matchups and/or providing early game minions without needing to actually run them (a fundamental weakness of faster decks top-decking late). Its 'discard-replace' synergy with our late-game, as well as Duskpetal Dust and meta-call flex cards is just icing on the cake. Finally, note how every early game card I've chosen scales well and still plays a role as the game goes later; as removal, Elusive blocking, tool-building, Burst-speed Nightfall, pings and cantrip Combat Tricks. This is an often overlooked but fundamental difference between Control early-drops, and aggro early-drops (such as Precious Pet). ~
Sunburst x 3
Vengeance x 3
These two cards, combined with any generated Obliterates, form the only proper removal this deck has - and were the catalyst for me creating this deck in the first place. All three of these removal types leave almost NO room for the opponent to interact with them, and I believe that is the sole condition for a high-cost removal spell to be playable in the current game state. NOTE: Ruination is easily and always played around at a high-level of play - and leaves the opponent with ALL of the agency/choice to play around it/bait it exactly how they wish, instead of you (whose only options are to play the card too early and get out-tempo'd afterward, use more than 3 mana elsewhere to catch-up at which point it becomes unplayable, or lose the game to a sudden-attack completely at your opponent's discretion) - the ultimate NO-NO for this deck: I never even considered putting it in. ~
Meta Call Flex Spots
Divergent Paths x 2
At times I feel as if this card could be cut to 1 copy, but right now 2 feels great against the current meta, and drawing into at least one is almost necessary in order to compete with Star Spring (Obliterate is conditional and too great a tempo loss early on). In other metas previously, I've experimented with 1 copy of Passage Unearned, as well as 2 extra copies of Lunari Shadestalker. ~
Literally Everything Else One Could Ever Hope to Need
Lunari Priestess x 2
Solari Priestess x 3
Mountain Scryer x 3
Moondreamer x 3
Starshaping x 3
I still believe that Invoke is one of the most broken mechanics currently in the game. This is one of the heaviest late-game decks I can possibly imaginable, yet the only cards above 5-mana we run are removal, and our mid-game minions and healing straight up provide whatever early OR late-game tools we might possibly need in any matchup - it's simply overly flexible (flexilibity in card games being a MUCH bigger deal than most people give it credit for) and not enough of a tempo/stat sacrifice IMO. I think that Invoke as a mechanic is even stronger when ran in bulk, and especially in a Control deck - as the game goes on slowly you generate a toolbox that can handle just about any dynamic situation that meta decks can throw your way. The spell-mana nerf to Living Legends has balanced it out quite a bit, however the same-nerf to Cosmic Inspiration still hasn't convinced me that it isn't in the top 5 least healthy effects that a game based on carefully stat-balanced of minion trading could ever have (hit me up with your Cosmic Inspiration hate!) - a large proportion our games are won by this disgusting effect. Solari Priestess and Starshaping need no introduction as some of the most popular, utilitarian Invoke cards, however Mountain Scryer and Moondreamer (not so much Lunari Priestess) really put in the work, and I've never seen anyone else play these cards. The former provides crazy mana-advantage as the game goes on given our huge focus on Celestials (it's a shame we can't afford to push its Invoke chances even higher), and the latter has juuussst the right stat distribution at 3/5 to blockade most midgame tempo plays out opponent might go for. NOTE: Aurelion Sol is straight up unnecessary to compete late-game, is always burdensome and clunky draw, ruins our surprise factor (though that doesn't exist anymore with this post being made), and we often outvalue decks running him anyway (don't forget that the original premise of this deck was 'How can I best remove Aurelion?'). ~
Matchups/Strategy (Order Based on Mobalytics Tier List)
Lee Sin (60/40)
A somewhat favored matchup - although more recent lists that have cut Bastion in favor of Nopify may be a bit more in their favor (a proper Ping Counter). Hard mulligan for Spacey Sketcher, Sunburst and our pings. Generating Silence (Equinox) for Mentor of the Stones/Zenith Blade is our main early game goal. Our Mid-to-Late game goal is removing all 3 Lee Sin's at the expense of practically everything else (the rest of their deck is pretty much completely irrelevant, but rushing them down is also pretty much impossible) - after which our win is basically guaranteed.
This matchup is sadly the most binary thing: Sunburst/Vengeance/Ping's VS Lee Sin/Spell Denial/Zenith Blade
The rest of both decks are basically irrelevant other than to slow down the level up/speed up the level up/Draw into above cards
Draw Draw Draw + Always save enough mana to Removal Spell + Ping if the opponent has 4 mana up late game
I believe that we are very, very heavily favored if played properly (although it's a VERY nuanced matchup to play right), and most of our losses come from bricking our early-game draws and/or not drawing/generating a single Starshaping/Golden Sister as their burn damage inevitably builds up. Hard mulligan for all 1/2 cost cards (only keep 1 Pale Cascade with a 1/2 cost minion).
NEVER, EVER play early minions proactively (e.g. NO turn 1 Lunari Duskbringer unless they play something) - only ever match however many minions the opponent has AND trade right away to minimise Make it Rain/TF value (For instance, if you proactively play a minion with nothing to trade it into, and then find yourself needing to play, say, Diana/Solari Priestess later - the opponent is basically guaranteed free additional AOE value: make EVERY chump blocker count)
ALWAYS open attack into Powder Keg's (usually with our single developed minion)
Take ANY trade you can get (even if somewhat unfavorable) to clear both sides of the board going into turn 8 - one of the ways we can lose is if Riptide Rex clears our heavy board and we only have time to develop one chump blocker before the onslaught - especially because Riptide is MUCH stronger against minions than the nexus > Late game, try to keep both sides of the board as empty as possible
If you find yourself with priority against their activated Plunder past turn 8, play small minions to bait out Rex without having to pass the turn OR play larger minions, especially with uneven health like Moondreamer to protect the rest of your board from potential cannons
ALWAYS try to find a NON-Rex'able position late game to develop Golden Sister, and save Pale Cascade if possible to protect her from Noxian Fervor and recover 6 previous health
ALWAYS have enough mana to remove Leviathan if the opponent has more than 8 mana on any given turn (prioritise Leviathan over Swain himself)
Sacrifice minions to TF attacks and remove Zap Sprayfin ASAP to minimise chip damage (which really builds up)
Be careful and make sure you always have a way to prevent Swain connecting with the Nexus (even if they develop him this turn and open attack the next); Pale Cascade is a good tool here
Pirate Aggro (55/45)
We are much more prone to bricking on draws here than Swain/TF, as we need quite a specific hand to deal with their onslaught - This is probably our most draw-dependent, low-agency matchup by far - as face-deck matchups tend to be. In addition - Captain Farron is much more effective against our removal strategy than the likes of Leviathan. Nonetheless, from my experience I think that we're still every-slightly-so favored in this matchup - often winning by the skin of our teeth. Starshaping/Golden Sister are mandatory late-game, and not bricking by not drawing/generating either is also basically a loss. Hard mulligan for all 1/2 drops, and keep a single Sunburst for Gangplank if your hand is already looking great.
There's nothing much to say here given the nature of their deck - pray your draws are good and take the obvious trades
A very unfavored and binary matchup (see below as to why) that has luckily become rarer recently. Mulligan for Removal/Invoke cards.
Save Starshaping for when you can actually make use of the heal (don't just play it on turn 3 because they're 'starting off slowly' - it's very important to maximise your leeway to survive Atrocity later on)
Try to remove Trundle on curve with Sunburst/Vengeance
Generate/Stockpile removal throughout the midgame
Sadly, none of these choices really matter in the end and the match comes down to luck - if Warmother's pulls a Level 1 Tryndamere on their attacking turn, the obvious open attack followed by a loss is all but guaranteed (Vengeance doesn't stop Atrocity in this case - leading to too great a health/tempo loss, and my previous Passage Unearned tech to deal with specifically this scenario simply wasn't worth the dead card in other matchups). We can also lose to a big levelled Trundle, or simply not generating/drawing into enough removal. Sadly these cases happen more often than not. Warmother's generated too much tempo if left unchecked by hard removal for even a single turn so there is little leeway for bad luck.
If Warmothers' timing and Invoke/draws are on our side, the matchup becomes pretty simple - Smartly use about a removal spell on their big guys for about 8 turns, play around Ruination and Atrocity, then cruise to victory.
This deck was basically created on Day 1 specifically to destroy Trundle/Asol. Sadly though, even at 75/25 the matchup is worse than it should be due to the nature of Invoke RNG - if one player draws into Cosmic Inspiration and the other didn't the match is over, full stop + the occasional shenanigans involving The Great Beyond uninteractibly going face and non-stop Living Legends value. Mulligan for Sunburst, Vengeance and pings.
Remove Trundle ASAP with Sunburst (Vengeance/Obliterates are best saved for Asol so getting Sunburst value while Trundle is still unleveled and 6 health is a big deal in terms of removal distribution)
Always try to remove Asol on the first turn he's played with Vengeance chaining into a ping to minimise the opponent's chance of getting game-winning Invoke RNG/matching your late-game value with free Celestials
If you still haven't drawn a ping late game, try to fish for Crescent Strike with Spacey Sketcher
Play around 7-mana Asol (Augur of the Old Ones) as much as possible
Pray you draw Cosmic Inspiration and the opponent doesn't
Discard Aggro (80/20)
I don't know why this deck is considered competitive - maybe because our matchup here is basically as favored as TF/Swain except without any gameplay nuance required on our part. Mulligan for 1-2 drops. Keep Solari Priestess/Sunburst if hand is good. Only necessary statistical losses to bad early draws against an aggro archtype.
Make obvious trades. Play around Mystic Shot on Diana. Chump block Draven/Jinx. Remove Draven/Jinx. Profit.
Another draw dependent, but quite favored matchup. Quite difficult to play though - you need to balance maintaining some modicum of tempo whilst also being able to deal with their crucial threats. Mulligan for 1-2 drops ESPECIALLY Pale Cascade/Pings, and Removal.
DON'T play ANY minion with less than 3 attack from turns 1-4 UNLESS you're getting tempo'd into the ground OR you have Pale Cascade (otherwise Fiora gets a free trade and the opponent gets to use their buffs reactively rather than proactively - giving you less leeway to remove her)
Save ping's for Fiora Barrier's, NOT Fleetfeather Tracker UNLESS you're getting tempo'd into the ground
Save a removal spell and mana for turn 3 Fiora, turn 4 Shen, turn 6 Genevieve and turn 9 Brightsteel UNLESS you're getting tempo'd into the ground
Basically the Pirate Aggro matchup but a tad bit slower and with no burn - giving you more leeway to make up for bad draws both early and late.
Make the obvious trades, pray to draw well and don't to let Genevieve get 2 attacks off
Basically the Trundle/Asol matchup except with no 'must remove ASAP' threats giving you more leeway to make up for bad draws. Celestial RNG and especially Cosmic Inspiration still give them a chance to win as usual. ~
Shyvana Dragons (50/50?)
I surprisingly, haven't faced too much of this deck yet personally, but looking at it's cards compared to ours, I think the matchup would be about 50/50 (an otherwise favourable looking matchup affected a bit by their high tempo removal and guaranteed Cosmic Inspiration in the form of Kadregrin). ~
This matchup is dependent on whether we draw removal for Ashe somewhat on curve, how much tempo they manage to build early on and whether we draw good enough to afford to play around Reckoning. Mulligan for Sunburst, Solari Priestess, Pings and Diana (only if you've already drawn support) as our other standard early drops are all pretty ineffective against theirs.
Remove Ashe ASAP
Try to Vengeance Sejuani on the attack if she directly attacks your Frostbitten minion in order to prevent the free value trade and maintain tempo on board.
Play around Reckoning as much as possible, especially if it wouldn't affect their own board too much compared to yours - maximise your 5+ attack minions to theirs if Reckoning begins to look more likely
Try to bait out an invested attack/Frostbite support for Trifarian Gloryseeker before pinging her - especially because Elixir of Iron is a bit rarer nowadays
Probably our most favored meta-deck matchup, and unfortunately rarer recently. Their win conditions - Kalista, Blighted Caretaker tempo, Neverglade Collector and They Who Endure simply don't stand a chance against our toolbox. Most losses come from unanswered Blighted Caretaker tempo. Mulligan for Spacey Sketcher, Sunburst and Pale Cascade.
ALWAYS pick Silence (For They Who Endure) or Stun (For Blighted Caretaker) off Spacey Sketcher
Try to hold a minion to play on turn 3/4 to kill an attacking Kalista with Pale Cascade AND get the Nightfall card draw
Play as reactively as possible with your pings - playing them proactively will almost always be answered by Glimpse Beyond, and when they run out of gas later on they will be forced to play their Glipmse proactively - your chance to strike!
Silence/Sunburst Blighted Caretaker as it comes down
SAVE Vengeance for They Who Endure - going into the late game, stockpile Silence/Sunburst and Vengeance and maintain enough mana (usually open-attacking) if necessary (IF can still afford to play They Who Endure that turn) to use one of the former followed by Vengeance to counter into their Atrocity: with this line of play, it's basically impossible to lose the combo
The biggest downside and sheer impossible matchup of this archtype. Maokai manages to pack even less interactivity/inevitability than we do, and the nature of our deck gives us no chance of out-tempoing Deep early OR late. Auto-concede. ~
A simpler aggro matchup than the others. Mulligan for 1-2 drops - especially Spacey Sketcher and Diana, as well as Sunburst.
ALWAYS pick the Stun spell off Spacey Sketcher, and save it for Diana, or of lesser priority, Nocturne/Ephemerals off Stalking Shadows
Removing Nocturne ASAP with either Sunburst or Vengeance is a HUGE priority
ALWAYS play around Pale Cascade
Play around Atrocity and Doombeast damage later on in the match
Another matchup that I haven't faced too much of just yet. Mulligan hard for Divergent Paths and Solari Priestess - Once we remove their uninteractive element trump-card in the Landmark win-condition, if we can survive their early tempo, the rest of the match should be a cinch given our heal/health-ignoring conditionless removal for their Champions. ~
Thanks for reading up to this point, and pardon my formatting, the ridiculous length and the sheer pomposity of it all. I still think Invoke is flexible to the point of being broken and the only reason the matchup spread is so good. I also think that with the release of this guide - more people will come to recognise this archtype and the element of surprise affecting enemy mulligans against an assumed more aggro, Nightfall-focused Diana archtype will be lost. People will also know to play around less common cards such as Sunburst, and I expect winrates to fall somewhat across the board. To conclude this guide, I'd like to say that this is this is not a healthy deck. At the deepest level, this deck is fundamentally about removing agency from your opponent and giving it to yourself, as well as securing the critical boon of having inevitability over your opponent in a game with the nature of LoR. If all decks were like this, LoR would completely cease to be fun. What else do I think is unhealthy right now? - Simple: anything removing interactivity from your opponent - ESPECIALLY as a win condition; Maokai, Star Spring, Cosmic Inspiration, Lee Sin. The avenues through which these cards can be interacted with are way too limited right now. A lot of the metagame nowadays is about having an uninteractable win condition, or focusing damage to face so fast the opponent has no chance to react - another form of non-interactivity. Here's hoping that the meta in the near future heads back in the direction of the close but fair midrange board battles we all came to love back in vanilla LoR. ~ (slinx4)
Gentlemen, Ladies and those otherwise addressed - we know you've been waiting for a good thing, and the survey results are finally ready! The answers were collected from you all during August 2020 with 1428 unique replies. That's a participation of 0.5% of all subscribers! That's really not too bad, when you keep in mind how popular these kind of surveys are. But we here at /peloton want to show you that this is all about presenting the information in the subreddit to cater better to our audience! Updated after a few hours to include some more historical data the final edit that for some reason wasn't copied properly
Without further ado, let's get cracking on the response
You and Cycling
1. Where do you live?
Largely the same picture as ever, with the US leading the way, the UK in second and then a sliding scale of Europeans countries. Slovenia continues to pick its way up the pile for obvious reasons! World Map to demonstrate
2. What's your age?
Pretty much the same as last year, with the usual reddit demographics of majority 20 somethings dominating.
3. What's your gender?
More normality here for reddit.
4. How much of the men's season do you watch/follow?
March '18 (%)
August '18 (%)
WT Stage races
WT One day races
Non WT Stage races
Non WT One day races
Literally everything I can consume
Whilst GT following may be down (somehow), all the lower level stuff is up, which makes sense considering how desperate we have been for any racing during the season shutdown.
5. Do you maintain an interest in women's professional road racing?
Do you maintain an interest in women's professional road racing?
Still very much a half/half interest in women's cycling on the subreddit.
6. How much of the women's season do you follow?
The following is true for the half of you that follows womens cycling.
Just the biggest televised events
Most of the live televised/delayed coverage stuff
All televised racing
Down to .Pro & beyond
7. How long have you been watching cycling?
Under a year
25 years +
Simplified the years a little this time, but whilst we have a fair number of newbies, most people have picked the sport up since around 2013/14.
8. Do you have like/dislike feelings about WT teams?
Once more, 14.4% of people really don't have feelings on the subject. Of those that do:
So, the most popular team this year is Jumbo-Visma, followed by Quick-Step & Bora-hansgrohe. Least popular are Ineos & UAE. As per usual, no one cares about NTT & CCC, with nearly 81% of users rating NTT as meh. Pretty damning stuff. Lastly, we have the usual historical comparison of how teams have fared over time, normalised to respondents to that question on the survey. Things to note then, firstly that the Astana redemption arc is over, seeing them back in the negative, maybe Fulgsangs spring issues helped aid that? The petrodollar teams of UAE & Bahrain are stubbornly negative too, with Israel keeping up the Katusha negative streak. Meanwhile, at the top end, EF & Jumbo go from strength to strength, whilst some others like Sunweb are sliding over time - their transfer policies no doubt helping that.
10. Do you ride a bike regularly?
No, I don't
Still a fairly small group of racers out of all of us
11. Out of the sports you practice, is cycling your favourite?
A new addition to the survey prompted by a good point last time, just over half of us rate cycling as the favourite sport we actually do.
12. What other sports do you follow?
Association Football / Soccer
Track & Field
Esports (yes, this includes DotA)
Motorsports (Not including F1)
Football always tops the charts, and Formula 1 continues to rank extremely highly among our userbase. Those who have a little following below 5% include Sailing, Fencing, Surfing, Boxing & Ultra-Running. Other cycling disciplines
13. Out of the sports you follow, is cycling your favourite sport?
Good. Makes sense if you hang out here.
14. How often do you participate in a /Peloton Race Thread whilst watching a race?
I always participate in Race Threads during races
I follow Race Threads during races
I often participate in Race Threads during races
I rarely/never participate in Race Threads during races
Slightly less invested than before, reverting back to an older trade.
15. How do you watch Races?
Free Local TV
Desperately scrabbling for Youtube highlights
Paid Streaming services
Year on year, paid streaming services go up - the increasing availability of live content legally continues to improve, and so do the numbers on the survey.
16. Where else do you follow races live (in addition to watching them)?
We can safely say that most of us were wrong about this one. That's not a lot of confidence in Richie Porte either, the man who was to finish on the third spot of the podium. Alexander Foliforov (0,23%) had just a tiny number of votes less, and that man wasn't even in the race.
24. What for you was the defining cycling moment of the previous decade?
We had a lot of brilliant suggestions, but these were the clear five favourites when we tabulated the results.
2018 Giro - Chris Froome Solo Attack
2016 TDF - Chris Froome Running up Ventoux
2019 TDF - Landslides, First Columbian Winner, Pinot's bitter abandon - This was one race for the ages
2016 Paris-Roubaix - Mostly known for Tom Boonen losing. Also, some guy called Mat won.
2019 AGR - MvdP with his incredible catch-up for the win.
Honorable mentions go to the Giro 2018, which had Tom Dumoulin winning, and of almost identical fascination to many of you - Tom Dumoulin going on someones porta-potty in the middle of the stage. Little bit of recency bias perhaps, but that's better than ignoring that this was for the last decade and firmly insisting Tom Boonens 2005 WC win was the biggest thing. Special shoutout to almost all the Danes present in /peloton who voted for Mads Pedersens WC win last year. It's an understandable reaction.
25. Any suggestions for the Survey?
Could you add a section on rider popularity, same as for the teams?
Ask how people became interested in cycling
Ask how people watch cycling (e.g. TV Channels/Streaming etc.)
If you could be an animal for one day, which one would it be?
Would you wear a facemask while watching a cycling race live?
Which race do you look forward to see the most every year?
Favourite riders of your own country?
How many bikes do you own?
We promise to feature one of these suggestions in the next survey Suggestions
Always have a “no” or “not interested” option
We will try to implement this. But it will also skew results. About the Survey
More questions about womens cycling would be nice.
Less questions about womens cycling
The subscribers are torn on Women's cycling, nearly a 50/50 split there as the survey showed - The moderators at /peloton are firmly in the "more cycling is better" basket, and we will continue to get as good coverage of womens cycling as possible.
Are you trying to give the moderators PTSD? Because this is how you give the moderators PTSD.
26. Any suggestions for the sub?
More stationary fitness bike related content
ALSJFLKAJSLDKJAØLSJKD:M:CSAM)=#/()=#=/")¤=/)! - Your moderator seems to be out of function. Please stand by while we find you a new moderator
The Weekly threads are great for these types of questions, where several people can contribute and build up once it is understood which information is relevant.
Allow limited doping talk in result threads.
Our experience is that "limited" will never be so, if we're going to moderate it fairly. Moderating is not a popularity contest, but believe it or not, we're actually trying to be as fair as possible. and for that, we need rules that are not subjective. Unless you have a stationary exercise bike.
Written original content is always great - recaps, old race reviews or interesting rider bios, etc.
More non-race threads
Try and do some AMAs with pro cyclists, coaches, trainers, etc
All of these are good suggestions, but remember that all of you can also contribute - The mods are sometimes stretched thin, specially in the middle of hectic race schedules. It's easier if one of you has a way to contact a rider or a person of interest and can facilitate the initial communication.
Standardize major event thread titles for better search.
We've worked on this! The Official Standard is now as follows: [Race Thread] 202x Race Name – Stage X (Class)
A wiki that explains how races work. Roles of diff riders/support staff. History of racing.
This sounds as a nice community project for the after-season, and hopefully many of you subscribers can contribute.
Tidy up the sidebar!
Come with suggestions on how to tidy it up!
Don't assume everyone reading is a man, "thanks, bro". But that goes for all of Reddit. I know you can't fix that.
We have chastised all the mods. They are now perfectly trained in gender-neutral pronouns. Be well, fellow being.
Have a buy you a beer link for the mods for all the work you do.
If we can implement this for hard liquor, you know we will.
Remove the spoiler rule during grand tours. It kills the hype.
The spoiler rule is one that is discussed frequently - in general - some users absolutely hate it, but a majority love it. Perhaps we'll include a question in the next survey to see how this divide is exactly.
Lose the spoiler tag when it is for serious things; Lambrecht death, Jakobsen fall.
We actually do - whenever there is a matter of life or death, we think public information is more important than a spoiler rule. But at the same time, we try to collect all the different posts into one main thread, so to keep things focused and letting very speculative posts meet with hard evidence from other sources.
Less downvoting of opinions that differ from the fashionable consensus.
This is a tough ask of the internet. While we can agree that voting should be done accordingly to what insights they bring, not subjective opinions, it is very hard to turn that type of thinking around. We can ask of you, our subscribers, that you please think twice about hitting that downvote button, and only do so because of you think a post is factually incorrect, not because it differs with your own subjective opinion. That's the primary analysis of the survey! Feel free to contribute with how you experience things here!
Binary options are complex, exotic trade options, but these are particularly simple to utilize and understand the way they work. The most familiar type of binary option it the high-low option and it’s relatively simple to comprehend. This technique is also referred to as the fixed-return option and provides access to commodities and foreign exchange, indices and stocks. Risk Disclosure: binary options is a form of high risk investment. This type of investment may not be suitable for all investors and due to this reason traders may lose part or all of invested funds. Please note: Binary365.com DOES NOT offer any investment advice nor any services related to binary options trading. All information provided on this website is for informational purposes only. The ... Binary Trading Guide – How To Trade Binary Options. This page explains binary trading from start to finish. Learn everything you need to know about trading binary options for profit. How to trade binary options explained, links to tutorials, example trades, strategies, tips and resources. Binary options provide a new form of trading for many investors and provide a relatively easy and ... Binary options traded outside the U.S. are typically structured differently than binaries available on U.S. exchanges. When considering speculating or hedging, binary options are an alternative ... The Most Complete Binary Options Guide - Start From 0 And End Up In The Money! Would you like to finally learn how to make money from home, with virtually 0 investment? This book is for you! The famous Binary Options finally reveled! The Problem Finding good and unbiased resources on binary options is becoming increasingly challenging due to disinformation, fake testimonials and more-than ... Welcome to the largest expert guide to binary options and binary trading online. BinaryOptions.net has educated traders globally since 2011 and all our articles are written by professionals who make a living in the finance industry and online trading. We have close to a thousand articles and reviews to guide you to be a more profitable trader in 2020 no matter what your current experience ... Binary Options Trading Tips,Investing in Binary Options,Binary Options and Its Benefits,The Simple Steps of Trading,Binary Options Trading Tips, The complete guide on binary options trading and online stock trading. Follow the tips. Become an expert and reap rich profits. Day trading secrets. Swing Trading: Expert Advice For Novice Traders – Minimize Your Losses And Maximize Your Gains Using ...
How to trade binary options in Nadex for profit step by ...
Binary Options are a fantastic way for beginning and advanced investors to get into trading currency and stocks. On this channel we will be sharing successfu... Binary Options Are Never Guaranteed To Profit 100% Of the Time. But This Strategy Sets the Bar HIGH. See inside here: http://tinyurl.com/RecommendedBrokerB... Binary Options Beginners Guide To Trade Size Money Management - Duration: 16:55. The Binary Lab 7,750 views. 16:55. Day Trading Options For Beginners - Duration: 13:04. ... Free practice account: https://www.nadex.com/demo/?CHID=13&QPID=514243624&QPPID=1&ref=YouTube Listen to Gail Mercer the founder of Traders Help Desk, guide y... Trusted spots blog https://trustedspots1.blogspot.com/?m=1 To register a free account on desktop or laptop, click here https://bit.ly/3ghvlt5 To register a f... https://binaryoptionsbeat.com/ #Binaryoptions #Nadex #Nadextutorial You can always contact me via [email protected] In this video I tried to explain ...