Alternativeto.net is a good resource for finding alternatives by filterable tags including platform! Also wine and proton have come a long ways, many windows apps work just fine in a small wine or proton container.
Alternativeto.net is a good resource for finding alternatives by filterable tags including platform! Also wine and proton have come a long ways, many windows apps work just fine in a small wine or proton container.
While it may be true that the master branch is more akin to a master record, not everyone knows the nuance and quite frankly it doesn’t matter, if it makes people uncomfortable then it shouldn’t be a problem to accommodate a simple change, most of the tech world has already done so. Computers used to have a literal slave/master relationship with hardware components and control systems and we moved past that just fine despite still having controllers and actors everywhere.
It was someone ranting about the many hours and days of lost productivity and cost of manually switching over 70+ legacy build pipelines all because of a branch name change. Also lots of condescending and insulting language from someone who thought their stubbornness and “standards” meant they were better than everyone else. Honestly I just probably set them off in my first message and they wouldn’t let it go, leading to increased levels of ranting and insults from them attempting to spout accomplishments while detailing their failings in the same breath. Admittedly that above description is a bit belittling from my end, I’m just annoyed they couldn’t keep their messages up for all to see.
I still stand by the opinion that changing branch strategies, names, or targets should not be a multi-hour multi-resource process and if it is, that’s a failure of the systems engineers / ops who put together such a plan. It’s possible to have CI/CD pipelines that run for years on end attached to critical infrastructure while being flexible enough for such simple config changes and maintained by one engineer.
Again, you’re conflating your own stubbornness with correctness and that just ain’t how it goes. Branch names are frivolous. So much so that changing the strategy or retargeting a branch one time shouldn’t be such a nightmare for your pipelines that you have to pretend like you’re the big dick on campus spouting accomplishments when someone mildly suggests there’s a mistake in your thinking. Look inward if you’re so upset by this that you have to make up irrelevant insults in a vague attempt to protect your own ego, then go fix your pipelines to make it easier to do for the next person after you’re gone.
lmao nothing you’ve said has anything to do with “Main is more concise and less problematic”. Just because you created more work for yourself by having 70+ pipelines that need to be rewritten for a branch name change doesn’t mean it’s less concise or more problematic. It means you messed up by not having a pipeline capable of such a basic feature – generalized targets with a separation of concerns. Standards change, requirements change, so do build pipelines. Being stubborn is not a reason against changing colloquial terms out of respect and growth in understanding.
The only statement in your ridiculous rant that has any validity is that of your legacy pipeline configurations. But pipelines need to be updated and validated semi-regularly and should be generalized to begin with, so it’s not really any good point that your legacy pipelines cannot handle a default branch name change like modern pipelines should.
Swap main and master in your comment and it reads the exact same with all the same shallow justifications.
No Money by Wild Ones 2017. This song is really good but the whole album just has this cohesive vibe that I wish more people knew about.
My only point was to explain that proxmox is great free software because it supports both simple virtualization needs, such as having several different VMs or containers running on one headless system with very little overhead, and complex multi-system setups that include multiple machines running proxmox and clustered together for both reliability and redundancy with distributed services and applications.
Off the top of my head from daily use;
Two standout ingredients: avocados and horseradish.
There’s a possibility we could get new or more complex crystal structures by processing materials in space, getting more resilient or better properties to then be used in actual chips after it gets back to earth. Space factories will be more for material handling and processing than actual fabrication (minus deep space ship construction).
Also the amount of management that doesn’t understand the difference between coders, programmers, and engineers. All quite different in scope and all completely necessary for at-scale production.
Any performance hit on the sandboxing? Even just a few ms latency?
Budget. Learn about good vs bad debt. Never live above your means and maximize savings and investments as early as possible. Time is your greatest asset when you’re young, there’s plenty of headroom in a comfortable lifestyle when you have an emergency fund and no outstanding debts.
Does relearning how to read sheet music and basic chord shapes on the guitar every other year count? One day I’ll figure it out.
Just add milk until the entire pile of cereal starts to lift. Usually when the milk reaches the base level of the cereal itself.
My only gripe is the lack of ChatGPT and search internet for answer options. I want to use both in various situations when Siri doesn’t get the answer directly.
I’m so annoyed that the 500 price increased so drastically yet doesn’t include PoE or NVMe support components despite having unpopulated pads on the board directly for “flexible future designs”. I’d prefer a $40 increase over the 400 to include these components instead of $20 more for blank spaces and no guarantee of making it work DIY style. Hopefully the 500B variant ends up with these corrections.
Exactly. This is a non-story and they already have a built in integrations system for escalating / customizing requests.