November 03

On Monday, 28 October 2024 at 01:06:58 UTC, Kyle Ingraham wrote:

>

I know vibe.d can do better so I'm thinking there's something I'm missing.

Sönke Ludwig solved this for me here: https://github.com/vibe-d/vibe.d/issues/2807#issue-2630501194

The solution was to switch to a configuration for eventcore that uses kqueue directly instead of CFRunLoop. Doing that brought performance back to the stratosphere.

Solution from the GitHub issue:

"You can add an explicit sub configuration to dub.json:

"dependencies": {
	"vibe-d": "~>0.10.1",
	"eventcore": "~>0.9.34"
},
"subConfigurations": {
	"eventcore": "kqueue"
},

Or you could pass --override-config=eventcore/kqueue to the dub invocation to try it out temporarily."

I elected to go with the command line flag approach.

November 04

On Sunday, 3 November 2024 at 00:42:44 UTC, Kyle Ingraham wrote:

>

"You can add an explicit sub configuration to dub.json:

"dependencies": {
	"vibe-d": "~>0.10.1",
	"eventcore": "~>0.9.34"
},
"subConfigurations": {
	"eventcore": "kqueue"
},

Or you could pass --override-config=eventcore/kqueue to the dub invocation to try it out temporarily."

I'm glad to hear that. In the world of software, there is actually no problem that cannot be solved; except for the halting problem :)

SDB@79

November 05

On Monday, 4 November 2024 at 18:05:25 UTC, Salih Dincer wrote:

>

I'm glad to hear that. In the world of software, there is actually no problem that cannot be solved; except for the halting problem :)

?

Id argue theres entire families of problems that are unsolvable; the halting problem may just be a root

1 2
Next ›   Last »