MooseBoys @ MooseBoys @lemmy.world

Posts

7

Comments

358

Joined

2 yr. ago

“Backwards compatibility” is a totally different thing from “cross compatibility”. Of course proprietary software is going to be less cross-compatible.

never break user code

That’s a fine mantra to have but is rarely true in practice. I’ve seen way to many needlessly breaking changes in open-source libs that are explained away with “users can just pin the old version until they update their code”.

To be clear, the linux kernel itself is almost never the cause of the breakage per se, but some other library often implementing one of the APIs it defines. Often the reason for the breakage is under-specification of the original API, for example including a uint32 flags field that is not checked against a known set of valid flags, and inevitably ends up populated with vendor-specific (and often conflicting) usages.

As much as API design is about exposing the functionality you want, it also involves avoiding exposing functionality you dont’t want to expose. Open-source software often omits that critical design consideration, waving it away under the false virtue of “openness”.

It’s not the spectrum; it’s Bluetooth vs fixed-pair generic RF.

Have you ever looked at linux kernel CLs? Many of the more substantial ones come from someone @intel.com, @microsoft.com, @google.com, etc.

more than motels on the side of the road

Not exactly; in that area, a Motel 6 costs around $300/night. California, man.

Wormsign spotted in D1.

Self-signed certs are not viable for general use because they’ll generate a browser warning that “Joes Liquor Co is not a trusted Certificate Authority” that will scare off 99% of users. And wildcard certs still need at least one specific domain, e.g. *.joesliquor.com. The only way I can imagine this working is if the vendor was handing out separate servers on client.vendor.com and giving each of them the same SSL cert for *.vendor.com.

Yep, as of Windows 10 there’s no longer a 30-day activation timer. You can run Windows for free indefinitely with only a couple minor inconveniences like the inability to change the desktop background.

They were issuing a single SSL cert to all of their clients.

How does this even work? Doesn’t the domain admin send their own CSR? Even if your company was serving as that admin, a single cert only works for the domain to which it’s assigned, so how could it be reused for multiple clients?

I think the majority of people who demand software cost $0 are hobbyists who write code themselves, but it bothers them that not all developers share their passion. I’ve written a little code and some 3D models that I’ve released under Apache2 / CC-BY, but the vast majority of the code I’ve written in my life was done in exchange for a paycheck.

It probably has. XP usage was almost entirely pirated copies in China. Then PUBG came out and the entire country upgraded to pirated copies of Windows 7 to play it because XP wasn’t supported.

Even code is not free. Any decent developer writing code does so with an opportunity cost. If those developers want to provide that software to others for free, that’s great. But it still costs their own time and skills that they could be monetizing. For many people it’s a hobby.

amdgpu: segfault in gem_free

Figure 1: Human discovers that hosting a web service for hundreds of thousands of users is expensive.

If the client is blocking OS fingerprinting by returning generic navigator.appVersion and userAgent values you should probably just assume Linux in the first place.

Wayland VRR works out of the box with most popular DEs like KDE or Gnome

Neither KDE nor GNOME even detect either of my 144Hz panels as capable of it. Logs indicate that amdgpu failed to parse their EDIDs. Forcing the mode with a kernel command option causes link training to fail altogether. Meanwhile, the exact same system, panels, and cables running Windows works perfectly.

AMD experience was nothing but flawless

See above. I’ve also tried NVDIA and had the same experience - neither HDR high-refresh panel are usable in Linux, but both work on Windows.

Plus there’s the fact that about 50% of the time, when the panels power off from idle, they never come back on. This is apparently a known issue on AMD that’s been around for years but nobody seems to care to fix - everyone just says to disable screen blanking.

And don’t even get me started on heterogenous DPI.

FL ends up churning out “educated professionals”

Who’s going to educate them? If that happens, a bachelors degree from USF will be worth about as much to an employer as one from DeVry.

concerned murmurs

Dumb. But I also thought smartphones without keyboards were dumb and look where we are now.

Is this a joke? X can’t do VRR at all and I have yet to find a Wayland DE that doesn’t require a separate server pinned to each monitor. And neither support HDR.