what is it like to 'bootstrap' D? I know in many languages you can forego the standard library and 'bootstrap' yourself on small platforms (C being the main example).
The reference D compiler is now open source
241–250 of 313 posts
Re: The reference D compiler is now open source
#242Earlier quoted context omitted.
> (or a very small one, by default). Some details here... every language other than assembly languages has some amount of runtime. This is Rust's: https://github.com/rust-lang/rust/blob/master/src/libstd/rt.... (as you allude to, many people refer to this amount of runtime as "no runtime" since it's very, very small.) You could also consider some other things as part of a runtime; for example, by default on most plat…
Do you depend on the C runtime as well?
IIRC no; basically the same thing is done though, just not as a dependency.
Re: The reference D compiler is now open source
#243Earlier quoted context omitted.
Say what? The words that come to mind when I think of Java tooling is certainly not "best". More like "Bloated, slow, too-fscking-much-XML"
XML? That's probable Spring. I hate that thing. But Java's tooling for monitoring is crazy good. The benchmarking harness that gives back the assembly code generated for hot code, unmatched on any other non-native language. The editors and how good hinting and auto-complete are, I don't know of another language that integrates so well. Java really raised the bar on tooling and other languages/platforms have really ha…
try spring boot. not a line of xml :)
Re: The reference D compiler is now open source
#244Tremendous effort. Congrats.
Re: The reference D compiler is now open source
#245This is great news. I was using LDC because the DMD backend was proprietary. Thank you Walter, Andrei and whoever made this possible.
We LDC developers of course hope that you will continue to use LDC for all your non-x86 and high-performance needs. ;)
It produces smaller binaries and it has fast compilation times. So yes, I will continue using it on x86 as well.
Re: The reference D compiler is now open source
#246Good news indeed. Switched to D 4 years ago, and have never looked back. I wager that you can sit down a C++/Java/C# veteran, and say write some D code. Here's the manual, have fun. They will with in a few hours be comfortable with the language, and be fairly competent D programmer. Very little FUD surrounding the switching to yet another language with D. D's only issue is that it does not have general adoption, whic…
How well does Dub work? That could be another issue preventing widespread adoption.
I use it for various smaller protects and have no issues with it. Looks good to me.
Re: The reference D compiler is now open source
#247Good news indeed. Switched to D 4 years ago, and have never looked back. I wager that you can sit down a C++/Java/C# veteran, and say write some D code. Here's the manual, have fun. They will with in a few hours be comfortable with the language, and be fairly competent D programmer. Very little FUD surrounding the switching to yet another language with D. D's only issue is that it does not have general adoption, whic…
Interesting. I prefer to write in high-level strongly dynamically typed garbage-collected languages when I can.
But of course I can't always do so and get the performance I want. My approach is generally to prototype in languages like Python, but implement in C89. See: https://www.youtube.com/watch?v=WNTOpl30MIQ . That's 10s of thousands of times faster than our initial prototype and...
We profiled all sorts of things in order to make it that fast. Right down to cache misses, branch mis-prediction, etc, how concurrency on the CPU interacts with I/O.
Re: The reference D compiler is now open source
#248Earlier quoted context omitted.
Java is very simple and has, hands down, the best tooling of any major language out today. That is why it is the most popular. Java isn't my favorite language, but even I can remove my blinders enough to see its strengths.
Say what? The words that come to mind when I think of Java tooling is certainly not "best". More like "Bloated, slow, too-fscking-much-XML"
Name another language + tooling ecosystem where you can do ALL of: * Perform automatic refactoring of a 100k+ LOC project and be confident that absolutely nothing breaks. * Reliable edit and continue in the debugger. * Fast incremental compile times. * Easily pull in third party libraries without messing with include-dirs, link-dirs and whatnot, and automatically get the documentation built in and ready for autocompletion.
I won't list all other things you can do but no other popular language even come close to the tooling of Java or C#. C and C++ has too many different build systems and too much lazy evaluated templates and typecasts for the IDEs to handle well. Python, Ruby, JS, PHP...well they are all dynamic so good luck with fancy IDE features.
Re: The reference D compiler is now open source
#249Earlier quoted context omitted.
Hm, I'm not sure I understand how that's answering my question. Neither of those seem to even define what the "memory safety" notion means for D so I can't compare. And, looking into it further, none of the links from https://dlang.org/spec/memory-safe-d.html define (or compare) what D means by "memory safety"/if it differs to the conventional definition. I guess your original comment was maybe meaning how D enforces…
Memory safety in D is the usual definition - making memory corruption impossible. There's no notion of "borrowing" in D nor any notion of "only one mutable access at a time".
By not having borrowing, do you mean the compiler doesn't stop one from mutating something that has a dependent scoped pointer pointing into it? How does D avoid dangling pointers for that?
Re: The reference D compiler is now open source
#250Earlier quoted context omitted.
Could one write a driver in D?
Here is someone writing a kernel in D: https://github.com/Vild/PowerNex
Another kernel written in D: https://github.com/xomboverlord/xomb/tree/unborn