Today my mind seems to be on how capitalists like Google, Microsoft, & Facebook have subverted free software into free labor for them.

This ties into my advice from this morning to:
1) Pay for the free software you use, &
2) Tackle projects which aren't interesting to them.

@alcinnz regarding "not interesting to them", use programming languages that interest you but aren't mainstream (in particular don't have a $name Foundation backing them, as those are ripe for takeover).

An environment without internal tooling support is kryptonite for large corporations and you'd have to have 100% market fit (in which case you're doing their job for them anyway) for them to overcome that hurdle.

@patrick That's one way!

I'd add that webdev & especially big data tools are ripe for cooption...

@alcinnz With big data, I think an important consideration is it you're ever going to need it: many problems have a neat solution for the regular case and only become complicated once you're scaling up.

Regarding web dev, I wouldn't want to leave the web to the big corps. But again, solutions that satisfy the nimble project tend to be unsuitable when scaling up, and those corps are all about scaling up. "Going small" is underappreciated and scalability might be the most rampant "memetic virus" in computing.

@patrick Agreed!

I make my own (noJS) browser engines for unusual mediums live voice assistants or TVs...

@alcinnz My target for web dev projects is "federated, at family scale". Not needing to be able to serve more than 30 people at most on an install simplifies _so_ much, and "family scale" also means that super high availability is no concern. 5 minutes downtime to reboot the server? Happens and nobody bats an eye.
@patrick @alcinnz Yeah, I quite agree on this kind of scale and availability.

That said I also just love services which just works enough that you could easily feel like going on vacation for ~2 weeks without fearing that your shit will be too down to access it a bit.
@lanodan @alcinnz I don't worry about instability a lot, the important stuff is on a rented server in a data center. But I also don't have to care about seamless updates and fail over and all that which complicates software architecture. That simple architecture keeps things alive for months at a time with no hand holding required.

Some consensus algorithm that has to decide if all 3 instances are in sync and, if not, which one to trust can stab me in the back at the most inopportune moment.
@patrick @alcinnz Yeah, I don't have to worry much about it either, in fact I'm quite too lazy when it come to maintaining my own things so I tend to prioritize a bit on things that could be kept permanent and having good redundancy.

@dragestil That's not guaranteed. But it sure seems to help one whole hell of a lot.


Sign in to participate in the conversation

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).