natesm

This isn't the case in Objective-C though.

@"foo" is an instance of the NSString class, which is a part of the Foundation library. However, it has its own special syntax. Now, Apple is adding @[] and @{}, which are NSArray and NSDictionary instances.

I guess that isn't the entirety of Cocoa, but Objective-C and Foundation are very linked now.

Enabling JS is free.

    int* foo = malloc(sizeof(int));

https://github.com/twitter/twui/blob/master/lib/UIKit/TUIScr...

This isn't about listening to something or reading something. It's about the ability to remix and build upon it.

> I think it's unreasonable to expect people who make things to be able to profit from them for more than 5 years.

It doesn't matter, because most people don't profit from their works after 5 years, if they ever profit from it at all. The current law helps the Disneys and bestselling authors and has little to no effect on small, independent creators. I don't think we should optimize for corporations, I think we should optimize for everyone being able to reproduce, distribute and build upon their culture - with a period of potential financial motivation to kickstart the creation of new cultural artifacts. If you're still living off your work 5 years on, you're probably already rich.

Girl Talk's music is literally illegal because his instrument comes with a license agreement. What if Stratocasters had come with one?

> Hell, why don't we make all property expire after 5 or 10 years?

This makes no sense. At all. Physical property and my culture are not comparable.

http://developer.apple.com/library/mac/#documentation/Cocoa/...

- Node-based layer system, like Quartz Composer and Max/MSP. Right now, any complex nesting of layer styles has to be done via Smart Objects, which is a terrible hack that has you saving, seeing what the effect on the final image is, then going back and making more changes, repeat.

- It's 2012. There should not be destructive filters anymore. All filters should just be another node in this layout. If you'd like to apply them, you should be able to right click a node and merge everything that feeds into it. Brushes should also be usable as layers. Composite everything.

- Where's this layer system going to go? Obviously, it will go on screen, but how about an iPad app that pairs with Photoshop for displaying and altering it? They already have something sort of like this for tools.

- Photoshop badly needs usable variables of some sort. I'm tired of jumping around 5 different places because I decided I want to change a color.

- Going with the last one, documents should be able to contain multiple images, like Illustrator does. This would be a great addition for icon design, since you could (easily, without ugly hacks) have all of your sizes in the same document. Combine that with variables, and...

- Finally, stop the sucky non-native UI already. Stop replacing perfectly good Cocoa widgets with terrible Air ones.

Adding fancy new features is nice and stuff, but the fundamental UI of this application is getting really dated.

I live in Williamsburg and ride the subway for about 20 minutes. Not really a big deal, and much better than any commute involving owning a car.

> To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries.

The obvious way that this works is that authors are motivated to create because they have the exclusive right to sell their creation (and thus make a profit). That seems pretty OK to me.

However, no amount of money is going to be able convince Mr. Lennon and Mr. Harrison to get the band back together. So, why are we still paying for that content? How is that advancing the arts? Would giving current creators the ability to use the entire back catalog of the Beatles without any cost or legal hassle advance the arts more? I would argue yes.

I can't find an article for this, so sorry, maybe someone can, but I believe that the majority of books go out of print rather quickly. However, we're not allowed to copy them freely. When those books go out of print, we're taking society backwards. They're impossible to acquire legally. That's really bad.

We need a balance. I think five to ten years would be fine. Opening up access to a new generation of small creators is better than providing further income to the JK Rowlings and Paul McCartneys of the world. They're already rich by that time anyways.

Think about button sizes. The iOS UI widgets are a specific physical size, optimized for the average human hand, which is then translated into pixels. Because all iOS devices have the exact same "pixel dimensions" (sure, there are four times as many now, but that doesn't matter much), supporting this is not a problem. The distance that the user will have to reach for a button and the dimensions of said button are physically identical on every single iPhone and iPod touch.

Android devices are many different sizes and shapes, so this sort of consistency is practically impossible (although I'd be really impressed if someone pulled it off, surely there's a way to get physical device dimensions in the Android SDK?).

Security scoped bookmarks allow persistent access to a filesystem resource. That's the only one I'm aware of, but it's a major upgrade.

Well, that's a little terrifying.

    objc_msgSend(self, @selector(bar));

    objc_msgSend(self, @selector(performSelector:), @selector(bar));

?

On the other hand, it strengthens the coupling between Objective-C the language the Cocoa the framework, and I'm not sure how I feel about that.

I do like it better than the property dot syntax though. (is a simple assignment to a struct member? is it an objc_msgSend of unknown complexity?)