4 ms·

I'm not quite sure who the article is actually written for. If it's written to generate interest from investors, or for some other such semi/non technical audie

I'm not quite sure who the article is actually written for. If it's written to generate interest from investors, or for some other such semi/non technical audience then please ignore this (although the fact that I can't tell who it's written for is in itself a warning signal). If it's written to attract potential users, however, then it's woefully light on useful content. I don't care in the slightest about your views on tech monopolies - why on earth waste such a huge amount of space talking about this? What I care about are three things: 1) what workloads does it do well and, and which ones does it do poorly at (if you don't tell me about the latter I won't believe you - no storage system is great at everything). 2) What consistency/availability model does it use, and 3) how you've tested it. As written, it's full of fluff and vague handwavy promises (we have PhDs!) - the only technical information in the entire post is that it's written in rust. For users of your application, what programming language it's written in is about the least interesting thing possible to say about it. Even going through your docs I can't find a single proper discussion of your consistency and availability model, which is a huge red flag to me.

adrn10 5y ago
This article broadly explains the motivation and vision behind our project. There are many object stores, why build a new one? To push self-hosting, in face of democratic/political threats we feel are daunting. Sorry it didn't float your boat. You're just not the article's target audience I guess! (And, to answer your question: the target audience is mildly-knowledgeable but politically concerned citizens.) I agree this is maybe not the type of post you'd expect on HN. But, we don't want to _compete_ with other object stores. We want to expand the application domain of distributed data stores. > I can't find a single proper discussion of your consistency and availability model LGTM, I would be dubious too. This will come in time, please be patient (the project is less than 2 yo!). You know Cypherunks' saying? "We write code." Well, for now, we've been focusing on the code, and we want to continue doing so until 1.0. Some by-standers will do the paperware for sure, but it's not our utmost priority.
- jfindley 5y ago
  Thanks for the response. It's great that you're trying to build something that will allow folks to do self-hosting well, I'm fully on board with this aim. My point about the political bits though, is that even for folks that agree with you, pushing the political bits too much can signal that you're not confident enough in the technical merits of what you're doing for them to stand on their own. Re: the paperwork vs code thing - While a full white paper on your theoretical foundations would be nice, IMO the table stakes for getting people to take your product seriously is a sentence or two on the model you're using. For example, adding something like: "We aim to prioritise consistency and partition tolerance over availability, and use the raft algorithm for leader elections. Our particular focus is making sure the storage system is really good at handling X and Y." or whatever would be a huge improvement, until you can get around to writing up the details. The problem with "we write code" is that your users are unlikely to trust you to be writing the correct code, when there's so little evidence that you've thought deeply about how to solve the hard problems inherent in distributed storage.
  - adrn10 5y ago
    It was actually deliberate to present our project through the political lens, today. You will find a more streamlined presentation of Garage on our landing page at https://garagehq.deuxfleurs.fr/ https://garagehq.deuxfleurs.fr/ Technical details are also documented (although it is insufficient and needs an overhaul): https://garagehq.deuxfleurs.fr/documentation/design/ https://garagehq.deuxfleurs.fr/documentation/design/ Thank you for your comments!
StillBored 5y ago
For the average user it shouldn't matter what its written in, but lately I've returned to the theory that language choice for a project signals a certain amount of technical sophistication. Particularly, for things like this, which should be considered systems programming. The overhead of a slow JIT, GC, threading model, IO model, whatever basically means the project is doomed to subpar perf forever and the cost of developing it has been passed on to the users, which will be forced to buy 10x the hardware to compensate.
- dspillett 5y ago
  > For the average user it shouldn't matter what its written in, True. > but lately I've returned to the theory that language choice for a project signals a certain amount of technical sophistication. Sometimes it can signal the opposite, if you think a given language/framework/other is not a great tool for the job. For a relatively new project it can be a sign that there might be otherwise avoidable growing pains later. From an open source standpoint what a project is written using can be very important from the point of view of what you are familiar with. If the project progress or support vanishes (for instance if the core maintainers move on to other things for whatever reason, or there is a significant license change making future work on the core project incompatible with your use) would others be able to maintain it securely in a fork and if no one else steps up would you be able to (at least until you migrated onto something else)?

adrn10 5y ago

This article broadly explains the motivation and vision behind our project. There are many object stores, why build a new one? To push self-hosting, in face of democratic/political threats we feel are daunting. Sorry it didn't float your boat. You're just not the article's target audience I guess! (And, to answer your question: the target audience is mildly-knowledgeable but politically concerned citizens.) I agree this is maybe not the type of post you'd expect on HN. But, we don't want to _compete_ with other object stores. We want to expand the application domain of distributed data stores. > I can't find a single proper discussion of your consistency and availability model LGTM, I would be dubious too. This will come in time, please be patient (the project is less than 2 yo!). You know Cypherunks' saying? "We write code." Well, for now, we've been focusing on the code, and we want to continue doing so until 1.0. Some by-standers will do the paperware for sure, but it's not our utmost priority.

jfindley 5y ago
Thanks for the response. It's great that you're trying to build something that will allow folks to do self-hosting well, I'm fully on board with this aim. My point about the political bits though, is that even for folks that agree with you, pushing the political bits too much can signal that you're not confident enough in the technical merits of what you're doing for them to stand on their own. Re: the paperwork vs code thing - While a full white paper on your theoretical foundations would be nice, IMO the table stakes for getting people to take your product seriously is a sentence or two on the model you're using. For example, adding something like: "We aim to prioritise consistency and partition tolerance over availability, and use the raft algorithm for leader elections. Our particular focus is making sure the storage system is really good at handling X and Y." or whatever would be a huge improvement, until you can get around to writing up the details. The problem with "we write code" is that your users are unlikely to trust you to be writing the correct code, when there's so little evidence that you've thought deeply about how to solve the hard problems inherent in distributed storage.
- adrn10 5y ago
  It was actually deliberate to present our project through the political lens, today. You will find a more streamlined presentation of Garage on our landing page at https://garagehq.deuxfleurs.fr/ https://garagehq.deuxfleurs.fr/ Technical details are also documented (although it is insufficient and needs an overhaul): https://garagehq.deuxfleurs.fr/documentation/design/ https://garagehq.deuxfleurs.fr/documentation/design/ Thank you for your comments!

StillBored 5y ago

For the average user it shouldn't matter what its written in, but lately I've returned to the theory that language choice for a project signals a certain amount of technical sophistication. Particularly, for things like this, which should be considered systems programming. The overhead of a slow JIT, GC, threading model, IO model, whatever basically means the project is doomed to subpar perf forever and the cost of developing it has been passed on to the users, which will be forced to buy 10x the hardware to compensate.

dspillett 5y ago
> For the average user it shouldn't matter what its written in, True. > but lately I've returned to the theory that language choice for a project signals a certain amount of technical sophistication. Sometimes it can signal the opposite, if you think a given language/framework/other is not a great tool for the job. For a relatively new project it can be a sign that there might be otherwise avoidable growing pains later. From an open source standpoint what a project is written using can be very important from the point of view of what you are familiar with. If the project progress or support vanishes (for instance if the core maintainers move on to other things for whatever reason, or there is a significant license change making future work on the core project incompatible with your use) would others be able to maintain it securely in a fork and if no one else steps up would you be able to (at least until you migrated onto something else)?