Disqus - Latest Comments for skyzyx

Re: Apple Music is quietly deleting songs from hard drives

Ryan Parman — Thu, 12 May 2016 02:21:40 -0000

*sigh* Please stop spreading misinformation as though it were fact.

Re: I got my music back. At least most of it

Ryan Parman — Thu, 12 May 2016 02:19:01 -0000

I've been using iTunes Match since it was available to beta testers, and signed-up for Apple Music on day 1. Other than thinking that Apple still sucks at radio, I have had zero issues with iTunes Match (a.k.a, iCloud Music Library).

You said:

> I can’t think of a single reason why I would download an album I already own, and album that is in my iTunes Library, only to delete it. I can’t think of a good reason for that.

Quality. I still have some albums left over from the Napster days, hanging out at 128 bitrate MP3. While I'm older now and have a steady paycheck (having been in college in 1999), these are albums that I would not likely ever buy, but listen to on occasion. Anyway, I had read that iTunes Match (pre-Apple Music) was paying copyright owners (i.e., record labels) per-download of matched tracks. Because of this, I didn't feel too bad about upgrading my 128 bitrate MP3s to 256 bitrate AACs.

Maybe this isn't your use-case, but it was certainly mine. The only issues that I have legitimately had are when downloading matched tracks to my iPhone, sometimes I get "clean" versions of "explicit" tracks. I would happily re-format my tracks to use an M4A container and add the "explicit" atom if I thought it would help. But that hasn't been confirmed, and I haven't cared enough to be the guinea pig.

Also, Time Machine, my friend. Time Machine.

Re: What you need to know about the Thunderstrike 2 worm

Ryan Parman — Tue, 04 Aug 2015 13:48:22 -0000

s/Chicken Little’s/Chicken Littles/

Re: L107-Accessing_Properties_in_a_Function

Ryan Parman — Mon, 02 Feb 2015 02:25:20 -0000

The text misspells "Different than Structs" as "Different then Structs". Even then, the correct usage would be "Different from Structs". I've seen a few of these throughout the text so far. It might be worthwhile to take another editing pass for grammar and spelling. :)

Re: L092-Adding_a_Random_Fact_Function

Ryan Parman — Sun, 01 Feb 2015 20:12:44 -0000

Slightly simpler and a bit more malleable: https://gist.github.com/sky...

Re: Mutating an Array

Ryan Parman — Sun, 01 Feb 2015 15:07:37 -0000

You keep mentioning that Arrays can only hold a single kind of Datatype, but this is wrong. It's only true if you explicitly type-hint the Array. For example, from looser to stricter:

var tigerNames = ["abc", 123, true, 456.789]
var tigerNames:[] = ["abc", 123, true, 456.789]
var tigerNames:Array = ["abc", 123, true, 456.789]
var tigerNames:[String] = ["abc", "def", "ghi"]
var tigerNames:Array<string> = ["abc", "def", "ghi"]

Re: Announcing Open Iconic — In the kitchen at Iconic

Ryan Parman — Mon, 14 Apr 2014 23:56:34 -0000

Well, shit. I was really looking forward to using this, but I won't touch it if it's GPLv3. Any chance of an open source license? Like MIT, BSD or Apache?

Re: Our commitment to your rights and privacy

Ryan Parman — Fri, 11 Apr 2014 16:16:07 -0000

I completely support this. Ms. Rice is highly qualified, and I choose to stand with Dropbox. This politically-based shaming is absolutely appalling.

Re: Coding Standards: Humans Are Not Computers

Ryan Parman — Wed, 12 Feb 2014 12:15:21 -0000

Yeah, I choose to follow PSR-1 and "the good parts" of PSR-2, while ignoring "the bad parts". (I actually took the time to document my style guide a couple of years before PSR-1/PSR-2.)

Re: Using SVG for sprites – a cautionary tale

Ryan Parman — Sat, 10 Aug 2013 23:45:33 -0000

SVG logos are bundled together into a single CSS file, separate from the rest of the site's CSS.

Re: Using SVG for sprites – a cautionary tale

Ryan Parman — Wed, 17 Jul 2013 01:55:21 -0000

Instead of doing that, I'm embedding multiple SVGs inside of a single CSS file as data URIs. All of the benefits of spriting with none of the drawbacks you're discussing here.

Re: WordPress.org bans Themeforest members from participating in official WordCamp gatherings

Ryan Parman — Sat, 26 Jan 2013 06:05:56 -0000

GPL code is free _to use_, however you absolutely, positively cannot do "whatever you like with it". The GPL is just as restrictive as any commercial license or EULA — just the other way. You are forced to re-license your own code as GPL whether you like it or not, against your will.

The GPL was written by a guy with Asperger's Syndrome who is anti-capitalism. It's an important distinction to understand. Free Software and Open Source Software are two very, very different things.

