misterdata

Some things I thought of: governmental registries, tracking history of physical assets (e.g. tracking of maintenance history of aerospace components), software licensing, storing timestamped cargo manifests (like the Maersk case). You could even build a currency on this with the right set of privileges.

The idea that some of these transactions store data is not any different from the idea that some transactions in Bitcoin add new coins to the system, or that some transactions in Ethereum create and store contracts (which are code and data).

Now of course you could, instead of storing the actual data and/or SQL, put data in a DHT and reference and timestamp that.

That said, this is obviously not meant to store large amounts of data. But you could quite easily build a currency on top of this (add a 'balances' table, and use grants to determine who can update what - a future version could even provide smart contracts through SQL stored procedures).

[1] https://github.com/pixelspark/catena/blob/master/Implementat...

Otherwise, nice app. How does it scale to larger CSV files? I have been working on something similar (https://warp.one) for Mac, which streams CSV files (apparently you use a SQLite database behind the scenes as cache?)

[1] http://voidtools.com

Real-world use: https://github.com/pixelspark/warp/blob/dcf57462bd400df6d067...

(the typealias thing is a bit weird here, I agree - it also doesn't crash without it. Nevertheless this compiled fine on 3.0 and should show a nice error, not require me to leave out every other file from the build to find out where it goes wrong, then bisect that file to find out which line causes it)

A safe language greatly helps to prevent the sort of bug that compromises within-process security.

[1] http://github.com/pixelspark/warp [2] https://warp.one