Earlier quoted context omitted.
Boycotting the Mac platform (which is pretty much free of any such absurdity) doesn't make a lot of sense to me. That's where Apple is doing things right . You should of course, shun iPhone OS devices if you feel this way. The system76 laptops are probably generic machines from Clevo, Sager or some such with a custom badge. Alienware used to do the same thing.
I wonder if Leo Laporte is going to be right about how he thinks that will Apple eventually stop making macs so that they can focus on more closed or controlled platforms like the iPod, iPhone, and now the iPad. They seem to be pretty good at making money with the closed systems. Maybe the next iBook will just be a foldable iPad with the same closed OS.
New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
271–280 of 495 posts
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#272Earlier quoted context omitted.
I think you're forgetting that it's also really fun to make an app that has the best "look and feel". I can make things that make people say "Wow." A lot easier on the iPhone than on Android. Developers will make apps where it is fun to make apps. I haven't had any horror stories with the app store, so it's still just more fun to make iPhone software than anything else.
The developers who make apps 'for fun' aren't producing the blockbusters that make the appstore so important to the iPhone.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#273Earlier quoted context omitted.
Nope. Apple doesn't have a monopoly in the phone market.
How is "market" defined, legally? They certainly have a monopoly over the "iPhone" or "iPhone App Store apps" markets. Of course, that reasoning could get absurd pretty quickly, so I'm sure it must be defined at a pretty generic, high level.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#274This is unsavory in the extreme. I had been writing an iPhone app in Haskell, and now I have to can it? What the fuck? Fuck you, Apple! Blowhards. Hope you guys enjoy the mass exodus of decent developers from your dumbass platform with kiddie languages.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#275Earlier quoted context omitted.
Tumult's point is not about writing a single script-based solution but rather about developing an enabling technology for a whole raft of solutions. A platform-on-platform.
Even granted that, the reason Apple doesn't want that is still because of the UX. Apps with the same codebase for Android/iPhone will automatically suck as far as the UI is concerned. Things like the lack of multitouch gestures on android, different screen sizes, &c. Certainly has never worked well on desktop platforms... see: Java UI toolkits, QT (which looks fairly native but tends to feel very wrong), Adobe Air, &…
>Apps with the same codebase for Android/iPhone will automatically suck as far as the UI is concerned
Hardly. There is the graphics api called opengl that works on both iPhone and Android (and your ps3 and computer).
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#276Getting 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…
Say, one wants to develop a touch user interface for a visual programming language for music composition and the core engine happens to be written in Common Lisp (say, something like PWGL or Open Music) - why can't I have that in Lisp? It is compiled, native and would use the Cocoa libs. There are not only consumers which want to download ebooks with ads. There could be an area of innovative and experimental use wher…
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#277I suppose C++ will be banned when QT for iPhone is ready.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#278Earlier quoted context omitted.
Boycotting the Mac platform (which is pretty much free of any such absurdity) doesn't make a lot of sense to me. That's where Apple is doing things right . You should of course, shun iPhone OS devices if you feel this way. The system76 laptops are probably generic machines from Clevo, Sager or some such with a custom badge. Alienware used to do the same thing.
The hardest thing to me about ditching Mac would be that Apple is the only company capable of doing a user interface. ALL other user interfaces by ALL other vendors suck. For some reason, no human beings on the entire planet other than those that work at One Infinite Loop in Cupertino are capable of doing a UI.
I'd say the all user interfaces from all vendors suck, including Apple.
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#279Getting 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…
Re: New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
#280Earlier quoted context omitted.
I have been a very loyal mac user for years and love it, but I'm seriously considering going back to Linux. I am not a free software "zealot" and don't mind some closed-ness, but this is getting absolutely insane. Enforcing which LANGUAGES can be used on a platform?!? Insane! Edit: I've been looking at these guys: http://www.system76.com/ (I don't work with or have any vested interest in them, but they look cool.)
> I am not a free software "zealot" and don't mind some closed-ness Maybe we were not that zealot after all when we free software "zealot" said that proprietary software allow their owners to treat their users badly and that eventually, this happens to every proprietary software. Just saying. It amazes me how surprised users of proprietary software are every time they get screwed by their masters even though this has…