371–380 of 495 posts
Earlier quoted context omitted.
Although historically I have always agreed with you, I dare say Microsoft is starting to figure it out. Slowly but surely. Win7 is almost a pleasant experience.
I've started using it this week. Alt+tab becomes more and more broken with every release. There was a time when excel was the only application that didn't behave properly.
Getting away from the frenzied rhetoric, my opinion is that what Apple really wants to prevent is people releasing multi-platform compilers. So taking Flash as just one example, if I can build one app and the compiler can make me an iPhone executable, an Android executable, and so forth, Apple don't want that. In my experience so far with such "cross platform compatibility layers," they always produce results that wa…
This change doesn't just cover Flash though; it also hits all of the Mono cross-compilers (and Scheme, and everything else that happens to cross-compile). I can't see any way that this turns out as remotely positive for developers.
Earlier quoted context omitted.
Sure, 'multiplatform compiling/targeting' is one thing. But banning non-approved languages is silly. Even apple is funding projects like RubyCocoa and bringing Python compatability to the Cocoa API. If somebody wants to write an app using CocoaTouch but finds Ruby, Python, Lua, or Mono to be a better fit for the project or their own capabilities than Obj-C, why stop them from doing so? If the apps still have to inter…
Think OS/4, think opening up multitasking to 3rd party apps, perhaps thats why they are being so anal about how apps should be written, if they are planning to make changes to the low-level libraries to support 3rd party app multitasking then they are going to want to make sure that 3rd party apps are linked against them.
Who's going to know? My C happens to look exactly like what Chicken Scheme generates!
"When we embarked on the task of developing PowerLoom® which had to be delivered in C++, we were faced with exactly this problem. Our response was to invent a new programming language, called STELLA, that incorporates those aspects of Common Lisp that we deemed essential into a language that can still be translated into efficient, conventional and readable C++ and Java code."
Getting away from the frenzied rhetoric, my opinion is that what Apple really wants to prevent is people releasing multi-platform compilers. So taking Flash as just one example, if I can build one app and the compiler can make me an iPhone executable, an Android executable, and so forth, Apple don't want that. In my experience so far with such "cross platform compatibility layers," they always produce results that wa…
They dont want anyone peeing in their pool. They purge the pornspam apps, they purge the rss-reader apps. I personally think this is a good thing, because developing a native iPhone app in C/C++/Objective-C means you will more likely have a vested interest in the iPhone/Mac platform other than to make a quick buck with a flatuence app. At the very least, you're a more dedicated developer.
What a rose-tinted way to describe lock-in.
Compared to the video game console industry, this is still pretty nice. Several of the companies require submission of the source code for review. And Nintendo in particular is renowned among my video game programming friends for having ridiculous, undocumented rules that change over time. If you think of the iPhone as a PC-like platform, yes, it's worth being crazy. But I think of mine as more like a game console. T…
First of all, lots of companies do license many 3rd party libraries, without their source code. Sometimes these said libraries are specifically compiled with latest bugfixes to the relevant project they've been used.
What the companies might require is usually symbols/debug information/etc. But never the source code!
After all, Microsoft, Sony, Nintendo are direct competitors. Why should an independent publisher (EA, Activision, THQ, Konami) be sharing source-code with them?
Getting away from the frenzied rhetoric, my opinion is that what Apple really wants to prevent is people releasing multi-platform compilers. So taking Flash as just one example, if I can build one app and the compiler can make me an iPhone executable, an Android executable, and so forth, Apple don't want that. In my experience so far with such "cross platform compatibility layers," they always produce results that wa…
It's not just with the consoles. I used to develop Lotus Notes applications. The problem with Notes was that the barrier to entry for developers was too low such that it hurt the platform, and it made it hard to distinguish good developers and good apps from the chaff. When a bunch of unqualified developers fill the world with junk it gives the entire platform a reputation as being junky. I now develop iPhone applica…
Earlier quoted context omitted.
They dont want anyone peeing in their pool. They purge the pornspam apps, they purge the rss-reader apps. I personally think this is a good thing, because developing a native iPhone app in C/C++/Objective-C means you will more likely have a vested interest in the iPhone/Mac platform other than to make a quick buck with a flatuence app. At the very least, you're a more dedicated developer.
"At the very least, you're a more dedicated developer" What a rose-tinted way to describe lock-in.
Earlier quoted context omitted.
Seems like Apple thinks the same restriction applies. If you use parenscript or coffeescript (or GWT) to generate your JavaScript, you are technically violating the contract you signed with Apple. Of course, if you didn't sign that, then you can do whatever you want.
If they started actively censoring/blocking websites that they determine haven't written javascript by hand, then that would be theonion.com territory (And the end of their sales) :)
As opposed to where they are right now? Enforcing what higher level language you write in before it gets compiled down to machine code?