Re: What are we going to do about mobile?

On Thursday, 24 August 2017 at 14:28:07 UTC, Joakim wrote: Unfortunately, not everything works great. Like LDC being version 0.14.0 ( 2014! ) on the Pi3 Debian images. And well, "_Unwind_RaiseException failed with reason code: 2128056904", on a simply compile. Not exactly hopeful. Have you

Re: What are we going to do about mobile?

On 2017-08-24 12:47, James W Hofmann wrote: Which leads me to a great armchair proposal: D should support Excel spreadsheets ;) Not sure what you had in mind but have a look at: http://forum.dlang.org/post/ubheswgdpafyeyboh...@forum.dlang.org -- /Jacob Carlborg

Re: What are we going to do about mobile?

On Thursday, 24 August 2017 at 10:47:07 UTC, James W Hofmann wrote: I happened across this old thread in a search for "mobile app dlang". I got a Chromebook recently and it represents a substantial phase shift in devices for me: * It's an ARM laptop (Asus Chromebook R13, big.LITTLE 2/2

Re: What are we going to do about mobile?

On Thursday, 24 August 2017 at 10:47:07 UTC, James W Hofmann wrote: I happened across this old thread in a search for "mobile app dlang". I got a Chromebook recently and it represents a substantial phase shift in devices for me: Arm has indeed become a more compelling platform, especially

Re: What are we going to do about mobile?

On Thursday, 24 August 2017 at 10:47:07 UTC, James W Hofmann wrote: Which leads me to a great armchair proposal: D should support Excel spreadsheets ;) You say that somewhat in jest but take a look at https://github.com/kaleidicassociates/excel-d

Re: What are we going to do about mobile?

I happened across this old thread in a search for "mobile app dlang". I got a Chromebook recently and it represents a substantial phase shift in devices for me: * It's an ARM laptop (Asus Chromebook R13, big.LITTLE 2/2 cores, 4GB memory) * It's also a tablet convertible * The main OS is the

Re: What are we going to do about mobile?

On Tue, May 09, 2017 at 09:08:17AM +, Joakim via Digitalmars-d wrote: [...] > On the other hand, even if sales are doubling, that doesn't mean you > aren't dying. Consider Blackberry, whose sales rocketed up even after > the iPhone was first introduced in 2007: > >

Re: What are we going to do about mobile?

On Tuesday, 9 May 2017 at 04:39:33 UTC, Jerry wrote: On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: That means this tidal wave of mobile swamping PCs is only going to get worse: https://twitter.com/lukew/status/842397687420923904 D is currently built and optimized for that dying PC

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: That means this tidal wave of mobile swamping PCs is only going to get worse: https://twitter.com/lukew/status/842397687420923904 D is currently built and optimized for that dying PC platform. There are only two devs working on

Re: What are we going to do about mobile?

On 5/8/17 9:26 PM, Bienlein wrote: Let's not forget Kotlin and Swift, things we'd really be competing against - that is the other NEW stuff. Kotlin/Native is now in the making and there is already a preview:

Re: What are we going to do about mobile?

Let's not forget Kotlin and Swift, things we'd really be competing against - that is the other NEW stuff. Kotlin/Native is now in the making and there is already a preview: https://blog.jetbrains.com/kotlin/2017/04/kotlinnative-tech-preview-kotlin-without-a-vm/

Re: What are we going to do about mobile?

On 1 May 2017 at 18:18, Iain Buclaw wrote: > On 1 May 2017 at 17:47, Johannes Pfau via Digitalmars-d > wrote: >> Am Mon, 1 May 2017 14:44:35 +0200 >> schrieb Iain Buclaw via Digitalmars-d : >> >>> On 1 May 2017 at

Re: What are we going to do about mobile?

On 1 May 2017 at 17:47, Johannes Pfau via Digitalmars-d wrote: > Am Mon, 1 May 2017 14:44:35 +0200 > schrieb Iain Buclaw via Digitalmars-d : > >> On 1 May 2017 at 14:40, Iain Buclaw wrote: >> > So that's 3 build

Re: What are we going to do about mobile?

