Re: [ANN] 3T Software Labs MongoDB tools for D programmers.
On Friday, 18 April 2014 at 03:54:46 UTC, Rikki Cattermole wrote: On Thursday, 17 April 2014 at 15:50:04 UTC, Graham Fawcett wrote: To clarify: you've built these tools in D? Or do the tools provide some kind of D API to MongoDB? Best, Graham Fawcett (not the 3T software Graham; last names are helpful!) They've posted this same thing to a number of different mailing lists in last day or so. Looks valid code however hence I didn't say anything earlier. Yep, a google search for the above text turns up almost identical posts to Clojure, Scala, Haskell, Ruby, and Ruby on Rails forums also. Looking at their website, it appears they're a three-person startup building dev tools, likely written in Java, for noSQL databases like MongoDB, mostly GUI tools to view and modify a database. So it doesn't appear to have anything specific to do with D, just GUI apps that those using MongoDB might find helpful.
Re: Z80 Emulation Engine
On Tuesday, 22 April 2014 at 06:41:58 UTC, Manu via Digitalmars-d-announce wrote: On 22 April 2014 16:29, Jacob Carlborg via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: On 22/04/14 07:57, Manu via Digitalmars-d-announce wrote: Yeah, I understand the license options essentially, but it's more than just the license text, there are license cultures that affect the decision, and people are borderline religious about this sort of thing. I mean, the GPL seems fine to me, but there are many people who see GPL and avoid it like the plague as a matter of superstition or something. I'd prefer to not discourage interest or contribution just because I wrote GPL near my code. Then people invented LGPL and in my experience, this makes some of them feel okay with it, and others still don't wanna go near it. What practical reasons are there to avoid GPL if your software is fundamentally open-source? Ideally, I'd like something like GPL, with the option that I can grant someone an exception to the license upon request. If you want to use some library that is not GPL, or incompatible with GPL. Or the opposite. If someone wants to use your code, but not want to use GPL, but still an open source license. BSD, for example, is much more flexible in these cases. But then you lose the incentive to return contribution back to the original community. I've worked in companies where we take OSS libraries, modified for our needs, and never offer the modifications back to the community. I've done it myself, and it's basically wrong. I am not aware of the license that encourages community contribution, but also doesn't infect your code like the plague? That would be the CDDL, which Sun came up with for OpenSolaris, and other file-based licenses like the MPL, which Mozilla came up with for the open-sourcing of Netscape: https://glassfish.java.net/public/CDDLv1.0.html The CDDL is like the GPL, in that CDD-licensed files have to stay open source when redistributed, but since it applies on a file-by-file basis, doesn't infect the rest of the codebase. Others can compile your CDD-licensed files with their own files that they license differently, as long as they provide the source for your CDDL files, including any modifications they've made to your files. All that said, simple licenses, like the BSD or MIT licenses, are probably best, because they work with almost everything else.
Re: D Breaks on to the TIOBE Top 20 List.
On Friday, 25 April 2014 at 19:51:22 UTC, Adam Wilson wrote: I know we don't place much value in TIOBE and it's brethren. However, I thought that this was a milestone worthy of a note anyways. http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html It's interesting that C++ has been declining for the last decade and especially the last year, with C and Objective-C taking its place at the top for compiled languages. Mobile has driven Objective-C use and will drive the next big language, a good opportunity for D given its efficiency and relative ease of use.
Re: Livestreaming DConf?
On Friday, 9 May 2014 at 19:48:20 UTC, Andrei Alexandrescu wrote: Hi folks, We at Facebook are very excited about the upcoming DConf 2014. In fact, so excited we're considering livestreaming the event for the benefit of the many of us who can't make it to Menlo Park, CA. Livestreaming entails additional costs so we're trying to assess the size of the online audience. Please follow up here and on twitter: https://twitter.com/D_Programming/status/464854296001933312 I demand a telehuman stream: http://youtube.com/watch?v=06tV60K-npw Facebook has one of those, right? ;)
Re: Livestreaming DConf?
On Wednesday, 21 May 2014 at 16:36:02 UTC, Kapps wrote: The stream is currently live at http://www.ustream.tv/channel/dconf-2014 Looking forward to watching the Meyers keynote and most of the other talks today. How did the panel go yesterday? Wish I could have watched it.
Re: Livestreaming DConf?
On Thursday, 22 May 2014 at 10:09:28 UTC, Nordlöw wrote: We at Facebook are very excited about the upcoming DConf 2014. Will the videos be available afterwards at Andreis Youtube stream like last year? I don't think it's certain yet, but here's what the MC James Pearce said in the chat yesterday: to those asking about videos, we'll have them all up on YouTube as promptly as possible (24-48 hours, hopefully) So if they can stick to that, there's no reason to livestream unless you really want to see it first. :)
Re: Dconf 2014 talks - when to be available
On Tuesday, 27 May 2014 at 02:51:51 UTC, Nick B wrote: Hi Can any one advise when we can expect the conference talks (and perhaps the slides as well) to available to download or via Utube ? I saw some of the streamed talks, but would love to view the rest. The MC said initially that they'd have them up in a day or two most likely, then Andrei said he wanted to stagger their release over a couple weeks like he did last time, apparently to stay on top of reddit for awhile. I'm sure they'll post something in the announcements forum eventually.
Re: My D book is now officially coming soon
On Tuesday, 27 May 2014 at 10:00:01 UTC, Szymon Gatner wrote: On Tuesday, 6 May 2014 at 19:58:10 UTC, Nick Sabalausky wrote: On 5/6/2014 9:11 AM, Adam D. Ruppe wrote: On Tuesday, 6 May 2014 at 12:40:48 UTC, Szymon Gatner wrote: Any way to see the TOC? Hmm, not on the website yet but here it is. [snip] Sounds awesome! Jus got mail from PacktPub: D Cookbook is now released: http://www.packtpub.com/discover-advantages-of-programming-in-d-cookbook/book Congratz! Thanks for the update. I have the pdf loaded up now, looking forward to going through it.
Re: Interview at Lang.NEXT
On Wednesday, 4 June 2014 at 06:19:05 UTC, Andrei Alexandrescu wrote: http://www.reddit.com/r/programming/comments/27911b/conversation_with_andrei_alexandrescu_all_things/ wtf, the Mid Quality video is 1280x720 resolution HD video, guess they think every programmer has a super-fast internet connection. ;) The mp4 for Android/iPhone is a bandwidth-friendly 640x360 resolution.
Re: Lang.NEXT panel
On Wednesday, 4 June 2014 at 06:13:39 UTC, Andrei Alexandrescu wrote: Of possible interest. http://www.reddit.com/r/programming/comments/278twt/panel_systems_programming_in_2014_and_beyond/ Andrei Nice panel. Not much really new there, but gives an idea of what you language designers are thinking about and who you are. I was never much interested in Go, but after seeing Pike for the first time, was a bit more interested in his language. Funny to see Bjarne swinging his legs on the high stool like a kid. :)
Re: Chuck Allison's talk is up
On Thursday, 5 June 2014 at 21:15:40 UTC, Olivier Henley wrote: On Thursday, 5 June 2014 at 16:33:49 UTC, Andrei Alexandrescu wrote: https://news.ycombinator.com/newest http://www.reddit.com/r/programming/comments/27e5d7/dconf_day_1_talk_3_a_real_d_in_programming/ https://www.facebook.com/dlang.org/posts/860528800627469 https://twitter.com/D_Programming/status/474587858812948480 Andrei Hi, I would love to spam my colleges here at Ubisoft Montreal with DConf 2014 talks ... but UStream is blocked studio wide. Is there any plans to mirror the talks somewhere else? We can stream from Vimeo and Youtube. Dicebot has been uploading them on youtube: http://www.youtube.com/channel/UCaYYN56VR7Z4SSoO7ws0-jA/videos I use his channel, as every web video player I've ever used blows in its own special way but youtube is the least bad.
Re: DConf 2014 Day 1 Talk 4: Inside the Regular Expressions in D by Dmitry Olshansky
On Tuesday, 10 June 2014 at 17:19:42 UTC, Dicebot wrote: On Tuesday, 10 June 2014 at 15:37:11 UTC, Andrei Alexandrescu wrote: Watch, discuss, upvote! https://news.ycombinator.com/newest https://twitter.com/D_Programming/status/476386465166135296 https://www.facebook.com/dlang.org/posts/863635576983458 http://www.reddit.com/r/programming/comments/27sjxf/dconf_2014_day_1_talk_4_inside_the_regular/ Andrei http://youtu.be/hkaOciiP11c Great talk, just finished watching the youtube upload. I zoned out during the livestream, as it was late over here and I was falling asleep during this fairly technical talk, but now that I'm awake, enjoyed going through it. Never knew how regular expression engines are implemented, good introduction to the topic and how D made your approach easier or harder. A model talk for DConf, particularly given the great results on the regex-dna benchmark.
Re: dmd front end now switched to Boost license
On Saturday, 14 June 2014 at 06:07:08 UTC, Nick Sabalausky wrote: I doubt it. First, it's the backend that's not technically OSI, frontend was (apparently) GPL. Second, I can't imagine any Linux distro rejecting GPL - they'd have to boot the kernel and core utils, too. Actually, the frontend was dual-licensed under the Artistic license and the GPL and dmd binaries were provided under the former, as the GPL doesn't allow linking against a non-GPL backend. The GPL alternative was likely for gdc to link the frontend against the GPL'd gcc backend.
Re: dmd front end now switched to Boost license
On Saturday, 14 June 2014 at 17:07:58 UTC, Leandro Lucarella wrote: No free license restrict commercial use. What using boost enable is only proprietary use, i.e. changing the DMD FE and keeping the changes private, even if you distribute the binary with the compiled DMDFE. As I said before, there are licenses that allow anyone linking your code to non-free code, but you still have to provide the source code of the modified DMDFE if you distribute it. An example is LGPL. The frontend was dual-licensed under the Artistic license, which also allows such proprietary use, so nothing has really changed. Rather than having two licenses, the Artistic license to allow linking against the proprietary dmd backend and the GPL to allow linking against the gcc backend, the dmd frontend now has a single Boost license that allows both, since the Boost license is considered GPL-compatible. From the standpoint of what the frontend's license allows, not much has changed, but the simplicity and clarity of the Boost license puts the frontend on firmer footing. I realize you prefer the LGPL, to force others to contribute back to the frontend if they modify and distribute it, but the Boost license is much simpler and as Walter points out, proprietary use can help D's adoption.
Re: dmd front end now switched to Boost license
On Sunday, 15 June 2014 at 01:08:00 UTC, Leandro Lucarella wrote: Joakim, el 14 de June a las 19:31 me escribiste: The frontend was dual-licensed under the Artistic license, which also allows such proprietary use, so nothing has really changed. Mmm, even when is true that the Artistic license is a bit more permissive than the GPL in some aspects, I think is hardly suitable for doing serious proprietary software (that you intent to sell). From the artistic license that was distributed by DMD: You may not charge a fee for this Package itself. However, you may distribute this Package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Package as a product of your own. Is a bit hairy, I don't think any companies would want to do proprietary tools using the artistic license :) https://github.com/D-Programming-Language/dmd/blob/083271a415716cf3e35321f91826397d91c0a731/src/artistic.txt I was referring to this clause from the Artistic license: 4. You may distribute the programs of this Package in object code or executable form, provided that you do at least ONE of the following: a) distribute a Standard Version of the executables and library files, together with instructions (in the manual page or equivalent) on where to get the Standard Version. So you could have always distributed a modified, closed ldc with the frontend under the Artistic license- it would have to be ldc as the dmd backend is proprietary- as long as you also provided an unmodified ldc along with it. I don't think the part of the Artistic license you excerpted would apply to such a modified program, but even if the advertising part applied, I doubt any commercial user would care. Usually those who take your code _don't want_ to advertise where they got it from. ;) I realize you prefer the LGPL, to force others to contribute back to the frontend if they modify and distribute it, but the Boost license is much simpler and as Walter points out, proprietary use can help D's adoption. Again, I think from the practical point of view is the same. If you use boost license and tons of proprietary tools come out CHANGING the DMDFE and not contributing back, then the D community might get a boost because the have better tools but they are missing the contributions, so is hard to tell if the balance would be positive or negative. If they don't change the DMDFE (or contribute back the changes), then using boost or LGPL are the same, because it doesn't matter. Having better-quality paid tools would be a big boost, whether they released their patches or not. You point out that commercial users could always link against a LGPL frontend as a library and put their proprietary modifications in their own separate library, but that can be very inconvenient, depending on the feature. Also, I've pointed out a new model on this forum before, where someone could release a closed, paid D compiler but have a contract with their customers that all source code for a particular binary will be released within a year or two. This way, you get the best of both worlds, revenue from closed-source patches and the patches are open-sourced eventually. Such mixed models or other experimentation is possible under the freedom of more permissive licenses like Boost, but is usually much harder to pull off with the LGPL, as you'd be forced to separate all proprietary code from the LGPL frontend.
Re: DConf Day 1 Talk 6: Case Studies in Simplifying Code with Compile-Time Reflection by Atila Neves
On Monday, 16 June 2014 at 17:26:51 UTC, Andrei Alexandrescu wrote: https://news.ycombinator.com/newest https://www.facebook.com/dlang.org/posts/867399893273693 https://twitter.com/D_Programming/status/478588866321203200 http://www.reddit.com/r/programming/comments/28am0x/case_studies_in_simplifying_code_with_compiletime/ Great talk, missed this on the livestream as I went to sleep. Between Dmitry's regex talk and this one, good to see talks demonstrating how they actually used D to build something interesting and how D-specific features helped them build it better. These talks are much better than the more abstract talks, hopefully we see more of them next year.
Re: DConf Day 1 Talk 6: Case Studies in Simplifying Code with Compile-Time Reflection by Atila Neves
On Tuesday, 17 June 2014 at 17:10:16 UTC, Mengu wrote: On Monday, 16 June 2014 at 22:14:01 UTC, Adam D. Ruppe wrote: The reddit response this year hasn't been particularly impressive it seems to me compared to last year :( r/programming and hn is all about rust and go. on hn many d posts are invisible after some time. i believe mods are taking action there. if we want their attention, we should compare d with others; we should benchmark d and brag about the results etc. other than that, people are not paying attention to D and it's beautiful features. I don't know why people bother with those silly sites, which I don't read at all unless they're linked here. None of these benchmarks or other links matter. Nobody paid attention to ruby for a decade, until David Hansson built rails with it. I have seen over and over again that nobody has the ability to reason about an idea or tool like this. You have to build something better with it, something they want, then they'll all flock to use or copy it. You want to show how great D is, build something great with it. Nothing else matters. and also the genius idea to post each talk seperately instead of having a nice talks page on dconf.org and providing a link for that. i'd understand the keynotes but for the rest of the talks this is / was not a good idea. Don't you know that it's better to maintain a steady stream of publicity for D on sites full of people who always dismiss it, rather than making the talks available immediately to the people who actually use D and want to watch them? endSarcasm(); I don't mind it as much, because I'm not bingeing on the talks and spreading out watching them instead, but it'd be nice to see the talks I missed on the livestream and want to watch now, rather than at some indeterminate date in the future.
Re: DConf Day 1 Talk 6: Case Studies in Simplifying Code with Compile-Time Reflection by Atila Neves
On Thursday, 19 June 2014 at 03:23:15 UTC, Saurabh Das wrote: I find it impossible to even find the posts on HN. Within a few hours of them being posted by Andrei, they are buried 4-5 pages deep in the 'new' section with very few upvotes. This search for DConf finds 5 of the 7 talks posted so far: https://hn.algolia.com/#!/story/past_month/prefix/0/dconf None have any comments and most have practically no votes, so that explains why you didn't find them on there. Two other talks were not labeled DConf for some reason, but only the Meyers talk, which wasn't about D, had any comments or much votes: https://hn.algolia.com/#!/story/past_month/prefix/0/meyers Last year I saw most of the talks (DConf13) on HN and r/programming. This year I find them only on this forum because the talks are not staying up on HN or r/p front pages for much time. There has been some suggestion that they are being moderated down. The Reddit postings get about a hundred votes, not sure if that's much on their site, as I don't use it. If you're aware of this forum, not sure why you're going there anyway. On Thursday, 19 June 2014 at 11:04:25 UTC, Jacob Carlborg wrote: My connection is specified to 10 Mbps. But it depends on how large the files are. Most of the files from DConf are under around 350MB in HD quality. On the other hand, Andrei's talk from LangNext 2014 is 1.3 GB and 48 minutes long while the talk by Bjarne is 2.8 GB and 68 minutes long. There are also 740 and 65.8 MB encodings of Andrei's talk that are perfectly usable. I should know, as I downloaded the latter. Same for Bjarne's talk, which I haven't downloaded.
Re: DConf Day 1 Talk 6: Case Studies in Simplifying Code with Compile-Time Reflection by Atila Neves
On Thursday, 19 June 2014 at 11:04:25 UTC, Jacob Carlborg wrote: My connection is specified to 10 Mbps. But it depends on how large the files are. Most of the files from DConf are under around 350MB in HD quality. On the other hand, Andrei's talk from LangNext 2014 is 1.3 GB and 48 minutes long while the talk by Bjarne is 2.8 GB and 68 minutes long. There are also 740 and 65.8 MB encodings of Andrei's talk that are perfectly usable. I should know, as I downloaded the latter. Same for Bjarne's talk, which I haven't downloaded. Sorry, I just noticed that you were only talking about HD quality. I don't know where you're getting the 350 MB figure, as all the HD recordings on archive.org are about 6-800 GB, but yeah, file sizes will vary based on the type of HD resolution and encoding used. I wouldn't call any hour-long video encoded into 350 MB HD quality though, as it's likely so compressed as to look muddy.
Re: DConf Day 1 Talk 6: Case Studies in Simplifying Code with Compile-Time Reflection by Atila Neves
On Thursday, 19 June 2014 at 12:16:20 UTC, Joakim wrote: Sorry, I just noticed that you were only talking about HD quality. I don't know where you're getting the 350 MB figure, as all the HD recordings on archive.org are about 6-800 GB, but 600 to 800 MB, not GB. :)
Re: DConf 2014 Keynote: High Performance Code Using D by Walter Bright
On Tuesday, 15 July 2014 at 16:20:34 UTC, Andrei Alexandrescu wrote: http://www.reddit.com/r/programming/comments/2aruaf/dconf_2014_keynote_high_performance_code_using_d/ https://www.facebook.com/dlang.org/posts/885322668148082 https://twitter.com/D_Programming/status/489081312297635840 Will there be a lower-res video of this talk than 1.3 GBs, as there was for other talks?
Re: DConf 2014: Declarative Programming in D by Mihails Strasuns
On Tuesday, 22 July 2014 at 15:39:39 UTC, Andrei Alexandrescu wrote: Vote https://twitter.com/D_Programming/status/491608304171634688 https://www.facebook.com/dlang.org/posts/889263017754047 http://www.reddit.com/r/programming/comments/2bei5x/dconf_2014_declarative_programming_in_d_by/ No download link for this one?
Re: DConf 2014 Day 3 Talk 2: Real-Time Big Data in D by Don Clugston
Just finished watching this talk for the second time, as I was distracted by IRC when watching the livestream. Good talk, though not as great as last year's from Don, which was the best one given at DConf 2013. This quote struck me when watching live, from the 40:35 mark of the video, and really needs to go up on the front page of dlang.org: Our infrastructure costs are 4X lower than the rest of our industry. I can't think of a better marketing line than that.
Re: Miscelaneous D tool updates
On Thursday, 7 August 2014 at 23:36:59 UTC, Brian Schott wrote: Tags and DUB support for all of this will happen when I get around to it. (Or when you get around to it and make a pull request) libdparse: https://github.com/Hackerpilot/libdparse * The lexer/parser/ast code for D written in D is no longer a part of the dscanner project. (This also means that DCD no longer includes a static analysis tool as a submodule. Yay.) dscanner: https://github.com/Hackerpilot/Dscanner * Static analysis check for declaring methods or variables named init or otherwise overriding built-in properties. (Why does the compiler let you do this in the first place?) * Tweaks to the opEquals, opCmp, toHash checks. * Static analysis checks are now configurable through an ini file. * Lots of random bug fixes. dcd: https://github.com/Hackerpilot/DCD * Autocomplete for selective imports. * Autocomplete for auto variables. (Finally!) * Show call tips for compiler-generated struct constructors. * Autocomple global-scoped symbols more accurately. * Several updates to editor integration scripts (Mostly EMACS) * Lots of bug fixes harbored: https://github.com/economicmodeling/harbored * Documentation - docs - harbor? * Documentation generator that is independent of DMD and its JSON output. * Example output: http://economicmodeling.github.io/containers/index.html * Lots of bug fixes. libddoc: https://github.com/economicmodeling/libddoc * D implementation of the DDoc macro system * Lots of bug fixes Thanks for all the nice work. :) I was just looking at using libdparse yesterday to help me with some phobos cleanup (https://github.com/D-Programming-Language/phobos/pull/2337) and I want to eventually try using it with dstep to separate out Glibc declarations in druntime.
Re: DMD v2.066.0-rc1
On Thursday, 7 August 2014 at 19:15:00 UTC, Jacob Carlborg wrote: On 2014-08-07 19:15, Dicebot wrote: And here I also mean that all other Windows builds of compilers / interpreters I have used / tried passed that simple sanity test. Some may require complicated setup to do complicated things but hello world is always just that simple. Microsoft seems to be the only company who can afford doing things like that with users and expect them to suck it _ On OS X both work well. You can either just press the button or use the command line, assuming you have installed the command line tools. This is kind of why I picked up a Powerbook a decade ago, to be able to use the command-line and Unix and still have multimedia work well (linux/BSD audio/video have made major strides since then). Then, among other reasons, I found out that Apple is using that money for stuff like this, and that's the first and last Apple product I ever bought: http://www.cnet.com/news/us-patent-office-rejects-apple-autocomplete-patent-used-against-samsung/
Re: Miscelaneous D tool updates
On Thursday, 7 August 2014 at 23:36:59 UTC, Brian Schott wrote: Tags and DUB support for all of this will happen when I get around to it. (Or when you get around to it and make a pull request) libdparse: https://github.com/Hackerpilot/libdparse * The lexer/parser/ast code for D written in D is no longer a part of the dscanner project. (This also means that DCD no longer includes a static analysis tool as a submodule. Yay.) dscanner: https://github.com/Hackerpilot/Dscanner * Static analysis check for declaring methods or variables named init or otherwise overriding built-in properties. (Why does the compiler let you do this in the first place?) * Tweaks to the opEquals, opCmp, toHash checks. * Static analysis checks are now configurable through an ini file. * Lots of random bug fixes. dcd: https://github.com/Hackerpilot/DCD * Autocomplete for selective imports. * Autocomplete for auto variables. (Finally!) * Show call tips for compiler-generated struct constructors. * Autocomple global-scoped symbols more accurately. * Several updates to editor integration scripts (Mostly EMACS) * Lots of bug fixes harbored: https://github.com/economicmodeling/harbored * Documentation - docs - harbor? * Documentation generator that is independent of DMD and its JSON output. * Example output: http://economicmodeling.github.io/containers/index.html * Lots of bug fixes. libddoc: https://github.com/economicmodeling/libddoc * D implementation of the DDoc macro system * Lots of bug fixes Oh, you might get more eyes on these projects if you put more of them on dub: http://code.dlang.org/publish I know I looked for libdparse on there before cloning it myself.
Re: COFF support for Win32 merged
On Sunday, 17 August 2014 at 13:01:07 UTC, bearophile wrote: ketmar: are you sure that you have latest git then? yes, i know that this is very silly question, but sometimes... ;-) OK, -m32mscoff works (probably I was using a wrongly written switch), but I don't see it listed among the other compiler switches. You will need to use his unmerged branches of druntime and phobos also: https://github.com/rainers/druntime/tree/coff32 https://github.com/rainers/phobos/tree/coff32 Hopefully those get merged next, as I think this could be a big feature for the 2.067 release. Nice work, Rainer.
Re: DMD v2.067.0-b1
On Friday, 29 August 2014 at 02:10:48 UTC, Manu via Digitalmars-d-announce wrote: Does this 2.67 release contain COFF32, and the new package fix? Yes to COFF32, though it's still undocumented in the help at the moment: https://github.com/D-Programming-Language/dmd/commits/2.067 No to the package fix as of now, though maybe it'll be merged later.
Re: Digger 1.0
On Monday, 22 September 2014 at 13:23:33 UTC, simendsjo wrote: My guess is the average for developers is ~8GB. 2GB RAM is really not enough for pretty much anything these days - the browser alone easily chews 3-4GB on moderate use. You have to admit that this is ridiculous. I updated to the 64-bit Chrome on Windows when it came out and it is a huge memory hog. Web browsers have grown out of control. On Monday, 22 September 2014 at 18:59:13 UTC, Vladimir Panteleev wrote: Firefox requires 4GB of memory to build. Chromium requires 8GB of memory to build. This is not a requirement for Chromium, merely a recommendation for faster builds. I regularly built Chromium for FreeBSD with 2 GBs of RAM up till a couple years ago. Perhaps it has gotten much more bloated since or maybe just on Windows, but phobos shouldn't be in the same class. If you want to work on big projects, you WILL need a decent computer. I think 4GB for a modern programming language's implementation is not an unreasonable requirement, even if it could be brought down in the future. Especially considering that you can't even buy a new laptop today with less than 4GB of RAM, and 3GB is becoming the norm for smartphones. I'd say it's unreasonable from a technical standpoint, maybe not that much from an affordability standpoint, which is what you're pointing out. My guess is the real problem is optlink on Windows, in which case I recommend that Nick try out the new 32-bit MSVC toolchain support, if he can't use the existing 64-bit Windows MSVC integration. I regularly build git HEAD of dmd/druntime/phobos in a linux VM with 512 MB of RAM and about the same amount of swap and have never had a problem. It's only when compiling the unit tests that I have to start increasing the allocated RAM.
Re: Programming in D book, draft of the first print edition and eBook formats
On Wednesday, 26 November 2014 at 23:16:11 UTC, Ali Çehreli wrote: On 11/26/2014 11:35 AM, Ali Çehreli wrote: I wonder whether Smashwords would allow me to also provide the book for free on my site? Found the answer to that question: 6c. Free Copies. As administrator of your work, Author may use the Smashwords platform to distribute complimentary copies of the work, or personally email free files to people, even when you are generally charging a fee. However, Smashwords files cannot be mass-distributed via download at blogs, websites or other retailers outside the Smashwords network. https://www.smashwords.com/about/tos I think you are misinterpreting that clause. I had never heard of Smashwords before, so I just looked at their site and their TOS. What they do is take your book in doc format and generate ebook formats that can be sold online and to other book retailers, as detailed in clause 5 of their TOS: 5. Formats of Digital Conversions. Author shall submit their Work as a Microsoft Word .doc file. Smashwords shall utilize its proprietary Meatgrinder technology to convert the book into multiple ebook formats, and publish the work for use in sampling, distributing and selling the work. The author/publisher is not authorized to independently sell or distribute Smashwords-generated file conversions outside of the Smashwords site or Smashwords distribution network without first receiving written permission from Smashwords (in other words, you cannot use Smashwords as a free file conversion service so you can sell the files elsewhere). You acknowledge that if you violate this requirement, you may forfeit any accrued earnings at Smashwords, and your account may be deleted without notification. I believe both clauses simply says you cannot distribute their converted ebook files: note that 6c says you cannot mass distribute Smashwords files, not the Work, which is how they refer to your book itself. They also say on their site that you are free to use other distributors and retain copyright over your work. Few would fault you for not wanting to give away free copies if you're selling the book, but I don't think Smashwords has a say in the matter.
Re: Programming in D book, decent ebook versions
On Monday, 15 December 2014 at 10:25:18 UTC, Ali Çehreli wrote: - Removed the unrelated Turkish menu from the English pages - Improved the ebook formats - Removed the download page and linked the ebook versions directly from the main page instead I consider these beta quality: http://ddili.org/ders/d.en/ (I am not sure why, but you may have to refresh the page in your browser.) I know that the format needs further improvements but please let me know if there are serious issues like some text not showing up at all. (Preferably, respond in this thread to avoid duplicate reports.) Ali Thanks for making these available, just been reading some of the web chapters and learned from them. Do you take donations for the electronic versions, as I have no interest in print? I'd like to send you a piece of bitcoin if you have a bitcoin address.
Re: 2D game engine written in D is in progress
On Friday, 19 December 2014 at 01:00:30 UTC, Kiith-Sa wrote: It's not a dethroner for the Unreal Engine 4, but I try my best to get it into work. It's current name is VDP engine, but if you can come up with a better name I might change it. I still haven't decided to make it open or closed source (if it'll be ever used by any game that makes profit, I'd like to get some share from it). Noticed there's a question at Reddit (a bot submits all announce threads to Reddit): https://www.reddit.com/r/d_language/comments/2pm2ba/2d_game_engine_written_in_d_is_in_progress/ Since others are mentioning commercial open-source models and that guy asked about using a more liberal license, let me mention another newer model. Develop most of the codebase in the open under a permissive license like MIT/BSD/Apache but keep some of the features or patches closed, particularly those that would most interest potential commercial licensees. This is the model used by Android, the most successful open source project ever, where AOSP is released as OSS then the hardware and smartphone vendors add their proprietary blobs and patches before selling the entire software bundle. It's probably the best model if you want to be open source, get wide usage, and still have good commercial possibilities.
Re: 2D game engine written in D is in progress
On Friday, 19 December 2014 at 11:35:54 UTC, ketmar via Digitalmars-d-announce wrote: On Fri, 19 Dec 2014 07:22:13 + Joakim via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: This is the model used by Android, the most successful open source project ever i can assure you that stupid policy with separating features has nothing to do with android popularity. I can assure you that it's _the_ reason it took off so much. If the Android project had insisted on pure open source, the hardware and smartphone vendors would have laughed at them and used Windows Mobile or LiMo or one of the myriad other alternatives at the time. It's why Samsung has their own proprietary multi-window implementation for Android and Amazon and Xiaomi forked Android and released their own proprietary versions. Commercial vendors want to differentiate with their own proprietary features, but AOSP provides a common OSS platform on which they can work together. This model has been extraordinarily successful for AOSP, as it has led to a billion smartphones running some version of Android and capable of running most common apps, albeit with some fragmentation too.
Re: 2D game engine written in D is in progress
On Friday, 19 December 2014 at 15:05:05 UTC, ketmar via Digitalmars-d-announce wrote: On Fri, 19 Dec 2014 14:46:33 + Joakim via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: On Friday, 19 December 2014 at 11:35:54 UTC, ketmar via Digitalmars-d-announce wrote: On Fri, 19 Dec 2014 07:22:13 + Joakim via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: This is the model used by Android, the most successful open source project ever i can assure you that stupid policy with separating features has nothing to do with android popularity. I can assure you that it's _the_ reason it took off so much. If the Android project had insisted on pure open source, the hardware and smartphone vendors would have laughed at them and used Windows Mobile or LiMo or one of the myriad other alternatives at the time. It's why Samsung has their own proprietary multi-window implementation for Android and Amazon and Xiaomi forked Android and released their own proprietary versions. Commercial vendors want to differentiate with their own proprietary features, but AOSP provides a common OSS platform on which they can work together. This model has been extraordinarily successful for AOSP, as it has led to a billion smartphones running some version of Android and capable of running most common apps, albeit with some fragmentation too. what you described here is a matter of licensing (BSDL vs GPL), not having some closed-source patches. Which of those OSS licenses are the proprietary features and blobs I listed offered under? None, and the choice of license is critical because you cannot offer closed-source patches under the viral GPL, ie it is the BSDL/Apache permissive licenses that make this winning mixed model possible. If your point is that AOSP is released as pure open source, no Android phone is sold running pure AOSP, including Nexus devices because of binary blob drivers. Without the proprietary add-ons, AOSP would be unusable.
Re: 2D game engine written in D is in progress
On Friday, 19 December 2014 at 17:21:43 UTC, ketmar via Digitalmars-d-announce wrote: it is still unusable. i don't care what problems samsung or other oem have, as i still got the closed proprietary system. Not exactly, as the flourishing Android ROM scene shows. While many people also jailbreak their Apple iDevices, it's not quite so easy to install your own ROM on them. That comes from much of the source being open for Android, though certainly not all of it. what google really has with their open-sourceness is a bunch of people that works as additional coders and testers for free. and alot of hype like hey, android is open! it's cool! use android! bullshit. What's wrong with reusing open-source work that has already been done in other contexts, through all the open source projects that are integrated into Android? Those who worked for free did so because they wanted to, either because they got paid to do so at Red Hat or IBM and released their work for free or because they enjoyed doing it. Nothing wrong with Android building on existing OSS. As for the hype, the source google releases, AOSP, is completely open. You're right that it's then closed up by all the hardware vendors, but I doubt you'll find one who hypes that it's open source. So you seem to be conflating the two. On Friday, 19 December 2014 at 18:50:14 UTC, ketmar via Digitalmars-d-announce wrote: On Fri, 19 Dec 2014 18:23:59 + Kagamin via Digitalmars-d-announce Well, those people want to do that, so why not? i have nothing against that, everyone is free to do what he want. what i'm against is declaring android open project. it's proprietary project with partially opened source. I'd say open source project with proprietary additions. :) But AOSP is not particularly open in how it's developed, as google pretty much works on it on their own and then puts out OSS code dumps a couple times a year. That's not a true open source process, where you do everything in the open and continuously take outside patches, as D does, but they do pull in patches from the several outside OSS projects they build on. In any case, AOSP releases all their source under OSS licenses, not sure what more you want.
Re: 2D game engine written in D is in progress
On Saturday, 20 December 2014 at 11:57:49 UTC, ketmar via Digitalmars-d-announce wrote: i still can't understand how buying closed proprietary crap supports FOSS. and android is still proprietary system with opened source, not FOSS. I'll tell you how. First off, all the external OSS projects that AOSP builds on, whether the linux kernel or gpsd or gcc, get much more usage and patches because they're being commercially used. Android has had their linux kernel patches merged back upstream into the mainline linux kernel. Once companies saw Android taking off, they started a non-profit called Linaro to develop the linux/ARM OSS stack, mostly for Android but also for regular desktop distros, and share resources with each other, employing several dozen paid developers who only put out OSS work, which benefits everyone, ie both OSS projects and commercial vendors: http://en.wikipedia.org/wiki/Linaro If they hadn't had success with Android commercially, there's no way they do that. I keep making this point to you, that pure OSS has never and will never do well, that it can only succeed in a mixed fashion. Linux, by the way, is not a real FOSS for me. not until it will adopt GPLv3, which will never happen. What will never happen is the GPLv3 ever taking off.
Re: 2D game engine written in D is in progress
On Saturday, 20 December 2014 at 15:48:59 UTC, ketmar via Digitalmars-d-announce wrote: On Sat, 20 Dec 2014 15:02:57 + Joakim via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: I'll tell you how. First off, all the external OSS projects that AOSP builds on, whether the linux kernel or gpsd or gcc, get much more usage and patches because they're being commercially used. can i see some statistics? i hear that argument (it got more patches) almost every time, but nobody can give any proofs. i can't see how x86 code generator got better due to android, for example. Why would we collect stats: what difference does it make if an OSS project is 10% commercially developed or 20%? There are patches being sent upstream that would not be sent otherwise, that's all that matters. As for the x86 code generator, Android has been available on x86 for years now: it's possible there were some patches sent back for that. ah, didn't i told you that i don't care about arm at all? somehow people telling me about how android boosts something are sure that i do or should care about that something. so i feel that i can do the same and argue that i don't care. Android has had their linux kernel patches merged back upstream into the mainline linux kernel. that patches are of no use for me. why should i be excited? Once companies saw Android taking off, they started a non-profit called Linaro to develop the linux/ARM OSS stack, mostly for Android but also for regular desktop distros, and share resources with each other, employing several dozen paid developers who only put out OSS work, which benefits everyone, ie both OSS projects and commercial vendors: you did understand what i want to say, did you? ;-) I keep making this point to you, that pure OSS has never and will never do well, that it can only succeed in a mixed fashion. why should i care if OSS will do well? i don't even know what that means. it is *already* well for me and suit my needs. making another proprietary crap do well changes nothing. more than that, it makes people forget about F is FOSS. so i'm not interested in success of OSS projects. You may not care about any of these patches for your own use, because you don't use ARM or whatever, but you certainly seem to care about FOSS doing well. Well, the only reason FOSS suits your needs and has any usage today is precisely because commercial vendors contributed greatly to its development, whether IBM and Red Hat's contributions stemming from their consulting/support model or the Android vendors' support paid for by their mixed model. You may resent the fact that it means some non-OSS software still exists out there and is doing well, but FOSS would be dead without it. If that were the case, there would be almost no F, just try doing anything with Windows Mobile or Blackberry OS. Your F may be less than a hypothetical pure FOSS world, but that world will never exist. Linux, by the way, is not a real FOSS for me. not until it will adopt GPLv3, which will never happen. What will never happen is the GPLv3 ever taking off. yes, corporate bussiness will fight for it's right to do tivoisation and to hide the code till the end. that's why i'm not trying hard to help non-GPLv3 projects, only occasional patches here and there if a given issue is annoying me. What you should worry about more is that not only has the GPLv3 not taken off, but the GPLv2 is also in retreat, with more and more projects choosing permissive licenses these days. The viral licensing approach of the GPLv2/v3 is increasingly dying off.
Re: 2D game engine written in D is in progress
On Saturday, 20 December 2014 at 18:49:06 UTC, ketmar via Digitalmars-d-announce wrote: On Sat, 20 Dec 2014 17:12:46 + Joakim via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: Why would we collect stats: what difference does it make if an OSS project is 10% commercially developed or 20%? 'cause i want to know what much more means. 1? 10? 100? 1000? 1? sure, 1 is much more than zero, as 1 is not nothing. but how much? There are patches being sent upstream that would not be sent otherwise, that's all that matters. nope. when i see much more, i want to know how much is that much. That still doesn't answer the question of why anyone would spend time collecting stats when it's pointless to quantify anyway. If it's 20%, is it all of a sudden worth it for you? 10%? 30%? You may not care about any of these patches for your own use, because you don't use ARM or whatever, but you certainly seem to care about FOSS doing well. i still can't understand what doing well means. what i see is that with corporations comes a rise of permissive licenses, and i can't see that as good thing. I've explained in detail what doing well means: these hobbyist OSS projects, whether the linux kernel or gcc or whatever you prefer, would be unusable for any real work without significant commercial involvement over the years. Not sure what's difficult to understand about that. It's not just corporations using permissive licenses. Many more individuals choose a permissive license for their personal projects these days, as opposed to emulating linux and choosing the GPL by default like they did in the past. Well, the only reason FOSS suits your needs and has any usage today is precisely because commercial vendors contributed greatly to its development i don't think so. OpenBSD suits too. it just happens that i didn't have an access to *BSD at the time, so i took Linux. yet i'm seriously thinking about dropping Linux, as with all those commercial support is suits me lesser and lesser. You think OpenBSD did not also benefit from commercial help? What you should worry about more is that not only has the GPLv3 not taken off, but the GPLv2 is also in retreat, with more and more projects choosing permissive licenses these days. The viral licensing approach of the GPLv2/v3 is increasingly dying off. that's why i'm against OSS bs. the success of Linux is tied with it's viral license. just look at FreeBSD: it started earlier, it has alot more to offer when Linux was just a child, yet it's permissive license leads to companies took FreeBSD and doing closed forks (juniper, for example). The viral GPL may have helped linux initially, when it was mostly consulting/support companies like IBM and Red Hat using open source, so the viral aspect of forcing them to release source pushed linux ahead of BSD. But now that companies are more used to open source and actually releasing products based on open source, like Android or Juniper's OS or llvm, they're releasing source for permissive licenses also and products make a lot more money than consulting/support, ie Samsung and Apple make a ton more money off Android/iOS than Red Hat makes off OS support contracts. So the writing is on the wall: by hitching themselves to a better commercial model, permissive licenses and mixed models are slowly killing off the GPL. I wrote about some of this and suggested a new mixed model almost five years ago: http://www.phoronix.com/scan.php?page=articleitem=sprewell_licensing What I predicted has basically come true with Android's enormous success using their mixed model, though I think my time-limited mixed model is ultimately the endgame.
Re: 2D game engine written in D is in progress
On Sunday, 21 December 2014 at 15:44:05 UTC, ketmar via Digitalmars-d-announce wrote: On Sun, 21 Dec 2014 07:54:53 + Joakim via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: That still doesn't answer the question of why anyone would spend time collecting stats when it's pointless to quantify anyway. If it's 20%, is it all of a sudden worth it for you? 10%? 30%? i believe that when someone says much more, he didn't take the numbers from /dev/urandom, and he already has very impressive stats. why else he would do comparisons? he must base his opinion on some numbers. or... or i just can say that with my contributions Linux got many more patches, so prise me -- and everyone will believe? i bet not, i will be asked for at least numerical proofs. so i won't buy bs about many more patches with android without numbers at least. and then i will ask to show *what* parts was changed, just to make sure that this is not a useless android-specific crap. But nobody cares to prove it to you. I made an assertion that patches were upstreamed, all the raw data is out there to show that. If you're unwilling to go look for it, doesn't bother me. see, m$ recently commits alot of patches, yet it's still very hard to say that microsoft help develops Linux. what those patches do is compatibility with their proprietary hyperv. useless crap. yet numbers still looks impressive. Except that Android obviously has nothing so narrow as Hyper-V to which it's isolated to. I've explained in detail what doing well means: these hobbyist OSS projects, whether the linux kernel or gcc or whatever you prefer, would be unusable for any real work without significant commercial involvement over the years. Not sure what's difficult to understand about that. you didn't give any proofs. moreover, you simply lying, as gcc, for example, was perfectly usable long before commercial vendors starts sending patches. and i can assure you that Linux and GCC are not the only [F]OSS projects which are very usable for real work (i don't know what real work and unreal work is, but hell with it). What would be proofs of being made much more viable by commercial involvement? As for linux and gcc not being the only mature projects, every other one you can think of very likely also benefited greatly from commercial investment. It's not just corporations using permissive licenses. Many more individuals choose a permissive license for their personal projects these days, as opposed to emulating linux and choosing the GPL by default like they did in the past. ah, so you saying that they specifically don't want to emulate Linux success? i knew that! Yep, they'd rather be _much_ more successful, like Android or llvm. :D from my POV the only sane reason why author can choose permissive license is to steal my code. so he can take my contribution, use it in proprietary closed-source version and make money from it. If he's the author, how is he stealing your code? Google runs a patched linux kernel on a million servers and mostly doesn't release their patches, did they steal code from all linux kernel contributors? i see nothing bad from making money from the product... until that product uses my code in the way that i can't get free access to product sources AND i can't pass those sources around freely. oh, i mean the code i wrote without payment. You always have access to your code, just not necessarily to code others wrote on top of your code. and i prefer GPLv3 over GPLv2 as GPLv3 closes tivoisation hole. Yes, you mentioned that before. You think OpenBSD did not also benefit from commercial help? if you'll go this way you'll found that nobody using hand-made computers for running FOSS software, so... i want numbers. again. and proofs that without such help the project will be in unusable state now. i don't know how you can make such proofs, but that's not me who claims that without commercial proof FOSS is not ready for real work, so it's not me who must give proofs. i'm telling you that... let's take emacs and GCC: emacs, GCC and GDB was perfectly usable before corporations started to take FOSS movement seriously. I see, you want proofs, but don't know how you can make such proofs. Awfully convenient to demand proof and not define what you'll accept as proof. As I said before, all the data is out there, you're free to prove it to yourself. you know what... the whole UNIX story started as guerilla OS. only when UNIX becames successfull, AT/T begins to invest money in it. and, btw, did that completely wrong, effectively killed UNIX. This is commonly the case, doesn't matter if it's OSS or not. The viral GPL may have helped linux initially, when it was mostly consulting/support companies like IBM and Red Hat using open source, so the viral aspect of forcing them to release source pushed linux ahead of BSD. But now that companies are more
Re: 2D game engine written in D is in progress
Sigh, I did ask you some questions, which you've answered with a couple more questions, so I'll give you one last response. On Sunday, 21 December 2014 at 18:52:00 UTC, ketmar via Digitalmars-d-announce wrote: On Sun, 21 Dec 2014 18:24:12 + Joakim via Digitalmars-d-announce digitalmars-d-announce@puremagic.com wrote: But nobody cares to prove it to you. I made an assertion that patches were upstreamed, all the raw data is out there to show that. If you're unwilling to go look for it, doesn't bother me. do you see how discussion without proofs has no sense at all? No, I see that you asking me to quantify something and then dodging the question of why it should be quantified, ie when I asked you what your magical threshold of relevance is, makes no sense at all. :) In any case, whatever you think that would prove, I have not offered to prove it to you. The raw data is out there: if you want certain statistics extracted from that data that only matter to you, it's up to you to collect them. ah, so you saying that they specifically don't want to emulate Linux success? i knew that! Yep, they'd rather be _much_ more successful, like Android or llvm. :D individial projects. android. llvm. you just divided by zero. Whatever that means. Both have become much more successful in recent years by using mostly permissive licenses. from my POV the only sane reason why author can choose permissive license is to steal my code. so he can take my contribution, use it in proprietary closed-source version and make money from it. If he's the author, how is he stealing your code? i obviously meant he accepted my patches, and then... If you sent him patches, he's not stealing your code. No wonder you left that part out, but your whole story made no sense without it. Google runs a patched linux kernel on a million servers and mostly doesn't release their patches, did they steal code from all linux kernel contributors? does google selling that servers with patched kernel? i was talking about selling the software product (as a standalone product or with accompanying hardware). using the product in-house to built some system whose output then sold is ok. I see, so it's okay if google takes outside patches for their kernel, creates a search engine on top of it, and then sells access to the advertising on that search engine without releasing any kernel source, but not okay if they sell those same servers with that patched kernel and search engine bundled without including any kernel source. This is the classic idiocy of GPL zealots, where they imagine they are purists for freedom then twist themselves in knots when it's pointed out the GPL actually doesn't accomplish that in any meaningful way, since most GPL code actually runs on the server. Of course, some then go use the AGPL, but that's a small minority. i see nothing bad from making money from the product... until that product uses my code in the way that i can't get free access to product sources AND i can't pass those sources around freely. oh, i mean the code i wrote without payment. You always have access to your code, just not necessarily to code others wrote on top of your code. and that is wrong. either not use my code at all, or give me all the code that is using my code, with rights to redistribute. Funny how you don't make the same demands of google or some other cloud vendor who runs your code. I guess distribution must be magical somehow, ie it's okay if they run your code on the server, just not on the desktop. I see, you want proofs, but don't know how you can make such proofs. Awfully convenient to demand proof and not define what you'll accept as proof. that wasn't me who created such situation. As I said before, all the data is out there, you're free to prove it to yourself. so you have no proofs. q.e.d. Lol, _you_ created the impossible situation of demanding proof you couldn't define, nobody is going to prove it to you. you know what... the whole UNIX story started as guerilla OS. only when UNIX becames successfull, AT/T begins to invest money in it. and, btw, did that completely wrong, effectively killed UNIX. This is commonly the case, doesn't matter if it's OSS or not. and that kills the whole your argument about OSS software can't be grown to use in 'real work' without corporate support. I was only agreeing that anything successful usually starts as guerilla and that when a large company starts investing a lot in it, they often make mistakes. No idea how you draw the conclusion from that that OSS can't be made more viable through corporate support, especially given that that has been shown invariably to be the case. why do you think that i should care how much money corporations will get? i know that most people don't give a shit about their freedom and would sell it for a dime. I already explained why: because
Re: 2015 H1 Vision
On Monday, 2 February 2015 at 05:17:40 UTC, Jerry Morrison wrote: On Monday, 2 February 2015 at 03:50:10 UTC, Joakim wrote: C and C++ are very general-purpose, but they can still be considered as a niche of performance languages. What's wrong with D aiming for that niche? Most uses of C C++ that haven't migrated to well-supported garbage-collected languages by now are those that cannot work with a garbage collector and/or are heavily tied to an existing C++ code base. Offering something much better for that niche/domain would be a great opportunity, and not a small niche. The point is to focus efforts for one release on fully addressing what that domain requires. The next release can focus on another domain. And so on. Well, given the current focus on @nogc and C++ integration, it appears that niche has been chosen, and you and Ola get your wish.
Re: Binutils 2.25 Released - New D demangling support
On Wednesday, 14 January 2015 at 14:42:09 UTC, Jacob Carlborg wrote: On 2015-01-14 09:46, Iain Buclaw via Digitalmars-d-announce wrote: I can't comment on that. Maybe via Macports? Otherwise if BSD have their own linker, someone will need to go and get friendly with the developers up their toolchain. Right, forgot about that the toolchain is BSD based. I was curious what they're actually using these days, so I looked it up. Appears to be some APS-licensed Mach-O linker they wrote themselves in C++: http://opensource.apple.com/tarballs/ld64/
Re: dfmt 0.1.0
On Friday, 20 February 2015 at 02:21:01 UTC, Brian Schott wrote: dfmt is a D source code formatting tool. https://github.com/Hackerpilot/dfmt/ https://github.com/Hackerpilot/dfmt/releases/tag/v0.1.0 Thanks, you should list some of the formatting changes it makes in the README.
Re: dfmt 0.1.0
On Friday, 20 February 2015 at 05:53:32 UTC, Brian Schott wrote: On Friday, 20 February 2015 at 05:23:45 UTC, Joakim wrote: On Friday, 20 February 2015 at 02:21:01 UTC, Brian Schott wrote: dfmt is a D source code formatting tool. https://github.com/Hackerpilot/dfmt/ https://github.com/Hackerpilot/dfmt/releases/tag/v0.1.0 Thanks, you should list some of the formatting changes it makes in the README. It doesn't do formatting changes. It wipes out the formatting during lexing and builds it up from scratch. The only thing that gets preserved is that it will look at line numbers on comments and try to keep them in roughly the same place. (For example, // comments that are on the end of a line instead of on the next line) Well, you should indicate what that new formatting is in the README, so potential users know what to expect without having to run it first.
Re: Silicon Valley D Users' first meeting
On Thursday, 22 January 2015 at 06:47:13 UTC, Ali Çehreli wrote: Thursday, January 22, 2015, 6pm Many people you know from the forums will be there. Andrei is giving a presentation as well: http://www.meetup.com/D-Lang-Sillicon-Valley/events/219413448/ Will there be a video or writeup for those of us who aren't in the area?
Re: 2015 H1 Vision
On Sunday, 1 February 2015 at 01:17:41 UTC, Andrei Alexandrescu wrote: Hello, Walter and I have been mulling for a while on a vision for the first six months of 2015. http://wiki.dlang.org/Vision/2015H1 This is stuff we consider important for D going forward and plan to work actively on. We encourage the D community to focus contributions along the same lines. We intentionally kept the document short and high-level as opposed to discussing tactical details. Such discussions are encouraged in the appropriate forums. Nice work, D needed some direction like this. I thought one oversight was no mention of ddmd, which seems to have gone into limbo over the last year. According to Daniel, it's pretty much done but is just waiting on Brad to add some support in the auto-tester, for 9 months now: http://forum.dlang.org/post/m8bt6s$1s86$1...@digitalmars.com Moving the dmd frontend to D would help encourage contribution, one of the explicit goals in the vision statement, and would help keep the C++ support up to date, as the backends will stay C++. I wish there had been some mention of mobile. Recent news was that 1 billion Android smartphones were sold last year: that dwarfs the 316 million PCs sold, a number that keeps declining. That doesn't even include the two hundred million tablets sold last year. Right now, there's two people working on Android support and one person on iOS support. Even Android has moved to Ahead-Of-Time compilation with Lollipop. Mobile is a giant opportunity for native languages, one D cannot afford to miss.
Re: 2015 H1 Vision
On Monday, 2 February 2015 at 01:43:02 UTC, Jerry Morrison wrote: On Monday, 2 February 2015 at 00:58:53 UTC, Andrei Alexandrescu wrote: On 2/1/15 3:52 PM, Jerry Morrison wrote: The other big thing missing from the Vision doc is picking a niche, That may as well come later - or not at all. We don't think it is now time to commit to a particular niche. OK. Just keep in mind that if you want to “cross the chasm” from visionaries to pragmatics, it requires meeting 100% of the needs of at least one niche (whether that's real-time, bare-metal, desktop apps, web servers, data analysis, mobile apps, or whatever). It does no good to meet 90% of the needs of many niches. https://blogs.saphana.com/2013/02/04/the-end-of-the-beginning-sap-hana-has-crossed-the-chasm/ What was the niche C++ aimed for a couple decades back, C with objects? D is aiming for the same niche as C and C++, a general-purpose, native-compiled language that allows you to extract almost-maximal performance while still being relatively easy to use, at least compared to the alternatives. Perhaps focusing on a smaller niche first would allow D to gain a larger following quicker, but that might box it in from becoming more general-purpose later, as early decisions optimize for that niche and might be tough to undo. Go certainly seems stuck in a niche now, though I'm not sure how much of that is because they just don't want to add more general-purpose features like generics, ie they're happy in their niche. C and C++ are very general-purpose, but they can still be considered as a niche of performance languages. What's wrong with D aiming for that niche?
Re: DMD's lexer available on code.dlang.org
On Tuesday, 6 January 2015 at 14:38:21 UTC, Dicebot wrote: It will be really cool when same package will be reused by DMD itself :P I believe ddmd has passed all tests on most platforms for a long time now, so there is nothing stopping those building from source from using ddmd now. :)
Re: DConf 2015 Call for Submissions is now open
On Tuesday, 13 January 2015 at 07:30:22 UTC, Brad Anderson wrote: On Tuesday, 13 January 2015 at 00:22:33 UTC, Mike wrote: I have a suggestion for any compiler implementers: How about a talk on how to get started hacking the compiler. Something that may lower the entry barrier and encourage participation. Some random thoughts: * General structure of the compiler * Walk through the data flow: Lexer - parser - AST - backend * How to add a new compiler switch (e.g. -fnotypeinfo) * How to add a new attribute (e.g. @notypeinfo) * What's your workflow for debugging the compiler? * Pick a bug, and fix it (Live demo) * Overview of CTFE and how it's implemented * (I'm sure you can think of more) I realize there's documentation on the wiki, and some of this was discussed briefly at DConf2013, but there's more that can be done to make it accessible and interesting. Mike Sounds like a good subject for Daniel Murphy to talk about. He spent a good hour explaining to me how a linker works in the Aloft bar after most people had retired (thanks for that, Daniel) and he certainly knows dmd extremely well. I second the vote for Daniel, as he seems fairly opinionated online and might make for a good speaker. I didn't even know if he goes to DConf, as he's never given a talk at the recent ones. He could talk about dmdfe's structure and the magicport/ddmd effort would also make for good material. Do we know if the DConf 2015 talks will be recorded? Walter said earlier in this thread that they're arranging something, though he's not sure about live-streaming yet.
Re: Gary Willoughby: Why Go's design is a disservice to intelligent programmers
On Monday, 30 March 2015 at 00:20:11 UTC, Laeeth Isharc wrote: https://www.quora.com/Why-didnt-D-language-become-mainstream-comparing-to-Golang fwiw Nice, well-written answer, enjoyed reading it.
Re: dsq-1: open-source software synthesizer
On Sunday, 29 March 2015 at 17:30:39 UTC, Foo wrote: On Sunday, 29 March 2015 at 17:24:53 UTC, Joakim wrote: Hmm, this sounds like it might be a bug or design flaw. debug is supposed to provide an escape hatch from even pure functions: I don't see why it wouldn't provide the same for @nogc and nothrow. At the very least, we should have a @nogc/nothrow alternative to writefln to allow such simple debugging. import core.stdc.stdio : printf; I'm aware of that option and thought of mentioning it, but it is inconvenient when dealing with D strings.
Re: This Week in D, issue 6 - DConf, ddmd, dmd beta, return ref, install tip
On Monday, 23 February 2015 at 01:14:29 UTC, Adam D. Ruppe wrote: Here's the newest This Week in D, the big news being ddmd and the dmd beta. http://arsdnet.net/this-week-in-d/feb-22.html The tip of this week has to do with installation: as a Slackware user, the new download page made me feel left out, but the zip still works the same, so I decided to call that out so people who want to try the new version will know too. Also on Reddit, hopefully we can get some more dconf attention: http://www.reddit.com/r/programming/comments/2wtkgz/this_week_in_d_6_dconf_ddmd_dmd_beta_return_ref/ I think you should note that ddmd only ports the dmd frontend to D, not any of the backends. The way you describe the port now might mislead some into thinking the entire compiler has been ported.
Re: Monday is last day for DConf 2015 registrations
On Monday, 18 May 2015 at 02:20:02 UTC, Andrei Alexandrescu wrote: On 5/17/15 6:56 PM, Walter Bright wrote: Because we have to give the head count to caterer on Tuesday. http://dconf.org/2015/registration.html Time to stop procrastinating! See you there! Also, to registrants and speakers: please make sure you made your hotel arrangements, hopefully via the discounted link on the conference page! -- Andrei For those of us not going, any update on the live streaming setup? That was a great way for those not there to take part last time, even posing after-talk questions and conversing with those there over irc. :)
Re: forum.dlang.org, version 2 (BETA)
On Thursday, 4 June 2015 at 15:04:05 UTC, Vladimir Panteleev wrote: http://beta.forum.dlang.org/ Many major and minor improvements. Man, I think we found the ultimate bikeshed topic for D, with 113 replies in one day. :) There is a bug in the currently deployed DFeed forum with Chrome on Android tablets, where it's necessary to click on an external link twice before it will load, which seems to be fixed in this beta. Hopefully, the fix is intentional and it won't recur.
Re: Walter, Brian, and Daniel's DConf 2015 talks are up
On Friday, 19 June 2015 at 22:47:03 UTC, Brad Anderson wrote: Walter: https://www.youtube.com/watch?v=znjesAXEEqw Brian: https://www.youtube.com/watch?v=FmFyB9e7edw Daniel: https://www.youtube.com/watch?v=5daHGXSetXk I've only just started watching but the editing seems to be well done so thanks to UVU for that. Three really good talks to kick off Dconf. The videos are done well, thanks to UVU for providing them.
Re: DConf 2015 has ended. See you in Berlin at DConf 2016!
On Saturday, 30 May 2015 at 05:08:18 UTC, Andrei Alexandrescu wrote: Why not DConf is carried out twice a year!? :) E.g. in May and in November. It would be really great. Please think about it! Hmm, there may be a little disconnect here. Organizing conferences costs money, which currently comes from Walter and my pocket. Whilst I understand how it's awfully exciting to enjoy quality content from the comfort of one's device, we need more attendees before more conferences to make the checkbooks balance. Besides, there is no substitute for being there, as I'm sure all of this year's DConf participants may attest. I've been thinking that D needs more globally-available talks like this throughout the year. One way to do it would be to schedule monthly livestreams of a D developer in front of his webcam, like the Jai programming language guy was doing. I could help organize something like this, but the problem isn't getting it up and running but having people actually give talks. I can't even get people to answer my emails for email interviews about D (with the exception of Mihails, who's been very prompt). No doubt everybody is very busy and D is a hobby that's easily pushed aside, but online talks could keep the conference momentum going throughout the year.
Re: This Week in D #23 - Interview with Dmitry Olshansky, dmd beta, std.experimental.color
On Thursday, 2 July 2015 at 10:26:36 UTC, Dmitry Olshansky wrote: On 29-Jun-2015 06:46, Adam D. Ruppe wrote: http://arsdnet.net/this-week-in-d/jun-28.html I should have probably said on the day one - AMA. P.S. Thanks to Joakim for editing my stream of consciousness into this tidy text ;) Can someone stick this interview link on reddit? I think others would find it interesting.
Re: D-Day for DMD is today!
On Sunday, 23 August 2015 at 05:17:33 UTC, Walter Bright wrote: https://github.com/D-Programming-Language/dmd/pull/4923 We have made the switch from C++ DMD to D DMD! Many, many thanks to Daniel Murphy for slaving away for 2.5 years to make this happen. More thanks to Martin Nowak for helping shepherd it through the final stages, and to several others who have pitched in on this. This is a HUGE milestone for us. Much work remains to be done, such as rebasing existing dmd pull requests. Thanks in advance for the submitters who'll be doing that. I hope you aren't too unhappy about the extra work - it's in a good cause! Great work, thanks to Daniel and others who helped out, can't wait to use ddmd and see all the changes that come with it in the next couple releases. Can we look forward to a complete ddmd, ie backend and everything ported to D too, anytime soon?
Re: Seattle D meetup
On Sunday, 2 August 2015 at 22:53:00 UTC, Walter Bright wrote: Seeing the threads on London, Silicon Valley and Berlin meetups, is there any interest for a Seattle one? btw, the Silicon Valley Meetup doesn't show up on this nice little worldwide map of Dlang Meetups on their website: http://dpl.meetup.com/ Maybe Ali or some other organizer needs to add the appropriate tag to their Meetup so it will? Would be cool if we could have a nicely populated Meetup map to show off on dlang.org somewhere.
Re: Case study on ranges and lazy evaluation
On Monday, 20 July 2015 at 17:26:31 UTC, Matt Kline wrote: With the general push to make more of Phobos use lazily evaluated ranges, Walter's DConf talk, and even C++ moving towards ranges (https://www.youtube.com/watch?v=uXBcwcF3ln4), I wrote a small article with a case study examining their merits. http://bitbashing.io/be-lazy-use-ranges.html The target audience is largely those unfamiliar with ranges (and to a certain extent, D), but I welcome any and all feedback. Nice, well-written piece, says something about reddit that it's not popular on there.
Re: LDC 0.16.0 has been released!
On Sunday, 25 October 2015 at 03:22:39 UTC, Joakim wrote: On Saturday, 24 October 2015 at 15:40:41 UTC, Jack Stouffer wrote: That's surprising given that many were worried that switching to ddmd would slow compilation speeds down by at least 30%. Also, this does not seem to be using any of ldc's optimization flags. Well, all three of those are ddmd: the only difference is whether ddmd is compiled by dmd, gdc, or ldc. The 30% measurement was based on comparing the previously completely C++ dmd with ddmd: http://forum.dlang.org/post/55c9f77b.8050...@dawg.eu Whoops, posted before I was done writing. The Travis CI run combines the time spent compiling ddmd, time spent compiling the druntime/phobos tests, and then running the tests. The original 30% comparison was only for time spent compiling a D codebase, like phobos or vibe.d. It's possible ldc takes longer to compile ddmd, but then the resulting ddmd takes less time to compile phobos. That would have to be separated out. It's also possible the backend is not the issue and the D frontend itself is slower than the C++ frontend, in which case using ldc to compile ddmd won't make a difference.
Re: LDC 0.16.0 has been released!
On Saturday, 24 October 2015 at 15:40:41 UTC, Jack Stouffer wrote: On Saturday, 24 October 2015 at 03:11:30 UTC, Joakim wrote: The associated travis CI run that finally went green with ldc 0.16.0 beta 2 took about as long as the other D compilers, so performance of ldc-compiled ddmd seems comparable: https://travis-ci.org/D-Programming-Language/dmd/builds/85017266 That's surprising given that many were worried that switching to ddmd would slow compilation speeds down by at least 30%. Also, this does not seem to be using any of ldc's optimization flags. Well, all three of those are ddmd: the only difference is whether ddmd is compiled by dmd, gdc, or ldc. The 30% measurement was based on comparing the previously completely C++ dmd with ddmd: http://forum.dlang.org/post/55c9f77b.8050...@dawg.eu
Re: LDC 0.16.0 has been released!
On Friday, 23 October 2015 at 20:10:17 UTC, Jack Stouffer wrote: On Thursday, 22 October 2015 at 19:00:07 UTC, Kai Nacke wrote: Hi everyone, LDC 0.16.0, the LLVM-based D compiler, is available for download! Congratulations! Has anyone on the LDC team done any benchmarks on how much faster ddmd is when compiled with LDC? ldc was recently added to the list of compilers that test ddmd continuously on travis CI: https://github.com/D-Programming-Language/dmd/pull/5025 The associated travis CI run that finally went green with ldc 0.16.0 beta 2 took about as long as the other D compilers, so performance of ldc-compiled ddmd seems comparable: https://travis-ci.org/D-Programming-Language/dmd/builds/85017266
Re: Fastest JSON parser in the world is a D project
On Thursday, 22 October 2015 at 20:54:01 UTC, Marco Leise wrote: Am Thu, 22 Oct 2015 06:10:56 -0700 schrieb Walter Bright: On 10/21/2015 3:40 PM, Laeeth Isharc wrote: > Have you thought about writing up your experience with > writing fast json? A bit like Walter's Dr Dobbs's article > on wielding a profiler to speed up dmd. Yes, Marco, please. This would make an awesome article, and we need articles like that! You've already got this: https://github.com/kostya/benchmarks/pull/46#issuecomment-147932489 so most of it is already written. There is at least one hurdle. I don't have a place to publish articles, no personal blog or site I contribute articles to and I don't feel like creating a one-shot one right now. :) The main D forum is as good a place as any. Just start a thread there.
Re: Calypso progress report (+ updated MingW64 build)
On Wednesday, 21 October 2015 at 23:40:15 UTC, Elie Morisse wrote: It's been a while since the last update, so here's a quick one before making the jump to LDC 0.16. You should write a blog post explaining what you have done so far and what remains to be done, then submit it to the usual link sites. I bet a lot of people would be interested in reading about this approach.
Re: "Programming in D" ebook is available for purchase
On Wednesday, 28 October 2015 at 08:01:29 UTC, Ali Çehreli wrote: Although the book will always be free[1], many of you have expressed a need to pay without having to buy the paper version. The ebook versions are now available at Gumroad: https://gum.co/PinD The price is the very affordable $0+ ;) and you can pay with credit card number or through PayPal. Ali [1] http://ddili.org/ders/d.en/ Do you have a bitcoin address I can use instead?
Re: D compiler daily downloads at an all-time high
On Monday, 16 November 2015 at 15:20:51 UTC, Andrei Alexandrescu wrote: http://erdani.com/d/downloads.daily.png There have been 1677 dmd downloads per day (net after discounting Travis CI) on average over the past 28 days (i.e. four weeks ending Sunday, November 15). That's a new all-times high ever since we started measuring on January 02, 2013. The previous record, 1630 average daily downloads, was established in the four weeks ending November 17, 2014. Probably has to do with your recent quora response becoming one of the top 30 most upvoted reddit links from the last year, plus one of the most commented on: https://www.reddit.com/r/programming/top/?sort=top=year=25=t3_2sn74k
Re: Atila's article on Reddit: "Rust impressions from a C++/D programmer, part 1"
On Monday, 16 November 2015 at 00:40:33 UTC, The Old One wrote: With the World turning to IOT, and most startups having an embedded system as at least a part of their offering, even old languages should take this seriously. Not everybody actually fathoms the size of this tsunami, or the disruption it'll bring. It's like the 80's when mini-computer corporations did't notice micro manufacturers. From their perspective, the tide turned overnight. And now it's us. Except IoT hasn't gone anywhere yet and I'm skeptical that it ever will. I thought the same of smartwatches and their sales so far haven't been great. Who really wants an internet-enabled toaster or refrigerator? I know I don't. You make a good point that D needs to aim for the larger embedded market, by providing better support for running stripped down. You'll notice that the vision statement says that we're looking for people to spearhead such an effort: http://wiki.dlang.org/Vision/2015H2 But I don't think IoT really matters, better to try and hit the actually existing embedded market.
Re: D 2.068.2 test runner for Android ARM, please test and report results from your Android device
On Thursday, 12 November 2015 at 02:21:08 UTC, Fer22f wrote: On Sunday, 1 November 2015 at 09:50:16 UTC, Joakim wrote: https://github.com/joakim-noah/android/releases/tag/runners You can install a test runner app or run a command-line binary. This is from a Moto Maxx (it's a Droid Maxx rebranded), Android v5.0.2 and Snapdragon 805. These tests hang: std.socket std.stdio Everything else went smoothly. I'm not an expertise android developer so I don't know how to get stacktraces from logcat, all I oculd get was the verbose of the test program (using "adb logcat test_runner:V *:S"). Thanks, there shouldn't be any stacktraces unless the app crashes. When it hangs, as it does in those two modules, some C function from bionic usually just doesn't return and you have to close the app eventually. I wasn't expecting any crashes from this apk, only mentioned it because you never know what might happen on new hardware. ;)
D 2.068.2 test runner for Android ARM, please test and report results from your Android device
I'm happy to announce test runners for Android ARM, which will run most tests from druntime and phobos on your Android device: https://github.com/joakim-noah/android/releases/tag/runners You can install a test runner app or run a command-line binary. Please report your results in this thread in the ldc forum, which requires no registration, with the info and format requested there: http://forum.dlang.org/thread/bafrkjfwmoyriyhmq...@forum.dlang.org You can build ldc from source yourself using the patches linked. I will soon make available a cross-compiler build of ldc on linux/x86 and write up the process of building everything, including the test runner apk, on the wiki. I'll also port some more sample OpenGL apps from the Android NDK. Help with all of the above and fixing the remaining issues would be appreciated. You may notice that the patches are not very large, other than Kai's patch for cross-compiling 64-bit reals. That's because of ongoing ARM work for years by Johannes, Kai, Martin, David, and others, the awesomeness of ldc and llvm, and the Android/x86 patches I've upstreamed over the last couple years. I'd like to help get some D/OpenGL app ported to Android and submitted to the Play Store. Please let me know if you have any such project I can help with.
Re: D 2.068.2 test runner for Android ARM, please test and report results from your Android device
On Sunday, 1 November 2015 at 18:41:26 UTC, Martin Nowak wrote: On 11/01/2015 10:50 AM, Joakim wrote: http://forum.dlang.org/thread/bafrkjfwmoyriyhmq...@forum.dlang.org Nice works for me as well (Galaxy S3 on cm-12.1 (5.1.1)). Would be nice to run this as automated test on an Android Emulator. Yes, would be good to integrate this with CI, I was thinking of trying to get ldc for Android going on Travis: http://docs.travis-ci.com/user/languages/android/
Re: iOS LDC 0.16.1 (2.067.1) binaries available
Great, your last announcement was linked in reddit comments about the 2.069 release, when asked about iOS support. On Thursday, 5 November 2015 at 08:05:39 UTC, Dan Olson wrote: Just noticed that tvOS and watchOS are now present in LLVM, so I think support for these could be added to LDC soon too. WatchOS and tvOS are bitcode-only, right? Have they specified their bitcode format yet or is it just whatever clang spits out? I thought there were problems with that because of bitcode format changes over time and other platform issues, that the PNaCl guys had to work on solving. I wonder if you'll have similar issues with the bitcode ldc spits out.
Re: iOS LDC 0.16.1 (2.067.1) binaries available
On Thursday, 5 November 2015 at 15:45:35 UTC, Dan Olson wrote: tvOS is essentially iOS and doesn't require bitcode (yet) like watchOS. I am looking at adding it soon because Xcode 7 enables it by default. I just looked it up, their official docs say bitcode is required for both tvOS and watchOS: https://developer.apple.com/library/watchos/documentation/IDEs/Conceptual/AppDistributionGuide/AppThinning/AppThinning.html I don't totally appreciate all the possible bitcode problems, but one of the suggestions that apps can be updated for new CPUs without rebuilding doesn't make sense. The IR/bitcode from clang for arm64 and armv7 is different. They would have to make all the ABIs identical first or have LLVM backend do more of the ABI work. Yeah, that's what google did with PNaCl, stabilize on one format and make it as architecture-agnostic as possible: http://www.phoronix.com/scan.php?page=news_item=MTQyNTE Maybe Apple doesn't really care about running on different architectures, but I wonder what they're doing to handle changes in the llvm bitcode format over time.
Re: LDC 0.17.0 alpha cross-compiler for Android/ARM, D 2.068.2
On Saturday, 7 November 2015 at 12:23:18 UTC, Andre Polykanine wrote: Hello Joakim, JvDda> http://wiki.dlang.org/Build_LDC_for_Android#Build_a_sample_OpenGL_Android_app_ported_to_D No way to do this on Windows, am I right? Not using this cross-compiler build for a linux/x86 host, no. However, you can build llvm/ldc from source on Windows using the patches earlier in that wiki page and in principle, it should work on Windows too. I haven't tried it, so I can't say for sure, but I think it'd work.
Re: iOS LDC 0.16.1 (2.067.1) binaries available
On Saturday, 7 November 2015 at 20:34:06 UTC, Dan Olson wrote: Joakimwrites: Hmm, that's strange, this commit didn't fix the 64-bit issues for you? I believe it fixed them for me on Android/ARM: https://github.com/ldc-developers/phobos/commit/9d1b49578ffa4b2e848159cfe5afe80b5e4c26eb Yes, but there is still one case not working for both iOS armv7 and arm64 in 0.16.1. It is only off by one ulp so I'll make a PR for that. https://github.com/ldc-developers/phobos/blob/ldc/std/internal/math/gammafunction.d#L540 OK, somehow doesn't assert for me on Android/ARMv7. And then this new stuff in 2.068 is failing in various places. https://github.com/ldc-developers/phobos/commit/9b86eebed53c800a58dfa7e065dcb9e11cdae5c5 Yeah, that's the new function I mentioned earlier. Initializing the constant maxY ends up calling log2 through CTFE, the intrinsic for which doesn't exist in Kai's longdouble2 branch. I was going to look at writing one, feel free to beat me to it. ;) Or if you added that log2 to your branch already, could be other issues too, haven't gotten that far.
Re: iOS LDC 0.16.1 (2.067.1) binaries available
On Saturday, 7 November 2015 at 19:20:02 UTC, Dan Olson wrote: Dan Olsonwrites: Joakim writes: btw, std.internal.math.gammafunction hasn't given me a problem since 2.067.1, the Win64 guys fixed it. 2.068 added a function that needs a CTFE-able 64-bit log2, but other than that, it just works now. You may want to revert your patch for that module and try it. Thanks for the tip, I'll check it out. It is the one remaining bad boy. Still bad :-( Hmm, that's strange, this commit didn't fix the 64-bit issues for you? I believe it fixed them for me on Android/ARM: https://github.com/ldc-developers/phobos/commit/9d1b49578ffa4b2e848159cfe5afe80b5e4c26eb
Re: LDC 0.17.0 alpha cross-compiler for Android/ARM, D 2.068.2
On Friday, 6 November 2015 at 20:10:36 UTC, Jakob Ovrum wrote: Thanks for the thorough instructions! LLVM is rather massive and I'd prefer to avoid building it if I can, so I downloaded the pre-built LDC binary from the release page. However, the binary is 32-bit and depends on libconfig, which doesn't appear to have a multilib package in Arch Linux. There are of course ways around this, but would it be possible to release a pre-built 64-bit binary? OK, I've rebuilt ldc with one small tweak: I've added the current directory to its rpath and bundled my system libconfig along with it, which is what the official ldc release does too. You shouldn't need libconfig installed by your system anymore. Please download the updated release of the Android/ARM cross-compiler and let me know if it works for you. Note that this linux/x86 ldc cross-compiler also depends on the ncurses and zlib shared libraries, so you'll have to install those if you want to run it.
Re: Release D 2.069.0
On Wednesday, 4 November 2015 at 01:50:38 UTC, Martin Nowak wrote: Glad to announce D 2.069.0. http://dlang.org/download.html http://downloads.dlang.org/releases/2.x/2.069.0/ This is the first release with a self-hosted dmd compiler and comes with even more rangified phobos functions, std.experimental.allocator, and many other improvements. See the changelog for more details. http://dlang.org/changelog/2.069.0.html -Martin Whoo, ddmd is out! Congrats to Daniel and everyone else involved.
Re: D 2.068.2 test runner for Android ARM, please test and report results from your Android device
On Sunday, 1 November 2015 at 09:50:16 UTC, Joakim wrote: You can build ldc from source yourself using the patches linked. I will soon make available a cross-compiler build of ldc on linux/x86 and write up the process of building everything, including the test runner apk, on the wiki. I've started writing the build process up on the wiki. You can build the ldc cross-compiler, a small command-line program, and the command-line test runner yourself: http://wiki.dlang.org/Build_LDC_for_Android
Re: Atrium - 3D game written in D
On Friday, 6 November 2015 at 09:04:05 UTC, Timur Gafarov wrote: Atrium (code name) is a work-in-progress science fiction game with physics based puzzles (gravity effects, force fields, etc) akin to Portal or Inverto. The game is fully written in D, it uses custom graphics engine based on OpenGL and SDL. Physics engine is also written from scratch. Source code: https://github.com/gecko0307/atrium IndieDB page: http://www.indiedb.com/games/atrium A precompiled demo for Windows: https://www.dropbox.com/s/qh8gai2n94qe8jj/atrium-testbuild-051115.zip?dl=0 Nice, graphics and physics look impressive in the demo video. If you ever want to try and get it on Android, let me know if I can help. I'll have a build of the ldc cross-compiler up for download in an hour, will be announcing it soon.
Re: iOS LDC 0.16.1 (2.067.1) binaries available
On Thursday, 5 November 2015 at 07:44:48 UTC, Dan Olson wrote: This is another set of binaries and universal libs for the experimental LDC iOS cross-compiler. It is now based on LDC 0.16.1 (2.067.1) and LLVM 3.6.2. https://github.com/smolt/ldc-iphone-dev/releases/tag/ios-0.16.1-151104 btw, std.internal.math.gammafunction hasn't given me a problem since 2.067.1, the Win64 guys fixed it. 2.068 added a function that needs a CTFE-able 64-bit log2, but other than that, it just works now. You may want to revert your patch for that module and try it.
LDC 0.17.0 alpha cross-compiler for Android/ARM, D 2.068.2
https://github.com/joakim-noah/android/releases/tag/runners You will need a linux/x86 host and the Android NDK, optionally the SDK if you want to create a GUI app. A slightly older build was used to create the test runners from earlier this week. You can use this cross-compiler to build command-line or GUI apps, by following the instructions from these sections in the wiki: http://wiki.dlang.org/Build_LDC_for_Android#Build_a_command-line_executable http://wiki.dlang.org/Build_LDC_for_Android#Build_a_sample_OpenGL_Android_app_ported_to_D Make sure to set the NDK environment variable to the path of your Android NDK. There are also instructions to build the cross-compiler and test runner from source yourself: http://wiki.dlang.org/Build_LDC_for_Android
Re: LDC 0.17.0 alpha cross-compiler for Android/ARM, D 2.068.2
On Friday, 6 November 2015 at 20:10:36 UTC, Jakob Ovrum wrote: On Friday, 6 November 2015 at 11:56:35 UTC, Joakim wrote: [...] Thanks for the thorough instructions! LLVM is rather massive and I'd prefer to avoid building it if I can, so I downloaded the pre-built LDC binary from the release page. However, the binary is 32-bit and depends on libconfig, which doesn't appear to have a multilib package in Arch Linux. There are of course ways around this, but would it be possible to release a pre-built 64-bit binary? Maybe, I'll see. In the meantime, you can use ldmd2, which doesn't depend on libconfig.
Re: LDC 0.17.0 alpha cross-compiler for Android/ARM, D 2.068.2
On Friday, 6 November 2015 at 20:41:11 UTC, Jakob Ovrum wrote: On Friday, 6 November 2015 at 20:24:18 UTC, Joakim wrote: On Friday, 6 November 2015 at 20:10:36 UTC, Jakob Ovrum wrote: On Friday, 6 November 2015 at 11:56:35 UTC, Joakim wrote: [...] Thanks for the thorough instructions! LLVM is rather massive and I'd prefer to avoid building it if I can, so I downloaded the pre-built LDC binary from the release page. However, the binary is 32-bit and depends on libconfig, which doesn't appear to have a multilib package in Arch Linux. There are of course ways around this, but would it be possible to release a pre-built 64-bit binary? Maybe, I'll see. In the meantime, you can use ldmd2, which doesn't depend on libconfig. But ldmd2 depends on ldc2, doesn't it? It seems to be trying to invoke it. Oh, never tried ldmd2, just knew that it didn't link against libconfig. Away from computer now, will look into it tonight.
Re: Beta D 2.069.0-b1
On Wednesday, 7 October 2015 at 22:33:09 UTC, Martin Nowak wrote: First beta for the 2.069.0 release. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.069.0.html Please report any bugs at https://issues.dlang.org -Martin I just noticed that you added the beta to the main download page, nice move, probably overdue. Has it increased the downloads much? Maybe you should add a warning there, for those who may not know the meaning of a beta.
Re: Four new DConf 2015 videos
On Wednesday, 8 July 2015 at 13:56:37 UTC, Andrei Alexandrescu wrote: On 7/8/15 6:29 AM, ZombineDev wrote: Andrei Alexandrescu -- Keynote: Generic Programming Must Go dconf link: http://dconf.org/2015/talks/alexandrescu.html video link: https://www.youtube.com/watch?v=mCrVYYlFTrA Found my talk on reddit already: https://www.reddit.com/r/programming/comments/3cjr4v/generic_programming_must_go/ Can you post last week's TWiD also, the interview with Dmitry? I don't use reddit, but I think it'd go over well there and be good publicity for D.
Re: LDC for iOS prebuilt binaries
On Friday, 10 July 2015 at 20:38:16 UTC, Rishub Nagpal wrote: On Thursday, 9 July 2015 at 06:32:28 UTC, Dan Olson wrote: I've made a set of binaries and universal libs for the LDC iOS cross-compiler. It is based on LDC 0.15.1 (2.066) and LLVM 3.5.1. https://github.com/smolt/ldc-iphone-dev/releases/tag/ios-0.15.1-150708 Only 32-bit devices currently; arm64 work starts next month when I acquire an iPhone 6. The download should have everything needed to run on an OS X build host in the same fashion as LDC downloads. But I may have missed something. Feedback appreciated. Good Work! I'd like to help get D to work on android, but I do not know much about llvm and arm compilers to be of much help. Last I heard there was an issue with exception handling and TLS, is that still so? That's funny, because I was just thinking about putting my Android patches for ldc online and trying to get more people to chip in on working through the remaining tests to be fixed for Android/ARM. I got TLS working a month and a half ago (http://forum.dlang.org/post/imkgasjuvbbasyghd...@forum.dlang.org) and exception-handling seems to be working since this fix I ferreted out last week (http://forum.dlang.org/post/qsfaussopqwwjuljd...@forum.dlang.org). Now it's just codegen issues, with about half of phobos modules' tests failing somewhere, though many of those modules only have a handful of tests that fail. For example, only three unit test blocks fail in std.stdio and one in std.path. Common causes appear to be problems with ranges and functions from std.random. I'm going through each module and commenting out failing tests and checking backtraces, a time-consuming process that's got me thinking about hacking the test runner, so that failing tests in one unit test block won't stop other test blocks from the same module from running, as is the case now. If you or anybody else is interested in chipping in, reply in the Android thread (first link above) and I'll put some patches and build info online. Unfortunately, to really fix any of these issues, you'll probably have to know something about ARM assembly, LLVM IR, and be comfortable stepping through the binary with gdb but without debug info, although simply triaging the tests to figure out what works and what doesn't could probably be done by almost anyone.
Re: This Week in D #23 - Interview with Dmitry Olshansky, dmd beta, std.experimental.color
On Friday, 10 July 2015 at 20:42:02 UTC, Dmitry Olshansky wrote: On 10-Jul-2015 23:34, Joakim wrote: On Thursday, 2 July 2015 at 10:26:36 UTC, Dmitry Olshansky wrote: On 29-Jun-2015 06:46, Adam D. Ruppe wrote: http://arsdnet.net/this-week-in-d/jun-28.html I should have probably said on the day one - AMA. P.S. Thanks to Joakim for editing my stream of consciousness into this tidy text ;) Looks like you have a question on reddit, not sure how he reached that conclusion though: https://www.reddit.com/r/programming/comments/3ck3ru/interview_with_dmitry_olshansky_author_of_ds/ Answered. Never knew it was there at all. Oh, he's probably reacting to these two quotes: In the end, it turned out that UTF decoding had become the bottleneck and it's soon to be removed. The key one is to remove decoding of UTF and match directly on the encoded chars
Re: This Week in D #23 - Interview with Dmitry Olshansky, dmd beta, std.experimental.color
On Thursday, 2 July 2015 at 10:26:36 UTC, Dmitry Olshansky wrote: On 29-Jun-2015 06:46, Adam D. Ruppe wrote: http://arsdnet.net/this-week-in-d/jun-28.html I should have probably said on the day one - AMA. P.S. Thanks to Joakim for editing my stream of consciousness into this tidy text ;) Looks like you have a question on reddit, not sure how he reached that conclusion though: https://www.reddit.com/r/programming/comments/3ck3ru/interview_with_dmitry_olshansky_author_of_ds/
Re: Moving forward with work on the D language and foundation
On Monday, 24 August 2015 at 18:43:01 UTC, Andrei Alexandrescu wrote: Hello everyone, Following an increasing desire to focus on working on the D language and foundation, I have recently made the difficult decision to part ways with Facebook, my employer of five years and nine months. Facebook has impacted my career and life very positively, and I am grateful to have been a part of it for this long. The time has come for me, however, to fully focus on pushing D forward. Can you elaborate on how you plan to push D forward, other than forming the foundation sooner? As sorry I am for leaving a good and secure career behind, I am excited many times over about the great challenges and opportunities going forward. Sorry to hear the two couldn't coincide, but I doubt you will regret this move. Next step with the D Language Foundation is a formal talk with the foundation's prospective attorney tomorrow. I hope to get the foundation in motion as soon as possible, though I'm told there are numerous steps to complete. I will keep this forum posted about progress. I'm also glad to announce that the D Language Foundation already has a donor - I have decided to contribute my books' royalties to it. I encourage others to respond in kind. Is there some way we can slap TDPL online in a more accessible format, like a paid blog of some sort if you'd like to keep it generating royalties? Print and pdfs are such antiquated formats, we can do much better.
Re: LLVM 3.7 released - LDC is ready to use it!
On Tuesday, 1 September 2015 at 21:45:32 UTC, Kai Nacke wrote: Hi all! LLVM 3.7 has been released some minutes ago! See the release notes here: http://llvm.org/releases/3.7.0/docs/ReleaseNotes.html Downloads: http://llvm.org/releases/download.html#3.7.0 Also note that LDC is mentioned in the release notes as one of the projects who are already supporting LLVM 3.7. Just recompile LDC using master/merge-2.067 branch from GitHub. This is the 7th time that LDC and D are mentioned in the LLVM release notes! Nice. Emulated TLS for ELF was added in llvm 3.7, looking forward to trying that on Android, which doesn't have native TLS.
Re: reggae v0.5.0: new features in the D meta-build system
On Tuesday, 22 September 2015 at 12:39:48 UTC, Per Nordlöw wrote: On Wednesday, 16 September 2015 at 14:07:17 UTC, Atila Neves wrote: http://code.dlang.org/my_packages/reggae What's new: Atila If you want to build a really revolutionary *new* build system you should turn reggae into a client-server-architecture that listens to file moves/copies/notifications via inotify on Linux. I'm not sure how the develop/builder interface would look like then, however. A web-client would be one way. Like ekam? https://github.com/sandstorm-io/ekam We talked about it when I interviewed Atila: http://arsdnet.net/this-week-in-d/sep-06.html
[OT] tablet programming
On Saturday, 12 December 2015 at 08:25:21 UTC, Walter Bright wrote: On 12/11/2015 10:13 PM, Joakim wrote: Desktop Android's certainly not there yet for everybody, but it is for my admittedly low demands, and soon will be for everybody, as google has said they're working on built-in multi-window for the next version of Android. One aspect (for me, anyway) is in order to program, I need a big screen, because I have several windows open at once. I've gotten so used to it it is very hard for me to program with a small display. And to think that when I started, 24*80 displays were the norm for a good decade! But then I'd print out a paper listing as a supplement, and spread that out over a big table. At a desk, it's easy to connect a large monitor to the tablet for people like you, though you'll need some sort of terminal or IDE app that splits the resulting space into much smaller windows, essentially an in-app windowing system of sorts. On the tablet itself, the Termux app supports opening multiple full-screen terminals with Ctrl-Shift-C, and then paging between them with Ctrl-Shift-1/2/3 and so on. Unless you're actively reading data from multiple terminals and need to see them all simultaneously, that should suffice. It does for me: I keep three open, which is partially why I haven't bothered buying and connecting a large monitor. This type of setup is probably the future for most people, replacing a desktop/laptop with the smartphone/tablet they already have. I've found that the hardware is more than capable, the software support is just not there yet, but all the major vendors- Google, Microsoft, Apple- are working on providing desktop functionality from their mobile devices. I'm simply trying it out early because I wanted to see what it's like, and have been pleasantly surprised at how well it has worked for me. I also cannot type from a cramped airline seat. I have never successfully done any work on an airplane. But reading a book on a tablet works just ducky. Yeah, I was just sharing my experience programming with a tablet, not talking about doing it while flying. I hate traveling, can't imagine getting anything done on a plane, other than just waiting for it to be over. But maybe frequent flyers get used to it and get stuff done. And I have a laptop, a small tablet, and a large tablet. Same here, never used the large 10" one much because I always felt it was heavy at 1.3 lbs, but I use the smaller and half-as-heavy 8.4" one a lot. The large one would make an even better display to prop up and use for programming, but it's older and the battery seems to be going. I get almost 9-10 hours out of the small, year-old tablet while programming, which is amazing and _much_ better than the 3-4 hours I was getting from the three year-old ultrabook, likely because the CPU is much more efficient and the tablet's OLED display turns off most of the pixels when programming in a black fullscreen terminal.
[OT] tablet programming
On Monday, 14 December 2015 at 15:01:36 UTC, Nick Sabalausky wrote: On 12/12/2015 01:13 AM, Joakim wrote: Desktop Android's certainly not there yet for everybody, but it is for my admittedly low demands, and soon will be for everybody, as google has said they're working on built-in multi-window for the next version of Android. Personally, I would need far more than just multi-window support for Android to be a worthwhile desktop OS for me. A lot of the issues (though not nearly all) relate to software ecosystem. Yes, even after Android gets multi-window, it will take years for all the software to adapt. Hell, there still aren't that many Android apps that have a tablet UI, despite Android tablets having been around for years. Also, this is purely psychological, but I feel claustrophobic when using multi-window that doesn't allow arbitrarily-sized and overlapping windows, even though I don't use that feature most of the time. For example, I can't even find a halfway decent alternative to windows notepad, let alone any better text editor. I find that hard to believe, considering Notepad may be the worst text editor I've ever used. :) I've been using the vim package in Termux, same as I do on every other machine. Basic undo/redo support is rare in Android software, as is saving/loading actual files and sharing user files between different programs on the same machine, which is something desktops had pretty much sorted out decades ago. I don't know about the prevalence of those features, as I uninstall far more apps from any Android device than the few I usually install, but I suspect undo/redo will become more common as Android starts getting used more for productivity and file support has always been there, if not front and center for mobile usability reasons. The whole backup/restore situation is a mess (there's an article that explains my issues with it better than I can, but my link to it is buried somewhere ATM), PalmOS already had backup/restore sorted out much better over a decade ago. Heck, even same with iOS if you can tolerate iTunes and, well, Apple/iOS. I've never restored an OS, so not something I've had to deal with. I usually simply manually backup any files I consider important, and almost never put anything worthwhile in app settings, so don't care about those. For example, I never bookmark anything in browsers, going from memory and google search instead. That's just a few off-the-top-of-my-head examples. There's many others, like the bluetooth keyboard lag/unresponsiveness that you've already mentioned, and I can confirm from experience. No doubt, it will take a while for mobile OS's to become more productive, as opposed to being used mostly for consumption, like browsing or listening to music. But that is inevitably what's going to happen, just as PCs killed off the more powerful workstations. My point was simply that if you program and like to do a lot of stuff from the command-line, the recently introduced Termux app actually makes for a surprisingly pleasant experience on an Android device. And programmers are guinea pigs for what everybody else eventually does.
Re: DConf 2016 news: 20% sold out, book signing
On Friday, 11 December 2015 at 19:59:54 UTC, Russel Winder wrote: On Tue, 2015-12-08 at 15:50 -0800, Walter Bright via Digitalmars-d- announce wrote: 2. Load up a tablet with lots of books. Or a real laptop so you can do Real Programming – which of course must be in FORTRAN. I know you're joking, but I've been using my tablet for programming for the last couple weeks and it's surprisingly great. Using the excellent and free Termux Android app for common OSS packages (https://play.google.com/store/apps/details?id=com.termux=en) and a bluetooth keyboard (the somewhat dated Rapoo E6100), I've been able to get ldc built natively on Android (http://forum.dlang.org/thread/ycvtkeiyffhaixxpz...@forum.dlang.org). The tablet display is only 8.4" but so high-resolution, at 359 ppi, that it doesn't matter, particularly for a shell prompt. Its Exynos 5420 octa-core CPU is surprisingly fast, building llvm-optimized phobos in just over a minute. I prop the tablet up against something on my desk, and if I want to read a webpage, I can simply pick it up and hold it in my hands while reading. I'm living in the future! Just thought I'd share. :)
Re: DConf 2016 news: 20% sold out, book signing
On Saturday, 12 December 2015 at 05:46:15 UTC, Walter Bright wrote: On 12/11/2015 8:28 PM, Joakim wrote: and a bluetooth keyboard Just to nit pick, using an external keyboard makes it more of a laptop than a tablet. A nitpick for a nitpick is fair game. :) However, there are distinct differences with this setup. For one, the tablet and keyboard combined weigh just under 1.5 lbs, which is much lighter than almost any laptop. And you'd have to compare it to one of the new detachable laptops, as you can't just pick up most laptop screens and read them in one hand, as I can with this tablet. Of course, it's all about trade-offs: I find myself surprisingly comfortable with this small 8.4" diagonal screen, others may not be. The bluetooth keyboard repeatedly loses a couple keystrokes when starting typing after a minute's break, which appears to be a known Android problem. Chrome on Android will annoyingly not save your zoom level for various websites, as the desktop version does, which is particularly needed for this high-resolution display, meaning I repeatedly have to Ctrl-+ or pinch-zoom on sites over and over again to get the right text zoom back. I do have split-screen multi-window for many apps, as it's a flagship Samsung tablet. Desktop Android's certainly not there yet for everybody, but it is for my admittedly low demands, and soon will be for everybody, as google has said they're working on built-in multi-window for the next version of Android.
Re: Better watch out! D runs on watchOS!
On Monday, 4 January 2016 at 09:26:39 UTC, Dan Olson wrote: Joakimwrites: On Thursday, 31 December 2015 at 00:11:34 UTC, Dan Olson wrote: [...] Sounds good, submit a PR and let's get it in. Was planning to get that PR going then got side tracked by a more difficult ARM exeption unwinding bug. It happens in std.random unittest at LDC -O2 or higher. Does this sound familiar Joakim? Yep, except tests were failing in three unittest blocks with -O1 too, but I never looked into exactly why: https://gist.github.com/joakim-noah/63693ead3aa62216e1d9#file-ldc_android_arm-L3139 The bug is a bad stack pointer which blows up when the last unittest returns. This unittest has all the right conditions to generate stack adjustments around some of the function calls that throw exceptions. The exception landing pad does not fixup the stack adjustment, thus a stack leak on each caught exception. The unittest function epilog restores the stack by adding a fixed offset to match the prolog, so the stack pointer stays wrong when the saved registers and return address are popped. Really looks like LLVM is not doing the right thing with landing pads. In the meantime I patched LLVM to generate epilog that always uses frame pointer to restore the stack pointer. WatchOS requires a frame pointer, so this isn't too bad. Now all unittests pass at -O3 for watchOS. Could be the same issue for me, not sure. If you put your fix online, I can try it and see. I am guessing iOS is not effected since it uses SjLj to restore the stack after an exception is thrown. I'll have to pursue this later. My mind is freed up for the original PR. That one is much simpler, let's get it in.
Re: D runs on watchOS! and on Android Wear too!
On Tuesday, 5 January 2016 at 20:39:02 UTC, Laeeth Isharc wrote: On Monday, 28 December 2015 at 01:17:15 UTC, Dan Olson wrote: [...] Fantastic news, Dan. I can confirm that D also runs on Android Wear (Huawei watch) and passes all unit tests. Forgive the slight hijack, but I mention this here as people might see this thread and not the obscure one where I reported this previously. [...] You two might have to write that post together, since you're the only two reporting running D on watches so far! :) I might have a commercial use for this in coming months (both on Android and watchOS). Since it's an internal application the rough edges are of less concern to me than if one expects 100,000+ users. [...] This should be pretty easy, it won't qualify as a GSoC project on its own. btw, sent you an email, let me know if you didn't get it.
Re: Better watch out! D runs on watchOS!
On Thursday, 31 December 2015 at 10:10:20 UTC, Jacob Carlborg wrote: On Wednesday, 30 December 2015 at 20:55:44 UTC, Dan Olson wrote: I'm going to start with Plan B.1 though because LLVM does nice optimizations for TLS. What is Plan B.1? -- /Jacob Carlborg Getting it into llvm: http://forum.dlang.org/post/m237um75x7@comcast.net
Re: Better watch out! D runs on watchOS!
On Thursday, 31 December 2015 at 00:11:34 UTC, Dan Olson wrote: On Wednesday, 30 December 2015 at 23:11:06 UTC, Joakim wrote: That sounds like this issue I ran into with ARM EH: https://github.com/ldc-developers/ldc/issues/489#issuecomment-143560075 I was able to work around it by disabling the mentioned llvm optimization pass: https://gist.github.com/joakim-noah/1fb23fba1ba5b7e87e1a#file-android_tls-L42 https://gist.github.com/joakim-noah/63693ead3aa62216e1d9#file-ldc_android_arm-L3133 Yup, that's exactly it! The approach I took was to leave optimization on, removed the casts, and byte load the data into the uint vars. If the dwarf data is not guaranteed to be aligned to the data type, then I think this is the approach to take. Sounds good, submit a PR and let's get it in.