[–] throwaway63467 7 hours ago
[–] viraptor 6 hours ago
> It's not about memory safety per se. It's about not losing an hour of analysis because a malformed .sav file or a zero-variance sample triggered a segfault or silent wrong output. SPSS crashes on bad data.
[–] solyin 6 hours ago
[–] viraptor 6 hours ago
[–] SweetSoftPillow 4 hours ago
[–] hodgehog11 7 hours ago
[–] throwaway63467 7 hours ago
[–] viraptor 6 hours ago
It's not rust specific, but any language which allows you to work on a higher level and with better typing helps close that gap. For example for a long time Linux kernel had an issue with marking user/kernel addresses which opened it up to bugs and security issues. In C those are just numbers. In Rust this is moot and correct by default because user addresses are explicitly UserPtr.
So yes, sometimes a better language allows you make some unintended things explicitly not compile. It won't solve the issue completely, but the scope of the mismatch gets much smaller.
[–] hodgehog11 7 hours ago
[–] cb321 7 hours ago
[–] archargelod 5 hours ago
You can take a lot more "smart" shortcuts in Nim, that are hard to reason about, and probably even harder when an automated system writes them.
[–] cb321 5 hours ago
[–] kobaltGIT 7 hours ago
[–] uniqueuid 7 hours ago
We have R/tidyverse which does 90% of everything and has an amazing community and procedures eg. around documentation. For everything else you have excel or python. So I don’t see the use case.
[–] hodgehog11 7 hours ago
[–] uniqueuid 7 hours ago
[–] hodgehog11 7 hours ago
[–] Traster 7 hours ago
What do we gain from a plethora of SPSS-alike tools? Nothing. There's literally no explanation on this page about why anyone who uses SPSS would want to use this. But it's "100% Safe Rust". Yes, that's a feature that someone who likes rust wants, not what someone who uses SPSS wants.
What do we lose by fracturing all academic statistical analysis into a dozen different tools instead of 1? Lots!
It's not even clear the person creating this even intends for anyone to use it. So (a) why are they doing it and (b) how do you even know if it actually works if absolutely no one is using it. In fact the danger now is someone who doesn't know the author is just an AI slop dilletante comes along looking for an SPSS-like tool and makes the mistake of trying to use it.
Is there really any difference between this and the people posting AI slop onto their reddit accounts. It's just raising the noise floor to the point where we're going to have to essentially shut down the public internet, everything of value will move to closed spaces.
[–] viraptor 6 hours ago
I'm extremely happy every time a closed format falls. Whether it's this one, Sibelius music scores, records from medical devices, data series from scientific measurements, or something else. Every one of them stopped me from doing something in the past (not on a technical level but "it's not worth spending a month on this") and I'll support efforts like this.
[–] Traster 1 hour ago
[–] yjftsjthsd-h 1 hour ago
[–] hodgehog11 7 hours ago
Proprietary software, especially at these prices, cause all kinds of issues. SPSS is one of the software packages that has a sizeable audience of people crying out for a true open source alternative. Just because you have the money to afford these things, does not mean that others do.
Also, if you are referring to the similarly named ArtCraft suite as a "pointless activity" then you are really out of touch.
[–] qubex 6 hours ago
[–] ben_pfaff 1 hour ago
The hard part is figuring out SPSS file formats. They are complex and IBM does not document them. I spent years figuring them out--and I am still working on the format for graphs and charts. Maybe they are trivial for claude, but I doubt it, because there aren't very many examples of the formats easily available. I've collected tens of thousands of examples myself for my use, but I don't have permission to share them, so instead I've documented what I've learned.
[–] roryirvine 5 hours ago
[–] nnurmanov 6 hours ago
[–] veggieroll 4 hours ago
I’ve long since switched to python & other normal programming for any stats needs. And I only ever scraped the surface of SPSS/PSPP anyways. But, I’d be interested to hear what PSPP doesn’t cover.
Good luck on your project.
[–] ben_pfaff 1 hour ago
[–] sehw 6 hours ago
[–] kachnuv_ocasek 7 hours ago
[–] tallesborges92 7 hours ago
[–] EdwardDiego 7 hours ago
You even let your LLM write the README.
Look, we nearly all use LLMs these days, but the phrasing of "I am... ...alone" is particularly weird when it's obviously not just you, it's you with LLMs.
Maybe title it as "A rewrite of IBM SPSS Statistics in Rust with no unsafe" - the 100% safe claim is something an LLM makes, it's not something a reasonable human would say, as it implies the Rust is totally safe, whereas you're trying to communicate that your Rust code uses no unsafe blocks, and these are two different things.
[–] Hizonner 3 hours ago
[–] nialse 7 hours ago
An oracle and fuzzing have been excellent when reimplementing software. Given implausible inputs, the black box shows its colours quickly. Rounding errors and different representations of floats are and endless source of debugging, eh, joy.
[–] hodgehog11 7 hours ago
[–] westurner 4 hours ago
GNU Octave is like Matlab. Matplotlib is like Matlab but doesn't support the same syntax.
Will it have a DataFrame API?
Before R data.frame and Pandas DataFrame and substrait.dataframe, there were labeled arrays in NumPy.
Pint uses numpy ufuncs to type numbers with physical units.
Here are the notes I had for pgrust a few months ago: https://news.ycombinator.com/item?id=49112449 ; Polars (already has tested SIMD and GPU-optimized routines), substrait interface, and file formats: LanceDB, Vortex, Arrow recordbatch
Here are my notes for the ArtCraft folks about methods for Rust ports (and whether it's necessary to also port Blender to Rust with an O3/Maturin Python API) https://github.com/storytold/artcraft/issues/2489 :
> port the tests [and check figures] first; use branch coverage metrics when testing; use cargo-llvm-cov and rust-nightly to test; make (.sh,) scripts that the .github/workflows/ call so that local builds are easy; run local builds using nektos/act; use rstest to keep tests and test fixtures maintainable; use cargo-insta to snapshot; use cargo-fuzz, and do coverage-guided fuzzing; use TLA+, Lean or similar formal methods and tools to model the critical parts of the app at least
In the ArtCraft issues, there are so many great ideas that any or many or all firms could benefit from.
[–] scrubs 7 hours ago
Op, is there any technical merit to this, or is this a step in some process to earn brownie points in some pathetic "I'm a morally superior hero club?"
What'd you expect the rest of us to feel? Chastened?
[–] kobaltGIT 9 hours ago
I started this because I believe statistical software should not crash on malformed data, should be scriptable by AI agents via MCP, and should not cost thousands of dollars per year.
Current state (11 days in, solo):
- 14 statistical blocks audited against SPSS 24 Algorithms Guide with ≤1e-6 SciPy precision
- Full .sav/.zsav codec, Excel/CSV import, SPSS syntax parser (.sps)
- 37 SPSS-style dialogs, pivot tables, Output Viewer with TSV export
- Built-in MCP server for Claude/ChatGPT/Ollama agents
- Zero unwrap/expect/panic in production; fuzzed on corrupted inputs — 0 panics
What I need help with:
- Testers with real SPSS datasets (the weirder the encoding, the better)
- Rust developers for the expression evaluator (3 known precedence gaps)
- Statisticians to validate output against their SPSS workflows
- Anyone who wants to port a procedure (regression, factor, reliability are in)
[–] frevib 6 hours ago
I think I’ll pass.
You don’t state StatCraft is clean room, but all Artcraft software is.
Talk to a lawyer to check if you’re not wasting your time.
https://en.wikipedia.org/wiki/Clean-room_design