Problem in some teams are the respective audiences for the commit activity v. the ticket activity.

The people who will engage on commit activity tend to have a greater common ground and sensibilities. Likely have to document your work and do code reviews as the code gets into the codebase and other such activity.

However, on the ticket side you are likely to get people involved that are really obnoxious to contend with. Things like:

• Getting caught up in arguments over sizing where the argument takes more of your time than doing the request
• Having to explain to someone who shouldn’t care why the ticket was opened in the first place despite all the real stakeholders knowing immediately that it makes sense.
• Work getting prioritized or descoped due to some political infighting rather than actual business need
• Putting extra work to unwind completed work due to some miscommunication on planning and a project manager wanting to punish a marketing person for failing to properly get their request through the process
• Walking an issue through the process to completion involves having to iterate through 7 states, with about 16 mandatory fields that are editable/not editable depending on which state and sometimes the process is stuck due to not having permission because of some bureaucratic nonsense that runs counter to everyone’s real world understanding.

In a company with armies of project managers the ticket side is the side of dread even if the technical code side is relatively sane.

I suppose it doesn’t have to be exclusively masculine. I’ll take what I could get if it could coerce some of these “must be manly” folks to actually aspire to good attributes versus what they seem to think masculinity means right now…

Yep, and then have to opt out all over again the next week when an update decides you need to verify you really mean to opt out again…

And if you managed to not have an MS account when you installed, interrupt your login and say “you cannot proceed like you have been doing for the past year without adding an MS account now”, and then look up how to get out of that dialog without doing the MS account…

You mean the man who can’t make his wife wet, and loudly proclaimed to the world that women don’t get wet down there?

Basically when I open up an MSOffice file, if there’s anything vaguely complicated it will not look like the way the office user intended.

Yeah, but the O365 crowd is pretty much 99% tied to the cloud anyway they slice it (MS really wants you to work exclusively in OneDrive).

LibreOffice may be able to handle it’s own documents fine, but interoperate with an MS Office user and it frequently is unable to be consistent.

The main hiccup for hardware support is GPU support, and as a side effect of the bigger business being in messing with LLMs and that use case preferring Linux, GPUs are getting more Linux attention.

For example, nVidia drivers went years and years with a status quo of “screw open source, compile our driver and deal with the limitations”. Only after they got big in the datacenter did they finally start working towards being fully open in the kernel space (though firmware and user space still closed source, but that’s a bit more managable)

Yes, it’s only a fraction, but most of the rest is going to SaaS through web browsers or mobile apps, because companies get to control and force subscriptions that way, but has a side effect of targeting a browser as a platform rather than an OS. Gaming in browser is more in the pain point of browsers, so it’s a use case that demands OS.

Sadly, LibreOffice isn’t up to the task.

However, more and more this stuff is done in browser anyway.

It’s funny because while some of it has to do with work to make Linux desktops better, a non-trivial amount of it is how worse Microsoft has made it to deal with Windows.

The display can get longer when dealing with porn?

Generally speaking, these platforms are not flashable unless they can boot a flash utility, assuming that whatever prior firmware is running is at least in good enough shape to boot to an update environment.

There are designs to be robust and accessible even in the face of all this, but relatively rare, effectively unheard of in laptop market. Even some of those emergency recovery environments may be more limited than you would like to repair this sort of thing.

On top of other responses, lots of folks are saying the conservatives are coming to power in Canada. Those conservatives would hate upsetting their advantage by contending with what would be an overwhelmingly liberal population.

Canadian conservatives would hate it. It would foul their apparent momentum in also getting control like the conservatives did in the US.

Unfortunately, despite electing a democratic governor, lt governor, and AG the state otherwise went full maga in voting choices.

Which is why this would really suck for a lot of folks. Today they may not quite get their preferences at home, but at least other states are keeping it competitive and may mitigate things. If those states left, then everything falls into a fanatical Christian fascist ethno state with no impediments.

I think another complicating factor is that military folks are moved around so much that they wouldn’t have the same loyalty to wherever they happen to be. So it’s likely to be quite bad, just staying that generally the military itself would split.

As to technically reporting to the president, well all bets would be off, since the act of secession is already a rejection of the current government and rule of law. There wasn’t any legal framework for the revolutionary war nor the civil war to happen, and yet they did.

Despite all this technicality, I’d really not want to see the nightmare of how this would play out in practice. Of course I could not see it happening until the GOP got too greedy and fully shut down elections or go too far away from free and fair elections. Ultimately confidence in elections serves as a release valve for anger with the government, and messing with that invites disaster.

Yeah, I need something like an OnlyFoes where people pay to inflict my content on someone they didn’t like.

Also the kernel makes those variable immutable by default now, except the well known standard ones, so even for buggy UEFI this is mitigated nowadays. Just pointing out it came from a once legitimate space as a consequence of “everything is a file in a monolithic file namespace”. Which on the one hand is bad if someone uses rm with all sorts of flags to overrule the “you don’t want to do this” protections in the utility. On the other hand what you accidentally managed to do in Linux represented a problem that windows malware could have exploited.

UEFI defines a structured way to have data shared with OS as read write variables, including the ability to create, modify, and delete variables that UEFI can see.

However, some firmware used this facility to store values and then their code assumed the variables would always be there. The code would then crash when it goes to read a deleted variable and not know what to do. The thing is deleting those variables per spec is a perfectly valid the due the OS to do, but firmware was buggy and the bugs not caught because normally OS would not bother those variables except for a few standard popular ones, like boot order.

While I agree it would go poorly, the way this would happen in theory is that the state would take their contributions to the federal military with them, and for California that would be a pretty sizeable chunk. So it’s not just local police and national guard.