Re: Vision document for H1 2018

[psychoticRabbit via Digitalmars-d-announce]

On Friday, 9 March 2018 at 21:43:53 UTC, Andrei Alexandrescu 
wrote:
Hello, the vision document of the Founation for the first six 
months of 2018 is here:


nice.

andd that 'langauge specification' is really important too.. or 
people will drift towards languages that 'are' properly specified.


None of us like to be surprised by what the compiler does. The 
spec should tell it what to do.


and...just don't implement a 'no hugs' policy, or I'm outta here 
;-)

Re: dpldocs now has cross-package search (experimental)

[Andre Pany via Digitalmars-d-announce]

On Saturday, 10 March 2018 at 00:09:18 UTC, Adam D. Ruppe wrote:

Looking for http libs? Behold:

http://search.dpldocs.info/?q=http


Oh my. Eats 2 GB of ram but with the newest patrons 
 I sprung for the beefier 
host. Only searches projects already on the site as of the 
beginning of each day (it loads what has already been 
generated, it doesn't seek to generate more at this time).


It loads one of my own deprecated modules as the top result. 
lol, it could still use some work. But it is started now.


That is so great. Thanks.

A little feature request. Could you group the found modules by 
dub package. Then the same license information can be shown once 
per dub package.


Kind regards
André

Re: Vision document for H1 2018

[bachmeier via Digitalmars-d-announce]

On Saturday, 10 March 2018 at 00:03:20 UTC, Joakim wrote:


Very nice, love how concrete this document has become, 
including listing the members of the core team, especially 
compared to the vague early vision statements.


One note about @nogc: I've seen complaints about the -vgc 
reports on reddit, that they're not very useful for mixed @nogc 
usage, where the GC is used for part of the codebase, not sure 
if something can be done about that.


https://issues.dlang.org/show_bug.cgi?id=18404

Re: Vision document for H1 2018

[rikki cattermole via Digitalmars-d-announce]

On 10/03/2018 10:43 AM, Andrei Alexandrescu wrote:
Hello, the vision document of the Founation for the first six months of 
2018 is here:


https://wiki.dlang.org/Vision/2018H1

In addition to the expected items, we have a new top-level priority - 
locking down the language definition. This is in recognition of the fact 
that we need a precise definition of the language going forward.



Thanks,

Andrei


I was going to edit the document and argue for it (but procedure has 
been a bit different this time), shared libraries.


From what I saw in 2017 and pre 2016 too they are the number one 
implementation issue of D that drives people away. Almost everything 
else can be worked around.


Now that we have @nogc exceptions, and are going pay-as-you-go for 
runtime, this is the biggest thing holding us back IMO.


We need clear use cases with example code that works cross-platform.

With D-host, With C-host, merged with host, unmerged to host. Stuff like 
that.

dpldocs now has cross-package search (experimental)

[Adam D. Ruppe via Digitalmars-d-announce]

Looking for http libs? Behold:

http://search.dpldocs.info/?q=http


Oh my. Eats 2 GB of ram but with the newest patrons 
 I sprung for the beefier 
host. Only searches projects already on the site as of the 
beginning of each day (it loads what has already been generated, 
it doesn't seek to generate more at this time).


It loads one of my own deprecated modules as the top result. lol, 
it could still use some work. But it is started now.

Re: Vision document for H1 2018

[Joakim via Digitalmars-d-announce]

On Friday, 9 March 2018 at 21:43:53 UTC, Andrei Alexandrescu 
wrote:
Hello, the vision document of the Founation for the first six 
months of 2018 is here:


https://wiki.dlang.org/Vision/2018H1

In addition to the expected items, we have a new top-level 
priority - locking down the language definition. This is in 
recognition of the fact that we need a precise definition of 
the language going forward.



Thanks,

Andrei


Very nice, love how concrete this document has become, including 
listing the members of the core team, especially compared to the 
vague early vision statements.


One note about @nogc: I've seen complaints about the -vgc reports 
on reddit, that they're not very useful for mixed @nogc usage, 
where the GC is used for part of the codebase, not sure if 
something can be done about that.

Vision document for H1 2018

[Andrei Alexandrescu via Digitalmars-d-announce]

Hello, the vision document of the Founation for the first six months of 
2018 is here:


https://wiki.dlang.org/Vision/2018H1

In addition to the expected items, we have a new top-level priority - 
locking down the language definition. This is in recognition of the fact 
that we need a precise definition of the language going forward.



Thanks,

Andrei

Re: Article: Why Const Sucks

[Nathan S. via Digitalmars-d-announce]

On Monday, 5 March 2018 Jonathan M Davis wrote at 
http://jmdavisprog.com/articles/why-const-sucks.html:
What Java has instead is `final`, which IMHO is borderline 
useless


In Java `final`  is extremely useful for efficient threadsafe 
code.

Re: Release: nanovega.d rendering lib like html5 canvas

[WebFreak001 via Digitalmars-d-announce]

On Thursday, 8 March 2018 at 22:08:30 UTC, aberba wrote:

On Thursday, 8 March 2018 at 19:24:43 UTC, WebFreak001 wrote:

On Thursday, 8 March 2018 at 03:55:35 UTC, Adam D. Ruppe wrote:

https://github.com/adamdruppe/arsd

nanovega.d

[...]


AMAZING! I think this will revolutionize how we do GUI and 
rendering in D, especially nogc. You can make really cool 
effects and renders very quickly.


Got some cool project ideas how you could use this already. 
You could make a WPF clone in D for example if you put in a 
lot of time, but it would probably be far superior than all 
other currently existing GUI toolkits if you get the data 
binding and event layer right.


And theming. Especially with a subset of CSS.


Yeah you can make really cool effects: https://wfr.moe/fFYvHH.png

---

string txt = "Text me up.";
float[4] bounds;
nvg.fontFace = "Roboto";
nvg.fontSize = 32;
nvg.textBounds(64, 64, txt, bounds[]);
nvg.beginPath();
nvg.roundedRect(bounds[0] - 32, bounds[1] - 8 + 8, 
bounds[2]-bounds[0] + 64, bounds[3]-bounds[1] + 16, 4);
nvg.fillPaint = nvg.linearGradient(bounds[0], bounds[1], 
bounds[2], bounds[3], NVGColor("#c50"), NVGColor("#860"));

nvg.fill();
nvg.beginPath();
nvg.roundedRect(bounds[0] - 32, bounds[1] - 8, 
bounds[2]-bounds[0] + 64, bounds[3]-bounds[1] + 16, 4);
nvg.fillPaint = nvg.linearGradient(bounds[0], bounds[1], 
bounds[2], bounds[3], NVGColor("#f70"), NVGColor("#a90"));

nvg.fill();
nvg.fillPaint = pattern;
nvg.fill();
nvg.beginPath();
nvg.roundedRect(bounds[0] - 32, bounds[1] - 8, 
bounds[2]-bounds[0] + 64, bounds[3]-bounds[1] + 16 + 8, 4);

nvg.strokeColor = NVGColor.white;
nvg.strokeWidth = 2;
nvg.stroke();
nvg.fillColor = NVGColor.black;
nvg.text(64, 64, txt);

Re: The New New DIP Process

[Joakim via Digitalmars-d-announce]

On Friday, 9 March 2018 at 12:59:07 UTC, Mike Parker wrote:
When I took on the role of DIP Manager last year, I didn't 
realize how much I had to learn. Most of the DIPs made it 
through just fine, but there were a few errors along the way. 
And there were some inefficiencies built into the system that 
weren't so obvious in the beginning. Recently, my new procedure 
document to revise the process was approved.


[...]


mistake: "for the all the details"

Re: Release D 2.079.0

[Jacob Carlborg via Digitalmars-d-announce]

On 2018-03-08 19:21, Martin Nowak wrote:


Also this offer still stands
https://forum.dlang.org/post/drcekmxvfszpwifbu...@forum.dlang.org


Who will decide if semver can/will be used?

--
/Jacob Carlborg

Re: Vibe.d web interface tutorial

[aberba via Digitalmars-d-announce]

On Friday, 9 March 2018 at 16:32:28 UTC, aberba wrote:

New blog post for the learning audience

aberba.com/2018/using-vibe-d-web-interface


http://aberba.com/2018/using-vibe-d-web-interface

Vibe.d web interface tutorial

[aberba via Digitalmars-d-announce]

New blog post for the learning audience

aberba.com/2018/using-vibe-d-web-interface

Re: Release: nanovega.d rendering lib like html5 canvas

[Adam D. Ruppe via Digitalmars-d-announce]

Now also on dub:

http://code.dlang.org/packages/arsd-official%3Ananovega

The New New DIP Process

[Mike Parker via Digitalmars-d-announce]

When I took on the role of DIP Manager last year, I didn't 
realize how much I had to learn. Most of the DIPs made it through 
just fine, but there were a few errors along the way. And there 
were some inefficiencies built into the system that weren't so 
obvious in the beginning. Recently, my new procedure document to 
revise the process was approved.


Structurally, the process is still the same. Now, it has more 
clearly defined responsibilities and time constraints. Hopefully, 
this will kill the inefficiencies we identified in the system, 
and I'll keep an eye open to adapting it as necessary.


This blog post summarizes the changes, their motivation, and my 
new attitude toward the role of the DIP Manager.


Blog:
https://dlang.org/blog/2018/03/09/the-new-new-dip-process/

Reddit:
https://www.reddit.com/r/d_language/comments/836fwt/the_new_new_dip_process/

Re: Released vibe.d 0.8.3

[Martin Tschierschke via Digitalmars-d-announce]

On Friday, 9 March 2018 at 10:07:28 UTC, Sönke Ludwig wrote:
[...]

Additionally, DMD 2.079.0 is finally supported,

[...]

"...write fast, read fast, and run fast.

Fast code, fast."

Thank you!

Re: Released vibe.d 0.8.3

[aberba via Digitalmars-d-announce]

On Friday, 9 March 2018 at 10:07:28 UTC, Sönke Ludwig wrote:
The deprecation phase of the legacy "vibe-d:core" module starts 
with this release by defaulting to the new "vibe-core" package. 
Additionally, DMD 2.079.0 is finally supported, and some 
notable improvements have been made to the HTTP implementation. 
URLRouter in particular has received memory optimizations (to 
avoid fragmentation) that can result in a heavy reduction of 
memory use.


See the change log for instructions to opt for the legacy 
vibe-d:core module in case of any issues with vibe-core.


Change log:
https://vibed.org/blog/posts/vibe-release-0.8.3

DUB package:
https://code.dlang.org/packages/vibe-d/0.8.3


Congrats!

Re: Released vibe.d 0.8.3

[bauss via Digitalmars-d-announce]

On Friday, 9 March 2018 at 10:07:28 UTC, Sönke Ludwig wrote:
The deprecation phase of the legacy "vibe-d:core" module starts 
with this release by defaulting to the new "vibe-core" package. 
Additionally, DMD 2.079.0 is finally supported, and some 
notable improvements have been made to the HTTP implementation. 
URLRouter in particular has received memory optimizations (to 
avoid fragmentation) that can result in a heavy reduction of 
memory use.


See the change log for instructions to opt for the legacy 
vibe-d:core module in case of any issues with vibe-core.


Change log:
https://vibed.org/blog/posts/vibe-release-0.8.3

DUB package:
https://code.dlang.org/packages/vibe-d/0.8.3


Great news. Good job!

Released vibe.d 0.8.3

[Sönke Ludwig via Digitalmars-d-announce]

The deprecation phase of the legacy "vibe-d:core" module starts with 
this release by defaulting to the new "vibe-core" package. Additionally, 
DMD 2.079.0 is finally supported, and some notable improvements have 
been made to the HTTP implementation. URLRouter in particular has 
received memory optimizations (to avoid fragmentation) that can result 
in a heavy reduction of memory use.


See the change log for instructions to opt for the legacy vibe-d:core 
module in case of any issues with vibe-core.


Change log:
https://vibed.org/blog/posts/vibe-release-0.8.3

DUB package:
https://code.dlang.org/packages/vibe-d/0.8.3

Re: "Advent of D" article on Reddit

[bauss via Digitalmars-d-announce]

On Friday, 9 March 2018 at 05:47:08 UTC, sarn wrote:

On Friday, 9 March 2018 at 05:34:31 UTC, bauss wrote:

Lmao I love Reddit.

The D hate has moved onto a new level.

Instead of hating on D, it's now geared towards the amount of 
upvotes a D post on reddit gets.


What an amusement.


To be fair, some things get posted to /r/programming that 
really should stay on /r/d_language.  Spamming doesn't create a 
good image.


Yes, but this is not one of those things.