On Thursday, 1 February 2018 at 17:13:52 UTC, Seb wrote:
>
> curl https://i.dlang.io/install.sh | bash -s dmd

Yeah..let's all run an untrusted shell script (with unknown contents), right off the web.

Will people never learn?

On Friday, 2 February 2018 at 02:15:55 UTC, psychoticRabbit wrote:
> On Thursday, 1 February 2018 at 17:13:52 UTC, Seb wrote:
>>
>> curl https://i.dlang.io/install.sh | bash -s dmd
>
> Yeah..let's all run an untrusted shell script (with unknown contents), right off the web.
>
> Will people never learn?

Relax and take a break. You can still download the script, review and then run it as required.

On Fri, 02 Feb 2018 01:42:08 +0000, Meta wrote:

> On Wednesday, 31 January 2018 at 11:42:14 UTC, Seb wrote:
> 
>> Yes, obviously the current situation isn't ideal, but it's not too bad
>> either and we have found one good, but probably not so well-known yet
>> way to tackle this: the dlang-community organization on GH
>> (https://github.com/dlang-community).
>> A lot of important, but more or less abandoned repositories have been
>> adopted, s.t. there's a common place to submit bug fixes and feature
>> PRs and its ensured by CIs that they are always in a good state, e.g.
>> always compile with the latest DMD.
> 
> Wait, have libdparse et al. been abandoned? What happened to Brian?

I don't think the intended interpretation is that all projects there were abandoned; many projects important to the D ecosystem have been moved there, which includes some otherwise-abandoned projects.

On Friday, 2 February 2018 at 02:33:30 UTC, rjframe wrote:
> On Fri, 02 Feb 2018 01:42:08 +0000, Meta wrote:
>
>> On Wednesday, 31 January 2018 at 11:42:14 UTC, Seb wrote:
>> 
>>> Yes, obviously the current situation isn't ideal, but it's not too bad
>>> either and we have found one good, but probably not so well-known yet
>>> way to tackle this: the dlang-community organization on GH
>>> (https://github.com/dlang-community).
>>> A lot of important, but more or less abandoned repositories have been
>>> adopted, s.t. there's a common place to submit bug fixes and feature
>>> PRs and its ensured by CIs that they are always in a good state, e.g.
>>> always compile with the latest DMD.
>> 
>> Wait, have libdparse et al. been abandoned? What happened to Brian?
>
> I don't think the intended interpretation is that all projects there were abandoned; many projects important to the D ecosystem have been moved there, which includes some otherwise-abandoned projects.

Yes, sorry for the poor wording of less abandoned". I picked it for Brian's project because it used to take ~1-2 months for a simple bug fix to get in. Now it can be merged within a day.
No worries, Brian is still developing his tools (e.g. https://github.com/dlang-community/dfmt/pull/318), but other people do more active development on/with his awesome libs at "upstream".

On Friday, 2 February 2018 at 02:25:47 UTC, Arun Chandrasekaran wrote:
> On Friday, 2 February 2018 at 02:15:55 UTC, psychoticRabbit wrote:
>> On Thursday, 1 February 2018 at 17:13:52 UTC, Seb wrote:
>>>
>>> curl https://i.dlang.io/install.sh | bash -s dmd
>>
>> Yeah..let's all run an untrusted shell script (with unknown contents), right off the web.
>>
>> Will people never learn?
>
> Relax and take a break. You can still download the script, review and then run it as required.

First I had a typo there - it should have been

> curl https://dlang.io/install.sh | bash -s dmd

(I type to much text on my tiny phone screen these days).

Apart from as Arun correctly pointed out, going the two step route of doing your audit locally:

---
wget https://dlang.io/install.sh
vi install.sh # do your audit
bash install.sh
---

Also:

- note that install.sh will download the official D keyring (https://dlang.org/gpg_keys.html), with which all binaries + the script itself are signed, s.t. it can verify binaries + updates to the script.

- it's a fairly common practice, e.g. https://www.rustup.rs

On Friday, 2 February 2018 at 02:25:47 UTC, Arun Chandrasekaran wrote:
> On Friday, 2 February 2018 at 02:15:55 UTC, psychoticRabbit wrote:
>> On Thursday, 1 February 2018 at 17:13:52 UTC, Seb wrote:
>>>
>>> curl https://i.dlang.io/install.sh | bash -s dmd
>>
>> Yeah..let's all run an untrusted shell script (with unknown contents), right off the web.
>>
>> Will people never learn?
>
> Relax and take a break. You can still download the script, review and then run it as required.

Yeah...it's not like I'm unfamiliar with that concept ;-)

But many (perhaps most) are not.

btw. Oh.. and I do hope that debian/apache webserver they use cannot be hacked... cause I've heard you can do some interesting stuff on people systems with shell scripts ;-)

On Thursday, 1 February 2018 at 15:27:02 UTC, Benny wrote:
> Suggestion:
>
> Is it maybe not better to have one "front-end" compiler visible that people download
>
> Example:
>
> D run main.d
> D run main.d --compiler ldc ( not installed? Auto download and compile using dub )
> D run main.d --compiler ldc --options -o3
> D run main.d --compiler gdc ( not installed? Auto ...)
>
> D package install web-d
>
> Seen this layout with a some other compilers where everything is clean integrated.
>
> - Compiler ( default )
> -- Run
> -- Test
>
> - Package
> -- Install
> -- Remove
> -- Update
>
> - Tools
> --- Format
> --- Check
> - Language server?
>
> No dub, no ldc, gdc, no confusion, just one clean interface. What happens behind the interface is nobody there business. It just presents better.
>
> Dub already does half this work with the compiler option but its a package manager not the "face of D". Hard to explain...
>
> Anyway, too much off-topic?

DUB can fill this role quite well. What it needs is clearer documentation on how to switch compilers. Better yet, outright compiler switches from the command line to designate a compiler, compile debug code, or run unittest code.


On another note, I do want to put in my two cents about this controversial thread, and the continuing GC threads that pop up. People that use D find it highly productive and performant in their domains. C and C++ programmers, ostensibly the target audience of D, continue to reject GC as some kind of albatross they'll never get over.

dlang.org needs front-page, clear as day examples of the speed benefits of optimized D code. Show that there is minimal or no impact from the GC is most modern use cases (i.e. within components of a web framework, within a database, within a desktop application). Compare performance of real solutions. And, if it can be done, show how maximally performant embedded code with no GC can be run on constrained real-time hardware with a significant gain in code readability.

tl;dr EXAMPLES EXAMPLES EXAMPLES

SHOW the world why the GC is not only not a big deal, but a good thing, and STOP trying to TELL them by playing defense in discussion threads around the Internet.

On Thursday, 1 February 2018 at 22:38:36 UTC, Walter Bright wrote:
> On 2/1/2018 3:11 AM, Martin Tschierschke wrote:
>> Idea: There should be some kind of news ticker for all enhancements and important decisions, maybe at first just via twitter  with a special #tag  beside #dlang where all updates are announced. And a place on the homepage, where this feed is displayed separately.
>
> It's already there on the right side of https://dlang.org/

>> with a special #tag  beside #dlang
The focus was on a feed with _two_ tags #dlang and #dfoundation for example.

In the feed on the homepage everything is mixed up and I am feeling a lot information about progress - made in the background - is missing.

Maybe there should be a blog post, with some kind of status report every .. weeks or .. month? Telling more about the focus of the D foundation, statistics of downloads, number of fixed bugs, partly similar to Adams week in D but more official. I think the content of such a post may find its way into more mainstream IT magazines, if marked as official d foundation  press release even more.

On Friday, 2 February 2018 at 08:21:33 UTC, Martin Tschierschke wrote:
> On Thursday, 1 February 2018 at 22:38:36 UTC, Walter Bright wrote:
>> On 2/1/2018 3:11 AM, Martin Tschierschke wrote:
>>> Idea: There should be some kind of news ticker for all enhancements and important decisions, maybe at first just via twitter  with a special #tag  beside #dlang where all updates are announced. And a place on the homepage, where this feed is displayed separately.
>>
>> It's already there on the right side of https://dlang.org/
>
>>> with a special #tag  beside #dlang
> The focus was on a feed with _two_ tags #dlang and #dfoundation for example.
>
> In the feed on the homepage everything is mixed up and I am feeling a lot information about progress - made in the background - is missing.
>
> Maybe there should be a blog post, with some kind of status report every .. weeks or .. month? Telling more about the focus of the D foundation, statistics of downloads, number of fixed bugs, partly similar to Adams week in D but more official. I think the content of such a post may find its way into more mainstream IT magazines, if marked as official d foundation  press release even more.

The best status report I've met is definitely the FreeBSD quarterly status report:

https://www.freebsd.org/news/status/status.html

I suggest to take a look at that, as an inspiration.... and yes, a quarterly report is enough.

/Paolo

On Friday, 2 February 2018 at 08:39:58 UTC, Paolo Invernizzi wrote:
> On Friday, 2 February 2018 at 08:21:33 UTC, Martin Tschierschke
[...]
>> Maybe there should be a blog post, with some kind of status report every .. weeks or .. month? Telling more about the focus of the D foundation, statistics of downloads, number of fixed bugs, partly similar to Adams week in D but more official. I think the content of such a post may find its way into more mainstream IT magazines, if marked as official d foundation  press release even more.
>
> The best status report I've met is definitely the FreeBSD quarterly status report:
>
> https://www.freebsd.org/news/status/status.html
>
> I suggest to take a look at that, as an inspiration.... and yes, a quarterly report is enough.
>
> /Paolo
Yes, looks very good!