![](https://lemmy.world/pictrs/image/833b7838-8526-4b13-a711-d2156171bcd1.png)
![](https://lemmy.world/pictrs/image/2e4870b7-4572-40b9-b469-63d1582317d6.jpeg)
Also back then you didn’t have SUV with size and weight of a freight truck and a flat surface in front. These days I think it’s less traumatic if someone just walks out of car and shoots you. You have higher chances of surviving.
Also back then you didn’t have SUV with size and weight of a freight truck and a flat surface in front. These days I think it’s less traumatic if someone just walks out of car and shoots you. You have higher chances of surviving.
Is it just me or people actually writing and using math daily never complain about this stuff? Only “it’s been a while I forgot the rules” crowd.
And quite a bit of inspiration came from Kurosawa’s movie Kakushi-toride no san-akunin.
Brainfuck would be my choice if we are making things harder for ourselves.
Yup. Welcome to the world of Java where such things are not only silly but encouraged.
Depends on amount of technical debt really. Sometimes rewrite is the only way. But in general fixing things can be done. It’s just matter of time, focus and effort.
Hardware is complex and mysterious enough without added complexity of an esoteric language.
Do people still think, after all this time and so many different languages, that there will be one language to rule them all? I mean technically you can drive nails with a rock, but you don’t see a carpenter using one. Right tool for the job. Always was, always will be.
Can be compressed very efficiently. I do dread the thought of writing a driver in brainfuck.
More to the point it refers to relation between elements and not the political correctness of the act. Just how the terminology is used in books, but reading one doesn’t imply you are a racist or condone slavery.
For a while, yes, you had to. Every new repo would be main
while old ones remained master
. Tools that default to a specific branch aside now you had to remember and check which branch you are merging into every time.
That’s like forcing people to have different color shoe laces and calling it good practice. In reality it changed nothing but forced a lot of people to work on solving issues with their scripts and automation tools for the sake of change instead of spending that time on writing actual code and fixing bugs.
This, sooo much this! People don’t realize that this change created a lot of unnecessary work to a lot of developers for no other reason than PR or to act smug about it. They solved slavery problem by renaming master
to main
equally well as they solved homophobia and transphobia by allowing people to specify pronouns on their profiles. Who the hell cares if you identify as tree sap. However many do care if your code sucks or doesn’t follow coding style.
I can’t wait for asshats to start calling for gender fluid connectors. What’s that, male 3.5mm connector, did you just assume my connectors identity?
How can you? I would understand if you have to, but Mercurial/Git approach is so much more flexible.
This is a huge pain in the ass for us as well. We have some automation with development environment and deployment of certain scripts. We had to redo a good chunk of them to first test whether there’s main
or master
. And it took us a long time to find stragglers that weren’t as frequently updated but would suddenly break deploymend after minor changes.
Had to refresh my memory, it’s been a while. They didn’t change branch on existing projects, but they did change it on new repos to main by default. Our tools indeed created repositories and configured everything for the developer automatically. However GitHub’s policy meant that you had to either change the tools to detect whether they are working with old repo or new, or go to every new project after automatic configuration fails, configure default branch and then rerun the tool. Same thing then happened to few of our tools that were used for CI.
All in all they made more work for us for no reason other than be smug about it and it changed exactly nothing.
They forced the change. If I wanted otherwise, I had to go and specify per project that master was the default branch, and there were many of those. And whole “insanely fragile” is just nonsense or are you trying to tell me people have conditions and scripts that detects what’s the default branch and use that instead of assuming default name that hasn’t changed for 15 years would remain default?
Whether you like Linus or not, whatever is released to users stops being a bug and becomes a feature. Not breaking user-space is a must. Instead they achieved nothing and caused a lot of unnecessary work to a lot of developers.
Oh, how upset I was by that decision. I still call out GitHub online every now and then thanking them for solving slavery by messing up my deployment scripts and development environments.
Some are. Others are stacked like this: