Windows for ARM ... PB for ARM ?

[USCode]

This thread is asking for ARM support which would be very good as it would allow mobile platforms to be supported. Android and iOS would be ideal targets. ...

Just to be clear, this thread originally started out asking what the interest would be in PB for Windows ARM support:
"Would a Windows version of PB for ARM be of interest anyone?"

[Danilo]

They are not, it is very open. If you don't like .NET languages, you can use HTML5 and JavaScript. Metro app programming is open to those experienced writing web based apps or those using standard .NET based development tools. You can't get more coverage and choice than that. Indie language users are still welcome to write standard Windows desktop apps just as they always have.

Indie languages that are more advanced like monkey and GLBasic should be able to add support for Metro apps without any major issues. Traditional indie compilers are a dying breed. Code translation seems to be the future for indie languages, for better or worse.

PB outputs x86 ASM and x64 ASM. It is no problem to output .NET CIL, ARM ASM or C too.
The problem is that Fred and freak can not support everything. They are now concentrating
on 3 platforms and this is already very much. Maybe too much for a hobby, who knows.

How much shocked would people be here if they decided to stop PB and start a new thing?
That is what Mark Sibly did a few times. It is not easy to decide what is right and what is wrong
and i can understand all sides. It is not easy atm, many things change.
But it can also be confusing. Look at all that "Windows 8 will fail.", "I hope Apple dies." etc.
Some people already seem to be very confused. Just relax a little bit more and do your work: write code.
You can think about tomorrow forever and procrastinate or you can see today's endless opportunities...

The best of the best always concentrated on one thing at a time to make this one thing perfect.
If you just want everything, it could easily be that you get nothing done at the end.
It is part of our culture. Most people dream about getting everything and winning lottery but get nothing
because they just watch TV all day. Few guys do something and get everything. That's life.

[Ramihyn_]

You seem very confused. Let me help you with your continued confusion.

Delphi has always been Delphi, it never had a different name several years ago. Trust me on this, I have used Delphi since it was first released. I used Delphi 1 a lot for Win 3.1 development and I even wrote a programming language with it. I switched to Delphi 2 when it came out because I needed 32-bit. I was actually able to make quite a bit of money off of my Delphi 2 work. At one point, I was even teaching Delphi 2 in my programming class. I continued using Delphi and C++ Builder up until Delphi 8 was released. IMHO, Delphi 8 was when Delphi officially jumped the shark. .NET literally destroyed a great language (much like it did with VB). I am not alone in this thought, as Delphi 7 is still in wide use (as is VB 6). Starting with Delphi 8, the development, marketing and licensing of Delphi has been nothing short of schizophrenic. Through it all, Delphi has always been Delphi, the only name change has been the company who owns the products.

You said: "Delphi is a native code compiler and does not compile to .NET." Those are your words, not mine. I merely corrected you and tried to help you learn about something you are clearly unfamiliar with. There have been several .NET versions of Delphi. As I explained to you, after buying Delphi, Embarcadero stripped .NET from Delphi and moved it to Delphi Prism (which was later shortened to just Prism). To claim that Delphi does not compile to .NET is not only incorrect, but shows a complete lack of knowledge of Delphi. Thousands of developers every day are happily developing .NET software using Delphi, not Prism.

You might want to actually buy Delphi to become familiar with it. I would not recommend anybody buy the crapware produced by Embarcadero, but there are many places to buy legitimate copies of older versions of Delphi, including all five of the Delphi versions that support .NET. Personally, Delphi 7 was the last version of Delphi I liked, but I am biased since I despise .NET.

Thanks for another totally pointless "lecture" about outdated Delphi products. You clearly are stuck several years in the past and ignore the current Delphi compilers for personal reasons. If you followed your own advise and actually tried to buy a current Delphi compiler, you would find out that your "Delphi" knowledge got outdated in 2008.

Thats btw. the reason why i said i think you are just trolling by now, you make your own personal "Delphi" definition which conveniently excludes the currently sold and maintained compilers and dismiss R&D engineers from the company which creates the actively sold and maintained compilers as "hackers" or "script kiddies" if they do something you declared "impossible".

Then you call everybody else confused who isnt stuck several years in the past and tell them to go buy old versions of Delphi to "educate" themselves

ps: it doesnt even make sense to claim that you kept refering to old Delphi .NET versions all the time, because i explicitly mentioned Embarcadero twice in my first posting with the links for the Delphi metro "hello world" sample and the Delphi roadmap. Even if you dont know who the R&D engineer is who did them and where too lazy to look him up before replying.

[Danilo]

Thanks, i'm fine.

[Rings]

topic splitted,
delphi stuff can be read here: