So we'll be able to make apps for phones and smart TVs? Using the standard OpenWindow() and event loops?User_Russian wrote:On your smartphone, tablet, smart TV, which processor?
Support of ARM CPU
Re: Support of ARM CPU
Re: Support of ARM CPU
I think you will need the other part of equation too, the O.S.
Re: Support of ARM CPU
Linux and windows 10 run on ARM uprocessors.
The nice thing about standards is there are so many to choose from. ~ Andrew Tanenbaum
Re: Support of ARM CPU
Yes my answer is about the BarryG comment, so not every ARM device will run PB code
Re: Support of ARM CPU
There is so many ARM boards and operating systems.
I think in most cases Linux (Ubuntu 20.04 LTS) and Raspberry Pi (3 or 4) is best combination for PB.
purenet
I think in most cases Linux (Ubuntu 20.04 LTS) and Raspberry Pi (3 or 4) is best combination for PB.
purenet
- the.weavster
- Addict
- Posts: 1537
- Joined: Thu Jul 03, 2003 6:53 pm
- Location: England
Re: Support of ARM CPU
+1
And I'll pay extra for it. (Probably annually, if asked!)
And I'll pay extra for it. (Probably annually, if asked!)
- the.weavster
- Addict
- Posts: 1537
- Joined: Thu Jul 03, 2003 6:53 pm
- Location: England
Re: Support of ARM CPU
Me too...Tenaja wrote:And I'll pay extra for it. (Probably annually, if asked!)
PB++ perhaps?
Re: Support of ARM CPU
I also !!the.weavster wrote:Me too...Tenaja wrote:And I'll pay extra for it. (Probably annually, if asked!)
PB++ perhaps?
-
- Addict
- Posts: 1443
- Joined: Wed Nov 12, 2008 5:01 pm
- Location: Russia
Re: Support of ARM CPU
People, you can regularly send donations to Fred.Tenaja wrote:And I'll pay extra for it. (Probably annually, if asked!)
Re: Support of ARM CPU
Sorry, but I'm really dumb (as in, I don't follow technology news and trends). Please explain like I'm five. PureBasic supports Windows, Linux, and Mac. How does ARM support change this? I don't get it. Is it just because newer Windows, Linux, and Macs will use ARM processors in future, and PureBasic doesn't currently support that? If so, will PureBasic still support older Intel PCs like my current one?
Re: Support of ARM CPU
Windows, Linux and MacOs are operating systems.
ARM is a processor architecture, like x86.
ARM chips are used in phones and on things like the Raspberry Pi.
Now, on the Raspberry Pi, you can run Linux. That means, you can probably run/compile PB applications on the Raspberry Pi (and others like it), when PB supports ARM in the future.
You can not code applications for Android phones, because PB does not support Android (independent of the chip architecture).
ARM is a processor architecture, like x86.
ARM chips are used in phones and on things like the Raspberry Pi.
Now, on the Raspberry Pi, you can run Linux. That means, you can probably run/compile PB applications on the Raspberry Pi (and others like it), when PB supports ARM in the future.
You can not code applications for Android phones, because PB does not support Android (independent of the chip architecture).
Re: Support of ARM CPU
So, I see no reason to get excited by ARM support when it comes to Windows programming? How will PureBasic supporting ARM make a difference to my Windows apps that I'm currently coding?
Re: Support of ARM CPU
It will allow them to run natively on the ARM version of Windows 10.BarryG wrote: How will PureBasic supporting ARM make a difference to my Windows apps that I'm currently coding?
Best wishes to the PB community. Thank you for the memories.
Re: Support of ARM CPU
Desktop use declines - mobile use increases. If the language you use for your desktop app, dies out due to funding problems in the future, you will know what it means to you.BarryG wrote:So, I see no reason to get excited by ARM support when it comes to Windows programming? How will PureBasic supporting ARM make a difference to my Windows apps that I'm currently coding?
It might simply be financially risky not to support this (partial) transformation of the market/industry. You can find an interview with Bill Gates where he talks about his biggest mistake. Missing industry transformations might simply have your customer base move away to other growing markets - till at some point - your old remaining market is too small and has become an economical niche. It might simply be risky to not follow how the market evolves. The money and customers are still there in the future, but they spend their money on another market.
The question is - how many of those mistakes can you afford to make?
The other effect is that there are solutions which cover both desktop and mobile market. If a desktop developer has to develop for mobile market in the future, they have to learn an additional language. Once they have done that, what will be the persons natural choice for their next desktop project? I know that for me it would be easier to get an expert on one development toolset, then having to deal with two. So i would naturally migrate to the one that supports both and prefer not having to maintain two different skillsets. So the existing userbase slowly gets smaller for one community, while another one gets larger.
Last edited by Bitblazer on Wed May 13, 2020 8:55 am, edited 1 time in total.