A spreadsheet it just a view broken up in to rectangle cells and that compares favorably to the JavaScript smalltalk variants I’ve seen online such as this one https://amber-lang.net/
The output when it’s not an error message can redirected in to another function and so on and so forth until it’s not entirely programming and not entirely a prebuilt interface. A smalltalk VM is like an operating system as a repl as long as you’re skilled enough to not keep hitting error messages.
"NTRU encryption algorithm, is an NTRU lattice-based alternative to RSA and elliptic curve cryptography (ECC) and is based on the shortest vector problem in a lattice (which is not known to be breakable using quantum computers)."[0]
NIST's first PQC standard, CRYSTALS-Kyber, is also a lattice-based system (with a more complex structure and based on LWE rather than the NTRU SVP. There are now solid implementations of it all over the place, so it's much easier to check out.
Thank you so much for creating this! I have been wanting something like this forever.
Please consider the potential for this - I think you could make something really fun and something people would be willing to pay for.
But the problem is you need a world someone else created (or one you painstakingly create yourself). You could consider Conan's Hyborian Age, H.P. Lovecraft, Sherlock Holmes, or Peter Watt's work[0] for a known world that is public domain to base your project on.
Want to state off the bat this this project is awesome and huge kudos to the author for spending their time, attention, and energy 1) working diligently to get this working at all and 2) sharing it with the broader 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)
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.
> 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.
> (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.
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.
