If you look through the task description on the phabricator task I linked, there is Paste file which has the contents of an extension to allow continued use of graphviz, however they state it's insecure and not supported.
>>never really considered myself good enough to pursue it though
Self-doubt is an evil, evil thing. Don't let it hold you back. I landed an opportunity to interview at $REDACTEDBUTITSATOPINTERNETPROPERTY. I didn't even want to fly out for the interview - I thought it would be a waste of time. It took lots and lots of convincing by my wife and other friends and family just for me to go out and interview. I guess you can see where this is headed - I start there in 2 weeks.
CBSSports.com http://developer.cbssports.com/ launched a similar product a few months back - it seems to be going well and offers more data than ESPN does, including fantasy data. My initial reaction is that ESPN hastily cooked this up as a response to what CBS did.
Disclaimer, I work for CBS Interactive, the parent company of CBS Sports.
I used to work for ESPN Digital and gave feedback on the early revs of this API.
I can tell you that this wasn't a hasty response from ESPN - we've been fighting for this in some shape or form for years now internally. Chris and his boss deserve a lot of credit for making space internally to make this happen.
There's a lot more behind this than meets the eye. Internally, these APIs essentially power all of ESPN's mobile alerts, fantasy products, etc. That's not a response to CBS.
Give these guys time. It takes longer to get a big company to move, especially when the potential market opportunity seems like a rounding error on the cable TV profits (at least to said TV execs). You've got a good person on the inside trying to open up more data. Don't give up on them, give them feedback - they're listening.
"Your Application must be designed to permit CBSi to comply with it's Privacy Policy, which may be updated by CBSi from time to time without notice to you. "
Pretty much everything in the TOS is some variant of "you must comply with this" and "we are not responsible for notifying you when we change it." This seems like a raw deal to me.
Updating for bugs is hard enough. But, this API forces developers to comply with UI guidelines (which are impossible to even write tests for) without anything back.
The API even requires that all financial transactions go through CBSi. Wow.
Apple and other app stores have gotten a lot of shit for changing requirements of their app stores, and rightly so. But, they started with compelling and clear offerings of the opportunity. The TOS of this API look so terrible up front I would not consider using it as a small developer. If your bosses at CSBi want to attract these types of people, I would recommend coming up with a tiered approach. ESPN does this better in this case.
That looks like TOC for "Machine Learning for Email", which is just a portion of the entire "Machine Learning for Hackers" book. The full "Machine Learning for Hackers" doesn't appear to be on Safari yet.
for whatever reason, there is a HUGE demand for etl and bi developers here in FL. Data Warehousing is evidently strong in these parts. You wouldn't know this from reading blogs/twitter/etc but there is quite a bit going on here.
I'm over word clouds by now. If you look at my site, you'll see that I've done my fair share of them, including one generated from the script of the big lebowski.
You are all 100% correct about the regex. Before converting the product-identifying matching code to Python, I did it in bash using grep -iw to match whole words.
for i in newton macintosh macbook ibook iie mac iphone ipod imac ipad II+ iigs LaserWriter osx 'apple ?tv' itunes '\]\[' imovie
do
stevejobs_tribute.txt |wc -l`"
echo "$i: `egrep -wi "${i}s?" $INPUTFILE|wc -l`"
done
But this was difficult to maintain. I wanted the ability to print a 'friendly' looking product name (the dict's key) and maintain the counts in a variable.
When I made the move from bash to python, I knew that there would be some overlap when I pushed this code (in the name of shipping!). I need to split the sentences into proper tokens and then check each token for a product match. I'm already splitting the sentence into tokens for part-of-speech tagging so it shouldn't be difficult to do.
tl;dr known issue on the Mac regex, I needed to publish it and get back to work!
