July 02, 2020
On 7/1/2020 10:00 AM, Steven Schveighoffer wrote:
> It may not be a dismissable problem, but it's also not someone anyone but Walter can fix. So the question from a community standpoint is (allowing that we have really no control over this), is it worth having Walter create an entirely new backend instead of doing other work? I'd say no.

I'm pretty sure that 3/4 of the backend can be used pretty much as-is. The optimizer, for example, is independent. The 16 bit stuff can be omitted, so can the floating point emulator and x87 code. The rest of the structure can be kept, just replacing the tinsel on the christmas tree. The exception handling support, symbolic debug support, and object file support should be the same.
July 02, 2020
On Thursday, 2 July 2020 at 00:12:03 UTC, solidstate1991 wrote:
>
> Money is still a concern for me, although I have a few plans to remedy it.

Hello,

I don't know your current status and plans, but we have a Bug Bounty program in Dplug that a D freelancer could use: https://github.com/AuburnSounds/Dplug/wiki/Bug-Bounty-Program

Those are are well defined and known tasks with hopefully reduced scopes.

(I'm p0nce#8282 on the D official Discord, if anyone wants to enter the conversation)
July 02, 2020
On 7/2/20 6:31 AM, Walter Bright wrote:
> On 7/1/2020 10:00 AM, Steven Schveighoffer wrote:
>> It may not be a dismissable problem, but it's also not someone anyone but Walter can fix. So the question from a community standpoint is (allowing that we have really no control over this), is it worth having Walter create an entirely new backend instead of doing other work? I'd say no.
> 
> I'm pretty sure that 3/4 of the backend can be used pretty much as-is. The optimizer, for example, is independent. The 16 bit stuff can be omitted, so can the floating point emulator and x87 code. The rest of the structure can be kept, just replacing the tinsel on the christmas tree. The exception handling support, symbolic debug support, and object file support should be the same.

Well, as I said, it's you who probably has to do it, so if you want to do it, then I would love to keep using DMD on my (future) macbook ;)

-Steve
July 02, 2020
On 7/1/2020 8:48 AM, Martin Tschierschke wrote:
> On Wednesday, 1 July 2020 at 08:22:25 UTC, Paolo Invernizzi wrote:
> 
>>
>> A 35$ Raspberry PI supports 2x 4K display, and comes with a Debian based linux complete with GUI. You can attach a keyboard, mouse and have a little ARM machine to toy with (but no precompiled LDC, its 32bit ...)
> 
> What do you mean by "no precompiled LDC?"
> 
> Just `sudo apt install ldc` and you go....
> 
> ldc2 --version
> LDC - the LLVM D compiler (1.12.0):
>    based on DMD v2.082.1 and LLVM 6.0.1
>    built with LDC - the LLVM D compiler (1.12.0)
>    Default target: armv6-unknown-linux-gnueabihf
>    Host CPU: cortex-a72
>    http://dlang.org - http://wiki.dlang.org/LDC
> 

Clearly, someone needs to write a D blog article explaining how to get a simple D program compiled and running on the Raspberry Pi. Note that the D Foundation pays for articles that are published on the D Blog.

What are you waiting for? :-)
July 02, 2020
On Thursday, 2 July 2020 at 20:42:25 UTC, Walter Bright wrote:
> Clearly, someone needs to write a D blog article explaining how to get a simple D program compiled and running on the Raspberry Pi.

apt install gdc

gdc program.d

where's my cash? :P

It really is that simple, with the one caveat that the gdc in the package manager is a bit old, so not all libraries will just work.

Getting gdc into gcc is a real victory - it is this simple on various Linux systems now.

I recently did a gpio module too and made a little D program to do audio and trigger leds on a raspberry pi http://dpldocs.info/this-week-in-d/Blog.Posted_2020_05_11.html#gpio.d
July 02, 2020
On Thursday, 2 July 2020 at 20:46:52 UTC, Adam D. Ruppe wrote:
> On Thursday, 2 July 2020 at 20:42:25 UTC, Walter Bright wrote:
>> Clearly, someone needs to write a D blog article explaining how to get a simple D program compiled and running on the Raspberry Pi.
>
> apt install gdc
>
> gdc program.d
>
> where's my cash? :P
>

How about on Windows? I guess that might be tricky.
July 02, 2020
On 7/2/2020 1:46 PM, Adam D. Ruppe wrote:
> On Thursday, 2 July 2020 at 20:42:25 UTC, Walter Bright wrote:
>> Clearly, someone needs to write a D blog article explaining how to get a simple D program compiled and running on the Raspberry Pi.
> 
> apt install gdc
> 
> gdc program.d
> 
> where's my cash? :P
> 
> It really is that simple, with the one caveat that the gdc in the package manager is a bit old, so not all libraries will just work.
> 
> Getting gdc into gcc is a real victory - it is this simple on various Linux systems now.
> 
> I recently did a gpio module too and made a little D program to do audio and trigger leds on a raspberry pi http://dpldocs.info/this-week-in-d/Blog.Posted_2020_05_11.html#gpio.d

Posting in the n.g. only reaches people already using D. The point of the D Blog is outreach.
July 02, 2020
On 7/2/2020 1:42 PM, Walter Bright wrote:
> Clearly, someone needs to write a D blog article explaining how to get a simple D program compiled and running on the Raspberry Pi. Note that the D Foundation pays for articles that are published on the D Blog.
> 
> What are you waiting for? :-)

If that's not incentive enough, consider that I know programmers with in excess of $1m in annual compensation. What do they have in common? They write blogs and articles about what they do.

It's great marketing for yourself.

You might be every bit good a programmer as they are, but nobody knows that because you don't write any articles, do any presentations at conferences, etc. When nobody knows you're good, you aren't going to be highly compensated.

BTW, something I'm very proud about, many people who presented at DConf have gotten very well paying jobs as a direct result.
July 02, 2020
On Thursday, 2 July 2020 at 21:40:24 UTC, JN wrote:
> How about on Windows? I guess that might be tricky.

So that is developing for the pi on the pi itself.

Cross compiling is easiest on ldc: you get ldc for your host system, grab ldc for the target, then merge the library directories and configuration files.

It still isn't hard, but it is a bit more work. I'm gonna be working with the ldc people some time later this month to make it very simple too (I did it for android already, just gonna generalize that to other targets as well), so you just do like "ldc setup" and check off the targets you want and then it sets it all up for you.
July 03, 2020
On Thursday, 2 July 2020 at 20:42:25 UTC, Walter Bright wrote:
> On 7/1/2020 8:48 AM, Martin Tschierschke wrote:

> Clearly, someone needs to write a D blog article explaining how to get a simple D program compiled and running on the Raspberry Pi. Note that the D Foundation pays for articles that are published on the D Blog.
>
> What are you waiting for? :-)

Its very tricky when dealing with the D folks. 😂 Sometimes its hard to know if it'll be any interesting. But yeah, I've got stuff in the pipeline to do something about it...not just on the D blog.