On Friday, 6 May 2022 at 11:57:47 UTC, Iain Buclaw wrote:
Hi,
I am proud to announce another major GCC release, 12.1.
[...]
Regards,
Iain.
Great!
On Sunday, 8 May 2022 at 22:09:37 UTC, Ali Çehreli wrote:
Congratulations! :) Looking forward to watching your
presentation at DConf... ;)
I wish I was able to speak publicly in English in front of an
audience :)
On 5/8/22 14:32, Andrea Fontana wrote:
> Every request is processed by a
Hello!
I've just released serverino. It's a small & ready-to-go
http/https server.
Every request is processed by a worker running in an isolated
process, no fibers/threads, sorry (or thanks?)
I did some tests and the performance sounds good: on a local
machine it can handle more than
On Sunday, 8 May 2022 at 21:32:42 UTC, Andrea Fontana wrote:
[...]
Andrea
Whoops, I forgot a couple of things. This was tested on linux
only and it should work fine on other posix systems (macOS
included!).
I don't have windows, but I think you need WSL to run it, since
I'm using a lot of
On Mon, May 09, 2022 at 12:10:53PM +1200, rikki cattermole via
Digitalmars-d-announce wrote:
> On 09/05/2022 11:44 AM, Ali Çehreli wrote:
> > While we are on topic :) and as I finally understood what
> > generational GC is[1], are there any fundamental issues with D to
> > not use one?
>
> This
On Sunday, 8 May 2022 at 22:09:37 UTC, Ali Çehreli wrote:
That effectively uses multiple GCs. I always suspected that
approach would provide better latency.
My cgi.d has used some fork approaches for a very long time since
it is a very simple way to spread this out, it works quite well.
On 09/05/2022 11:44 AM, Ali Çehreli wrote:
While we are on topic :) and as I finally understood what generational
GC is[1], are there any fundamental issues with D to not use one?
This is not a D issue, its an implementation one.
We don't have write barriers, that's it.
Make them opt-in
On Friday, 6 May 2022 at 11:57:47 UTC, Iain Buclaw wrote:
Hi,
I am proud to announce another major GCC release, 12.1.
Thanks, Iain. All is good on OpenBSD.
~Brian
Congratulations! :) Looking forward to watching your presentation at
DConf... ;)
On 5/8/22 14:32, Andrea Fontana wrote:
> Every request is processed by a worker running in an isolated process,
> no fibers/threads, sorry (or thanks?)
That effectively uses multiple GCs. I always suspected that
On Monday, 9 May 2022 at 00:32:33 UTC, Ali Çehreli wrote:
On 5/8/22 17:25, H. S. Teoh wrote:
> somebody should make a dmd
> fork that introduces write barriers, plus a generational GC
(even if
> it's a toy, proof-of-concept-only implementation) to see if
the
> performance hit is really as bad
On 5/8/22 16:10, Adam Ruppe wrote:
> On Sunday, 8 May 2022 at 22:09:37 UTC, Ali Çehreli wrote:
>> That effectively uses multiple GCs. I always suspected that approach
>> would provide better latency.
>
> My cgi.d has used some fork approaches for a very long time since it is
> a very simple way
On 5/8/22 17:25, H. S. Teoh wrote:
> somebody should make a dmd
> fork that introduces write barriers, plus a generational GC (even if
> it's a toy, proof-of-concept-only implementation) to see if the
> performance hit is really as bad as believed to be.
Ooh! DConf is getting even more
The deadline for DConf '22 submissions is next Sunday, May 15th.
If you've got an idea for a talk, send it in!
On Sunday, 8 May 2022 at 09:25:08 UTC, Mike Parker wrote:
The deadline for DConf '22 submissions is next Sunday, May
15th. If you've got an idea for a talk, send it in!
All the details are here:
https://dconf.org/2022/index.html#schedule
On Sunday, 8 May 2022 at 23:44:42 UTC, Ali Çehreli wrote:
While we are on topic :) and as I finally understood what
generational GC is[1], are there any fundamental issues with D
to not use one?
I implemented one a long time ago. The only way to get write
barriers with D is memory
15 matches
Mail list logo