Am Mon, 1 May 2017 14:44:35 +0200 schrieb Iain Buclaw via Digitalmars-d : > On 1 May 2017 at 14:40, Iain Buclaw wrote: > > So that's 3 build servers - 1x ARM7, 1x ARM8, and 1x x86. ;-) > > With the latter also testing all crosses we can do

Re: What are we going to do about mobile?

On 1 May 2017 at 14:40, Iain Buclaw wrote: > So that's 3 build servers - 1x ARM7, 1x ARM8, and 1x x86. ;-) With the latter also testing all crosses we can do (there are 18 different gdc cross-compilers in Ubuntu, for 12 distinct architectures).

Re: What are we going to do about mobile?

On 16 April 2017 at 11:54, Iain Buclaw wrote: > On 16 April 2017 at 11:20, Johannes Pfau via Digitalmars-d > wrote: >> Am Sun, 16 Apr 2017 10:13:50 +0200 >> schrieb Iain Buclaw via Digitalmars-d : >> >>> >>> I

Re: What are we going to do about mobile? [OT]

On 04/13/2017 06:16 PM, Joakim wrote: From a certain point of view, you could say PC sales are only down 25% from their peak, that's not dead yet. But the chart I linked shows their share of personal computing devices, including mobile, has dropped from 78% to a little less than 14% over the

Re: What are we going to do about mobile?

On 16 April 2017 at 11:20, Johannes Pfau via Digitalmars-d wrote: > Am Sun, 16 Apr 2017 10:13:50 +0200 > > I tried concourse-ci which seems nice at first, but it's too > opinionated to be useful for us (now worker cache, no way for newer > commits to auto-cancel

Re: What are we going to do about mobile?

On 16 April 2017 at 11:20, Johannes Pfau via Digitalmars-d wrote: > Am Sun, 16 Apr 2017 10:13:50 +0200 > schrieb Iain Buclaw via Digitalmars-d : > >> >> I asked at a recent D meetup about what gitlab CI used as their >> backing platform,

Re: What are we going to do about mobile?

Am Sun, 16 Apr 2017 10:13:50 +0200 schrieb Iain Buclaw via Digitalmars-d : > > I asked at a recent D meetup about what gitlab CI used as their > backing platform, and it seems like it's a front for TravisCI. YMMV, > but I found the Travis platform to be too slow (it

Re: What are we going to do about mobile?

