#ossdev — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ossdev, aggregated by home.social.
-
Constellation update:
I resumed principal development around Christmas. The first effort was some technical debt resolution, to clean up after the mad dash to get it to MOC.
Finished that up this morning. This greatly improves some of the main APIs and puts me in a much better place moving forward.
Next batch of work will focus on core capabilities I'll need to get to initial operating capacity (IOC).
-
Constellation update:
I resumed principal development around Christmas. The first effort was some technical debt resolution, to clean up after the mad dash to get it to MOC.
Finished that up this morning. This greatly improves some of the main APIs and puts me in a much better place moving forward.
Next batch of work will focus on core capabilities I'll need to get to initial operating capacity (IOC).
-
Constellation update:
I resumed principal development around Christmas. The first effort was some technical debt resolution, to clean up after the mad dash to get it to MOC.
Finished that up this morning. This greatly improves some of the main APIs and puts me in a much better place moving forward.
Next batch of work will focus on core capabilities I'll need to get to initial operating capacity (IOC).
-
Constellation update:
I resumed principal development around Christmas. The first effort was some technical debt resolution, to clean up after the mad dash to get it to MOC.
Finished that up this morning. This greatly improves some of the main APIs and puts me in a much better place moving forward.
Next batch of work will focus on core capabilities I'll need to get to initial operating capacity (IOC).
-
Constellation update:
I resumed principal development around Christmas. The first effort was some technical debt resolution, to clean up after the mad dash to get it to MOC.
Finished that up this morning. This greatly improves some of the main APIs and puts me in a much better place moving forward.
Next batch of work will focus on core capabilities I'll need to get to initial operating capacity (IOC).
-
Constellation was fully approved for open-source release last week, and I have migrated all content at this point and finished setting it up on github yesterday, and am resuming principal development.
The design docs (highly technical) are here: https://github.com/constellation-system/constellation-system.github.io/wiki
It is still very much work-in-progress, and there's a way to go before I have even a skeleton of the whole system. But I'll be developing it in the open and reporting on what I'm doing from here on.
-
Constellation was fully approved for open-source release last week, and I have migrated all content at this point and finished setting it up on github yesterday, and am resuming principal development.
The design docs (highly technical) are here: https://github.com/constellation-system/constellation-system.github.io/wiki
It is still very much work-in-progress, and there's a way to go before I have even a skeleton of the whole system. But I'll be developing it in the open and reporting on what I'm doing from here on.
-
Constellation was fully approved for open-source release last week, and I have migrated all content at this point and finished setting it up on github yesterday, and am resuming principal development.
The design docs (highly technical) are here: https://github.com/constellation-system/constellation-system.github.io/wiki
It is still very much work-in-progress, and there's a way to go before I have even a skeleton of the whole system. But I'll be developing it in the open and reporting on what I'm doing from here on.
-
Constellation was fully approved for open-source release last week, and I have migrated all content at this point and finished setting it up on github yesterday, and am resuming principal development.
The design docs (highly technical) are here: https://github.com/constellation-system/constellation-system.github.io/wiki
It is still very much work-in-progress, and there's a way to go before I have even a skeleton of the whole system. But I'll be developing it in the open and reporting on what I'm doing from here on.
-
Constellation was fully approved for open-source release last week, and I have migrated all content at this point and finished setting it up on github yesterday, and am resuming principal development.
The design docs (highly technical) are here: https://github.com/constellation-system/constellation-system.github.io/wiki
It is still very much work-in-progress, and there's a way to go before I have even a skeleton of the whole system. But I'll be developing it in the open and reporting on what I'm doing from here on.
-
Big update: Constellation received final approval for open-source release today. I will be moving it to github later this week.
-
Big update: Constellation received final approval for open-source release today. I will be moving it to github later this week.
-
Big update: Constellation received final approval for open-source release today. I will be moving it to github later this week.
-
Big update: Constellation received final approval for open-source release today. I will be moving it to github later this week.
-
Big update: Constellation received final approval for open-source release today. I will be moving it to github later this week.
-
Was stuck the past week(s) in my #lisp implementation in #zig on #closures, as they provide an real challange with their capturing properties. Espc bc I didn't wanted to resort to using things like arbitary "rules" to restrict the language only for closure to work, or already implementing a tracing #garbagecollector for this.
I rather choose to use #ARC (Atomically Reference counting) for this, which comes with a few problems. And as I found nobody that has solved this problem, I've come up with a solution to it myself: 'Switchable references with strongchain elemination'. A bit bulky name, and the technique is still in it's beginning, but when implemented in rust the compiler dosnt complain and valgrind dosn't detects any leaks.
I've written a fairly big blogpost about it too, including not only the whole explanation how it works but also alternatives I've considered. Check it out if you're interested!
Now I only need to translate it over to zig, but hopefully that dosnt take so long x3
#coding #programming #software #oss #foss #ossdev #fossdev #lisp #zig #rust #softwaredevelopment #pldev #programminglanguages #referencecounting #rc #arc
-
Was stuck the past week(s) in my #lisp implementation in #zig on #closures, as they provide an real challange with their capturing properties. Espc bc I didn't wanted to resort to using things like arbitary "rules" to restrict the language only for closure to work, or already implementing a tracing #garbagecollector for this.
I rather choose to use #ARC (Atomically Reference counting) for this, which comes with a few problems. And as I found nobody that has solved this problem, I've come up with a solution to it myself: 'Switchable references with strongchain elemination'. A bit bulky name, and the technique is still in it's beginning, but when implemented in rust the compiler dosnt complain and valgrind dosn't detects any leaks.
I've written a fairly big blogpost about it too, including not only the whole explanation how it works but also alternatives I've considered. Check it out if you're interested!
Now I only need to translate it over to zig, but hopefully that dosnt take so long x3
#coding #programming #software #oss #foss #ossdev #fossdev #lisp #zig #rust #softwaredevelopment #pldev #programminglanguages #referencecounting #rc #arc
-
Was stuck the past week(s) in my #lisp implementation in #zig on #closures, as they provide an real challange with their capturing properties. Espc bc I didn't wanted to resort to using things like arbitary "rules" to restrict the language only for closure to work, or already implementing a tracing #garbagecollector for this.
I rather choose to use #ARC (Atomically Reference counting) for this, which comes with a few problems. And as I found nobody that has solved this problem, I've come up with a solution to it myself: 'Switchable references with strongchain elemination'. A bit bulky name, and the technique is still in it's beginning, but when implemented in rust the compiler dosnt complain and valgrind dosn't detects any leaks.
I've written a fairly big blogpost about it too, including not only the whole explanation how it works but also alternatives I've considered. Check it out if you're interested!
Now I only need to translate it over to zig, but hopefully that dosnt take so long x3
#coding #programming #software #oss #foss #ossdev #fossdev #lisp #zig #rust #softwaredevelopment #pldev #programminglanguages #referencecounting #rc #arc
-
Was stuck the past week(s) in my #lisp implementation in #zig on #closures, as they provide an real challange with their capturing properties. Espc bc I didn't wanted to resort to using things like arbitary "rules" to restrict the language only for closure to work, or already implementing a tracing #garbagecollector for this.
I rather choose to use #ARC (Atomically Reference counting) for this, which comes with a few problems. And as I found nobody that has solved this problem, I've come up with a solution to it myself: 'Switchable references with strongchain elemination'. A bit bulky name, and the technique is still in it's beginning, but when implemented in rust the compiler dosnt complain and valgrind dosn't detects any leaks.
I've written a fairly big blogpost about it too, including not only the whole explanation how it works but also alternatives I've considered. Check it out if you're interested!
Now I only need to translate it over to zig, but hopefully that dosnt take so long x3
#coding #programming #software #oss #foss #ossdev #fossdev #lisp #zig #rust #softwaredevelopment #pldev #programminglanguages #referencecounting #rc #arc
-
Was stuck the past week(s) in my #lisp implementation in #zig on #closures, as they provide an real challange with their capturing properties. Espc bc I didn't wanted to resort to using things like arbitary "rules" to restrict the language only for closure to work, or already implementing a tracing #garbagecollector for this.
I rather choose to use #ARC (Atomically Reference counting) for this, which comes with a few problems. And as I found nobody that has solved this problem, I've come up with a solution to it myself: 'Switchable references with strongchain elemination'. A bit bulky name, and the technique is still in it's beginning, but when implemented in rust the compiler dosnt complain and valgrind dosn't detects any leaks.
I've written a fairly big blogpost about it too, including not only the whole explanation how it works but also alternatives I've considered. Check it out if you're interested!
Now I only need to translate it over to zig, but hopefully that dosnt take so long x3
#coding #programming #software #oss #foss #ossdev #fossdev #lisp #zig #rust #softwaredevelopment #pldev #programminglanguages #referencecounting #rc #arc
-
-
-
-
-
So, because I'm probably going to have to sort this out in the near future, what CI/CD setups do people use for open-source projects?
Hosted seems to be the thing these days; what do people use?
-
So, because I'm probably going to have to sort this out in the near future, what CI/CD setups do people use for open-source projects?
Hosted seems to be the thing these days; what do people use?
-
So, because I'm probably going to have to sort this out in the near future, what CI/CD setups do people use for open-source projects?
Hosted seems to be the thing these days; what do people use?
-
So, because I'm probably going to have to sort this out in the near future, what CI/CD setups do people use for open-source projects?
Hosted seems to be the thing these days; what do people use?
-
So, because I'm probably going to have to sort this out in the near future, what CI/CD setups do people use for open-source projects?
Hosted seems to be the thing these days; what do people use?
-
Constellation: victory is in sight! All the wiring is done, all that remains is to fix the core protocol state machine, update about 7000 lines of tests, and fix some annoying but non-gating issues.
I could probably resolve a consensus round now, actually. The protocol I have should actually work, it's just not quite the Castro-Liskov protocol.
Then there's some issues with some threads hanging at shutdown and not cleaning things up, but that's not major.
Close now, very close..
-
Constellation: victory is in sight! All the wiring is done, all that remains is to fix the core protocol state machine, update about 7000 lines of tests, and fix some annoying but non-gating issues.
I could probably resolve a consensus round now, actually. The protocol I have should actually work, it's just not quite the Castro-Liskov protocol.
Then there's some issues with some threads hanging at shutdown and not cleaning things up, but that's not major.
Close now, very close..
-
Constellation: victory is in sight! All the wiring is done, all that remains is to fix the core protocol state machine, update about 7000 lines of tests, and fix some annoying but non-gating issues.
I could probably resolve a consensus round now, actually. The protocol I have should actually work, it's just not quite the Castro-Liskov protocol.
Then there's some issues with some threads hanging at shutdown and not cleaning things up, but that's not major.
Close now, very close..
-
Constellation: victory is in sight! All the wiring is done, all that remains is to fix the core protocol state machine, update about 7000 lines of tests, and fix some annoying but non-gating issues.
I could probably resolve a consensus round now, actually. The protocol I have should actually work, it's just not quite the Castro-Liskov protocol.
Then there's some issues with some threads hanging at shutdown and not cleaning things up, but that's not major.
Close now, very close..
-
Constellation: victory is in sight! All the wiring is done, all that remains is to fix the core protocol state machine, update about 7000 lines of tests, and fix some annoying but non-gating issues.
I could probably resolve a consensus round now, actually. The protocol I have should actually work, it's just not quite the Castro-Liskov protocol.
Then there's some issues with some threads hanging at shutdown and not cleaning things up, but that's not major.
Close now, very close..
