Re: Beta 2.087.0
On Sunday, 16 June 2019 at 22:47:57 UTC, Martin Nowak wrote: Glad to announce the first beta for the 2.087.0 release, ♥ to the 66 contributors. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.087.0.html As usual please report any bugs at https://issues.dlang.org -Martin Cool! Lots of goodies are on the way.
Re: Optional 0.15.0 now compatible with vibe-d, @safe, @nogc, betterC.
On Tuesday, 4 June 2019 at 07:22:34 UTC, aliak wrote: Hey, I've recently released optional 0.15.0 [0] that includes support for vibe-d serialization/deserialization. So you can use it instead of Nullable for types that may or may not be there (I got bit by Nullable again so felt this had to be added [1]) Thanks! I've recently ran into the vibe-d serialization as well. It's awesome to be able to use Optional there.
Re: DConf 2019 Day 2 Livestream
On Thursday, 9 May 2019 at 07:45:41 UTC, Andrei Alexandrescu wrote: Just checked, it works: https://youtu.be/Vj6jNAlv03o Thank you! I've shared it among friends.
Re: DConf 2019 Livestream
On Wednesday, 8 May 2019 at 10:13:35 UTC, Ethan wrote: On Wednesday, 8 May 2019 at 07:57:40 UTC, Mike Parker wrote: The venue uses WebEx for livestreaming. All the information is available in this PDF: https://drive.google.com/open?id=1yekllbfOmxHqJNuuWIVeP9vNeROmfp1I Good news everyone! A Youtube stream will be arriving after the lunch break. Cheers for your patience. Is there a URL we can share (for today)?
Re: Using const to Enforce Design Decisions
On Monday, 25 March 2019 at 20:59:41 UTC, Rubn wrote: I guess obligatory http://jmdavisprog.com/articles/why-const-sucks.html Good to read a different take on the subject. Jonathan uses a lot of arguments that I recognize (and adds a few that I didn't encounter in my project). I am a firm believer of using the type system and the compiler to aid development. Personally, I found it supplemental to the way I write code (with a strong DDD influence). I've also tried to use pure, but (ironically) I found it harder to use. I think it's easier to understand when an object will be mutated or not than to predict whether there are side effects. Would be nice to see the source code for this mahjong game as well. https://github.com/Zevenberge/Mahjong I've been learning on the job, so there are a few quirks of earlier times that managed to avoid the blade of refactoring (including a case I discovered yesterday where mutable state could potentially leak). In general, I'm quite happy with it though. The code for the example in the blog is, among others: https://github.com/Zevenberge/Mahjong/blob/master/source/engine/flow/turn.d We are looking at a part of the state machine modelling the various moments (phases) in a mahjong turn, more precisely the action decided by the turn player (e.g. discard or declare a win). A message is sent to the players (UI or AI). The message exposes a read-only view on all game data relevant for making a decision. Manipulations can only be done through predefined methods in the message (conceptually a return message). This means that the turn player can declare a win through a method in the message, but not restart the game, as that would require access to a mutable game object.
Re: I'm the new package maintainer for D on ArchLinux
On Thursday, 10 August 2017 at 15:18:31 UTC, Dicebot wrote: Thanks for bringing my attention to it, I have disowned both it and dstep-git. Note though that you could take it over anyway if you intend to move it to [community] as a TU - contacting original author is only matter of politeness. I didn't want to take it over if you still wanted to maintain it And of course congratulations for becoming a TU! :) Thanks, and while I have you here, is there any reason why all the dtools programs have 'dtools-' as a prefix?
Re: I'm the new package maintainer for D on ArchLinux
On Thursday, 10 August 2017 at 14:26:41 UTC, Jacob Carlborg wrote: That's great. Do you want to maintain the package for DStep as well as Dicebot did? I could do that, but what I can see Dicebot still maintains it https://aur.archlinux.org/packages/dstep/ But it could just be that he has forgot to orphan it.
I'm the new package maintainer for D on ArchLinux
Hi everyone,
The D packages for ArchLinux has been orphaned since Dicebot
stepped down as the maintainer and no one else stepped up. So I
decided to step up and apply to become a Trusted User, and I got
accepted yesterday[1]. So from now on I will be the one who
maintains all the D packages (in the [community] repo), and it
will be my job to fix them if they break.
If you haven't heard of me before (which is probable because I
mostly lurk), my name is Dan, I'm 21 years old and I'm the
developer of PowerNex[2], a D kernel/OS, and I livestream coding
at Twitch[3].
Currently only dmd, dtools, ldc and lib{,l}phobos are in the
[community] repo. I would like to move over dub, dcd, dscanner
and dfmt (some of these were dropped from [community] due to
being orphaned). You guys can help by voting on AUR packages that
you want to be moved to [community].
Feel free to ping me on anything that is related to packaging or
the ArchLinux packages.
I hope I can maintain ArchLinux as a great environment to use D.
Ways of contacting me:
- a...@vild.io
- wild on freenode (I lurk in #d, #archlinux, #powernex)
- Vild on github
- Discord: https://discordapp.com/invite/bMZk9Q4
Thanks
- Dan
[1]
https://lists.archlinux.org/pipermail/aur-general/2017-August/033463.html
[2] https://github.com/PowerNex/PowerNex
[3] https://www.twitch.tv/wildn00b
Re: Call for arms: Arch Linux D package maintenance
On Monday, 10 July 2017 at 23:39:36 UTC, rjframe wrote: I couldn't find a documented deprecation process, but they do deprecate packages; perhaps if that could be pushed forward it would allow someone to maintain something in AUR. I can maintain the packages if they are moved to the AUR. I maintain most of the dlang packages in there already. [1] I been thinking of applying to become a TU, but haven't gotten around to do it. (I will probably do this in the future if needed) [1] https://aur.archlinux.org/packages/?K=dlang
Re: code-d 0.12.0 - The user friendly release (code-d for noobs)
On Wednesday, 5 October 2016 at 13:32:55 UTC, Rory McGuire wrote: I haven't used anything else since I started using Sublime because of CTRL+d (multi select the next match of my current selection) and fuzzy search of the available commands. Both Atom and Vscode have the ctrl+d feature and should have the fuzzy features (I don't remember). After all Atom and Vscode are open source clones of Sublime.
PowerNex - The Userspace update! (also first birthday)
Hey! To celebrate the first birthday[1] of PowerNex, my D kernel, I've made a new release. This is a big release compared to the old one, because this one contains a userspace mode where you can load and execute ELF executable. I've also implemented TLS so userspace programs don't need to spam __gshared all over the place. If you want to download a precompiled ISO or read more about this release you can go to this github release page: https://github.com/Vild/PowerNex/releases/tag/v0.2.0 The project is fully open source and located at https://github.com/Vild/PowerNex under the MPLv2 license. All feedback is appreciated. - Dan [1] I only missed it by a week because of a stupid bug.
Re: PowerNex - New release of my D kernel
On Sunday, 26 June 2016 at 07:43:37 UTC, Werner wrote: Latest release shows this: http://imgur.com/QOPsqkc.png Looks like you didn't give it enough RAM. What command did you run?
Re: Project Highlight: The PowerNex Kernel
On Friday, 24 June 2016 at 15:09:41 UTC, Satoshi wrote: On Friday, 24 June 2016 at 14:09:12 UTC, Mike Parker wrote: Not that long ago, Dan Printzell announced his D OS Kernel, PowerNex [1], in this forum. It is now the subject of the first project highlight on the D Blog [2]. [1] https://github.com/Vild/PowerNex [2] http://dlang.org/blog/2016/06/24/project-highlight-the-powernex-kernel/ Its funny how he took existing sources from my OS https://github.com/Rikarin/Trinix rewrite it during stream session on Livecoding and get more popularity than my OS. Do you want me to remove all the code that is influenced by your code in the kernel and rewrite from scratch? Because I don't want my project to contain illegal/controversial code.
Re: Project Highlight: The PowerNex Kernel
On Friday, 24 June 2016 at 14:11:43 UTC, Mike Parker wrote: On Friday, 24 June 2016 at 14:09:12 UTC, Mike Parker wrote: Not that long ago, Dan Printzell announced his D OS Kernel, PowerNex [1], in this forum. It is now the subject of the first project highlight on the D Blog [2]. [1] https://github.com/Vild/PowerNex [2] http://dlang.org/blog/2016/06/24/project-highlight-the-powernex-kernel/ And the reddit thread is here: https://www.reddit.com/r/programming/comments/4pn19m/from_the_d_blog_project_highlight_the_powernex/ Someone posted it to Hacker News: https://news.ycombinator.com/item?id=11969891
Re: Project Highlight: The PowerNex Kernel
On Friday, 24 June 2016 at 17:09:28 UTC, Ola Fosheim Grøstad wrote: On Friday, 24 June 2016 at 15:27:14 UTC, Wild wrote: Ya, I did borrow some code, mostly because my 64-bit code didn't play nice in the beginning. But I think I have rewritten all the code that I borrowed from you. Be careful with that. A rewrite may still be considered a translation, and the original author retains copyright of your rewrite and thus your code may have to obey the original license. A translation does not have to be literal for the copyright-ownership to carry over. I didn't know that, thanks. But I don't think this case would fall under a translation, but I'm no lawyer so I can't be 100% sure.
Re: Project Highlight: The PowerNex Kernel
On Friday, 24 June 2016 at 15:09:41 UTC, Satoshi wrote: On Friday, 24 June 2016 at 14:09:12 UTC, Mike Parker wrote: Not that long ago, Dan Printzell announced his D OS Kernel, PowerNex [1], in this forum. It is now the subject of the first project highlight on the D Blog [2]. [1] https://github.com/Vild/PowerNex [2] http://dlang.org/blog/2016/06/24/project-highlight-the-powernex-kernel/ Its funny how he took existing sources from my OS https://github.com/Rikarin/Trinix rewrite it during stream session on Livecoding and get more popularity than my OS. Ya, I did borrow some code, mostly because my 64-bit code didn't play nice in the beginning. But I think I have rewritten all the code that I borrowed from you. But I still mentioned you in the Thanks-to [1] section. [1] https://github.com/Vild/PowerNex#thanks-to
Re: PowerNex - New release of my D kernel
There is a Q about the development of the kernel over at https://www.reddit.com/r/programming/comments/4lwtn9/first_release_of_powernex_an_os_kernel_written_in/
PowerNex - New release of my D kernel
Hey! I have new release of my D kernel called PowerNex. This release should be a bit more interesting than the last one that I release back in November 2015. This one contains a working memory manager, a custom TTY renderer, BMP image renderer, a VFS, etc. More information is in the Github release. https://github.com/Vild/PowerNex/releases/tag/v0.1.0-ALPHA The Github release also have a precompiled ISO. The project is fully open source and located at https://github.com/Vild/PowerNex under the MPLv2 license. Hopefully someone will find this interesting. All feedback is appreciated. -Dan
Re: PowerNex - My 64bit kernel written in D
On Wednesday, 25 November 2015 at 16:18:56 UTC, Piotrek wrote: Hi, No worries :) Feel free to use whatever license you want. It is your code. However my point was that the code released with license other than Boost (or similar) cannot be included in Phobos. That's one thing. The second is, non liberal licenses put burden on commercial adoption and put risk on legal actions. I know that from the employee POV who worked for many corporations and was obliged to follow the rules. The bottom line is that viral licenses (with varying aggressiveness) are in opposition to business. Yes, I know GPL is used by companies but the cost is high. To use analogy: you can live with viruses, but you need money for medicines. BTW. Sorry if I sounded to harsh and forgive me stealing your announcement for my propaganda ;) I'll try to figure out a way to present my ideas in proper way before I have to many enemies. Piotrek No offense taken. It's important for a project to have a fitting license. I chose MPLv2 because I like the code to be free like BSD, for it to be able to be located in all sorts of project, but I still want the code to remain open source. I will maybe change the license in the future, if needed. But currently I don't see a reason to do it. - Dan
Re: PowerNex - My 64bit kernel written in D
On Saturday, 21 November 2015 at 11:34:57 UTC, Piotrek wrote: On Tuesday, 17 November 2015 at 23:35:58 UTC, Wild wrote: Hey! I have recently started working on a 64bit kernel ... Hi, Good to see more work in the OS area. I am even more happy there is more developers interested in GUI stuff. I have one fundamental question though: Is it possible for you to pick the Boost license (especially for libs)? This is my general concern for all libs developed by the D community. IMO license other than Boost is very cumbersome and doesn't comply with the D core libs. Piotrek Like cym13 said, there should not be any problems with the MPLv2 license. MPLv2 is basically LGPL but at a file level and it won't "infect" any other files. My code can included in any close source projects. The only thing is that if any of my files are changed, those changes need to published. - Dan
Re: PowerNex - My 64bit kernel written in D
On Wednesday, 18 November 2015 at 11:20:58 UTC, Rikki Cattermole wrote: Will you being going down the path of libc/posix compat layer or straight up D all the way? I want to go D all the way. But if I have to get a libc, I will try and implement one in D.
Re: PowerNex - My 64bit kernel written in D
On Wednesday, 18 November 2015 at 09:31:04 UTC, Luis wrote: Nice! https://github.com/Vild/PowerNex/blob/master/kernel/src/io/textmode.d#L64 not should be "cast(slot[w*h] *)" ? Fixed and pushed, Thanks!
Re: PowerNex - My 64bit kernel written in D
On Wednesday, 18 November 2015 at 03:04:49 UTC, Rikki Cattermole wrote: So whats the plan? - 32bit support - ARM support What else? Well don't have a fixed plan on what I want to implement. I might do 32bit, I have not decided yet, but I think I will skip it. I will not add ARM support because this would require alot more research. Maybe in the future when PowerNex is in a more feature complete state. The long term goal is that userspace programs should be able to use phobos.
Re: PowerNex - My 64bit kernel written in D
On Wednesday, 18 November 2015 at 06:06:52 UTC, lobo wrote: This project looks great and it's not easy writing a x86-64 bootloader even with GRUB and a reference to work from, Nice work! Thanks :D
PowerNex - My 64bit kernel written in D
Hey! I have recently started working on a 64bit kernel written in only D (and a little bit of assembly where it is really needed). I finally got it to boot today in 64bit mode. All it currently do is just print some text and numbers to the screen. It uses Adam D. Ruppes minimal D runtime, with some small modifications. I have a precompiled ISO here, if anyone wants to try it: https://github.com/Vild/PowerNex/releases/tag/v0.0.0-ALPHA The project is fully opensource and located at https://github.com/Vild/PowerNex I livestream the development of this almost everyday at https://livecoding.tv/Wild/ Hopefully someone will find this interesting. All feedback is appreciated. //Dan
xcb-d - First release
Hi! I've just release the first version of xcb-d. It's a bind for xcb that is generated via d_client.py, a heavy modified c_client.py script from the libxcb repository. This file uses the xml files from the libxcb-proto repository. With this approach it will be really easily updated to the lasted version of xcb when it is released. Currently it's for xcb version 1.11. I'm looking forward to some feedback if there is any. DUB package: http://code.dlang.org/packages/xcb-d Github: https://github.com/Vild/xcb-d -Dan
