• 4 Posts
  • 1.37K Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle



  • It can potentially allow 1 worker to do the job of 10. For 9 of those workers, they have been replaced. I don’t think they will care that much for the nuance that they technically weren’t replaced by AI, but by 1 co-worker who is using AI to be more efficient.

    That doesn’t necessarily mean that we won’t have enough jobs any more, because when in human history have we ever become more efficient and said “ok, good enough, let’s just coast now”? We will just increase the ambition and scope of what we will build, which will require more workers working more efficiently.

    But that still really sucks because it’s not going to be the same exact jobs and it will require re-training. These disruptions are becoming more frequent in human history and it is exhausting.

    We still need to spread these gains so we can all do less and also help those whose lives have been disrupted. Unfortunately that doesn’t come for free. When workers got the 40 hour work week it was taken by force.






  • They add a lot of overhead and require extra tooling to stay up to date in a maintainable way. At a certain scale that overhead becomes worth it, but it takes a long time to reach that scale. Lots of new companies will debate which architecture to adopt to start a project, but if you’re starting a brand new project it’s probably too early to benefit from the extra overhead of micro architectures.

    Of course there are pros and cons to everything, don’t rely on memes for making architecture decisions.


  • It’s just not worth it until your monolith reaches a certain size and complexity. Micro services always require more maintenance, devops, tooling, artifact registries, version syncing, etc. Monoliths eventually reach a point where they are so complicated that it becomes worth it to split it up and are worth the extra overhead of micro services, but that takes a while to get there, and a company will be pretty successful by the time they reach that scale.

    The main reason monoliths get a bad rap is because a lot of those projects are just poorly structured and designed. Following the micro service pattern doesn’t guarantee a cleaner project across the entire stack and IMO a poorly designed micro service architecture is harder to maintain than a poorly designed monolith because you have wildly out of sync projects that are all implemented slightly differently making bugs harder to find and fix and deployments harder to coordinate.









  • Depends on which part is altered. Lots of Linux distros are just curated collections of software, drivers, and configuration. You can easily achieve your OS goals without touching the code of the base distro at all. If they didn’t need to modify the base code then there’s nothing to distribute back. That would be like distributing your personal OS power user config settings. If you’re not touching source there’s nothing to contribute.



  • I didn’t know how much work they put into customizing it, but being derived from Android does not mean it isn’t custom. Ubuntu is derived from Debian, that doesn’t mean that it isn’t a custom OS. The fact that you can run the apk on other Android devices isn’t a gotcha. You can run Ubuntu .deb files on other Debian distros too. An OS is more of a curated collection of tools, you should not be going out of your way to make applications for a derivative os incompatible with other OSes derived from the same base distro.