Re: WordPress.org bans Themeforest members from participating in official WordCamp gatherings

Ryan Parman — Sat, 26 Jan 2013 06:00:52 -0000

False. The client who paid for the work is forced, by the GPL, to license it as GPL and release the source. GPL means that the source code is forced open, whether you like it or not.

And the GPL talks about "linking" which is something that happens in compilation — which doesn't apply to PHP. The language is specific. Even if you agree with Mullenweg's interpretation (which I do not believe would hold up in a _knowledgeable_ court), it very clearly does not apply to anything which does not leverage GPL source. Period.

F**k the GPL.

Re: Instapaper Receives Update With New Features, But You Probably Can’t Afford It

Ryan Parman — Fri, 18 Jan 2013 00:05:15 -0000

You guys realize that Marco, of Instapaper, isn't the developer of the Android version of the app, right? He does the iOS version. A third-party developer does the Android version. He's not a jerk if he wants to be paid a reasonable price for a worthwhile app. Just sayin'.

Re: Pocket for Mac: Read It Later on Your Mac

Ryan Parman — Fri, 26 Oct 2012 05:53:08 -0000

I took it for a spin for a couple of hours today, and while it's good looking, it lacks a number of features that it's pre-cursor (Read Later.app) had. One of the big things (besides the removal of Instapaper support) is a limited set of typographical controls.

Also, for me, organizing articles into folders fits my brain better for this type of service than applying tags. For Pinboard/Delicious, sure, tagging is great. But for things I want to keep track of for reading then archiving, folders work better.

Needless to say, my experiment with Pocket resulted in a move back to Instapaper. YMMV.

Re: My Xbox Live.App (iOS) Not Compatible With iOS 6? - User generated tech content, galleries and more - TekSocial

Ryan Parman — Sun, 24 Jun 2012 23:30:42 -0000

I'm encountering exactly the same thing, but this is perfectly expected. Unlike Google, when Apple says "beta", they really mean it.

Microsoft hasn't issued an update to the app since iOS 6.0b1 was released. I'm sure that between now and October, it'll be updated.

Re: How To Rip Blu-Rays on a Mac: The Complete Guide

Ryan Parman — Fri, 16 Mar 2012 16:22:56 -0000

MetaX sucks. MetaZ is better. Subler is leaps and bounds better, faster, and more consistent.

Re: Review: Apple TV

Ryan Parman — Fri, 16 Mar 2012 12:50:57 -0000

Most shows on Hulu Plus are restricted to browsers anyway. Very little is available on TV/Mobile. Yes, Hulu Plus would be a nice addition in theory, but until the content owners decide to visit the 21st century, what difference does it make?

Re: Mac OS X Maverick Leaving Apple

Ryan Parman — Wed, 23 Mar 2011 14:57:52 -0000

Typo: "NeXTcube’s" should be "NeXTcubes".

Re: Google and H.264 - Far From Hypocritical

Ryan Parman — Wed, 12 Jan 2011 14:55:55 -0000

It's an alternative to H.264 that Google owns.

Re: Google and H.264 - Far From Hypocritical

Ryan Parman — Wed, 12 Jan 2011 14:54:31 -0000

I've been down this road before. The EXISTING code is under a perpetual license. FUTURE code may or may not be, although to be honest, I doubt Google will change it.

Re: PHP SDK for Amazon Web Services - till's blog

Ryan Parman — Thu, 30 Sep 2010 12:25:39 -0000

I'll discuss this with my team. :)

Re: PHP SDK for Amazon Web Services - till's blog

Ryan Parman — Wed, 29 Sep 2010 11:42:16 -0000

Actually, there are TONS of unit tests -- we have upwards of 90% code coverage. I just didn't think that they'd be particularly valuable to the community-at-large, so we decided to leave them out of the distribution. We are, however, re-using some of the PHPT unit tests as method examples in the SDK documentation (the most relevant and instructive tests, anyway). That way, we know that all of the examples work because if they didn't, the test suite would fail.

That said, we're always listening to the community (the AWS SDK for PHP began its life as a third-party open-source project, after all), so if there's enough interest we can certainly provide them to the community.

Contributing back to the SDK is conceptually similar to contributing to YUI (http://developer.yahoo.com/yui/community/) where there's a CLA that needs to be signed before accepting a pull request. Contribution details should be published soon.

Re: PHP Coding Standards

Ryan Parman — Sat, 14 Aug 2010 02:52:44 -0000

Done. :)

Re: PHP Coding Standards

Ryan Parman — Wed, 04 Aug 2010 14:07:52 -0000

Made updates around file naming, PHP namespaces (5.3+), indentation for associative arrays, and whitespace for typecasting.