geoff-codes

Link: http://blog.codinghorror.com/standard-markdown-is-now-common...

Of course its not. After all, why would it be?

Suggest putting this in a repo somewhere, in the vein of:

https://github.com/vhf/free-programming-books/blob/master/fr...

https://github.com/ligurio/free-software-testing-books/blob/...

etc.

I don't think this holds water at all.

The crux of the article is:

> ...one last gap remains in the middle of this stack of system exclusivity: Apple licenses the instruction set architecture for its mobile devices from ARM.

But Apple already not only designs the own SoCs independently already, they regularly add their own opcodes to the ARM instruction sets they license, as they see fit.

The alternative to not licensing from ARM, even if they "invented their own ISA", would be to pay an exorbitant sum in royalties to ARM and every other patent-holder whose technology they might dare use in their chip. So paying ARM for their technology in one go just makes the most economical/legal sense.

Not particlarly; in fact, apple has basically done this exact thing twice in the past (https://en.wikipedia.org/wiki/Mac_68k_emulator), (https://en.wikipedia.org/wiki/Rosetta_(software).

But I believe we're (hypothetically) talking about ARM, not x86, code.

Perhaps the word is 'pwn'?

> There are LLVM targets with corresponding ABIs that are nonspecific to architectures like PNaCL but Apple is not using them

They do indeed support LLVM IR target(s) that are, in fact, much more architecturally-nonspecific than PNaCl, namely the spir[64]-unknown-unknown target. See https://github.com/KhronosGroup/SPIR and /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/openclc (on a Mac, since 10.7).

I don't know if bitcode with this target triple is necessarily suitable for the Apple Watch, however.

A few more (particularly nspr and apr): http://www.shlomifish.org/open-source/portability-libs/

Agreed. Should have said "hopefully" rather than "probably".

Ongoing? Maybe not. But, rather than talk IBM in 1984 (which is probably a bad example vis-a-vis Apple products and their breakthrough impact), I'll refer you to the facial tissue breakthrough product of 1980: https://www.youtube.com/watch?v=dLa0IGW1k8g

OK.

Per this 2011 article (http://www.nytimes.com/2011/09/28/business/media/researching...), Kleenex has a 47.1% share of the facial tissue market. I assume these numbers reflect the U.S. (rather than global) facial tissue market.

Per this recent article (http://www.macrumors.com/2015/09/03/iphone-us-market-share-c...), Apple has a 44.2% share of the U.S. smartphone market.

Although the text of the article doesn't say it explicitly, the title of this article effectively screams "Apple isn't well diversified! Its making too much money on one thing!" I really don't see the sky falling here by any means. Barring a seismic shift in the smartphone market, Apple will continue to dominate the smartphone market, making obscene amounts of money; they will probably also continue to innovate. And Kleenex will continue to dominate the facial tissue market.

Ha. Having conquered the paywall:

Ridiculous. COBOL. AppleScript. Lego Mindstorms. Also:

Is it difficult to develop a programming language which is closely related to human language? (http://programmers.stackexchange.com/questions/267489/is-it-...)

Or, in one of the clearest and most succinct pieces Dijkstra ever wrote:

On the foolishness of "natural language programming".

https://www.cs.utexas.edu/users/EWD/transcriptions/EWD06xx/E...

To answer my own question (and for anyone else who's an idiot like me): Google the title of this post and look at Google's cache. i.e., http://webcache.googleusercontent.com/search?q=cache:EI3f-tS...

Ok, got it, and fair enough. So, per said item/policy:

> It's ok to ask how to read an article or to help other users by sharing a workaround.

So, can anyone share the workaround for this one? In a desktop browser, I get a paywall; 'x'ing out of it, I'm redirected to the front page; and blocking the paywall's html element reveals that the article behind it is empty.

"We're not sure this will work, but if it does we'll do it from now on."

I don't believe this has now been "done from now on" I don't think?

I write homebrew formulae.

Identical is pretty easy. Maybe something like this.

    #!/bin/sh
    here=$PWD
    dir=.
    depth=
    rm -f /tmp/list
    
    [ $# -eq 1 ] &&
      [ -e "$1" ] && dir=$1 || depth=$1 
    
    [ $# -eq 2 ] && for i in "$@"; do
      [ -e "$i" ] && dir=$i || depth=$i
    done
    
    for each in $(find -L $dir -type d -depth $depth 2>/dev/null); do
      [ -x "$each" ] && cd "$each" &&
      sha=$(tar c . 2>/dev/null | tar xmvO 2>&1 | xz | shasum | sed 's| .*||') 
      [ $(find . 2>/dev/null | wc -l) -gt 1 ] && echo $sha $each >> /tmp/list
      cd "$here"
    done
    
    for sha in $(cat /tmp/list | sed 's| .*||' | sort | uniq); do
      [ $(grep $sha /tmp/list | wc -l) -gt 1 ]  &&
        echo Identical directories: && grep $sha /tmp/list | sed 's|.* ||' && echo
    done

Similar and "similar-and-strictly-newer" both are much trickier as you have to invent a rubric for what "similar" mean, and `diff -qr` isn't going to tell you if, say, the files are mostly the same, but have been moved into a subdirector. So I'd probably use git, traversing the file tree by moving the .git dir around and adding each candidate directory as a different branch, and doing a `git gc` each time to try to keep the size of the index manageable. Then doing a `git diff [--word-diff] [--stat] --find-copies-harder` between branches will pick up files that have been moved around, etc. You could literally do this for every directory and subdirectory, but if you can narrow it down to, say, directories with the same baseman, it would be substantially easier.

On the other hand, I would say I suffer from this same ailment, I just mostly don't bother sorting it out. I just use something like http://cpansearch.perl.org/src/ANDK/Perl-Repository-APC-2.00... to make hard links between identical files, keeping the size of the monstrosity in check.

> I recently found a new a job hoping to gain some mentorship

I this is probably the real error. Lacking greater context, what made you expect that your boss at this new position would be able to mentor you?

Is he supposed to know how to parse a CSV? (Manually? Like, with awk or something?) Or is that why he hired a hacker/programmer like you?

I'm not saying your boss isn't incompetent. Maybe he is. But you shouldn't expect that your superior is always going to be more technically competent than you.

This is awesome. Thanks!