On 16 April 2017 at 09:41, Johannes Pfau via Digitalmars-d wrote: > Am Sat, 15 Apr 2017 15:11:08 + > schrieb Laeeth Isharc : >> Gitlab has test runners built in, at least for enterprise version >> (which is not particularly

Re: What are we going to do about mobile?

Am Sat, 15 Apr 2017 09:52:49 + schrieb Johan Engelen : > I'd be happy to use the Pi3 as permanent tester, if the risks of > a hacker intruding my home network are manageable ;-) > If you want to be sure use a cheap DMZ setup. VLAN based: Connect your PI to some switch

Re: What are we going to do about mobile?

Am Sat, 15 Apr 2017 15:11:08 + schrieb Laeeth Isharc : > > Not sure how much memory ldc takes to build. If it would be > helpful for ARM I could contribute a couple of servers on > scaleway or similar. At least for GDC building the compiler on low-end

Re: What are we going to do about mobile?

On Saturday, 15 April 2017 at 15:11:08 UTC, Laeeth Isharc wrote: Not sure how much memory ldc takes to build. If it would be helpful for ARM I could contribute a couple of servers on scaleway or similar. That'd be great. Can you take initiative and send a mail to Kai and ask him about the

Re: What are we going to do about mobile?

On Saturday, 15 April 2017 at 09:52:49 UTC, Johan Engelen wrote: On Thursday, 6 April 2017 at 09:39:05 UTC, kinke wrote: What LDC would primarily need is a CI platform supporting ARM (and ideally AArch64) in order to make it a true first-class target. We don't know of a free CI platform, so

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 09:39:05 UTC, kinke wrote: What LDC would primarily need is a CI platform supporting ARM (and ideally AArch64) in order to make it a true first-class target. We don't know of a free CI platform, so ARM isn't tested automatically, and it's currently mostly up to

Re: What are we going to do about mobile? [OT]

On Wednesday, 12 April 2017 at 19:20:27 UTC, Nick Sabalausky (Abscissa) wrote: I *strongly* agree with the notion that mobile/ARM/iOS/'droid/etc needs to be a major part of D's immediate future. However... On 04/06/2017 01:24 AM, Joakim wrote: I have been saying for some time now that

[OT] Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 09:39:05 UTC, kinke wrote: we already have (unlike DMD, fully free!) D compilers able to ... DMD is now fully free: https://forum.dlang.org/post/oc8acc$1ei9$1...@digitalmars.com

Re: What are we going to do about mobile?

On 13/04/2017 10:30 AM, Iain Buclaw via Digitalmars-d wrote: On 13 April 2017 at 10:12, Russel Winder via Digitalmars-d wrote: On Wed, 2017-04-12 at 10:59 +0100, rikki cattermole via Digitalmars-d wrote: […] Considering it was created in 2014, I think we're safe

Re: What are we going to do about mobile?

On 13 April 2017 at 10:12, Russel Winder via Digitalmars-d wrote: > On Wed, 2017-04-12 at 10:59 +0100, rikki cattermole via Digitalmars-d > wrote: >> […] >> >> Considering it was created in 2014, I think we're safe implementing >> extern(JNI) support either which

Re: What are we going to do about mobile?

On Wed, 2017-04-12 at 10:59 +0100, rikki cattermole via Digitalmars-d wrote: > […] > > Considering it was created in 2014, I think we're safe implementing  > extern(JNI) support either which ways. > > Although a little strange since nobody has completed a full JNI  > implementation yet! JNI

Re: What are we going to do about mobile? [OT]

I *strongly* agree with the notion that mobile/ARM/iOS/'droid/etc needs to be a major part of D's immediate future. However... On 04/06/2017 01:24 AM, Joakim wrote: I have been saying for some time now that mobile is going to go after the desktop next

Re: What are we going to do about mobile? [OT]

On 04/06/2017 08:52 AM, Adam D. Ruppe wrote: I don't even own a mobile device and don't see that changing any time soon (they are really expensive, slow, and just generally hard to use*). That last point is so very true. Bugs me so much that 99.999% of mobile users never really understood

Re: What are we going to do about mobile?

On 12/04/2017 10:54 AM, Russel Winder via Digitalmars-d wrote: On Wed, 2017-04-12 at 10:43 +0100, rikki cattermole via Digitalmars-d wrote: […] JNI itself isn't hard to work with, its mapping classes for D easily to it which is hard. Especially when inheritance comes into play. JNI is on

Re: What are we going to do about mobile?

On Wed, 2017-04-12 at 10:43 +0100, rikki cattermole via Digitalmars-d wrote: > […] > > JNI itself isn't hard to work with, its mapping classes for D easily > to  > it which is hard. Especially when inheritance comes into play. JNI is on notice for being retired, but clearly this is Java so

Re: What are we going to do about mobile?

On 12/04/2017 10:37 AM, Joakim wrote: On Friday, 7 April 2017 at 09:40:26 UTC, rikki cattermole wrote: On 07/04/2017 10:34 AM, Joakim wrote: On Thursday, 6 April 2017 at 05:32:41 UTC, rikki cattermole wrote: IMO there is two things that need to be done to get D for mobile: 1: ldc needs to

Re: What are we going to do about mobile?

On Friday, 7 April 2017 at 09:40:26 UTC, rikki cattermole wrote: On 07/04/2017 10:34 AM, Joakim wrote: On Thursday, 6 April 2017 at 05:32:41 UTC, rikki cattermole wrote: IMO there is two things that need to be done to get D for mobile: 1: ldc needs to natively target and distribute binaries

Re: What are we going to do about mobile?

Am Sun, 09 Apr 2017 12:44:15 + schrieb Nick B : > > I'd say we just have /more/ fully capable computers around us > > nowadays. I'd probably roughly split it into > > - web/cloud server machines, often running VMs > > - scientific computation clusters > > - desktops

Re: What are we going to do about mobile?

On Friday, 7 April 2017 at 14:47:03 UTC, Marco Leise wrote: Am Thu, 06 Apr 2017 05:24:07 + schrieb Joakim : D is currently built and optimized for that dying PC platform. As long as the world still needs headless machines running web sites, simulations, cloud

Re: What are we going to do about mobile?

On Saturday, 8 April 2017 at 05:37:24 UTC, Jethro wrote: On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: I have been saying for some time now that mobile is going to go after the desktop next (http://forum.dlang.org/thread/rionbqmtrwyenmhmm...@forum.dlang.org), Samsung just announced

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: I have been saying for some time now that mobile is going to go after the desktop next (http://forum.dlang.org/thread/rionbqmtrwyenmhmm...@forum.dlang.org), Samsung just announced it, for a flagship device that will ship tens of millions:

Re: What are we going to do about mobile?

On Friday, 7 April 2017 at 14:47:03 UTC, Marco Leise wrote: Am Thu, 06 Apr 2017 05:24:07 + schrieb Joakim : [...] That's what I meant by embedded programming. Not those 1mb RAM boards. Smart devices/IoT (home automation, smart cards, industrial machines, etc.) using

Re: What are we going to do about mobile?

Am Thu, 06 Apr 2017 05:24:07 + schrieb Joakim : > D is currently built and optimized for that dying PC platform. As long as the world still needs headless machines running web sites, simulations, cloud services, ...; as long as we still need to edit office documents, run

Re: What are we going to do about mobile?

On 07/04/2017 10:34 AM, Joakim wrote: On Thursday, 6 April 2017 at 05:32:41 UTC, rikki cattermole wrote: IMO there is two things that need to be done to get D for mobile: 1: ldc needs to natively target and distribute binaries for Android (MIPS, ARM, at least). I'm not sure what you mean by

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 05:32:41 UTC, rikki cattermole wrote: IMO there is two things that need to be done to get D for mobile: 1: ldc needs to natively target and distribute binaries for Android (MIPS, ARM, at least). I'm not sure what you mean by "natively target." Do you mean that

Re: What are we going to do about mobile?

On 4/6/17 7:24 AM, Joakim wrote: I have been saying for some time now that mobile is going to go after the desktop next (http://forum.dlang.org/thread/rionbqmtrwyenmhmm...@forum.dlang.org), Samsung just announced it, for a flagship device that will ship tens of millions: [snip] The latter may

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 19:02:00 UTC, aberba wrote: On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: and pitch in, like this guy who's now trying ldc out on an embedded device with an old ARMv5 core: https://github.com/ldc-developers/ldc/issues/2058 What is currently needed

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: and pitch in, like this guy who's now trying ldc out on an embedded device with an old ARMv5 core: https://github.com/ldc-developers/ldc/issues/2058 What is currently needed for D in IoT?

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: I have been saying for some time now that mobile is going to go after the desktop next (http://forum.dlang.org/thread/rionbqmtrwyenmhmm...@forum.dlang.org), Samsung just announced it, for a flagship device that will ship tens of millions:

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: There are only two devs working on mobile, Dan and me, I don't think anybody on the core team has even tried our work. I don't even own a mobile device and don't see that changing any time soon (they are really expensive, slow, and just

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: That means this tidal wave of mobile swamping PCs is only going to get worse: That remains to be seen. Even Microsoft has announced that they're taking another shot at ARM, ie Windows is coming to ARM again, this time with x86

Re: What are we going to do about mobile?

On Thursday, 6 April 2017 at 05:24:07 UTC, Joakim wrote: D is currently built and optimized for that dying PC platform. I don't think x86 is dying soon, but I agree that embedded architectures get more important every day and should get more focus. I would even go so far as to say it may

Re: What are we going to do about mobile?

IMO there is two things that need to be done to get D for mobile: 1: ldc needs to natively target and distribute binaries for Android (MIPS, ARM, at least). 2: extern(JNI) seriously, its a pain to work with Java over JNI otherwise. It would be worse then not having extern(Obj-C).

What are we going to do about mobile?

I have been saying for some time now that mobile is going to go after the desktop next (http://forum.dlang.org/thread/rionbqmtrwyenmhmm...@forum.dlang.org), Samsung just announced it, for a flagship device that will ship tens of millions: