scc VS Seaweed File System

View on GitHub

Going to say my own https://github.com/boyter/scc/ which I have used to turn down projects of "Oh we just need to do X"

It allows me to evaluate the code-base quickly and see where potential issues are, and find hidden complexity in the code. I have said no a lot due to it. The only reason it exists was because I got caught out from another project, which wasted months of my time.

Otherwise IntelliJ and the JetBrains IDE's in general.

Very cool to see this here, Ben! It was fun beating the ins and outs of your work on this in the TZ discord.

Also, off-topic but as you know, I recently tried out your scc tool and am eagerly awaiting its support for Elixir templates (.eex, .heex)!

https://github.com/boyter/scc

I believe tokei is the best rust option as of now, but despite my burning passion for rust I've switched to using scc instead as I find it faster and more convenient. Not really an option for you if you're trying to bake line counting into the binary, obviously.

I've seen some real world example where Go was as fast or faster than Rust for CPU / io intensive task.

Go is a fast language even with a GC.

https://github.com/boyter/scc/#performance

I don't trust your qualitative "LARGE" for the project. I would recommend you pass your project through something like a software metrics tool https://github.com/boyter/scc to better measure what you're up against in terms of Flutter/Dart AND Rust code base.

BTW, for technically inclined, here is scc output for an exported inventory tracker app (you can see actual app build @ https://www.bappaz.com/video or step by step process to build the app @ https://www.bappaz.com/learn )

FYI: Planning to move from github.com/chrislusf/seaweedfs to github.com/seaweedfs/seaweedfs in the coming days. It may cause some problem for package reference, building, documents, and links. Sorry for the change!

Besides storage itself, S3 API access cost can be high if frequently accessed. And latency is unpredicatble.

You can use SeaweedFS Remote Object Store Gateway to cache S3 (or any S3 API compatible vendors) to local servers, and access them at local network speed, and asynchronously sync back to S3.

https://github.com/chrislusf/seaweedfs/wiki/Gateway-to-Remot...

If you are looking at MinIO you might find SeaweedFS interesting as well.

I believe what you want is a horizontally scalable object store with tiered storage. SeaweedFS is free / open source https://github.com/chrislusf/seaweedfs

I don't know if it fits all of your requests, but you can take a look at seaweedfs, which is pretty good

Seaweedfs deserves a mention here for comparison as well.