4 ms·

I don't know if 2021 is much different than, say, 2012, in that I don't mind compiling something as long as it works? I'm sure there are intricacies with ruby's

I don't know if 2021 is much different than, say, 2012, in that I don't mind compiling something as long as it works? I'm sure there are intricacies with ruby's configuration, specifically. And that you invested time and have a good understanding of it. But I'm not convinced it's a product and not a service, or a task for someone on staff for larger organisations. As but one thing: to be a product it needs to have some universal value for a significant chunk of scenarios (possibly with some configuration options). But at that point, it's not clear why it shouldn't be a contribution to the upstream project. Is there, possibly, an "Enterprise Edition" or "Cloud Deployment Pro Plan" in the works? I'm also (and that's neither here or there but I can't help myself) not entirely sure how democracy got involved here. While the rule of law and a participatory citizenry do tend to lead to obvious benefits, "reaping" evokes a one-way process that is sorta antithetical to the cooperative nature of democracies? Dunno, maybe it's just me. It's also on some buzzword bingo cards, although I can't quite say in what specific context...

FooBarWidget 5y ago
> But I'm not convinced it's a product and not a service, or a task for someone on staff for larger organisations. From my experience with users and the industry at large, the amount of people who are comfortable with compilation and sysadmin-y tasks are rapidly declining, proportion-wise. The industry is heading towards ever-more specialization. Many many backend developers nowadays don't want to think about infrastructure at all, they just want to focus on business logic. There are a huge amount of backend developers who have never seen './configure && make install'. In an organization with sufficiently advanced human capital, yes there is someone who can take care of that. But the existance of such a person can be taken less and less for granted nowadays even in very large organizations. There is also the factor of: should we do this work ourselves? Lots and lots of developer tooling nowadays are extremely slick. We've been spoiled. I have been spoiled. I can still write C++ but I don't want to bother with './configure && patch && make install' anymore. The standard nowadays is higher. Why should I spend a day installing a custom-patched Ruby when someone else can do that for me and all I have to do is to add an APT repo? Especially when I always have better things to do? > it's not clear why it shouldn't be a contribution to the upstream project. This is explained in the FAQ: https://github.com/fullstaq-labs/fullstaq-ruby-server-edition#why-a-new-distribution-why-not-contribute-to-ruby-core https://github.com/fullstaq-labs/fullstaq-ruby-server-editio... There is also a discussion here: https://news.ycombinator.com/item?id=27870740 https://news.ycombinator.com/item?id=27870740 > Is there, possibly, an "Enterprise Edition" or "Cloud Deployment Pro Plan" in the works? There is not. There are absolutely no paid features, nor plans to monetize. There are even enough reasons to not monetize. See the FAQ: https://github.com/fullstaq-labs/fullstaq-ruby-server-edition/blob/main/README.md#will-fullstaq-ruby-become-paid-in-the-future https://github.com/fullstaq-labs/fullstaq-ruby-server-editio... And the project vision, which is community-based: https://www.joyfulbikeshedding.com/blog/2020-05-15-why-fullstaq-ruby.html https://www.joyfulbikeshedding.com/blog/2020-05-15-why-fulls... > I'm also (and that's neither here or there but I can't help myself) not entirely sure how democracy got involved here. Democratization, not democracy. Democratization is about making something available to as many people as possible. Which is a different concept from democracy. Given that so many people are uncomfortable with compiling, or with LD_PRELOAD, or with anything outside of "bundle install", asking people to "just compile Jemalloc 3, make sure to apply this patch, then modify your systemd init script to include LD_PRELOAD" is too much to ask. It shuts down an entire range of people from benefiting from Jemalloc. With democratization, I seek to combat this.

FooBarWidget 5y ago

> But I'm not convinced it's a product and not a service, or a task for someone on staff for larger organisations. From my experience with users and the industry at large, the amount of people who are comfortable with compilation and sysadmin-y tasks are rapidly declining, proportion-wise. The industry is heading towards ever-more specialization. Many many backend developers nowadays don't want to think about infrastructure at all, they just want to focus on business logic. There are a huge amount of backend developers who have never seen './configure && make install'. In an organization with sufficiently advanced human capital, yes there is someone who can take care of that. But the existance of such a person can be taken less and less for granted nowadays even in very large organizations. There is also the factor of: should we do this work ourselves? Lots and lots of developer tooling nowadays are extremely slick. We've been spoiled. I have been spoiled. I can still write C++ but I don't want to bother with './configure && patch && make install' anymore. The standard nowadays is higher. Why should I spend a day installing a custom-patched Ruby when someone else can do that for me and all I have to do is to add an APT repo? Especially when I always have better things to do? > it's not clear why it shouldn't be a contribution to the upstream project. This is explained in the FAQ: https://github.com/fullstaq-labs/fullstaq-ruby-server-edition#why-a-new-distribution-why-not-contribute-to-ruby-core https://github.com/fullstaq-labs/fullstaq-ruby-server-editio... There is also a discussion here: https://news.ycombinator.com/item?id=27870740 https://news.ycombinator.com/item?id=27870740 > Is there, possibly, an "Enterprise Edition" or "Cloud Deployment Pro Plan" in the works? There is not. There are absolutely no paid features, nor plans to monetize. There are even enough reasons to not monetize. See the FAQ: https://github.com/fullstaq-labs/fullstaq-ruby-server-edition/blob/main/README.md#will-fullstaq-ruby-become-paid-in-the-future https://github.com/fullstaq-labs/fullstaq-ruby-server-editio... And the project vision, which is community-based: https://www.joyfulbikeshedding.com/blog/2020-05-15-why-fullstaq-ruby.html https://www.joyfulbikeshedding.com/blog/2020-05-15-why-fulls... > I'm also (and that's neither here or there but I can't help myself) not entirely sure how democracy got involved here. Democratization, not democracy. Democratization is about making something available to as many people as possible. Which is a different concept from democracy. Given that so many people are uncomfortable with compiling, or with LD_PRELOAD, or with anything outside of "bundle install", asking people to "just compile Jemalloc 3, make sure to apply this patch, then modify your systemd init script to include LD_PRELOAD" is too much to ask. It shuts down an entire range of people from benefiting from Jemalloc. With democratization, I seek to combat this.