221–230 of 294 posts
I for one think it's great that people are willing to make things a little more accessible for more people. If people want to be part of our community of developers I think it's great that these organizations listen to people who might have a problem with certain terminology. Even though I don't have a problem with those terms, I think it's still worth evaluating if they're worth keeping if it makes it harder for som…
I for one think it's great that people are willing to make things a little more accessible for more people. If people want to be part of our community of developers I think it's great that these organizations listen to people who might have a problem with certain terminology. Even though I don't have a problem with those terms, I think it's still worth evaluating if they're worth keeping if it makes it harder for som…
Earlier quoted context omitted.
Seeing black / whitelists discussions I always wonder, if white color is racist also by containg all wavelengths, while black suffers by absencing visible light.
>if white color is racist also by containg all wavelengths, while black suffers by absencing visible light. This definition of white/black colors is context dependent. In some contexts white is defined as a combination of colors, and black is absence of colors. In some contexts (e.g. art) white is defined as absence of colors, and black is a combination of colors.
Typical computer displays generate colors by adding light of different wavelengths. However, paint pigments generate colors by absorbing light of different wavelengths.
Whether a system emits light directly, like a computer screen, or reflects incoming light, like a painted canvas, the perception of color is still determined by the wavelengths of the photons reaching the observer.
Yeah, I get it. It is a necessary change just so you take this of the table and not deal with the sporadic complaints that would come. Keeping the 'master' or 'master-slave' (in context of HA) terms just isn't worth potentially offending someone, or losing a sale, or getting bad press. We changed our verbage a couple years in our product as well just for that reason (Master-Slave to Primary-Secondary). The previous c…
Yeah, I get it. It is a necessary change just so you take this of the table and not deal with the sporadic complaints that would come. Keeping the 'master' or 'master-slave' (in context of HA) terms just isn't worth potentially offending someone, or losing a sale, or getting bad press. We changed our verbage a couple years in our product as well just for that reason (Master-Slave to Primary-Secondary). The previous c…
I don't mind so much when the renames make sense or are more comprehensible… master to primary for DBs, master to main for git. Indeed whitelist/blacklist is just ridiculous overreach, what can you do. But Github went way too far by aggressively pushing devs to rename their own local master branches to main. This caught me by surprise and I almost accidentally renamed the branch of one of my previous clients. https:/…
Since we're talking about naming branches, what are your preferred names for branches ? I like 4-letter names: - `main` points to the last release for libraries (along with tags for history) - `prod` points to production in deployable projects (not libraries) - `next` is the development branch for the next version - `deps` is a temporary branch for dependency updates, squashed and merged regularly onto `next`
Good for you that you found something that works for you. But why the random length restrictions to 4 chars, seems kind of outdated? Also, how does using only a "next" branch for development scale for teams (maybe using a fork-based workflow?). While I use a similar approach like yours on my personal projects, I still prefer the widely known and battle proven Git-Flow when working on agile teams: - master - develop (…
Yeah, I get it. It is a necessary change just so you take this of the table and not deal with the sporadic complaints that would come. Keeping the 'master' or 'master-slave' (in context of HA) terms just isn't worth potentially offending someone, or losing a sale, or getting bad press. We changed our verbage a couple years in our product as well just for that reason (Master-Slave to Primary-Secondary). The previous c…
Sounds like justification for capitulating to the woke nonsense and cancel culture to me. >....feels like we're now just looking for things to be offended by Exactly, no one should have ever listen to this nonsense. There is no end goal here being offended is the goal. Just imagine the millions of man-hours* of non-productive work this will cause over the next decades. *nothing here lol
Nop, it’s a mean. Being perceived as a victim is very bankable these days, so the craze will continue with more people being offended and asking compensations (often monetary) for it.
Earlier quoted context omitted.
It reinforces black is bad and white is good. Also, deny list and allow list are more precise terms anyway.
>Also, deny list and allow list are more precise terms anyway. Are they? Black/whitelist feels way more natural to me. You can also say things like "blacklisted this ip" instead of "adding to the deny list" or something.
Yeah, I get it. It is a necessary change just so you take this of the table and not deal with the sporadic complaints that would come. Keeping the 'master' or 'master-slave' (in context of HA) terms just isn't worth potentially offending someone, or losing a sale, or getting bad press. We changed our verbage a couple years in our product as well just for that reason (Master-Slave to Primary-Secondary). The previous c…
This will absolutely cost customers.. The rest of the world is getting fed up with the US. Most of the world is not as deeply racist and the US... Master is not associated with anything negative here.
Yeah, I get it. It is a necessary change just so you take this of the table and not deal with the sporadic complaints that would come. Keeping the 'master' or 'master-slave' (in context of HA) terms just isn't worth potentially offending someone, or losing a sale, or getting bad press. We changed our verbage a couple years in our product as well just for that reason (Master-Slave to Primary-Secondary). The previous c…
That’s a lot of words to say “this is a good change and nothing has been lost.” Incredible that this post has almost 200 comments.