• 1 Post
  • 386 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • China also has an established, robust, and technically advanced manufacturing sector. That honestly is the biggest thing keeping manufacturing there. Things made from raw resources could be moved easily but the lower labor costs would be offset by the decreased demand due to most of their customers being back in China.

    Things are even worse for anyone making something that requires manufactured components as all those suppliers are in China so now not only are they taking a hit for reduced demand, but also the headaches of having to import their components from China just to build anything. Labor would need to be ridiculously cheap compared to China for that to start looking like a good idea.



  • My job has a 3rd kind of complexity, non-essential complexity, which is like essential complexity in that it comes from the business domain, but isn’t actually required. It’s non-technical decisions about how our apps and services must function that introduce all our complexity and massively complicates our code bases. At one point we literally have to attempt to predict the future because they adamantly refuse to simply ask the customer what they’re planning.


  • The crux of it is that it allows for commercial use without needing to distribute the source code. Whether that’s a good thing or not depends on who you ask. There’s basically a continuum for open source software with GPLv3 at one end and MIT at the other.

    GPLv3 guarantees that corporations can’t play games with patents or weird DRM to hobble an open source library and tie it to their closed source product. A lot of corporations will specifically bar employees from using GPLv3 code out of fear it could force them to open source their proprietary code as well.

    At the other extreme you’ve got MIT which basically says do what you want with it. Fork it, embed it in your projects, sell copies of it if you want. Anything goes as long as you include a copy of the MIT license along with your software.

    Rust tends to get a lot of commercial usage so GPLv2 or MIT tend to be chosen over GPlv3, and between them most companies feel more comfortable with MIT.


  • I think it’s more that most people just aren’t aware of any equivalent alternatives, or in some cases like where there literally aren’t any alternatives. Look at phones, both Apple and Google suck and their mobile OSes are terrible but what’s the alternative? Sure there’s a few Linux phones out there and that’s almost an alternative but it’s not there yet. You could go with a “dumb” phone, but for most people that’s not going to work. So you pick your lesser evil and bitch about it whenever the latest round of enshitification hits.

    If you asked most people what alternatives exist for Spotify they’d probably say Pandora, and maybe Apple Music or Youtube Music and then struggle to come up with anything else. The better alternatives are suffering from a massive discovery problem.






  • I think part of the problem is that “good” UX isn’t a single thing but a continuum. It’s very dependent on the skill level of the user. Often what makes a good UX for a newbie is a bad UX for a power user and vice versa. OSS tends to attract power users and particularly the ones working on some software in a particular area tend to be domain experts. That in turn can lead to designs optimized for very advanced use cases that end up being frustratingly opaque to an “average” user or even worse a newbie.

    Blender is an excellent example of this. It’s regarded as one of the best 3D programs out there but it’s far from a simple piece of software to pick up. What saves it is that all the commercial alternatives are just as obtuse as it is and so the ground level expectation is that it’s going to be complicated.

    Likewise many OSS and Linux tools expect or even require CLI usage which while great for power users putting together scripts and pipelines are often opaque and unintuitive to someone who is still learning the domain.

    This focus on power users leads to turning newbies away and funneling them towards the commercial offerings where they then get used to their quirks and limitations of those apps so that when they do eventually become power users the quirks and limitations of the OSS alternatives feel strange and off-putting to them.


  • File format standards certainly, and OSS generally embraces those (at least if they’re non-proprietary), but UI doesn’t have to be standardized. On the other hand though not everything needs to be a unique snowflake. UIs should take the things that work well and experiment with what doesn’t.

    Lets also not pretend that proprietary apps don’t screw around with UI design just as much. I can’t count how many times now Microsoft has redesigned the UI of something that was perfectly fine and didn’t need redesigning only to end up making it worse.