They might have set up the user agreement for it. Stackexchange did and their whole business model was about catching businesses where some worker copy/pasted code from a stackexchange answer and getting a settlement out of it.
I agree with you in principle (hell, I'd even take it further and think only trademarks should be protected, other than maybe a short period for copyright and patent protection, like a few years), but the legal system might disagree.
Edit: I'd also make trademarks non-transferrable and apply to individuals rather than corporations, so they can go back to representing quality rather than business decisions. Especially when some new entity that never had any relation to the original trademark user just throws some money at them or their estate to buy the trust associated with the trademark.
One time, I arrived at a small store as an employee was finishing their smoke break, exchanged friendly words as we both went towards the door. In that moment, I realized that if I open the door, it'll be right in his way and I paused, unsure about how to handle it. He ended up opening it for me, but the whole thing felt awkward as fuck, like my pause was because I was waiting for him to open it for me. Easily the worst door opening experience I've ever had. I'm a dude btw.
I really don't understand people who want that. It's so infantilizing to have someone else do basic shit for you, especially if you need to wait for it. It crosses a line from basic politeness to learned helplessness and is often a motivation for weaponized incompetence, so I also don't understand the people who do those things for a partner that demands it. It would be an instant loss of interest for me.
It also requires not being dominated by people who think lack of options is a feature they can exploit and would happily destroy society if it meant that whatever was left was more dependent on them (partially to profit from it, partially to hold the keys to control who can access it and how).
Oh yeah, I understand the sentiment entirely. With so many dark patterns dominating the world we live in because we live in a society that decided to embrace greed instead of seeing it as a primary motivator of evil, I can't blame anyone that looks at the state of things with suspicion anytime there are downsides. And while it isn't realistic to expect as good audio from a built-in system as a separate dedicated audio system, I do think it's ridiculous that the standard is so dysfunctional that you either can't understand what people are saying or explosions are way too loud. Especially in this digital world where mixing separate audio channels isn't a difficult task. Streaming services should just have a stereo and mono version of the audio that is mixed well for that format if it is actually a harder problem than I think it is.
Some of it is practicality, but I don't doubt that greed also plays into it. I mean, even on the modularity side, I don't have the option of easily finding a TV without any speakers at all, or a TV without smart features that a) aren't as good as other options I have to access those features and b) were actually thrown in to spy on data, as your previous comment mentioned.
So yeah, I don't blame you at all for being suspicious of the companies that absolutely are trying to fuck their users because their real customers are data buyers, even if I do prefer my soundbar.
I appreciate TVs not wasting resources on putting decent speakers in it that I'll never use because I did buy a soundbar over a decade ago that has decent sound and has outlasted the TV I bought it for. Plus TVs are so thin these days that they probably can't even drive decent bass, and the speakers they do have are rear facing, so they don't even drive the sound towards you.
Sucks that they don't and that they don't do the open source thing so that the community could improve the quality. Is it because of wayland or something else that it isn't fully compatible?
Yeah, when you're compiling from source code, it's much easier to add in ARM support. Kernels do need to handle more hardware-specific stuff, like interrupt handling, context switching, feature enablement and the like will likely need custom ASM code and might have different parameters/events to handle. But at the user level, you can often compile for ARM by just changing a few command line arguments and it'll be fine as long as you don't rely on inline ASM and have ARM versions of any libraries you need.
You still might need to do some adjustments for specific behavior differences when it comes to concurrency and atomicity of operations. It didn't surprise me to see that the previous attempt to make an ARM ReactOS didn't support multi-threading, because trying to enable it was probably an unreliably buggy mess with race conditions all over the place.
Guess I'm one of the few. No idea what to expect, watched it because it was Hal. Then some guys make fun of his disabled son and he walks out of the store while his wife is hoping he'd do something, and I thought "ah, shit, this won't be any good, Hal is a coward in this one". And then he walks through the front door and punches them out, and they hooked me with that scene because Hal was a badass. And he kept being a badass, to the point where I didn't even really care about the morality (first viewing at least, I hated him the second viewing, though he's still entertaining to watch) and just wanted to watch Hal take over or burn down the world. It's a wild ride, even after multiple viewings.
Better Call Saul is even better, though I found that one dragged a bit at the start and it took a couple tries to get into it.
They tried to jump right into the "popular thing drives high demand for popular spaces in popular thing" and skip the whole "make thing popular" step, banking on their name and people thinking it'll make them a ton of money.
Though tbh I can't say that was necessarily the wrong move (at least not if their entire goal is maximizing gains), since it wasn't going to get popular like they wanted in the first place, so skipping that step and going straight to fleecing those dumb enough to throw money at it might have made the most sense.
That said, I think they put more money into it than they got out of it, so I doubt that it was deliberate. Zuck probably just thought if he paid people to make it, users would just flock to it and it would be as popular as fictional VR worlds are, despite missing the tactile VR system they tend to use or the whole "VR world is popular (or the focus of everyone's life)" being a plot point rather than the consequence of someone building the world and people choosing to spend their time and money there.
Also, I'm in the demographic that probably would have been the most interested (like as a user of VR, not someone looking to just make money from it), but their offering didn't even raise enough curiosity for me to check out what they made. There is an anti-meta bias in play, but even if it had been offered by a separate entity, I still wouldn't have been interested because it sounded enshitified from the moment of concept.
Running another uarch is a whole new level of complexity vs just running on a different OS but with the same uarch, especially if concurrency is involved because translating from one instruction set to another can break atomicity assumptions that concurrency depends on to maintain coherency. You'd need to do thorough analysis of the code to determine where special care is needed, and even then, it won't be trivial setting it up in a way that avoids deadlock because you have to understand what the threads are doing before you can say if it's safe for one thread to wait for another (since they could end up waiting for each other).
Whereas running code meant for a different OS just requires implementing that OS' API (and behaviour, possibly including undocumented behaviour some code relies on, which can vary from application to application, hence windows compatibility modes where they add a translation layer themselves). Not saying this is trivial, but compared to the above problem, it kinda is.
Not that ARM support is impossible, just if they manage that, it will be proclaimed loudly, not something that requires digging. If they don't say it supports ARM, just assume it doesn't.
Would you like some caviar and the finest champagne with that order of plural potato?