Re:Spice: Fine-grained parallelism with sub-nanosecond overh...
by pverghese on Monday August 12, 2024 @09:02PM
(#41231137)
You are welcome to add it. This is a proof of concept
Re:Spice: Fine-grained parallelism with sub-nanosecond overh...
by jd3 on Monday August 12, 2024 @09:07PM
(#41231170)
> Spice is primarily a research project. Read along to learn more about it, but if you're considering using it in production you should be aware of its many limitations.
Ah, I missed that upon first read. In that case, that caveat/limitation is definitely justified.
Re:Spice: Fine-grained parallelism with sub-nanosecond overh...
by dsp_person on Monday August 12, 2024 @09:15PM
(#41231210)
> sharing it with the broader HN community
Note that I posted this, but I am not the author
Re:Spice: Fine-grained parallelism with sub-nanosecond overh...
by stareatgoats on Tuesday August 13, 2024 @08:39AM
(#41234865)
> (cough the initial Docker project Show HN thread cough)
Docker was largely met with enthusiasm here when it was launched. I believe you must refer to how Dropbox was received — famously negatively, initially.
Re:Spice: Fine-grained parallelism with sub-nanosecond overh...
by WaffleIronMaker on Tuesday August 13, 2024 @09:12AM
(#41235119)
Yeah, that seems right:
April 5, 2007: "Show HN, Dropbox"
Re:Spice: Fine-grained parallelism with sub-nanosecond overh...
by Dylan16807 on Tuesday August 13, 2024 @08:08PM
(#41241207)
Looks positive to me!
Re:Spice: Fine-grained parallelism with sub-nanosecond overh...
by jd3 on Wednesday August 14, 2024 @10:06AM
(#41246243)
Yes, I meant to say dropbox
Re:Spice: Fine-grained parallelism with sub-nanosecond overh...
by dagw on Tuesday August 13, 2024 @08:45AM
(#41234907)
HN community, who are generally known to by hyper-critical to a pedantic degree and/or overly pessimistic (cough the initial Docker project Show HN thread cough)
So you made me dig up the announcement, and contrary to how you recall, it is almost universally positive.
I also really appreciate that the author recognizes the limits of their own project, which preemptively addresses most of the usual snark.
> Lack of tests: Spice contains a lot of gnarly concurrent code, but has zero testing coverage. This would have be improved before Spice can be responsibly used for critical tasks.
Testing correctness of execution for critical tasks is one thing, but I would expect a library which implements "gnarly concurrent code" to at least have regression tests — what guarantee is there to an end-user that functionality which exists in a working state today might not break tomorrow due to a subtle yet nefarious regression?
sqlite has 590 times as much test code and test scripts as it does raw c source code [0]; this fact, along with its stability and portability, is one of the numerous reasons why it has proliferated to become the defacto embedded database used across the planet. While we're comparing apples to oranges in this contrived example, the general point still stands — regression tests beget stability and confidence in a project.
In epics where I work, if we _must_ defer baseline regression tests, we usually create a follow-up ticket inside of the same epic to at least write them before feature/epic launch, usually.
[0]: https://www.sqlite.org/testing.html