Sex differences in intimate relationships (pdf) - <AUTHOR> http://arxiv.org/pdf/1201.5722v1 <comment><USER2> They don't seem to do a great job interpreting their data. Looking at the chart, people have their "best friend" (aka, most called person) of the opposite sex until around age 50, when it becomes pretty even.

A better interpretation of this is just that until that age you generally call your partner the most, which is usually the opposite sex. But when you are older, you probably call your children the most, whose genders are uncorrelated with yours.

<comment><USER3> "But when you are older, you probably call your children the most, whose genders are uncorrelated with yours."

Unless you are female, which is the salient point of the article. Mothers show a gender bias towards their daughters, whereas middle-age men don't appear to have a gender bias.

Figure 1a (best friend) is basically symmetrical: gender bias of the best friend is opposite sex. The bias peaks for women at 27 and for men at 32, gradually decreasing until the best friends for both are slightly female- biased in their 70s.

In Figure 1b (second-best friend), the 2nd-best friend for 20-something males is another male. The bias gradually declines until by 40 his second-best friend is 50/50 male/female.

But for second-best friends, "women show a striking reversal" from same-sex to opposite-sex. A 20-something female's 2nd-best friend is also female, but it strongly reverses towards males (peaking in her late 40s).

If my interpretation (of their interpretation) is correct, these graphs are showing that a female's best friend is initially her husband, but he is gradually replaced by her daughter: "the younger (25-year) peak for 50- year- old men is half that for women and shows a more even sex balance, whereas that for women is strongly biased in favour of female alters (presumably, daughters)". The husband, in turn, falls from 1st-best friend to 2nd-best friend (replacing the formerly female one).

"Finally, fourth, our results provide strong evidence for the importance of female matrilineal relationships in human social organisation. There has been a tendency to emphasise the importance of male-male relationships in an essentially patrilineal form of social organisation as defining human sociality [20], but our results tend to support the claim that mother-daughter relationships play a particularly seminal role in structuring human social relationships, as has been suggested by some sociological studies [21]."

EDIT: attempted to increase clarity. Not sure what the HN takeaway is.

<comment><USER4> > Mothers show a gender bias towards their daughters

Or men simply dislike it way more to be called by their mother (or calling her). I am a bit guilty of that myself.

<comment><USER5> It makes complete evolutionary sense, though: Women are always completely sure that their children are theirs, and men can never be.

So if your daughter physically came out of you, any people that physically comes out of her are undoubtedly your actual grandchildren. A safe investment. Your son, on the other hand, could always get cuckolded.

</comment></comment></comment></comment><comment><USER6> It would be nice if they had more data in their network, e.g. a dump of the Facebook graph that they could match to the phone records they used, so that they had information on parent/child relationships and romantic connections. I wonder if social networking companies would be open to cooperating in such research.

Of course, it opens a can of worms on the privacy front. I'm not sure where they got the data from that they used, but I can't help but wonder how they could legally do this research, since prima facie any use of phone records for this purpose would be against most EU privacy legislation. (not saying they did anything 'illegal', just that at first glance it seems to be at least pushing the envelope).

</comment><comment><USER7> Aren't boyfriends/girlfriends/spouses/partners the obvious confounders here? They don't seem to address that point, yet they observe that the "best friend" is usually of the opposite sex. That may be true, but the study seems to be making an argument about "friends," not sexual/romantic partners.

In other words: this paper seems to fail the whiff test.

<comment><USER8> I'd be much more concerned that it's talking about cell phone usage in a single European country, and tries to make more universal conclusions. Now, it may tell you something about the culture, but to use an evolutionary framework seems to be... a bit of a stretch.

<comment><USER9> From which country is this data. I cannot find it in the article.

