191–200 of 1001 posts
The Apache big data suite (Hadoop/Spark/Yarn/Hive/HDFS/etc). In several years of big data engineering work, I've believe I've seen only one application that couldn't be refactored into a simple multi-instance framework-free program. People use the big data frameworks as glorified distributed-job management tools, and the resulting systems are more fragile, more complex, more vulnerable to weird version compatibility…
Google Drive. I have no idea how a company with a search background produced software where it is impossible to find something.
Microsoft Teams. I am forced to use it (work) and it is missing really basic features that messenger software had in the 1990s like Push-To-Talk, real multi-window (even with the recent "pop-out" functionality), and its UI is all the worst modern trends. You cannot extend it or fix these issues (e.g. plugins, custom CSS styles, etc). Plus it is buggy, I keep not getting calls/messages/etc, and every time my computer…
Maven, since the dependency hell and that __every__ single project requires the same ugly boilerplate and yak shaving tasks, worsened if the infamous release plugin is used. Jira, because it's too slow and bloated from features you never use anyway. IntelliJ, because it freezes on every 6-7 autosuggestions, on projects of 50-80K LOCs.
Docker. I use it and love it every day in both dev and prod, but I also really kind of hate it. I'll keep my complaints short. There should not be a system-wide daemon. (Or any daemon). It should not require root at all (no setuid either). From outside the container, the container and its processes should be a single process (with threads). (Like glueing a bunch of processes together.) The containers should be nest-a…
I agree about the daemon. Podman is a daemonless alternative, though I've never used it myself. Strongly disagree about Docker Compose though - I actually really like the ability to compose a stack of different containers together with some simple yaml.
It meant that a bunch of my beta users suddenly had broken PhotoStructure configurations because their docker-compose implementation had received a minor update. Why require a version to your configuration file and not increment it on breaking changes?
I ended up tearing out the script that helped people create their own docker-compose.yml file, and replaced the installation instructions with an annotated call to `docker run`.
And don't get me started on how janky it is to update existing containers to new images without docker-compose: there seems to only be one third-party tool to assist with this automatically (lighthouse), but is essentially abandoned. I'd love to be wrong about this, please point me to other solutions if they exist!