Compiler scalability. Question inspired by OOM errors seen by Crystal language
I'm referring to this thread about Crystal -- https://lobste.rs/s/dyitr0/its_fun_program_crystal_is_it_scalable Crystal is strongly typed, but overwhelmingly uses type inference, rather than explicit types. Because Crystal aims to be spiritually—and frequently literally—compatible with Ruby, that’s a problem: to accomplish that, Crystal relies on sometimes-nullable types with implicit structure and implicit unions, such that, frequently, the only way to even begin type inference is to load the entire program’s AST into RAM all at once and then start your massive type inference pass. What you’re seeing in this thread is how a “simple” fix to a YAML parser error reporting hit that problem, causing Crystal to use a critical amount too much RAM and OOM. How does D compare in this regard, especially in cases where `auto` storage class specifiers are used liberally throughout the code base?
Re: Weka.IO in the news... but not mentioning Dlang... why?
On Thursday, 3 August 2017 at 20:47:30 UTC, Joakim wrote: Please tell me which enterprise storage company advertises the programming languages they implemented their product in. ;) We hope to have a post on the D blog with info from Weka sometime soon, that should be a good way to get the word out. They do mention it on their jobs page - http://www.weka.io/company/careers/ (see under "Data Path Developer" position).
Re: We gunna be rich
On Saturday, 2 April 2016 at 15:43:53 UTC, Andrei Alexandrescu wrote: D Language Foundation (dlang-20). There are a couple of things that we can do to increase awareness of the Foundation and ways to contribute to it: 1. Link to the foundation website. (do we have one?) 2. On the foundation website/page provide information on how to contribute to the foundation, including but not limited to paying by paypal, and monthly subscriptions. I donate regularly to a charitable foundation this way and in my opinion, the easiest way to give money. 3. Add the link to the Foundation website in the "Community" drop-down menu on the top-navigation.
Re: Autocompletion not working on Xamarin Studio for D
On Friday, 29 January 2016 at 21:05:00 UTC, nbro wrote: Hi! I am trying to write some code in D using Xamarin Studio, but it's not autocompleting the code as I would expect. For example, it does not even gives you autocompletion for libraries, but apparently only for the language's primitives, i.e. keywords, etc. Is this the expected behaviour or is there's something wrong with my settings? Thanks! I wrote this up https://www.btbytes.com/posts/xamarind.html (Xamarin Studio with auto completion etc., for D on Mac) HTH.
Re: Tutorials section on vibed.org
On Monday, 4 January 2016 at 14:31:21 UTC, Sönke Ludwig wrote: Added! The footer of the website still says 2012-2014. Please fix that!
Re: Some feedback on the website.
On Wednesday, 16 December 2015 at 15:02:24 UTC, Guillaume Piolat wrote: On Wednesday, 16 December 2015 at 14:23:54 UTC, Pradeep Gowda wrote: pandoc comes with an unbelievable amount of dependencies. Notably the LaTeX dependency: on Mac the LaTeX distribution is a whopping 2gb download. It seems nice in theory, but in practice pandoc takes things like \newpage (latex code fragments) in their Markdown input. And Markdown already accepts HTML tags! I much prefer DDoc. I use pandoc everyday. This is provably false. You do not need LaTeX to use pandoc. On linux and mac it's a self-contained binary. (I don't use windows, so i don't know). This is how i use it everyday: 1. write markdown and convert to docx for sharing with coworkers. Not a single line of LaTeX 2. just finished writing a paper in IEEE format using just pandoc, which i converted to latex and yet did not have to use a single inline latex command in the main document. 2. write my website/notes in markdown and convert to HTML using hakyll which uses pandoc as a library. No Latex there either.
Re: Some feedback on the website.
On Wednesday, 16 December 2015 at 13:52:05 UTC, Andrei Alexandrescu wrote: On 12/15/15 9:01 PM, deadalnix wrote: On Wednesday, 16 December 2015 at 01:15:45 UTC, Andrei Also, ddoc always appeared to me like a big NIH syndrome. What would you have done instead? While I like ddoc for inlined documentation, I believe that using a easy to learn, and well supported (in IDEs, editors, github, familiar to programmers coming from any other language background) format like Markdown is the way to go. I'm very partial to using pandoc (http://pandoc.org/) as a universal processor for converting markdown to various output formats. Rust used pandoc as their processor till they wrote their own toolchain. (writing markdown parsers appears to be right of passage to some...). Of course, there are multiple implementations of what "markdown", but http://commonmark.org/ is a step in the right direction (created by the author of Pandoc, with others).
Re: Some feedback on the website.
On Tuesday, 15 December 2015 at 07:07:23 UTC, deadalnix wrote: The usual for a programming language goes as follow : - Logo, color as per branding. - Language name, quick blurb about what it is, usually ending with a link to tutorial. - Big fat download button. - Some sample code. The one we have on the front page is way too big. It should be a piece of code that someone with 0 experience in the language can understand. - A menu with quick access to what more experienced users want : stdlib reference, code repository, wiki, forum, language spec, news, this kind of thing. 1. https://www.python.org/ 2. https://www.ruby-lang.org/en/ I think the above two websites do a better job of fitting your requirements than Scala's homepage etc., Let not the dynamic typed nature of the language(s) dissuade you from learning how to build a very popular language **community**.
How does D compare to Go when it comes to C interop?
I read this post about the difficulties of using go/cgo to interface with C code: http://www.cockroachlabs.com/blog/the-cost-and-complexity-of-cgo/ How does D do in comparison? specifically in regards to: 1. Call overhead (CGo is 100 times slower than native Go fn call) 2. Memory management. (I guess D is not immune from having to manage memory for the C functions it calls.. but is there a difference in approach? is it safer in D?) 3. Cgorountes != goroutines (This one may not apply for D) 4. Static builds (how easy/straight-forward is this in D?) 5. Debugging (ease of accessing C parts when debugging)
Re: DConf keynote speaker ideas
On Wednesday, 18 November 2015 at 11:49:33 UTC, Paulo Pinto wrote: On Wednesday, 18 November 2015 at 10:40:47 UTC, Frank Fuente wrote: On Tuesday, 17 November 2015 at 18:47:58 UTC, Andrei Alexandrescu wrote: I'm thinking of inviting a notable industry luminary to deliver a conference keynote. Please reply to this with ideas! -- Andrei Niklaus Wirth... :-) +1 Given his work has been on how to do systems programming with memory safe languages. +1 to Prof Wirth.
try.dlang.org
One of the best ways to get new programmers a flavour of the language is a playground. Examples: - Kotlin - http://try.kotlinlang.org/ - Haskell - https://tryhaskell.org/ - Ceylon - http://try.ceylon-lang.org/# (JVM lang by RedHat) - Go - on the homepage - Ruby - http://tryruby.org/ - Rust - https://play.rust-lang.org/ I know there is a D playground, but I can't remember the URL for the life of me. Is it possible to host or create a CNAME for the current playground at http://try.dlang.org or http://play.dlang.org/ ? It is small things like this that can help newbies "discover" a language and goes a long way in adopting the language.
