Ask HN: What would an MVR mean to you?
So earlier I stumbled onto the idea of a "Minimum Viable Repository."What would that mean to you?
And that's because of bias. Moreover, I've cited authors who are leaders of these fields, who present at TED and speak in recent discussion forums. McKenna is modern. Stamets is modern.
You just don't read these people, and that's why I cited the madinamerica.com article.
You're just telling me about linguistic and intellectual biases that I'm already fully aware of, and that I tried to anticipate with my post.
And operative word: "if" -- "if" that research is flawed. What are you even arguing? I could argue that against modern medicine, but that is circumstantial and requires precision. What you are saying is not precise, and hardly even relevant; or rather it is too vague to be relevant. Any research can be flawed. But there is even a further question of interpretation of that research; hence why I say "understand." You're using broad strokes as if I am doing so, when I am not.
I honestly just think it's linguistic/information exchange bias going on here. I'm citing those I'm reading. You're telling me that anything could be inaccurate or falsehood; that doesn't get us anywhere.
How did you get that? Honestly? How? I'm telling you to read up on how ancient mysticisms categorize these problems and relate them to advanced, therapeutic drug use.
Somehow you got "ignore the problems" when I explicitly tell you to go read alternative research on the topic.
Honestly, wtf? My post says "Go read book X" on the matter, and you want to start jumping to claims of "ignorance."
Dude.
And I'm saying "Many," dude. "Many."
Where are you getting "ignorance" etc? I'm not espousing universals here. I'm not at all saying it's black or white. I too am speaking in generalization which can be subject to counterexample.
Read. May I add some color to my writing? Gosh.
If you're going to start throwing out "your wrong," I must ask you to read. Read.
And we're talking about schizophrenia. Why am I being charged with opinions that I haven't even expressed on psychosis? I'm not here to discuss the whole range of psychosis.
— http://www.madinamerica.com/2012/02/why-anti-authoritarians-...
There are too many everyday people armed with psychiatric terms.
Stop it. Many nootropic and psychotropic drugs induce many of those hallucinations. Accept it. And learn how to understand what your body is telling you, rather than treating it like it's some operating table experiment that you'd being graded to poke and prod. Your body is a diagnostician, albeit a cryptic one that has needs, demands and quirks of its own. Most of you simply do not know how to live in your skin because, for one, you were likely raised religious and you've learned how to spite your own "holy temple," not only with deeds but in your minds, your mental habits and cognitive hygiene.
Read a book, like Food of the Gods or something about the organic complexity and biodiversity of this world. Understand.
Stop fearing Nature, and understand how to become harmonious with it.
So earlier I stumbled onto the idea of a "Minimum Viable Repository."What would that mean to you?
Good on Money elf!
"Huzzah!"
Why not use github Pages and scrape the github repository for necessary data? It's all harmless recipe stuff anyway. Non-github users could be asked to use e-mail to place recipes, and can be informed that they can use markdown. Or even present a web form that sends an encrypted e-mail for them, employing that wicked JS textarea enhancer we saw the other day, for markdown syntax or even allow haml.
Re: {url_block}/new
Recipe Name: {name}
Date: {extracted_from_email}
Subject:
{haml_recipe_body}
The github haml pages can have links station'd at the top or bottom to pre-fetch categories, previous, and next pages. The github Page Index can include a JS that builds the UI of the site via DOM manipulation, based on a lightweight Web app hosted elsewhere and called in via ajax.Summary: Total MVR (minimum viable repository).
"Never attribute to malice that which is adequately explained by stupidity."
I am asking _why are you using inline styles?_ I'm trying to explain "stupidity," not "malice." You're interpreting assumption of malice from my tone, style, and frustration. And I am frustrated, furious even. I'm furious about typesetting. I'd happily go down being that guy. The guy who foams at the mouth and rages about typesetting; what's more, when it's about liberating dyslexic users.
Yes, go ape-shit about typesetting.
I'm citing my sources, and making my arguments. You're not reading me aright. And that's a matter of "opinion filter"; that's all I can really say about that. We don't read the same self-help books. Where I come from, Nietzsche and Mencken are the tour de force, not diplomatic tongue. My apologies if you feel that is inappropriate for Web development practices; but I honestly do not care. And moreover, I just saw Torvalds flip off Nvidia. So, what? Who do I follow? Not one of you has the right idea on personal brand.
I'm asking why. The question is why. Why? It's "why?" "Why?"
I'm calling them "poor development practices." How do you get blame out of that?
"(nonemotional deadpan) How?"
Right here.
With classes like "divOutlineItem" and inline CSS padding, not one of you bothers to note that. It's like I'm wasting by bloody time learning best practices only to bring them back to developers who just do not seem to care. And I'm supposed to yield to claims of "amazing software" and age-authority.
I'm not even sure what to say anymore. You're absolutely right. I, as a Web Developer, for whatever that is worth, have no business being here in the Hacker News community.
Cheers.
"One does not have to be evil to be hated. In fact, it’s often the case that one is hated precisely because one is trying to do right by one’s own convictions. It is far too easy to be liked, one merely has to be accommodating and hold no strong convictions. Then one will gravitate towards the centre and settle into the average. That cannot be your role. There are a great many bad people in the world, and if you are not offending them, you must be bad yourself. Popularity is a sure sign that you are doing something wrong." -- http://halfhalf.posterous.com/dont-work-be-hated-love-someon...
What makes you right and that ^ wrong? Given that you are trying to guide me, for some reason, I think this is an absolutely fair question. Why follow your advice and not Adrian Tan's? I'd absolutely love to understand where you are coming from since what I have quoted, and then twice, outright contradicts what you are saying.
And it actually fits well within the framework of this entire thread, even if it does not get my dyslexic-accessibility agenda further.
Further, it might be amazing software. But that is an opinion. Plone is amazing software, but I wouldn't work in it. Diazo is amazing software, I wouldn't work in it. Drupal is amazing; wouldn't work in it. Joomla, etc., etc., etc.
I know things can be fixed. My concern is right now, what are the consequences of architectural decisions like his software? -- In my mind, immediately: larger Web footprint, inaccessible to dyslexics, more costly (even if it is tiny, but that is relative total footprint).
I'm not calling you names or insulting your intelligence. I'm being critical, and expressing frustration in an intimate way. The all caps are a rare thing, but as I said: I am mad. I want you to know that. So please stop re-iterating that it is not "effective." I don't think anyone here has the background in sociology or communications to really support their arguments on that matter. Just one programmers' opinion to another.
My selector works on just about every other site. I assume most of them do not have inline styles on every paragraph.
Thanks for the advice. I'll keep my distance then.
You haven't even tested it, nor do you even really know what Stylish is, it seems, and you're arguing with conviction.
What am I doing here?
"One obvious quick and low-cost solution is to make a CNAME Record that renders the dyslexic font via CloudFlare; like mobile."
I just spurted that out while reviewing another forum where I have made the suggestion to render dyslexic fonts. The above suggestion would not have to impact anyone, and it is trivial to pull off. The outcome is there becomes a reserved DNS space for http://{dyslexic_contextualization}.{domain}.{ext}.
So, for example, like with mobile's http://m.domain.com: http://d.domain.com or http://dys.domain.com.
What is needed here is not more code, but agreement and strategy. But before all of that, an understanding that this is a problem, regardless of the number of people it affects. Dyslexia is a feature of nature; so pointing out that it only affects a small number says nothing about the future holds. And even further, dyslexia is a spectrum disorder, so it plausibly could be and probably is more widespread than we understand it. Most people live with it out of shame or fear the consequences of "coming out."
I'm _sure_ we're all on the same page with these points I've made, and that I really did not need to express them. Then again, the tech industry is hotly debating sexism as if women were "coming out of the closet": "I'm a programmer!"
If that's what you mean by your concluding comments. Yes, I should be working on software for these issues, and I am; -- but in my morning reading time, my crutch was kicked out from under me. If you want to say that you disagree with my style, that's fine. I disagree with yours. Most people, most of the time, disagree when it comes to details, and certainly, even further, on opinions of style. I'm not going to lose sleep over people disagreeing with my diction. If I did that, then I'd never get any sleep. (That is, I have not, and I will not change my style. I'm being myself, and using my own voice.)
And it still isn't even clear why this is the case, that my Stylish "!important" overrides are not overriding the inline styles of that Web page. I've provided a link to my post which contains my Stylish snippet. You can see it for yourself, that this should not be happening, given the rules of CSS Specificity.
I dig your suggestion, but your criticism I feel lacks sufficient observation.
I'm happy if it is a rocky start. But I side with Wittgenstein: "My difficulty is only an — enormous — difficulty of expression."
Do you understand what the wanted effect is? Because I'm pretty sure the gist of this entire discussion is: Don't use inline styles, which any front-end developer worth their salt would already agree to[1], outside of the accessibility debate. But what is more, accessibility might be one of many reasons why a front-end developer would raise the point about inline style at all.
And it would be terribly presumptuous of you to assume that my persona given here is found in all of my social activities. If you assume this, you're not being fair (really, to yourself).
You need to understand that a handicapped person just hit a Web page, out of the hundreds, if not thousands, that are hit a day, that, in my understanding, just overrides that dyslexic person's crutch, that handicapped person's wheelchair. When that page loaded, I personally _felt like_ someone (accidentally) kicked my crutch out from under me, or criticized me because I am not able to perform as well because of a handicap. This is how accessibility issues play out[1]; people feel hurt and victimized by facts of their obscurity which they cannot control.
I am very confident that you are not fully appreciating the gravity of the issue here.
But thank you for the advice.