beatrix bitrotcapitalism is what's wrong with software development tbh
Koz@bea How?
@Koz with software there's practically infinite ways to cut corners and do weird sketchy shit
people will do it to get ahead of the competition because they have to
There are other things but that's mainly what I was thinking of
So you're talking about "time to market". People cut corners, or release the minimum viable product (MVP) in order to get out first and gain market share.
It's certainly a strategy, and it can pay off.
But I don't think it's a sure win. Quality matters too; cut too many corners and you'll have a non-functioning product. Fail to maintain it and people will go elsewhere.
And sketchy shit will absolutely sink a piece of software.
@bea
I'm not necessarily in agreement that "capitalism" as a system causes bad software. But I do think the software business model has outraced people's understanding of what they're trading. People can understand the value of a product versus what currency they hand over for it. But when software is presented as being "Free" (ie, no price), there's poor understanding of what the price truly is....in terms of personal information of the recipient.
I'm not necessarily in agreement that "capitalism" as a system causes bad software. But I do think the software business model has outraced people's understanding of what they're trading. People can understand the value of a product versus what currency they hand over for it. But when software is presented as being "Free" (ie, no price), there's poor understanding of what the price truly is....in terms of personal information of the recipient.
@bea
That, in my opinion, is a failure of transparency by the seller, and lack of understanding by the consumer.
That, in my opinion, is a failure of transparency by the seller, and lack of understanding by the consumer.
@Koz sure
For context, when I made the original post the discussion at the time was about electron and why people use it
@bea Gotcha, missed that part!
So is electron favorable, or not?
@Koz it's more or less universally despised but also recognized as probably the easiest way to make cross platform apps
Ah, the old "software everyone loves to hate but can't help using it cause it's so gosh darn easy!"
What's the problem with it though?
@Koz it takes up a lot of memory and is slow and just is otherwise about what you'd expect from making an app out of js and embedding a browser with it to run/render it...
Ahhh, yeah. So I'm familiar with this now. (Wire runs on this model, and I have a love/hate relationship with it.) It's basically JRE all over again; write once, deploy to many. Except there's a huge fuckin' abstraction layer there to act as an intermediary.
I agree completely, but the alternative is to maintain a separate client for each platform. So I can see the allure. Which is better? Think it comes down entirely to how many resources one has. I'd prefer to see native, but developers are few...