It exists, and it is wonderful. Hands down the best stuff for diaper rash I've ever used.
834 karma · joined May 14, 2009
One question: That seems like a really permissive license for a $9.99 app (I realize GitHub's just got the core). Are you worried about someone cloning it?
One request: I don't know if it's possible, but in iOS Tweetbot the bot's pictures show the unmodified picture first (requiring a swipe to see the bot's work). It feels to me like it would be better to show the primitive version first, but I realize this may not be feasible or universally preferred.
I am sympathetic to the author's UX arguments, but it has always seemed to me like the OS vendor was clearly the party whom I wanted to handle my virus protection, if any. I'm already obliged to trust them and they're in the best position to do the job (API access, etc.)
If you as a third party want to convince me you're better at protecting my computer, you've got an uphill battle considering the hacks necessary to do the job (and it never seemed like lots of AV API support is the answer, since you could just build first party AV functionality instead with better integration). Also not convincing: hundreds of non-AV features like a password manager.
"Better user experience" would not be the way I describe it.
Consciously making a decision before deciding to buy a new thing is a laudable practice; it's the mindless spending of money that really kills you.
It is said that it took Steve Jobs ten years to buy a couch. Without making a value judgement one way or the other on that long decision, I'll just point out that in the end, he did buy that couch.
I tend to think of Ansible as supporting a flexible combination of declarative and procedural approaches. Within a particular sequence of tasks, it's procedural. Those lists of tasks are typically combined into a role or the like that is typically more declarative in its application. Of course application of roles is actually procedural in that it happens in the same obvious order it's defined, but the higher level organizational constructs like roles have more of a declarative feel to me (I'd assume that's by design).
Sure, I'm not thrilled with having to learn another language to get anything done. But it's so much better than what came before that I don't care. Besides, Bash and friends certainly have their quirks as well.
Not a fan of "worlds" as proposed below. I have a feeling we're all just projecting our own favorite genre conventions here, but your different approaches remind me of different characters more than anything else. Ever play a game where you had a choice of approaches with different characters? Or had to switch between them and coordinate action or share information?
I'm sure there's plenty of people who possess the union of these skill sets (and of course, there will be plenty of actual human players that will), but you could describe your trees more as character growth/background/capabilities/backstory.
You would then have interesting story possibilities here—I would love the idea but I suspect you guys might consider story elements as potentially distracting.
Since you're here: have you considered adding Kickstart file syntax? RHEL's pages tend to be pretty bad (the CentOS ones are better I know).
I realize there's a good deal of handwaving here--particularly at 3 and especially 4. But, is this a bad idea? Seems like 4 can be replaced simply by the owner reforking, too.
I bet it's frustrating, though, that you can't do more to address the real problems, like lack of (apparent) incentive to keep this stuff up to date. You have to resort to clever sort-of hacks like "put this magic string in your request so someone will read it". A solution which, I might add, sounds a lot like the problems people are talking about when they talk about inscrutability.
Very much of the time I feel, "If I knew what the problem[s] [was|were] it'd be solved by now!" That's not exactly true of course but of course diagnosis is a large part of the total solution.
This type of an answer that Colin gave above does not exactly win friends and influence people in most situations where you're part of a team or hierarchy. Can anyone share what they've done to give better answers in these cases? I understand why people want the answers, but I don't have them to give right away particularly when it's Someone Else's system.