</comment></comment></comment><comment><USER10> Document over at Google Docs PDF Viewer [https://docs.google.com/viewer?url=http://arxiv.org/pdf/1201...](https://docs.google.com/viewer?url=http://arxiv.org/pdf/1201.5722v1)</comment>


Ten things every coder-programmer do - <AUTHOR> http://dhirubhaism.com/ten-things-every-coder-programmer-do/

<comment><USER2> Well, if you have to put up with such people, you have my condolences.</comment>


Leonardo Da Vinci's "Codex Atlanticus" Now Online - <AUTHOR> https://mymodernmet.com/leonardo-da-vinci-codex-atlanticus/ <comment><USER2> Example of too much design and JS, cluttering up the value of the content. Here is the 10 first images with higher resolution. Increment the number to get the rest: [http://codex- atlanticus.it/assets//2000/000R-1.jpg](http://codex- atlanticus.it/assets//2000/000R-1.jpg) [http://codex- atlanticus.it/assets//2000/000R-2.jpg](http://codex- atlanticus.it/assets//2000/000R-2.jpg) [http://codex- atlanticus.it/assets//2000/000R-3.jpg](http://codex- atlanticus.it/assets//2000/000R-3.jpg) [http://codex- atlanticus.it/assets//2000/000R-4.jpg](http://codex- atlanticus.it/assets//2000/000R-4.jpg) [http://codex- atlanticus.it/assets//2000/000R-5.jpg](http://codex- atlanticus.it/assets//2000/000R-5.jpg) [http://codex- atlanticus.it/assets//2000/000R-6.jpg](http://codex- atlanticus.it/assets//2000/000R-6.jpg) [http://codex- atlanticus.it/assets//2000/000R-7.jpg](http://codex- atlanticus.it/assets//2000/000R-7.jpg) [http://codex- atlanticus.it/assets//2000/000R-8.jpg](http://codex- atlanticus.it/assets//2000/000R-8.jpg) [http://codex- atlanticus.it/assets//2000/000R-9.jpg](http://codex- atlanticus.it/assets//2000/000R-9.jpg) [http://codex- atlanticus.it/assets//2000/000R-10.jpg](http://codex- atlanticus.it/assets//2000/000R-10.jpg)

UPDATE: Threw together some simple HTML/JS for simple interaction: [https://toogoodtogo-alerter.com/static/davinci.html](https://toogoodtogo- alerter.com/static/davinci.html) (no analytics)

<comment><USER2> UPDATE Nr2:

-All images to browse on Dropbox: [https://www.dropbox.com/sh/kf39feyjhqub1rq/AABsKUe3YB7Jxo4ub...](https://www.dropbox.com/sh/kf39feyjhqub1rq/AABsKUe3YB7Jxo4ubqz22Fl7a?dl=0)

-One big ZIP: [https://www.dropbox.com/s/82alw5mex6zqz6f/davinci-img.zip?dl...](https://www.dropbox.com/s/82alw5mex6zqz6f/davinci-img.zip?dl=0) (1,1GB before+after zip)

Thanks to opsecisameme for the wget trick

<comment><USER3> I turned the .zip into a .PDF based on a simple alphabetical sort on the filenames.

[https://www.dropbox.com/s/35xdelkimqc1k4i/codex_atlanticus.p...](https://www.dropbox.com/s/35xdelkimqc1k4i/codex_atlanticus.pdf?dl=0)

My guess is that the page ordering is pretty far out of whack, but at least it's browsable and easily-archived now.

</comment></comment></comment><comment><AUTHOR> Link to the actual Codex Atlanticus itself:

[http://www.codex-atlanticus.it/#/](http://www.codex-atlanticus.it/#/) (scroll to bottom right for link to English language version of site)

</comment><comment><USER4> Some of these are awesome, cool enough to put up on my wall on canvas or so. But for that something a bit more high-res than 2000x2000 would be nice. Does anyone know of a higher res version?

<comment><USER5> Resized some to 2x with great results: [https://waifu2x.booru.pics/](https://waifu2x.booru.pics/)

</comment></comment><comment><USER6> Cool fact. All of this writing is in mirror image reverse writing so that no one in contemporary times could read his notebooks.

He taught himself how to write in mirror image.

<comment><USER7> This always baffles me. It's significantly less secure than rot13 (similar in its idempotence) and it seems to me that any curious mind would identify the letter shapes, notice that they're backwards, and soon work it out. Was this actually a mystery, or was it merely a foil that would prevent comprehension if somebody only got a glimpse?

<comment><USER8> I suspect the latter, but most people take a while to puzzle it out. I got good at reading upside down for some reason, and the skill still rewards me on occasion.

<comment><USER7> When I was in high school, I taught myself to write mirrored, and tortured (which, in retrospect, was kinda flirting with...) an english teacher. The teacher was annoyed/impressed/tolerant, and their approach was to read my papers in the bathroom with the mirror. They were dismayed when I simply held the paper up to the ceiling light.

To this day, I'm occasionally confounded by doors that have "HSUP" written on clear glass -- it's actually a "PULL" but I read the "PUSH" and _smack_. Other than that, I'm happy to have the skill. :P

</comment></comment></comment></comment><comment><USER9> It's beautifully organized, but I want to ask about why they say it's _"now"_ online? Weren't these available online before (in a less organized way or in lower res)? If not, why not? Was someone preventing copyright-free material from being published?

<comment><USER10> These were not available in their entirety online before.

That is because the only copy was held by the Ambrosian Library, and presumably they have had other priorities than digitizing those 1200 pages.

</comment></comment><comment><USER11> A while back I read a text by DaVinci describing the process of drawing (if I can find it I will add a link) and his description seemed to me almost like he was describing how a ray tracer works.

This 3D sketch of his makes me think that if computers had existed, he could easily have been the first to have coded a ray tracer:

[http://codex-atlanticus.it/assets//2000/000R-710.jpg](http://codex- atlanticus.it/assets//2000/000R-710.jpg)

</comment><comment><USER12> Looks like the app was built with Vue.js. [1]

The design is very "consultant"-y, which means over-engineered and focusing on what looks "cool" over web usability. But looking at the website I believe it was mean't to be deployed via touchscreen kiosks at the actual library/museum. So the form factor makes more sense for that than consumption via web browsers and search engines.

The keyboard controls are less than to be desired, you can't zoom in and go to the next page without it reverting to the previous view and doing a big transition. Which is not how most document viewers or image galleries work...

[1] [http://www.codex-atlanticus.it/#/Overview](http://www.codex- atlanticus.it/#/Overview)

</comment><comment><USER13> Is there a torrent or something so that I can look at this in a reasonable format?

<comment><USER14> If you consider a bunch of JPGs reasonable, just

      wget http://codex-atlanticus.it/assets//1000/000{V,R}-{1..1118}.jpg

<comment><USER13> Thank you for this!

        wget http://codex-atlanticus.it/assets//2000/000{V,R}-{1..1118}.jpg

for 2k x 2k res

I'm grabbing all of these, if people are interested I can make a torrent so we don't slam their servers too much.

<comment><USER15> magnet:?xt=urn:btih:D69E07DD344D26ED13396141F6EA77A1DFC2348C&dn=codex- atlanticus.it

<comment><USER16> missing 527 verso, for example.

Read this [https://news.ycombinator.com/item?id=19947001](https://news.ycombinator.com/item?id=19947001)

<comment><USER15> 000V-527.jpg and 000R-527.jpg are included. Is there a third file?

</comment></comment></comment></comment></comment></comment><comment><USER17> Anyone found a high-quality printed edition of these? I only found a couple fragmented versions with questionable quality.

<comment><USER18> Yes. Go to [http://www.leonardodigitale.com/index.php?lang=ENG](http://www.leonardodigitale.com/index.php?lang=ENG). Flash must be enabled. Click on "Browse", choose "Codex Atlanticus" ( _not_ the Hoepli edition). Then for every page you read, it displays the text (in Italian) from that page in the other "window".

Screenshots in action: [https://i.imgur.com/HLhnEKQ.jpg](https://i.imgur.com/HLhnEKQ.jpg) [https://i.imgur.com/gH81s52.jpg](https://i.imgur.com/gH81s52.jpg)

<comment><USER17> Thank you, although I'm looking for a high-quality printed reproduction/book, not digital.

<comment><USER18> Oh, I thought you meant "printed" as opposed to "handwritten" or "cursive". Oops.

</comment></comment></comment></comment><comment> master-litty I dream of making something to this effect; A notebook full of your life's deepest works. I'm sure many others feel the same way too.

I wish I could make more time.

</comment><comment><USER6> I really want there to be a couple pages with cat paw prints in ink walking across the pages.</comment>


How I turned a MVP into a SaaS in 1 month - <AUTHOR> I don't know if you remember but I already posted here, my app was called LongLiveSS, it was a very bad choice... I know, but the idea was good and few people were interested in the solution and subscribed to the newsletter so I decided to make a better version.
The first release (built in 7 hours) was horrible, the app wasn't loading JavaScript on some pages, meaning a blank image as screenshot, sometimes the server freeze because I was using the free plan on heroku and so many other bugs I discovered.. that wasn't very serious but now it's here. The 2.0.
This app is still very minimal and does only one thing but it does it well, taking screenshots at regular intervals. On free accounts it's 3 days min. interval but if you decide to upgrade you can take a screenshot every 5 min.
I am planning to add these features pretty soon
- Up to 3 Links
- ZIP archive download
- Push notifications
What would you like to see in the next version?
Learn more at https://urusparadox.com/?utm_source=hackernews <comment><USER2> What are the use cases for taking regular screenshots?

<comment><AUTHOR> Everyone is asking me this question so I guess I have to add this info on the homepage, you can use the app to make sure your ad/content is showing in the right place, spy on your competitors, track your seo ranking over time or simply archive your favorite website!

<comment><USER3> Your pitch makes it sound like this is a desktop app that takes screenshots of my PC screen, so I was very confused on why anybody would want this. You should talk about why your product is beneficial -- skip the boring feature sales pitch until later on down the page after I'm interested -- don't make people think too hard about what you're offering. If it's for

> to make sure your ad/content is showing in the right place, spy on your > competitors, track your seo ranking over time or simply archive your > favorite website!

then you should clearly say that so that you immediately identity your product as the solution to a problem, and the people with that problem don't have to put the puzzle together themselves.

<comment><AUTHOR> I updated the landing page!

</comment></comment></comment></comment><comment><USER4> Very cool. Congrats on the progress made. Hope you keep making iterative improvements to your product - that's the only way to built a successful startup.

<comment><AUTHOR> Thank you, appreciate it. Without paying customers it will be very hard to keep improving the product but I just launched a campaign on Google ads, will keep you updated..

</comment></comment><comment><USER5> Just curious, how are you different from the legion of other screenshot automaters?

<comment><AUTHOR> The story behind it, I was homeless and now I build online businesses so I can travel the world and hopefully achieve financial freedom before 30

<comment><USER6> This is nice, but nobody is going to buy a product because of your story and ambition. People make purchasing decisions based on value.

<comment><AUTHOR> I agree, I am not mentioning anything about my story in the website so I am only selling the value of the product, maybe it's not clearly explained, I didn't spend too much time on copy..</comment></comment></comment></comment>


The Web We Broke - <AUTHOR> https://ethanmarcotte.com/wrote/the-web-we-broke/ <comment><USER3> _> ARIA, the language created to help make interfaces more accessible, was found on more than sixty percent of the home pages surveyed. Unfortunately, those home pages were more likely to have detectable accessibility errors._

 _> Pages containing popular JavaScript frameworks were more likely to have accessibility errors than those that didn't use those frameworks._

This was obvious to me all along, but it's nice to have official statistics on this.

I would like to use this opportunity to point out the astounding hypocrisy of front-end developers who claim to be in favor of better accessibility, but then vehemently oppose the idea that HTML should have built-in component that cover basic web use cases without the need for scripting.

Sure, getting controls "right" in browsers is hard. But hoping that all web developers get them right when choosing/writing their own implementations of everything is absolutely hopeless. Accessibility should be the reasonable default you get "out of the box" when not doing something overly fancy or stupid.

<comment><USER4> > front-end developers who claim to be in favor of better accessibility, but > then vehemently oppose the idea that HTML should have built-in component > that cover basic web use cases without the need for scripting.

Is this a thing? (specifically that the front-end devs are the problem) I'm a dev with plenty of front-end experience, but back in the day I was sad when login pages became a thing (as opposed to built-in browser authentication), and frankly if Apple would stop being a problem I still retain hope that HTML5 form validation could actually be common.

The problem has always been (in my experience) - when browsers provide an insufficient/notably unfriendly experience (no means of managing forgotten passwords or registering logins, for example), when browser vendors refuse to play ball (IIS/IE only supported BASIC authentication, for example. Today Apple is the hold out on HTML5 validation), and/or when designers want to be "different" or have a brand that is consistent across platforms (despite those platforms having their own conventions).

Usually the front-end _devs_ want things to work with minimal effort. It's only when they are asked to do things the browsers won't do that they/we waste time rolling our own reinvented solutions.

When you run into yet-another-page that screws with how scrolling works - <USER2> you think the front-end _dev_ wanted to work on that bug-ridden task?

<comment><USER5> _If Apple would stop being a problem I still retain hope that HTML5 form validation could actually be common._

[https://caniuse.com/#feat=form-validation](https://caniuse.com/#feat=form- validation)

According to this, haven't both desktop and mobile Safari supported HTML5 form validation for about two years?

<comment><USER6> > Apple would stop being a problem

The amount of work Apple has put into making iOS accessible astounds me. Apple are not the bad guys here from what I can tell... (Disclaimer: I usually go Android, but iOS kicks Android's arse on more than one feature IMHO)

</comment></comment></comment></comment><comment><USER7> As a front-end dev, I'm trying to bake this into my process as much as possible. I am only around 20% of the way to that. Last year I focused on baking in testing into my process, now I'd like to do the same for accessibility. Big ups to Google for making Lighthouse an easy to use tool.

A business will likely never give explicit permission or budget for A11y work. Just like unit tests or e2e tests are rarely line items too. At my midsize consultancy we don't even mention it, we just bake it into the work we do. We find the time-- we make it work. It's our job. Writing inaccessible sites is kind of like building a car but ignore all environmental regulations. Your bosses boss might be ok with it, but should you be ok with it?

Think about all the work you do as a front-end dev that is not explicitly writing production code. You research libraries. You learn from screencasts. You read blog posts. You form complicated opinions about Redux. You have long code reviews. You agonize over naming. You can take similar care with accessibility. And lastly, it's not only important to be 100% accessible, it's also important to care and constantly improve. This a reminder to myself more than anyone else.

<comment><USER8> _A business will likely never give explicit permission or budget for A11y work._

A11y is the second highest priority in the web sites I build. But I'm in the healthcare industry.

<comment><USER7> Yep, definitely industry specific. I'm currently working in manufacturing, so on the other end completely.

</comment></comment></comment><comment><USER9> This is sad, but in no way surprising. It has the same root cause as many websites misusing javascript to a point where they become unusable, and that is people not really knowing how to use the tools they are given.

One not so dirty secret of accessibility has always been that it is not something you do afterwards, but that you have already done 80% of what needed to be done by just writing valid, standard compliant, semantic HTML.

So I would argue, if you really want to do something to make the web more accessible, usable and a generally nicer place, learn the tools of your trade. No, HTML and CSS are not so simple that they are not worth your time. They are easy to learn, true, but put in the time to get them right. Headings are an H tag, Navs are lists of links, paragraphs are p, not div. Easy stuff like that. And of course, CSS goes hand in hand with that.

You know display: none on a dropdown menu breaks accessibility, right? Of course it does, you tell the browser to not show the content. So use position: absolute; left: -999em or something. These are simple things you could and probably should know and if you do them, you already eliminated most of the problems.

Alt Tag on Images? Yeah, they are easy to forget, but they are also mandatory! So if you tend to be forgetful, use something like pink css borders around images that don't have them, so you won't in the future.

And for using tables for layout: There was a time, way back when, when css 2 was sparkling new and the young guys in the office bought a copy of Zeldmans "Designing with web standards" so the old farts would learn that the world was better now and we didn't need old crutches. If you are still using tables for layout today, you are not a web developer. Harsh but true. They got obsolete with float and position and you also have flexbox or css-grids today. I think you still actually don't need these for 95% of designs, but if you find them easier to use, please do!

And those aria tags or skip to content links? They are actually not the problem. They are icing on the cake. Include them if you like, people might thank you for them, but they also have had tools to compensate for these shortcomings for years, so they are not the real problem. Not displaying content properly or not at all without 500K of JS is, though.

So do something for accessibility and the web and learn the basics, it goes a long way to making you a better and more efficient developer and making the web more pleasant to use for all of us!

<comment><USER10> Well, tables for layout are necessarily in one very specific case. Namely, coding HTML emails, where CSS support is pretty horrible and (for some reason only known to them), Microsoft decided that they'd use Microsoft Word's rendering engine for Outlook.

Yeah, it's screwed up, and god knows what the accessibility of these things is like because of it. Someone needs to start a Zeldman esque web standards push for that media too.

<comment><USER9> Yeah, HTML emails are really a sad state of affairs. So many basic CSS things wont work there consistently. You don't need to even think about position or float when you got trouble setting colors.

I actually felt HTML mails were finally coming along and getting better standard support until Microsoft decided to use Words engine instead of IE/Edge. Since then, all is lost on that front.

</comment></comment></comment><comment><USER6> Drew is one of our users: Drew is 70, with poor but functional eyesight, and they have shaky hands. I try to ensure our product works for Drew because many other users are on a spectrum with similar problems.

Chris is one of our users. Chris has a unique disability within our clientbase, and they work for a government department. There are two developers working on UI, and it would take me 3 man months to write code to make our product work for Chris. I am a founder so I have the authority to make our product work for Chris, but there is no external pressure on us to do so (not even by the government department).

The fundamental question that occurs is: should we invest 3 months working on functionality specific to a single person (Chris) or should we invest 3 months working on a feature that benefits all our users a small amount?

<comment><USER11> at least make sure your buttons have a slight border and that u re not rendering #eee text over #fff background. usability issues are usually just small changes to the UI, not something that will disadvantage all users a small amount.

<comment><USER6> Totally agree. And a non-human issue with your example:

We had #EEF as a subtle light-blue 5px resizer handle on a #FFF background. However the resizer handle was invisible on a newly unboxed monitor the other day (benq 32 inch 4k monitor) - because it was showing up as white on white.

It was fixed by replacing the HDMI cable.

I think the HDMI connection was dropping back to a lower bitrate. Screenshot, and displaying the screenshot on another monitor, showed that the blue resizer line was there but it was not being displayed correctly.

<comment><USER12> _It was fixed by replacing the HDMI cable._

Unfortunately that only fixed it on that single computer. The _correct_ fix would have been to use a different color.

<comment><USER6> I agree.

I admit I am still unsure how to decide what is an acceptable colour difference in the face of both human issues and technological complications.

<comment><USER12> There are tools out there - [https://webaim.org/resources/contrastchecker/](https://webaim.org/resources/contrastchecker/)

Google actually added a new 'AAA' contrast checker to Chrome 73 in the devtools ('AA' was already there). [https://www.youtube.com/watch?v=uddZX9ZK6wY](https://www.youtube.com/watch?v=uddZX9ZK6wY)

<comment><USER6> I just tested that on pure red, and iOS button blue, on a white background. They both fail the AAA contrast test (on WebAIM and Google devtools).

The majority of apps and websites would fail the AAA test in heaps of places (unless they have a "high-contrast mode").

#F00 on #FFF: fail on AAA (pure red on white: contrast 4).

#07F on #FFF: fail on AAA ("iOS" button blue on white: contrast 4.13).

<comment><USER12> Yes. 'Pure' colors tend to be bright, so white text doesn't contrast well enough. As a rule, designers don't use the pure color. I suspect lots of sites get accessibility wrong because developers prioritize using nice round numbers (eg F00 rather than D00) instead of accessible colors.

</comment></comment></comment></comment></comment></comment></comment></comment><comment><USER13> Once I suggested we get a partially sighted person help with recommendations for clients, the goal was to get more business in as a client might need a site rebuild if it is deemed bad on the accessibility front.

I explained how Google rank according to accessibility and how GoogleBot is the biggest 'screen reader' there is, so accessibility should be part of the SEO sales pitch.

The men in white coats from the local mental health hospital did not come and collect me but I did feel that this was the expectation, particularly for suggesting we bring a partially sighted person into the process.

The web is hampered by a visual design process that was necessary a decade ago when you did need to know what you were doing with non-standards-compliant browsers. However, a whole industry has built up around this process and mockups are never made from simple HTML documents structured with semantic HTML elements such as 'aside', 'section', 'article', 'nav' and so forth. What emerges from a visual design process always gets coded up with some allegedly 'agile' process with many 'div' elements and maybe a 'header' element thrown into the mix because someone on the SEO team has demanded it for SEO.

Fundamentally it is this visual led design process rather than mocking up the content with semantic HTML that is getting the div soup industry into this accessibility problem. If you mark up a document with the proper HTML tags and put it through the WAVE tool then it comes up good.

For instance, rather than using 'div' containers for images, if you use 'figure' then you can add a 'figcaption' in there. The 'figcaption' can describe the picture, e.g. 'my cats dinner' and the 'alt' tag on the img can be 'messy bowl with prawns in it'. In this way you can have 'what it is' and 'what it looks like'. What is there not to like from a SEO perspective? Never mind accessibility!

I hope that the work Google are doing with Lighthouse that flags accessibility can be brought in to actively down-rank websites that fail on this metric, with an upranking for HTML5 semantic usage where there is document structure instead of divs bloated with class tags from lame frameworks.

</comment><comment><USER14> One of the strategies that I'm thinking of to advance accessibility is to tout it as a way of cost-cutting. Blasphemy! How? Well because the major pain point I see in a11y is _over-designing_. Managers are being a control freak on the UX and designers are already overwhelmed by the newer features and ever- changing requirements and standards. Just give it up! Go back to a website with simple features and focus on what actually matters - clarity, relevance and easy workflow. I don't know if this works for other people but this is my take on a11y issues.

</comment><comment><USER15> Often, HTML is not hand-crafted by developers but created by content authors in WYSIWYGs or generated from markdown. Of course developers could find ways to force content authors to write accessible content, but most content needs to be cheap, so people will always find ways to take shortcuts.

I don't want to say that modern JS frameworks aren't problematic, but I think they might only account for a small part of these bad numbers.

</comment><comment><USER16> Around last christmas there was this long discussion on a mailing list I followed about people being unable to access websites because their computers were too old to reasonably run modern encryption algorithms in browsers. Much of the internet is pushing for https-only access, which, it would appear, locks out an entire bunch of end devices of perfectly healthy, yet not very wealthy people.

The guy defending unencrypted traffic got bullied and called names, and I stepped in but not to the amount of success that would have anyone from the opposing side acknowledge that there is indeed a case to be made for it. I ultimately cancelled my subscription, because I realized all the arguments had been repeated several times over to no effect.

<comment><USER17> > _their computers were too old to reasonably run modern encryption algorithms > in browsers._

Do your remember any of the examples of such computers given?

I'm aware of the problem of no-longer-supported _software_ too old to have added support for modern encryption, but I'm unfamiliar with this being a hardware problem.

<comment><USER18> Android 4.0 and earlier has no TLS1.1+ support, and both Firefox and Chrome no longer support it.

<comment><USER17> Yeah, exactly. These are software limitations in Android.

The above comment seemed to be referring to older hardware so I was wondering if they were simply conflating bundled software (like pre-installed OS) or actually talking about hardware limitations.

While there is of course plenty of hardware that would be too limited for modern encryption, but I would seriously doubt anyone would be using it due to budget constraints (as in, these would more likely be specialised hw for niche embedded applications).

</comment></comment></comment></comment><comment><USER19> I would partly blame the web browsers. They should have better dev tools to check that pages are accessible.

I know that Firefox has its accessibility dev tool tab, but I don't really understand it. It looks very technical.

Chrome has Audit tab which checks that the web page is accessible. Fixing the errors helps, but I still have no idea how screen readers or other assisting technologies show the page.

Why web browsers can't have accessibility mode which changes the web page to show only data that screen readers and other accessibility tools see. Replace images with alt texts, remove css layout and colors, etc.

Browsers have a mode to check responsive layouts for mobiles. They should have a similar mode for accessibility.

<comment><USER20> > Why web browsers can't have accessibility mode which changes the web page to > show only data that screen readers and other accessibility tools see. > Replace images with alt texts, remove css layout and colors, etc.

if they did, they wouldn't be able to shove advertisements in your face. What you're talking about sounds like Reader view, which Firefox and Safari sure support, but often times popovers and "You've read 3 of your 5 free articles.." garbage blocks you and prevents Reader view from working. I've had visually impaired users complain about this very thing.

</comment></comment><comment><USER11> this looks like something that a trained AI can solve: recognize the meaningful parts of a page and adapt it to the user's needs. just like with every web standard, technology and hype made those accessibility tags obsolete very soon.

<comment><USER21> This would be a good use case for AI. Unfortunately the implementation right now is pretty poor, at least when it comes to MS PowerPoint. When I add an image to a slide deck, PPT automatically attempts to add a caption with its best guess of what the image is. 90% of the time it says "An image of a cell phone", and I have never once added that image.

</comment></comment><comment><USER22> Blind guy here with some thoughts:

1\. Even if accessibility is somehow done, it's often for marketing reasons and just for the most visible part. A perfect example is Netflix. They make special movie description tracks for the blind, but they only do that because of public outrage[0]. Their website in general is usable but it could be way better. The only big company that used to be different was Apple, but then Jobs died and they've gotten much worse. Still the best of the FAANG companies but much worse than before. For example, the accessibility of the coding app for kids is apparently amazing because they can use it to show off, but Xcode is apparently still very, very bad.

2\. Accessibility is not just about disability. Denying access to people under a certain age, living in a certain location or even using a certain (non JS) browser is inaccessibility too. This is something the law actively encourages (particularly when age and location come into play). I don't think it should be the developer's job to decide such things. A perfect example here is BBC. They do a really amazing job at the "classic" accessibility, but their geo restrictions are horrendous.

3\. If you really can't do the accessibility, fine, but don't actively try to make the job harder for others. Don't be Twitter, don't break your API for special clients for the blind that are much easier to use.[1] Don't be the polish railroad company and don't actively change your API in such a way that the accessibility-focused third party app stops functioning.[2] Don't be Amazon, don't lock screen readers out with all the piracy apps when designing your DRM solution.[3] Not being able to do anything is acceptable. Being dicks is not.

[0] [https://www.theverge.com/2015/4/14/8413569/netflix- daredevil...](https://www.theverge.com/2015/4/14/8413569/netflix-daredevil- audio-descriptions-now-available)

[1] [https://twblue.es](https://twblue.es) [https://twitter.com/euroblind/status/983246388216631296](https://twitter.com/euroblind/status/983246388216631296) [2] [https://translate.googleusercontent.com/translate_c?depth=1&...](https://translate.googleusercontent.com/translate_c?depth=1&rurl=translate.google.com&sl=auto&sp=nmt4&tl=en&u=https://www.dobreprogramy.pl/Moj- Pociag-nie-dziala-przez-PKP-PLK.-Kto-ma-racje-w-sporze-o- rozklad,News,80382.html&xid=25657,15700023,15700186,15700190,15700248,15700253&usg=ALkJrhgAugslXaeq9NoZtcMTdD2d0CS1VQ) [3] [https://github.com/smythp/blind-hackers](https://github.com/smythp/blind- hackers)

<comment><USER23> It seems that more public pressure on Apple might make a difference here.

<comment><USER22> No no no. Public pressure doesn't work that way. If you make public pressure, Apple will fix the few isues the public was outraged about and leave the invisible rest untouched. That's "marketing accessibility". The impressive, very visible and not that useful stuff is usually accessible, the invisible nitty gritty details of some settings dialog burried deep in the application that you suddenly need aren't. Even if it is accessible, this kind of accessibility done because of regulation or marketing can be horrible, see Google Docs. Is it useful? yes. Is it extremely verbose, speaking too much when the user does not need or want it? Yes. Is it completely unlike what blind people are used to? Also yes. I can elaborate more and provide examples if interested.

</comment></comment></comment><comment><USER24> I have doubts about the validity of the findings.

Firstly, I'm suspicious of "big data" in general and any emotional interpretation of machine-driven analysis of that data. But who cares, let's look at the findings..

> _2,099,665 layout tables were detected compared to only 113,737 data tables_

I'm calling bullshit.

First of all, they found 2 million tables in 1 million websites? That's ridiculous. But not as ridiculous as the claim that all those 2 million tables were layout tables. Come on guys, think about it. That's not happening unless the samples included "way back machine" versions of those sites.

Find me ONE website in the list with a layout table. I challenge you. There's no way that any site in the top 1000 is going to have layout tables or "abysmal" accessibility.

This is "million-something" clickbait. Any time someone does something involving a "million" somethings, everyone stops what they're doing and looks.

</comment><comment><USER25> Are ADA lawsuits not applicable to the web? It seems a financial incentive is the only way to really resolve this.

<comment><USER26> They are and there have been many _rather bullshit_ drive-by lawsuits in regards to them too. With no leeway to give you time to fix the problem either.

Compliance is almost impossible for small teams. You can't rely on a lot of 3rd party code/widgets since many of them are non-compliant so now you require an in-house development team to recode a 3rd party widget to follow WCAG guidelines. Don't forget that you can't post any videos without transcripts! Transcripts cost money and time to create. So now people are simply denied videos altogether. [0]

These lawsuits have done far more harm to the public than good. Because they aren't focused on actually helping users, but turning a profit for some lawyer instead.

I'm the "go to" person regarding WCAG 2.0 / ADA within my company. I actually despise my job because I don't get to spend time making our websites more accessible to users but instead spend most of my time appeasing lawyers with too much time on their hands.

[0] [https://www.insidehighered.com/news/2017/03/06/u-california-...](https://www.insidehighered.com/news/2017/03/06/u-california- berkeley-delete-publicly-available-educational-content)

<comment><USER27> > You can't rely on a lot of 3rd party code/widgets since many of them are > non-compliant so now you require an in-house development team to recode a > 3rd party widget to follow WCAG guidelines.

We've gotten a lot of mileage out of going nuts with "UX" and styling on the web. Maybe it's time to stop thinking about whether or not we could, and start thinking about whether or not we should.

Of course you gotta get the money folks and the designers on board or you're out of luck. A lawsuit or ten should do the trick. Though, yes, "this is bad give us money" is a place these complaints probably shouldn't be able to start.

<comment><USER26> The end result of that is an internet ran by businesses and large corps capable of _affording_ to be on the internet. Ma & Pa shops and small restaurants may not be able to afford to have a website, which could be enough to put them out of business.

Additionally I believe that if something can benefit people by simply existing it is better to have that thing than not have it at all if some small percentage of users aren't able to use that thing. For example, the Suicide Prevention Hotline website is not fully adhering to WCAG 2.0. I'd much rather that resource _exist at all_ for those who may need it than to not let it exist because it doesn't adhere to WCAG 2.0

It's also very much accessible enough for actual people - but not quite "free from drive-by lawsuits" territory because it doesn't fully adhere to the guidelines.

</comment></comment></comment></comment><comment><USER28> Without regulatory action this will never happen. There isn't any money in it and so the laws of capitalism more or less push towards ignoring the issue until it can't be ignored any longer because there is a price attached to that.

The annoying thing is that the web was made with accessibility and screenreaders in mind, your typical javascript powered piece of shit one-page application is a nightmare for screenreaders and other kinds of accessibility aids. And this is getting worse over time, when form trumps function and pixel perfect placement of text is more important than the text itself there is not much hope for self-governance.

<comment><USER27> Part of it's the platform's defaults, part of it's every product owner and designer thinking every part of their "experience" needs to be some special snowflake crap.

PO - "We need an alert dialog, just some text." Dev - "Cool, gimme a few seconds... and there you go, window.alert()" PO - "No it needs to match our styling and look exactly the same no matter where it's running." Dev — "sigh."

Meanwhile, a bunch of the most successful sites are ugly as sin. But whatever. I'm sure it's worth thousands of extra dollars (though not enough thousands to also match all the built-in functionality of the feature you're replacing!) to make the datepicker pretty, but break a11y and keyboard shortcuts.

The base platform _is_ pretty ugly and feature-starved, though. Like, date/time formatting and conversion to the user's preferred TZ should be a built in to HTML rather than re-invented a thousand times in JS or server- side. Some basic table sorting feature that'd serve 90% of all needs ought to be built in. Maybe alerts could allow more styling while still being accessible and safe. The datepicker widget should be good enough that no-one feels the need to make their own—though to be fair I've still seen that crap happen on mobile, where the platform widgets are basically fine, though part of that was Android's fault for sometimes having god-awful datepickers depending on version and vendor. The default styling mostly _is_ bad (alerts actually aren't too shabby these days, at least in some browsers, though). It's a crappy state of affairs.

<comment><USER29> There is a bit of a chicken and egg problem here. As long as most of the popular websites are styled to extremis so that the users think they look nice, then there is no "market" for browsers and/or plugins that have features like sorting tables and "nicer" default styling in general.

If only a few big sites went "vanilla" then you can bet a browser that could "make them look nice" would become popular very quickly.

</comment></comment></comment><comment><USER30> >Pages containing popular JavaScript frameworks were more likely to have accessibility errors than those that didn't use those frameworks.

probably the least surprising part

</comment><comment><USER31> More work is put into bogus GDPR cookie warnings no one cares about.

<comment><USER32> Not complying with GPDR is a legit threat to a company's bottom line. A11y much less so.

<comment><USER33> Depends: for a company operating purely in the US/outside Europe, an ADA lawsuit, or customers from fields that have a11y requirements not buying their product, seems more likely than GDPR fines. At least for now, there's little indication of GDPR tools being even attempted against companies not explicitly doing business here.

</comment></comment></comment><comment><USER34> Everywhere I have ever worked, accessibility is 100% an afterthought if it ever even came up at all. In the places where people tried to do something about it, it was never a business priority or explicitly given resources; just something people did out of the kindness of their hearts. And I think that's the whole story. If you want this to change, press on companies to build this in as a concern, the way they should do with performance, security, localization, and whatever else.

<comment><USER31> Exact same experience.

12 years in industry across stacks b2b dev experience here. The word "accessibility" or "disability" never even uttered out loud by developers, stakeholders or otherwise during every single project.

Maybe in like 50 more years it will be more common?

It's not just deadlines that gets a11y chopped off. It's not even remotely considered to begin with, unless a client demanded it specifically. Which never happened. Closest thing I've seen is internationalisation demands.

I've read sentiments and articles indicating that if you DO include good a11y support - these users love you. It garners massive loyalty, as one could imagine.

If you're a grunt serving in the lines? Good luck filling out a comment card after your desk-eaten 23 minute brown bag lunch and maybe the CEO won't fire you for the insubordination of suggesting work off of the most minimal track to $$$. I actually get anxiety sitting here thinking of how much trouble and internal political strife that would have caused in some places.

Businesses in the software industry care 0%. Negative zero.</comment></comment>


OS X Mavericks kernel_task eating 100% CPU - <AUTHOR> https://discussions.apple.com/thread/5497235?start=0&tstart=0 <comment><USER2> I had a strange problem appear after I spilled tea on my 2010 MBP last year. Continually, kernel_task was using an entire core (150-250% in top) and no amount of reboots could fix this. The built-in hardware diagnostic indicated it was not compatible with my Mac, and I could find nothing else that apparently was wrong. My computer was running very slowly though, and the system load was always over 4.

Finally I found through research that this is somehow related to power management. Apparently the system will have the CPU loop simple operations to prevent the processor from doing actual work and heating up. Sure enough, disabling power management by hacking a kernel extension made the kernel_task problem go away. My Mac has run perfectly for three months ever since I made that fix, after being nearly disabled for a year.

<comment><USER3> Damn, my 2009 Macbook has been running _very_ slowly for the past 4 months or so and no amount of rebooting would resolve the problem. I was actually puzzled when it slowed down to a crawl becoming basically useless and would even restart with the same slowness. Could you elaborate on your fix?

<comment><USER4> See my comment above - it might help.

<comment><USER3> Thank you.

</comment></comment></comment></comment><comment><USER5> Any other company that would DARE completely ignore the cries for help of its consumers would be publicly shamed and their reputation would suffer.

Yet, not a single word in this thread about how silent they tend to be about issues effecting thousands of users (which is a common trend with them)...

I wonder how they manage to pull that off, it's magic.

<comment><USER6> Really? Name one non open-source company that will jump on forum threads and fix it, rather than just putting it in their internal bug tracker to investigate.

I have a Logitech gaming keyboard. Their drivers are shockingly bad and freeze up every so often requiring me to re-plug the keyboard to get them to to work again. This is mentioned in the forums for at least 6 months, no fix has been announced.

I'm not defending Apple here, they should at least comment on their own forums, but they're not alone.

<comment><USER7> Back in the day, when there was no internet (only the arpanet) and Unix systems shipped with 10 manuals in nicely bound cases (I had one I was in my 20's at the time) things moved much slower and a vendor would never consider acting like this because they served primarily business customers (and institutions). Just the memory on my first Unix system was like $4000 a MB. It came with a 70mb hard disk.

To me the change most likely came around 1981 when the IBM PC came out and was sold to consumers who basically believed that it was them that was stupid and not something wrong with the machine. Manufacturers then learned that they could shove things into the pipeline and fix them later and that they actually got a fair amount of slack in the marketplace from the "stupid" end users. People who knew their shit using these machines were totally outnumbered by computer illiterate people. In other cases the ubiquitous "tech guy" made money because things didn't work so who was he to complain? That's what kept Microsoft in power. The tech guy ecosystem.

I'm curious if anyone else agrees at all with my take. Strictly my opinion having been around computers so many years.

<comment><USER6> It really depends on the number of customers.

If you have 1 million $10 customers and 10,000 have a problem the cost of losing their business isn't amazingly huge, especially as most of them probably won't switch vendors.

When you have ten $1,000,000 customers you might listen more if one has a problem.

</comment></comment></comment></comment><comment><USER8> This, along with my wifi connection dying every hour or two (requiring a restart) makes me wish I had never upgraded to Mavericks.

Link to wifi discussion: [https://discussions.apple.com/thread/5535320](https://discussions.apple.com/thread/5535320)

<comment><USER9> I've had this problem with all my Macs at home, although it would never occur with other Wi-Fi access points. This leads me to believe it has something to do with the wireless access point itself.

I was never able to fix the problem, but it went away after I bought an AirPort Time Capsule, which now serves as my wireless router. It has an extremely limited feature set compared to a real router, but I haven't had connection problems once since implementing it.

<comment><USER8> Do you use a bluetooth keyboard? My wifi flakiness seems to be much less of a problem when my lid is open and I'm typing on the builtin keyboard than when the lid is closed and I'm using the Apple bluetooth keyboard.

It's so intermittent that it's very hard to diagnose, but that's one thing I've noticed.

<comment><USER9> No, I don't have a bluetooth keyboard. On the Macbooks I use the built-in. On the iMac I use a wired keyboard.

</comment></comment></comment></comment><comment><USER10> In my opinion, Mavericks is the worst OS X version so far. It's caused a handful of crashes/hangs to my Macbook Pro, which I only encountered with about once or twice a year with Snow Leopard, Lion and Mountain Lion. I'm not sure it is caused by the OS itself or the compatibility of the apps I installed, but it's still bad.

I just had a crash few mins ago after I reinstalled the OS entirely last week. According to the crash log, it has something to do with the "kernel_task". That sucks!

<comment><USER11> > Mavericks is the worst OS X version so far

You have clearly never used Cheetah.

<comment><USER12> As someone thats been on the osx train since 10.2. I get somewhat amused by the "OSX N+latest is the worst OSX" comments.

I had the (dis)pleasure of using someone's 10.1 machine, oy wow, surprised that even got released.

As a counterpart, mavericks has been the most stable osx for myself so far. Additionally the battery life improvements gave me an extra hour on battery alone. You can pry mavericks from my cold dead hands at this point. The energy tab is also really useful at finding out what is using up battery needlessly (looking at you chrome/firefox).

<comment><USER10> I feel jealous with your luck. I've had as many crash as I can imagine since switching to Mac from Windows (before, I don't even remember how many times I got freezing apps or BSOD). And it seems to occur that _often_ since Mavericks so it's my sole assumption.

I agree about the battery life improvements part as a nomadic user. However, it's totally depends on which applications you are using. For me, chrome/firefox, which eats up most of the battery, is used constantly, therefore, cannot be turned off (to save energy, because it doesn't support AppNap, I suppose). I don't see any help looking at the Energy Tab as whatever it's like, I don't have a choice there.

</comment></comment></comment></comment><comment><USER13> Problems I have, on a brand new 15 retina MBPro: 1- after wake from sleep, wifi needs to be turned off and on to find anything

2- no sound from internal or external speaker until restart, although the OS behaves as nothing is wrong, the onscreen indicators and system preferences act as if they are muting and unmuting and changing the volume

3- kernel panics every now and then

4- display jitters (like graphic buffer corruption) a couple of times

5- after wake up from sleep , keyboard does not respond while track pad is, which means I cannot login, needs force shutdown,

<comment><USER14> "on a brand new 15 retina MBPro"

You have a warranty. Use it.

Complaints here do not solve your problems.

If Apple cannot solve your problems, within the terms if your warranty, they will offer alternatives (eventually) - up to and including a refund.

I understand people want to raise issues to "public awareness" that they feel are something Apple should pay attention to. And in the case of the original submission, VERY SPECIFIC details were figured out - and Bug Reported to Apple! Apple even closed some of the reports as a duplicate. They know about this problem - and it's for a new OS that has only been out for a handful of months - and the issue is for specific hardware builds.

They are working on it.

You, however, have a laundry list of real issues - USE YOUR WARRANTY.

<comment><USER15> Some of those (minor) problems, in fact most, are the standard kind of "new OS" bugs. None of them sounds like its about hardware faults. So your advice is not really applicable here. He'd better wait for 10.9.2 and such.

<comment><USER14> My advice is 100% applicable. Especially with issue #5, but in general as well.

You don't seem to understand: He is unhappy with what he purchased because he is experiencing problems that should not exist in the product. A brand new product. And not just a single issue - but several of them!

This isn't a device that (in his personal experience) worked fine at some point in the past on a different version of software but now is having problems on the latest software update.

This is a device that, brand new from Apple, has problems. This point is especially relevant as you cannot downgrade a Mac from Apple to an OS version that came out prior to the introduction of that specific model of machine. The Late 2013 MacBook Pro Retina devices shipped with Mavericks. They will _never_ run Mountain Lion, you cannot avoid Mavericks on them for the time being.

This is the entire point of a warranty (and lemon laws in many locations): You don't have to "wait" for something you just bought to get better / work properly.

You take it back and show them the problems you're having.

Either they can fix it or they can't. If they can't fix it, he can get his money back or some other alternative offered by Apple that he might agree to (maybe a different model, or a complete replacement).

His money is not trapped in this device, so he doesn't have to put up with this experience - unless he actually _prefers_ to complain and be unhappy.

<comment><USER15> > _You don 't seem to understand: He is unhappy with what he purchased because > he is experiencing problems that should not exist in the product. A brand > new product. And not just a single issue - but several of them!_

Which product came with a brand new OS version. And which, like most OS launches has several software issues. Which are not gonna be solved if he returns his device (or only randomly, if they affect just one of a few Apple OEM partners chipsets etc).

> _This is the entire point of a warranty (and lemon laws in many locations): > You don 't have to "wait" for something you just bought to get better / work > properly._

That only holds if it's a faulty device. For OS and driver bugs, you very much have to wait. And no matter how long you wait, there will always be some bugs to, err, bug you, in it.

</comment></comment></comment></comment></comment><comment><USER16> I've had no problems with my MBP for the last 2+ years. Happy user here.

<comment><USER17> No overheating?

<comment><USER16> Nope, it gets as hot/noisy as I feel is appropriate for the amount of work it's doing.

</comment></comment></comment><comment><USER18> guys there's a fix. i have a 2013 mba. the problem is in applehda. you can look at the hpet shoot up after sleep using `powermetrics`

here's a video to reproduce the issue

[http://youtu.be/Q8OqdMq98j4](http://youtu.be/Q8OqdMq98j4)

and here's a dmg that has the fix. basically it replaces applehda with the one from 10.8.5

[http://puu.sh/5RBvj.dmg](http://puu.sh/5RBvj.dmg)

i've been using it happily for ten days. some people claimed it wouldn't work with haswell, but it does for me. YMMV though

<comment><USER19> it doesn't work for rmbp 2013 late.

<comment><USER18> i think the latest mbp's might have a different product id on the intel hda. does your sound disappear with the old driver?

<comment><USER19> yep. but it solved the kernel 100% problem.

</comment></comment></comment></comment><comment><USER20> Workaround:

\- First. stop playing music (in your browser, itunes or whatever).

\- Next wait 5 minutes

\- Last, close lid (go to sleep) and open again again.

Works for me.

My biggest problem is that my mac freezes once a day.

<comment><AUTHOR> Closing the lid (sleeping) is what is causing it for many people (myself included). I just have to leave it open or reboot.

<comment><USER21> My Mac freezes a few times a week. Just the window manager, because I can still ssh in. I know it isn't the lid, because it is an iMac, but it may be going to sleep that kills it.

</comment></comment></comment><comment><USER22> Another (much more) common issue which seems to be related to Mavericks is the Finder problem where clicking Finder results a sudden hang of the system a the spinning colour wheel.

I'm fairly new to Apple products (~2 years ago) this is the worst problem so far but I'm surprised at such little feedback from Apple on it.

<comment><USER23> Not Mavericks-specific, but Finder is notorious for hanging when mounted volumes become unavailable or unreliable. And it's certainly possible that some of the network filesystem changes in Mavericks — in particular, it now uses SMB in certain cases where previous versions would have defaulted to AFP — could lead to this behavior in situations where you didn't see it before.

</comment></comment><comment><USER24> Solution on a late 2013 MBP for me (when the issue occurs no sound is playing anymore - no system sounds, no videos, no audio): Plugging in earphones and unplugging. Killing the coreaudio process as recommended at a few places online doesn't do the trick, unfortunately.

</comment><comment><USER25> I've been wrestling this as well, and found this post too. Another problem I frequently wrestle with is my air sleeping on not coming back (the keyboard stays lit though). Only way to get it back is too reboot.

</comment><comment><USER26> I experienced this right out of the gate after upgrading. I was very curious to see what my battery savings would be and decided to ditch my charger, only to have my battery gone in an hour. It's since subsided– I'm not really sure why, though at one point I did about everything I could think of short of reinstalling. I removed all kernel extensions I had added (KR4MB for example), removed SIMBL, reset PRAM, cycled the battery, etc. Now the only issue I have is about 10s after closing the lid, the fan goes nuts for another 10s before going to sleep.

Edit: Spring 2011 MacBook Pro.

</comment><comment><USER27> My personal list of gripes (1st-gen 15" MBPr) is short, but it's sad that they all appeared after the Mavericks upgrade:

1\. wifi will fail to reconnect on wake.

2\. almost 40% of RAM (about 6 GB of 16) in use _right after boot_ with no apps running. Was about 15% before Mavericks.

3\. I got the dreadful Keychain error once, luckily managed to fix it (I use FileVault, so no SafeBoot for me and losing the key would have been fairly disastrous).

All these very clearly appeared after I took the plunge and moved to 10.9.1. Somebody screwed up.

<comment><USER28> Same problems. Have to plug and unplug headphones. to fix kernel_task

</comment></comment><comment><USER29> It's related to the audio driver and is triggered most frequently when you close the laptop with headphones in. Simply unplug them, close the laptop, and wait for 5-10 seconds. reopen... you will still see the cpu spike, but it will end within a few seconds of everything awaking... it is annoying, but this seems to resolve it for now.

</comment><comment><USER30> I gave up on Mavericks after it went on an irreparable rampage of asking me for a "keychain password", then after trying a fix it just wouldn't boot anymore.

It required me to recover using Time Machine (and had a lot of workarounds, because it can't recover booting from the recovery partition in the HD, sigh)

<comment><USER31> I had the same issue with the keychain and repaired permissions on files to fix the issue.

<comment><USER30> Yeah, this might have helped.

The solution I tried involved changing some files in /Library/Keychains, but it didn't work

And the worse thing is that after that, a disk scan (using the Recovery boot) showed some errors on the HD, but these were non-recoverable

<comment><USER32> If you boot into recovery drive and go under Utilities -> Terminal type 'resetpassword' and in that same window there will be a ACL ( OS X Access Control Lists ) reset for an account. If you do that when you reboot, it prompts you to make a new keychain before logging you in.

</comment></comment></comment></comment><comment><USER33> I've been running into this problem with my 2013 MBA. It happens on wake, and the only that fixes it is a reboot. I'm getting pretty fed up with the issue since it's tanking my battery life and there seems like nothing I can do to fix it permanently.

</comment><comment><USER34> Unrelated to this particular issue, but lately Adobe Updater has taken to running lsof in a tight loop, waiting for me to exit Acrobat so it can update. Makes for a pretty solid red bar of system CPU use.

</comment><comment><USER35> On mine, unplugging the external screen for a while fixes everything [http://www.youtube.com/watch?v=_kppD1PotFw](http://www.youtube.com/watch?v=_kppD1PotFw)

</comment><comment><USER36> That explains why my Mac has been crazy sluggish lately...

<comment><USER37> Could also be other issues unless you see this specific set of symptoms. Mine gets sluggish but it seems to have something to do with the 'systemstats' process. When I open up something that queries it (e.g. click on the power icon in the menu bar to make it go to "Collecting power usage information...", or open Activity Monitor), it goes nuts, pegging the CPU and ballooning to >2GB of memory. Haven't figured out what to do about that, besides kill -9'ing it and avoiding doing anything that'll cause it to respawn.

<comment><USER37> Reply to self, in case anyone comes across this:

Moving the /private/var/db/systemstats directory out of the way and rebooting seems to have solved the problem. Guess something there was corrupt or too large.

</comment></comment></comment><comment><USER38> One key thing that I've noticed consistently is this happens when I have my headphones plugged in. Unplug them, put it back to sleep and wake it.

</comment><comment><USER39> I had an issue with mavericks on an old early 2008 MBP - - mavericks nearly cooked the computer on a fresh install.

</comment><comment><USER40> This bug appeared for me after the update to 10.9.1 (from 10.9) on my 2013 MBA.

</comment><comment><USER41> yup, also have this bug. It remedies itself after a minute or two.

</comment><comment><USER42> Maybe you're holding it wrong. #antennagate

<comment><USER15> Antennagate? You mean that old non-issue blown up by some media out of all proportion, that happened to phones before and since (including competitors phones), and despite which "issue" the iPhone 4 went on to sell further tens of millions of devices with the same design?

No, I think unlike that, this is a real problem.</comment></comment>


Three Years of Logging My Inbox Count - <AUTHOR> http://warkmilson.com/2015/05/15/three-years-of-logging-my-inbox-count.html <comment><USER2> Perhaps a recipe for disaster but I consider ignoring email count and avoiding sorting as a form of zen. The result is you use your fallible mind to prioritize and remember important mental threads. And if that fails often you may find it better to improve the mind (such as taking a vacation, sleeping better) rather than finding more tools to replace it.

Also, consider that if you are focused on quickness and efficiency that there will be times that the communication this produces, while gratifying for you, is disappointingly hollow for others. And it probably has an additional effect on actual character, similar to how bar tenders form of conversation in personal life may over time start match the chitchat form from work.

<comment><USER3> That is what I do as well. I leave mails in the inbox and flag those that need action or follow-up, and unflag them when I am done. I rely on search to look for an e-mail, There is a rule set up that moves unflagged threads older than X to archive. What counts is not the size of inbox, but unread and flagged count.

This works especially well for mobile clients where it is pretty inconvenient to sort e-mail.

</comment></comment><comment><USER4> I wonder if the name "inbox" is what causes people so much stress. I don't think of it as an actual inbox. It's just where my mail goes - all of it. I _read_ everything, but I don't bother organizing it. Occasionally I'll mark some message as important, or keep a few open so I can get to them later. But most often, I don't.

Search is easy. I don't see the point in organizing my mail.

<comment><USER5> True for Gmail (and similar, I'm sure), not so true for my corporate Outlook account where search sucks and is really slow, and has ridiculously tiny storage allocated so I actually have to archive older messages in an actual file...

<comment><USER6> What about something like OfflineIMAP + notmuch or mu? That works for me, and search is as good (or better) than it was for me using Gmail.

<comment><USER7> Not all Exchange setups are configured to allow IMAP access...

</comment></comment></comment></comment><comment><USER8> Working in email right now I can tell that this data is canonical. The email age graph is probably the most interesting.

As I interpret it, most people keep some very old mails for a period of time, mostly because they use it often. This might be because they contain useful information (like a password...) or because they represent a task. If it is the latest it becomes a perpetual problem because it adds some kind of noise from this feed of info you get everyday.

In our business we tried to separate these by either saving the useful part and discarding the rest (highlight and save) or by putting the thread somewhere else (in an Important category).

For all the rest it appears it is just temporary info, updates, FYIs, etc... So we basically decided to reverse our email usage. Instead of focusing on the inbox we left it untouched but saved everything that mattered in other panels. We still have work to do to improve the usage but it seems promising. You can check it at getnimb.ly if you'd like

</comment><comment><USER9> I don't understand this "Inbox Zero" stress. How hard is it to set up filters on your email? How hard is it to swipe it away to archive it? How many emails do you have to write a day?!

<comment><USER10> You're using the Gmail model, where mail has labels and gets archived. I think a lot of people are using the other model, where email goes in folders and gets deleted.

Living in the MS world, I struggle to use the Gmail model. I create an Archive folder and put it as a favorite folder. When I'm done with an email, instead of deleting it like Outlook wants, I stick it into the Archive folder. I constantly have to check my Sent Items folder to move those into the Archive folder as well, as there doesn't seem to be an automated way to move those there.

<comment><USER11> [https://support.office.com/en-za/article/Introduction-to- Aut...](https://support.office.com/en-za/article/Introduction-to-AutoArchive- in-Outlook-d3112f36-a590-4795-9f09-e7ec292bbb80)

Right click on the folder (Sent Items in this case). Select properties, go to the AutoArchive tab. Specify the rules (where to move it and when). AutoArchive gets executed periodically, but you can also force it through the File menu. File -> Info -> Cleanup Tools -> Mailbox Cleanup -> AutoArchive (probably a faster way but that's the way I found).

<comment><USER10> Ah yes, AutoArchive.

Much as how AutoRecover (Word) is not AutoSave (N++), AutoArchive is not Archive.

Archive is the manual process of dropping your mail into another folder when you've processed it from your inbox, in order to keep yourself organized. AutoArchive, as the link suggests, is an automated tool that will age mail from your archive folder (and rules-based folders) into older storage folders, for technical reasons - folder capacity is finite, but we can make more folders.

Confusion between the two is probably exacerbating the Inbox Zero crisis.

</comment></comment></comment></comment><comment><USER12> [https://www.beeminder.com/gmailzero](https://www.beeminder.com/gmailzero) will do this automatically for you. Together with [https://www.followupthen.com/](https://www.followupthen.com/) it makes it pretty easy to keep Inbox Zero.

</comment><comment><USER13> Weird.

I have 2,200+ e-mails in my inbox dating back to 2011. They're all read and just archived and I positively give zero shits about them -- except occasionally I do a search to find an e-mail that I got months ago (often package deliveries or itineraries or something like that). If it scrolls off of the page then its largely out of sight and out of mind. I didn't respond to it, so I probably won't.

Maybe the solution is to just stop caring about them as much and be a bit more brutal about your instant triage of if you're going to respond to them, and how much time you need to spend responding to them?

</comment><comment><USER14> I currently have 2500 unread emails in my inbox :/

<comment><USER2> 5287 in my inbox (not gmail, all local, no lists) and not the least bit bothered. I treat it like a phone in perpetual silent mode.

</comment></comment><comment><USER15> I feel like Google Inbox and the concept of snoozing emails helps a lot with this. A lot of emails that lie around in one's inbox are there because other people are blocking the task; snoozing the email allows for an "Inbox Zero" state while pushing off priorities until their proper due date, when they can be archived.

</comment><comment><USER16> I'm interested in reading the solutions promised in part 2.

<comment><USER17> The easiest is: stop using your Inbox as a todo list, and use a dedicated Todo list system instead (like GTD). Any email that can be answered straight away is, anything else is archived and becomes an item in your Todo ledger.

<comment><USER18> I've trie this, but I never manage to deal with stuff once I file it. It piles up like my inbox.

How do you deal with the dozens/hundreds of tasks that may accumulate?

<comment><USER19> If you get dozens to hundreds of tasks to do in a short period of time, isn't that the root of the problem?

I suspect if you get too much email, it's usually because 1. You are the boss and insist on being CCed on everything, 2. Your job description is vauge, and everyone sends tasks to you, or 3. Your coworkers feel like they have to notify you of everything. All three are organizational dysfunction, and not a technology problem.

<comment><USER18> Entrepreneur. Though I didn't mean they all arrive at once. I meant I file them, work on something else, never process the filed stuff, and then it grows large and overwhelming.

I stay on top of stuff sometimes, but then my main work goes slower.

I do outsource a bunch, but some things I've found difficult.

</comment></comment></comment></comment></comment><comment><USER20> Thanks for sharing! I use email in exactly the same way and it's very validating to learn I'm not the only one who's so "bad" at it.</comment>