4 ms·

Really nice. The only thing that would prevent me to give it a real go to is that it is a one man project not backed by any company...

jazoom 10y ago
Valid concern. I'll do my bit to reverse the downvotes.
- jdmichal 10y ago
  Is being a one-person gig really a valid concern for open-source? What's the worst case? That the bus factor kicks in and someone has to fork it to continue the work? That's not such a terrible outcome. Certainly better than, say, when Google decides to wind-down a closed-source project.
  - jazoom 10y ago
    Yes. There are thousands of 1-man projects that have been abandoned. People here quoting the examples where something starts as a 1-man project and is now super popular just illustrates the wisdom in waiting to see which few of the many actually catch on. What's the benefit? The benefit is that you aren't left as the 1-man crew maintaining the project after the other 1-man gives up. Would I use a 1-man backed CSS framework? Probably. But that doesn't mean melicerte is wrong.
nrjames 10y ago
Well, that's sort of how d3.js grew.
talmand 10y ago
Why does that matter? There have been major projects backed by a company that have gone away. There have been major projects backed by one person that have been around for years.
- jazoom 10y ago
  It's all about probability.
  - jdmichal 10y ago
    The probability of what? You'll always be able to use this, as it's open source. Even if it somehow wasn't, it's CSS, so you'd still be able to tweak it however you want. I don't understand what the downside is here.
pc86 10y ago
Isn't one of the main tenants of OSS that it can organically grow beyond a single person without the need for company backing?
NKCSS 10y ago
Vue is an example of a one-man project lots of people build on; it can be done and be done well :)
azurvii 10y ago
Wasn't Linux originally a one man job as well?
- jazoom 10y ago
  Would you use a 1-man-developed OS on your servers? Linux is no-longer a 1-man show.
fweespeech 10y ago
> Really nice. The only thing that would prevent me to give it a real go to is that it is a one man project not backed by any company... I understand this position for large, dense frameworks (i.e. Rails, Zend, Spring) that you are basing your entire codebase on. Heck, I can even see an argument with Javascript (largely due to Node, React, etc. having a substantial impact you design around). This is CSS. Pretty much any front end developer can maintain a CSS framework that was dropped by its creator if push came to shove.
pyre 10y ago
Well... Angular Material is a multi-person project that is (seemingly) backed by Google, but they are abandoning 1.x release (1.0 was just released last October) to make the 2.x release Angular 2.x-only even though Angular 2.x isn't really ready for prime time (at least in my opinion). They also made promises last fall about how it would be "supported for a long time to come." So, let's say that more people and a company don't necessarily equate to better, longer-lasting support.
- jazoom 10y ago
  One counter example does not detract from the point. A company-backed project is far more likely to last a long time. I could point you to thousands of examples of abandoned 1-man projects.
  - pyre 10y ago
    I'm just saying that it's never a sure thing, not that the opposite is always true.
grumpywizards 10y ago
From my experience this is a non-issue in the OSS environment, you got to pick your frameworks based on other criteria; popularity, fit for purpose, community engagement, learning curve to maintain yourself etc. All of which has nothing to do with company or individual ownership. Blaze benefits from an MIT licence so it's totally accessible

jazoom 10y ago

Valid concern. I'll do my bit to reverse the downvotes.

jdmichal 10y ago
Is being a one-person gig really a valid concern for open-source? What's the worst case? That the bus factor kicks in and someone has to fork it to continue the work? That's not such a terrible outcome. Certainly better than, say, when Google decides to wind-down a closed-source project.
- jazoom 10y ago
  Yes. There are thousands of 1-man projects that have been abandoned. People here quoting the examples where something starts as a 1-man project and is now super popular just illustrates the wisdom in waiting to see which few of the many actually catch on. What's the benefit? The benefit is that you aren't left as the 1-man crew maintaining the project after the other 1-man gives up. Would I use a 1-man backed CSS framework? Probably. But that doesn't mean melicerte is wrong.

nrjames 10y ago

Well, that's sort of how d3.js grew.

talmand 10y ago

Why does that matter? There have been major projects backed by a company that have gone away. There have been major projects backed by one person that have been around for years.

jazoom 10y ago
It's all about probability.
- jdmichal 10y ago
  The probability of what? You'll always be able to use this, as it's open source. Even if it somehow wasn't, it's CSS, so you'd still be able to tweak it however you want. I don't understand what the downside is here.

pc86 10y ago

Isn't one of the main tenants of OSS that it can organically grow beyond a single person without the need for company backing?

NKCSS 10y ago

Vue is an example of a one-man project lots of people build on; it can be done and be done well :)

azurvii 10y ago

Wasn't Linux originally a one man job as well?

jazoom 10y ago
Would you use a 1-man-developed OS on your servers? Linux is no-longer a 1-man show.

fweespeech 10y ago

> Really nice. The only thing that would prevent me to give it a real go to is that it is a one man project not backed by any company... I understand this position for large, dense frameworks (i.e. Rails, Zend, Spring) that you are basing your entire codebase on. Heck, I can even see an argument with Javascript (largely due to Node, React, etc. having a substantial impact you design around). This is CSS. Pretty much any front end developer can maintain a CSS framework that was dropped by its creator if push came to shove.

pyre 10y ago

Well... Angular Material is a multi-person project that is (seemingly) backed by Google, but they are abandoning 1.x release (1.0 was just released last October) to make the 2.x release Angular 2.x-only even though Angular 2.x isn't really ready for prime time (at least in my opinion). They also made promises last fall about how it would be "supported for a long time to come." So, let's say that more people and a company don't necessarily equate to better, longer-lasting support.

jazoom 10y ago
One counter example does not detract from the point. A company-backed project is far more likely to last a long time. I could point you to thousands of examples of abandoned 1-man projects.
- pyre 10y ago
  I'm just saying that it's never a sure thing, not that the opposite is always true.

grumpywizards 10y ago

From my experience this is a non-issue in the OSS environment, you got to pick your frameworks based on other criteria; popularity, fit for purpose, community engagement, learning curve to maintain yourself etc. All of which has nothing to do with company or individual ownership. Blaze benefits from an MIT licence so it's totally accessible