Re: DConf 2019 Livestream
On Wednesday, 8 May 2019 at 08:31:22 UTC, Per Nordlöw wrote: On Wednesday, 8 May 2019 at 08:21:33 UTC, Thomas Brix Larsen wrote: I had to click Audio Connection -> Computer to get audio. Where did you find those menus? Button with three dots -> Audio Connection -> Call Using Computer for Audio.
Re: DConf 2019 Livestream
On Wednesday, 8 May 2019 at 08:25:18 UTC, Mike Franklin wrote: On Wednesday, 8 May 2019 at 08:21:33 UTC, Thomas Brix Larsen wrote: I am able to join with Firefox. I can see the video, but no audio. I'm still troubleshooting. Mike I had to click Audio Connection -> Computer to get audio. You mean the "Call using computer" option. That gives me an error: "Can't Call Using Computer, We're having a problem connecting to audio using your computer. Choose another audio connection option or try again." I guess it's unique to my computer. I'll have to try from another computer. Can you see Walter's presentation though? It looks like just an overexposed whitewash. I can't see anything on the presentation screen except white. Mike Yeah the slides are unreadable.
Re: DConf 2019 Livestream
On Wednesday, 8 May 2019 at 08:16:23 UTC, Mike Franklin wrote: On Wednesday, 8 May 2019 at 08:00:15 UTC, Andrej Mitrovic 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 "When joining: Please connect using Internet Explorer, not Google Chrome or another web browser." You guys can't be serious, you're using WebEx? I am able to join with Firefox. I can see the video, but no audio. I'm still troubleshooting. Mike I had to click Audio Connection -> Computer to get audio.
Re: Spasm 0.1.3 released - with bindings to web apis
On Wednesday, 30 January 2019 at 11:49:17 UTC, kinke wrote: On Wednesday, 30 January 2019 at 11:03:13 UTC, WebFreak001 wrote: I install LDC from the arch repositories, which should just be the prebuilt binaries from the ldc repo I think Nope, they aren't. I guess your problem is that you cannot *link* wasm; that will only work with v1.14 for distro packages (without integrated LLD). The targets wasm32 and wasm64 are missing in the Arch package.
Re: Cap'n Proto for D v0.1.2
On Wednesday, 19 April 2017 at 19:30:03 UTC, Thomas Brix Larsen wrote: On Wednesday, 19 April 2017 at 18:24:46 UTC, Jay Norwood wrote: [...] Ok, thanks. I took a look at several capnproto implementations just now, and didn't see any tests for a mmap 'feature'. The roadmap doc below indicates it doesn't exist, and perhaps there are some details yet to be resolved to make it 'friendly' for a mmap. But reading using random access *is* a feature of Cap'n Proto. So when reading a memory mapped Cap'n Proto file, getters will be faster if you use it in a non-sequential way. I have made some minor changes to make adaptors responsible for allocating buffers. This made it possible to add a new adaptor MemoryMapped and a sample[1] to show it off. I have also verified that no buffer allocations happen while reading using MemoryMapped. Note that writing using memory mapping is still not possible. [1]: https://github.com/ThomasBrixLarsen/capnproto-dlang/blob/master/source/samples/mmap.d
Re: Cap'n Proto for D v0.1.2
On Wednesday, 19 April 2017 at 18:24:46 UTC, Jay Norwood wrote: [...] Ok, thanks. I took a look at several capnproto implementations just now, and didn't see any tests for a mmap 'feature'. The roadmap doc below indicates it doesn't exist, and perhaps there are some details yet to be resolved to make it 'friendly' for a mmap. But reading using random access *is* a feature of Cap'n Proto. So when reading a memory mapped Cap'n Proto file, getters will be faster if you use it in a non-sequential way. The format of Cap'n Proto doesn't currently support *writing* to a memory mapped file.
Re: Cap'n Proto for D v0.1.2
On Wednesday, 19 April 2017 at 16:34:02 UTC, Jay Norwood wrote: [...] This info from stackoverflow also seems to imply that MappedByteBuffer would be required for some of the capnproto features. So, could you explain a little more about what are the capabilities of the current d library implementation, with just the ByteBuffer implemented from the java nio code? Thanks, Jay [...] The port of ByteBuffer just wraps a slice when reading in D. Take a look at FileDescriptor[1]. It is a class I've added to support read/write using File from std.stdio. You can create a similar streamer using std.mmfile. I believe that this would be enough for memory mapped reading. [1]: https://github.com/ThomasBrixLarsen/capnproto-dlang/blob/master/source/capnproto/FileDescriptor.d
Cap'n Proto for D v0.1.2
"Cap’n Proto is an insanely fast data interchange format and capability-based RPC system. Think JSON, except binary. Or think Protocol Buffers, except faster." This is the initial public release of my optimized port of the Java implementation of Cap'n Proto. State: * Passes Cap'n Proto testsuite. * Optimized. Just a little slower than the official C++ implementation (see benchmarks on github). * Missing RPC part of Cap'n Proto. http://code.dlang.org/packages/capnproto-dlang https://github.com/ThomasBrixLarsen/capnproto-dlang
Re: Release D 2.069.0
On Monday, 9 November 2015 at 03:15:29 UTC, rsw0x wrote: On Monday, 9 November 2015 at 02:15:17 UTC, Andrei Alexandrescu wrote: On 11/8/15 2:58 PM, rsw0x wrote: Interestingly, GDC seems *very* popular - it has a 4:1 install rate of gccgo and only trailing slightly behind the golang-go package(reference compiler?) on Ubuntu's popcon. Link? -- Andrei debian: https://qa.debian.org/popcon-graph.php?packages=gdc%2Cgccgo%2Cgolang_installed=on_legend=on_ticks=on_date=_date=_date=_fmt=%25Y-%25m=1 ubuntu: http://ubuntu-popcon.43-1.org/cgi-bin/graph.pl?name=gdc http://ubuntu-popcon.43-1.org/cgi-bin/graph.pl?name=golang-go http://ubuntu-popcon.43-1.org/cgi-bin/graph.pl?name=gccgo note that dmd is not redistributed on most linux distros due to licensing issues Opt-in stats from Arch: https://www.archlinux.de/?page=PackageStatistics go 19.45% rust5.92% gcc-go 5.61% dmd 2.56% ldc 1.72% gdc 1.60%
