Switched to Intellij and use other jetbrains product, never looked back
Switched to Intellij and use other jetbrains product, never looked back
Other than that, there s probably a way for you to propose a change, ive worked on the same nightmare you describe and, well, I was lucky enough I guess I could make enough changes to both stack it was possible to get either a light java subset running just the frontend to test, or make the js independent for testing, yes with a yarn soup lol, which is how I learned it in the first place I guess.
I don't know about them right now but before I resign, I told them "have you ever calculate how much time and money wasted by just restarting our app server for local dev? you probably should be worry about that because I believe you pay us to wait for app server comes online more than we develop a feature"
Another big problem they have to solve is how to make the crash character fits into the system with too many "models"
when we are still using monolith and using old deploy to one server, that would be easy. Then there is scaling issue and that's where the cloud came because really, when you have to manage a lot of things at once, it's better to let someone manage it for you and you can focus on your business logic.
Obviously, the practice wasn't perfect. A lot of "micronization" comes up instead domain driven problem but that's the problem on mostly people not the tech
You keep asking "why?" and only want one 'thing' to be 'actionable'... you will raise my frustration level. The root cause is an emergent property of understaffing, poor communication practices and a belief that everything can be reduced to a jira card providing sufficient context and understanding for a diverse audience with different skills and needs.
I feel like story of my move the Mac is not at all uncommon: in the very late 90s, when I was doing mostly consulting and not really any coding, my work life revolved around emails and office docs. Windows on laptops of the era was AWFUL -- long boot times, unstable/unusable device sleep, frequent crashes, etc.
I had a coworker using a G3 PowerBook, and his actual user experience was drastically better than mine by every metric (except, I guess, in that his Powerbook was significantly heavier than my super-sleek ThinkPad). Crashes were rare. Boot time was fast, but it mattered less because sleep actually worked.
I switched. Then the dot-com crash happened, and our company failed, and I hung my own shingle out -- and right about that moment, OS X happened.
My Mac went from being difficult to work on (for a LAMP-stack person) to being the IDEAL platform. I had a real bash prompt, on a machine that shipped with all the tools I wanted, and on which I could easily install most anything else (even if, early on, I had to build from source) -- and this same machine ran true Office, and had a host of really well-designed other applications and utilities that made my more productive and happier. It was a total win. And now, 20+ years later, I'm still here, typing on a Mac.
If OS X hadn't happened, then the work I had after the dot-com crash would've pushed me and a lot of other people like me to full-time Linux.
The symptoms is always generally poor performance after the system has been running a while (4h to a week, varies), usually with WindowServer using CPU cycles non-stop and UI that felt choppy across all programs.
This seemed to happen frequently after "opening many files", like doing some recompiling with Xcode for a few hours, or indexing a large volume with Spotlight. Rebooting helps temporarily.
Today I realized that data read/written since boot was about 1TB in a few hours on a brand new OS install, and I traced this back to the com.apple.Safari.History process. Somehow having bookmarks and previously using Safari 15.x caused a huge amount of I/O that wouldn't stop - the solution was to remove all bookmarks and reading list items. Performance was immediately back to normal, no reboot needed.
So just logging in with your iCloud id, you could be "importing" whatever performance problem you're having on a new install.
I recommend you reboot and take a look at your disk I/O stats - maybe this will help someone!