And... for those that missed it RaW and Ral means???
And really neither one is a GREAT way of solving things, they're just the ONLY way to solve things until they're expressly cleared up in the FAQ.
The problem with Rules as Written is that sometimes rules are badly written. They wind up having interactions with other cards which the designers didn't predict when they wrote them, they fail to use important keywords clearly and consistently *coughFFGcough*, they don't bother to dub something like a Boost or a Barrel roll a 'Maneuver Action' or something similar so it falls under the rules for maneuvering onto a proximity mine, etc.
The problem with Rules as Intended is that you have no idea what the designers actually intended. You may think you do. You may even be right. But just as often, what you consider to be the obvious, "common sense," (god I hate that phrase - it means common as in shared or uniform, and NOBODY has the same experiences and biases, so everyone brings a very different, uncommon brand of common sense to the table, making the phrase meaningless) interpretation of something, the designers may have come at it from a completely different angle.
Maybe they wrote the rule with a future card or rule in mind, and that's why it seems a little weird and out of place. Maybe (see rules as written) they flat out wrote the card wrong, giving you the wrong impression of their intent. Whatever the cause, as bad as following the Rules as Written can be (assuming you can even agree on an interpretation of THAT), delving into the land of "here's what they "obviously" meant by that" is even more dangerous, because you're not doing what the developers intended - you're doing what you'd like to think they intended, and that's a very slippery slope.
It reminds me of that old Churchill quote about how democracy is the very worst possible form of government, except for all of the other ones. Reading the rules as written is usually the worst possible way to try and interpret a questionable rule - except for all the other ones.
Because you don't know.
With the Vader thing, for example, you have two ways of taking the Rule as Intended. The developers intended Vader to be able to use his effect and blow up his ship, even if it only had 1 hull remaining to pay the 2 damage cost. OR The developers worded it the way they did to ensure you couldn't use his ability unless you had at least 2 hull remaining.
You could make an argument for either, both come from a fairly straightforward point of view. You were meant to pay the entire cost; if you can't, you can't use the ability, OR, you take both damage simultaneously, and are meant to be able to use his ability even if you are destroyed without being able to technically take two damage before doing so. As you've seen, there are cases to be made for both, there are precedents pointing to both, parallels for both arguments can be drawn from other examples in the rules, and both sides obviously feel that their side is the one the developers intended.
Which makes the entire concept of Rules as Intended one purely of bias couched in the disguise of this mythical 'common sense,' projecting your own interpretation and intention onto the rule and calling it the developer's. So again - Rules as Written is a terrible way to interpret a difficult rule. It's just better than the other way.