News for hackers. Stuff that matters.
Re:The coming civil war over general purpose computing by ekianjo on Monday August 27, 2012 @02:12AM (#4437650)
There's no such thing as "near free". Free is a boolean variable, either it is free or it is not free.

Apple does not distribute any free tools to develop and run software for their systems, period. If you want to be a free hacker, it's Linux or Windows, currently. And as another person responded to you, you cannot use the UI elements via javascript and all. Get some docs, seriously.

Re:The coming civil war over general purpose computing by nicholassmith on Monday August 27, 2012 @08:26AM (#4438445)
Actually, Apple does distribute free tools to develop and run software it's in the distribution of the software that you need a license and only if you want to share it with people running Mountain Lion who don't understand how to open something unsigned.

https://developer.apple.com/xcode/ 'Download Xcode 4 for free.'

Re:The coming civil war over general purpose computing by snowwrestler on Monday August 27, 2012 @10:45AM (#4439029)
Xcode is a free download. The Apple development documentation is available for free on their website. You need to register in both cases but it is a free registration.

In addition, Macs ship with a certified compliant Unix interface, and a wide variety of developer tools such as a powerful CLI shell (only recently added on Windows), compilers, vim, etc.

And unlike Windows, Apple donates quite a lot of their code to open source, including the kernel of their OS. Does Windows do that? I don't think so.

http://opensource.apple.com/

Re:The coming civil war over general purpose computing by gizmo686 on Monday August 27, 2012 @02:32AM (#4437699)
Windows hacker? Finding information about system internels is more often then not an easter egg hunt on google.
Re:The coming civil war over general purpose computing by chao- on Monday August 27, 2012 @04:20AM (#4437917)
Say what you will about Windows (and I will even join you), but Microsoft can put out some alarmingly competent docs. I say "can" and not "always do", because where they are lacking, I agree it can be frustrating. That said, in one such scenario the solution for me was to get in touch with a PM at MS and say:

"You designed [system #42]. I'm trying to accomplish [nifty goal] that is an obvious extension of what you suggest that [system #42] should be used for. You said some examples are included with the most recent Windows SDK. After downloading it, I found no such example and the problem seems a little intractable. What gives?"

The response contained an attachment of the overlooked/unincluded examples, and some clarifications about the system I was working with and even explained that some of what I was doing was explicitly NOT possible, for very good reasons (for the record, an earlier version of Windows Search).

I say this as a desktop Linux user, where at times my only recourse for "Why won't [application x] properly fullscreen?" is to go and do just what you suggest: an easter egg hunt on google. Furthermore, the end-all-be-all solution is the same as it is with our Windows example: get in touch with someone at the project and ask for clarification. The difference lies in that with one case, it's someone's job to provide clarification for the system they designed. In the other case, the possibilities are too varied to speculate on (e.g. unmaintained project, antisocial developer).

Re:The coming civil war over general purpose computing by gizmo686 on Monday August 27, 2012 @04:58AM (#4437999)
What you are talking about sounds more like windows developer than windows hacker. Still, almost all of my programming experience has been based on greping source trees in place of documentation. When I do get good documentation (it does happen) I don't know what to do with it and still look at the source.

What really sets open source apart for me in terms of hacking is that I can change the way any component operates, instead of having to jerryrig what would be a simple change using external APIs.