Re: New DConf Blog Post
On 4/6/19 6:30 PM, bauss wrote: Just going to respond to this: "If you haven’t visited the site in a while, you’ll surely notice that it’s been redesigned. The old version was not responsive and was quite annoying to manipulate on small screens." The design is terrible and it really looks unprofessional. While the old site wasn't responsive, the design was at least slightly better. It just doesn't look very well done. I'm not trying to be negative or anything, but it looks like someone who just learn html/css in 1999 tried to make the design of the page. Aside from perhaps an overuse of padding on the left navbar, it looks good to me. Whaddya want, a bunch of those vaguely-relevant full-screen introductory images you have to scroll past just to get to any nuggets of actual content there might be? The vast majority of "responsive" pages I've seen out there are absolutely god-awful for both aesthetics and practicality. This design is far better than any of them. Bear in mind too, that not playing an endless game of follow-the-crowd with design is a far cry from looking "terrible" or "unprofessional". Not saying there isn't room for improvement, but "The design is terrible and it really looks unprofessional." makes it seem like you're looking at completely different site than I am.
Visual D 0.49.0 released
Hello, the new release of Visual D has just been uploaded. Some major improvements of 0.49.0: * support for Visual Studio 2019 * parallel compilation supported by VC projects * catch up with recent language changes * new "Language" configuration page for -transition=/-preview=/-revert= options See http://rainers.github.io/visuald/visuald/VersionHistory.html for the full list of changes. Visual D is a Visual Studio extension that adds D language support to VS2008-2019. It is written in D, its source code can be found on github: https://github.com/D-Programming-Language/visuald, pull requests welcome. The installer can be found at http://rainers.github.io/visuald/visuald/StartPage.html Rainer
Re: LDC 1.15.0
On Sunday, 7 April 2019 at 14:26:16 UTC, Thomas Mader wrote: Were there some changes to the shared phobos unittest runners between beta2 and the final release? I ask because I have the problem on macOS with the final release that libphobos2-ldc-unittest-shared.85.dylib is not fixed by my fixing step to switch to absolute paths referencing. I use install_name_tool and run this step after I do 'make all-test-runners'. It used to work previously and also with beta2. My guess is that libphobos2-ldc-unittest-shared.85.dylib is getting created after my fixing step now for some reason. No changes wrt. the test runners, especially none wrt. build order. The only CMake change was the frontend version. See https://github.com/ldc-developers/ldc/compare/v1.15.0-beta2...v1.15.0.
Re: LDC 1.15.0
On Saturday, 6 April 2019 at 17:40:39 UTC, kinke wrote:
Glad to announce LDC 1.15:
* Based on D 2.085.1.
* Support for LLVM 8.0. The prebuilt packages ship with LLVM
8.0.0 and include the Khronos SPIRV-LLVM-Translator, so that
dcompute can now emit OpenCL too.
* New -lowmem switch to enable the GC for the front-end,
trading compile times for less required memory (in some cases,
by more than 60%).
* New generic @llvmAttr("name") parameter UDAs, incl. @restrict
with C-like semantics.
* Dropped support for 32-bit macOS. Min macOS version for
prebuilt package raised to 10.9.
* Prebuilt packages don't depend on libtinfo/libedit and don't
require SSSE3 anymore.
* Fix: functions annotated with `pragma(inline, true)` are
implicitly cross-module-inlined again.
Full release log and downloads:
https://github.com/ldc-developers/ldc/releases/tag/v1.15.0
Thanks to all contributors!
Were there some changes to the shared phobos unittest runners
between beta2 and the final release?
I ask because I have the problem on macOS with the final release
that libphobos2-ldc-unittest-shared.85.dylib is not fixed by my
fixing step to switch to absolute paths referencing.
I use install_name_tool and run this step after I do 'make
all-test-runners'. It used to work previously and also with beta2.
My guess is that libphobos2-ldc-unittest-shared.85.dylib is
getting created after my fixing step now for some reason.
Re: hunt-time library 1.0.0 beta1 released
Am 07.04.2019 um 09:09 schrieb bauss: On Thursday, 4 April 2019 at 11:25:34 UTC, Andre Pany wrote: On Thursday, 4 April 2019 at 10:49:46 UTC, zoujiaqing wrote: Hunt time released the first beta version. hunt-time is a time library and similar to Joda-time and Java.time api. [...] I am not sure but did you rewrote the java.time library (copyright of Oracle) from Java to D? I am not an expert but I have some fear using this library due to legal consequences. Did you contacted Oracle and asked wheter that is ok? I honor your work, but if I want to develop commercial applications i have to think twice which libraries I use to avoid any legal issues. Kind regards Andre It's only copyrighted by Oracle if you use Oracle's Java implementation but if you reference OpenJDK then there shouldn't be any problems. But as explained above there aren't any in this case anyway since Oracle's implementation is based on something with a fine license. Except that OpenJDK is L-GPL (AFAICS), so that it can't be changed to Apache in the process.
Re: jupyter-wire v0.0.3 - markdown/HTML support
On Friday, 5 April 2019 at 12:03:48 UTC, Atila Neves wrote:
http://code.dlang.org/packages/jupyter_wire
It's now possible to send markdown or HTML to a jupyter
notebook from D:
return markdownResult("# Header");
Simple, but looks pretty.
Thanks Atila for all your great work and projects!
Re: hunt-time library 1.0.0 beta1 released
On Thursday, 4 April 2019 at 11:25:34 UTC, Andre Pany wrote: On Thursday, 4 April 2019 at 10:49:46 UTC, zoujiaqing wrote: Hunt time released the first beta version. hunt-time is a time library and similar to Joda-time and Java.time api. [...] I am not sure but did you rewrote the java.time library (copyright of Oracle) from Java to D? I am not an expert but I have some fear using this library due to legal consequences. Did you contacted Oracle and asked wheter that is ok? I honor your work, but if I want to develop commercial applications i have to think twice which libraries I use to avoid any legal issues. Kind regards Andre It's only copyrighted by Oracle if you use Oracle's Java implementation but if you reference OpenJDK then there shouldn't be any problems. But as explained above there aren't any in this case anyway since Oracle's implementation is based on something with a fine license.
Re: New DConf Blog Post
On Sunday, 7 April 2019 at 06:19:31 UTC, Mike Parker wrote: On Saturday, 6 April 2019 at 22:30:58 UTC, bauss wrote: The design is terrible and it really looks unprofessional. While the old site wasn't responsive, the design was at least slightly better. It just doesn't look very well done. I'm not trying to be negative or anything, but it looks like someone who just learn html/css in 1999 tried to make the design of the page. Perhaps raising money to pay an experienced web designer would be a good topic for a fundraiser later this year. I think that would be a great idea. I'd tip in with some cash for that.
Re: New DConf Blog Post
On Saturday, 6 April 2019 at 22:30:58 UTC, bauss wrote: The design is terrible and it really looks unprofessional. While the old site wasn't responsive, the design was at least slightly better. It just doesn't look very well done. I'm not trying to be negative or anything, but it looks like someone who just learn html/css in 1999 tried to make the design of the page. Perhaps raising money to pay an experienced web designer would be a good topic for a fundraiser later this year.
