Jump to content

Sauron

Member
  • Posts

    28,056
  • Joined

  • Last visited

Awards

Profile Information

  • Gender
    Male
  • Location
    Mordor
  • Interests
    Rings. And elaborate, painful ways to kill hobbits.
  • Biography
    Read The Silmarillion
  • Occupation
    Lord of Barad-dûr, Gorvernor of Mordor until Morgoth returns
  • Member title
    Lord Of The Rigs

System

  • CPU
    AMD Ryzen 3900X
  • Motherboard
    Asus STRIX B550-F wifi
  • RAM
    2x16GB G-Skill Trident Z 3600MHz CL16
  • GPU
    Asus Dual RX 6700XT (OC)
  • Case
    Corsair Obsidian 800D
  • Storage
    Sabrent Rocket Q 1TB + Samsung 850 EVO 500GB + WD black 1TB 7200rpm + random seagate 1TB 7200rpm
  • PSU
    EVGA Supernova G2 850 Watt
  • Display(s)
    LG 27UL650 + Philips 23IE + LaCie 324 (frankenstein surround)
  • Cooling
    Gelid Phantom Black
  • Keyboard
    CMstorm quickfire XT - MX brown switches
  • Mouse
    Logitech G400s
  • Sound
    Asus ROG Orion headset + cheap logitech stereo speakers (hey, they work fine!)
  • Operating System
    Arch Linux, MSX Pro

Recent Profile Visitors

38,720 profile views
  1. Could have been useful as a built-in development tool if done differently, as for actually using android apps though... probably not that useful. I've used bluestacks for a couple of things but realistically I could just as easily have used a native program, it's been more useful to test some open source apps before sideloading them straight into my device.
  2. in the roughly 2010-2018 time frame consumer cpus barely got any better, especially in terms of game performance (partially due to the console generation of the time relying on relatively slow CPUs) so it really didn't make much sense to upgrade your CPU regularly. Nowadays if you have a cpu from those times it's probably holding your system back.
  3. As I said, experimental support. It also only works on wayland afaik. I'm sure it can be made to work if you're willing to spend the time on it but it's quite restrictive and certainly not something you can expect of someone who just wants to use their computer out of the box.
  4. You should never trust computers to do anything. If a computer is doing a dangerous or mission critical task it should always have redundancies and external safeguards. If anything, computers have become less reliable and predictable as the complexity of hardware and software has skyrocketed; while at the dawn of computing you could have a comprehensive understanding of everything going on with a given machine, today you have to place your trust in millions of lines of code written piecemeal by thousands of people who may or may not have documented any of it, running on proprietary and extremely complex hardware. That doesn't mean that we should go back to having humans do what we entrust computers with today, but a healthy degree of suspicion should be maintained.
  5. IMO the main and most relevant reason not to is software support. This doesn't just mean games, but also (and notably) drivers. I answered a post yesterday where OP was asking about HDR support to tell them that it pretty much doesn't exist on Linux aside from very experimental implementations. GPU drivers are mostly inferior to their windows counterparts (through no fault of Linux or distribution developers and maintainers, but nonetheless it is the case) and on occasion you run into situations where they just make your desktop unusable. Most of the other reasons people give are either misinformed, a product of habit or personal taste. That's not to say that habit and personal taste aren't valid reasons not to change, but they're not really something that can be addressed by developers; either you're willing to spend a little time adapting to something you're not used to, or you're not. This is not a good metric. Unused ram is wasted ram and caching is used when possible to speed up your system, both in Windows and in Linux; this doesn't mean that that memory will not be available if you open more programs that have active need for it. "Bloat" has become (and possibly has always been) a useless buzzword that today seems to simply refer to "using system resources", no matter what those resources are being used for.
  6. Which is why I want them to be forced. That's not their criterion, and their scans as mentioned do not work very well. Yes, that's how the law should work. Instead Apple blacklists developers based on whether they abide by their own, non legally mandated, terms of service. It's absolutely a security risk because those APIs give you access to operating system functions that a non-root app should not have, at least not without explicit user consent. This has been used in the past to bypass iOS' privacy guards and sandboxing, for example. Not to mention this means that any obfuscated code, even malicious code, will not be detected.
  7. Partially, but given recent developments their rules seem to be "we must like you personally and you must not in any way prevent us from making money". Despite the propaganda their security checks have never been very good, even within the app store... if you obfuscate your hidden API calls your app will just breeze through the filter with apple being none the wiser. Or they could just make this opt-out with a big ol' warning that disabling the restrictions exposes you to risk. As you mentioned, idiots will get phished and scammed anyway through regular old websites. Or, they could have a collective verification system that doesn't entirely depend on Apple's interested opinion, and their mediocre security checks, determine whether an app should be allowed. Except here it's also an abuse of monopoly power. As an app developer you can either play ball with them and accept any condition they impose or lose what, a third of your potential market? That's mob level behavior.
  8. support for 10 ends in almost exactly 19 months. There's no sugar coating this, even if you can get all of this to run it will not run as well as on Windows. If all your main use cases require Windows only software then your Linux experience will inevitably be sub par. HDR support in Linux is mostly absent with the exception of some very experimental implementations in specific desktop environments; don't count on it ever working. If you really want to quit windows and have a decent experience you should look into which Linux native software you could use instead of these programs. Wine, proton etc. should be seen as crutches to run a couple of programs or games that aren't available for Linux, not the main use case.
  9. *Gets to the benchmark* *14% of issues resolved* ok dude I'm quaking in my boots
  10. I know, I'm wondering why they left that path in despite no official support, only to remove it later.
  11. I guess in that case the question becomes "why did it ever work in the first place?", considering C2Ds were never officially supported
  12. I agree they wouldn't care, I just don't understand why they'd intentionally and suddenly start using this instruction they didn't use to before. I guess it's possible they had a "core 2 support" flag in their pipeline that they intentionally removed and it caused the compiler to sprinkle the instruction around, but I doubt they went out of their way to use this specific instruction more.
  13. I think it's unlikely this was intentional, someone probably accidentally changed whichever compiler option was telling it not to use that instruction and the rest is history.
  14. There are plenty of proprietary drivers for Linux, they just aren't listed in debian's repos because debian only offers foss packages by choice.
  15. It's not so much that AMD has great linux drivers but rather that at least their drivers are open source, as opposed to nvidia. In my personal experience, intel iGPUs have worked the best on Linux. The difference being that while Torvalds is actually competent in the field, Jobs was not; his talents lay in marketing and business management, not in tech. While Torvalds is known to have a temper, he can be reasoned with and has endeavored to make the kernel community more welcoming, as well as trying to be more polite in the mailing list. Well, we have the timestamp: "always" seems to mean "less than a week". On real hardware, where you might encounter legitimate driver problems, at most we're talking two days since here he was still in a VM:
×