What is this mysterious device that requires specific libraries and kernel modules? So I can state the fuck away from the device and the brand
What is this mysterious device that requires specific libraries and kernel modules? So I can state the fuck away from the device and the brand
if you’re using windows and expect any privacy at all […] throw that notion out the window
Correct. And the same is true even if you are using linux, macOS, android, or a butterfly to manipulate bits to send a message through the internet.
Because if your message ends up on the screen of a windows user, it’s also going to be eaten by AI.
And forget the notion of “anything you post on the internet is forever”, this is also true for private and encrypted comms now. At least as long as they can be decrypted by your recipient, if they use windows.
You want privacy and use linux? Well, that’s no longer enough. You now also need to make sure that none of your communications include a (current or future) windows user as they get spyware by default in their system.
Well maybe not quite by default, yet
I thought mint was switching to a debian base but it looks like I am mistaken. While LMDE exists, it’s still not the default.
Got the feeling that’s probably gonna change soonish, we’ll see.
I remember playing lots of sims 2 as a kid. Could not play sims 3 due to not having a pc that could run it, and I found sims 4 extremely disappointing.
Been keeping an eye on Life by You and Paralives for modern takes at the genre.
I wonder if EA will try to innovate with sims 5 and if they’ll try to optimize the unbelievable loading times (talking about sims 4 here) due to the competition or if they hope to coast on reputation alone.
I thought Life by You was trying to fill that gap.
With both that and Sims 5 (edit: oh an Paralives of course, was forgetting about that) on the horizon will this new studio be able to find its space in the market?
Guess more competition is always good, hopefully it doesn’t flop immediately.
Since my previous example didn’t really have return value, I am changing it slightly. So if I’m reading your suggestion of “rewriting that in 3 lines and a single nested scope followed by a single return”, I think you mean it like this?
int retval = 0;
// precondition checks:
if (!p1) retval = -ERROR1;
if (p2) retval = -ERROR2;
if (!p3 && p4) retval = -ERROR3;
// business logic:
if (p1 && !p2 && (p3 || !p4))
{
retval = 42;
}
// or perhaps would you prefer the business logic check be like this?
if (retval != -ERROR1 && retval != -ERROR2 && retval != -ERROR3)
{
retval = 42;
}
// or perhaps you'd split the business logic predicate like this? (Assuming the predicates only have a value of 0 or 1)
int ok = p1;
ok &= !p2;
ok &= p3 || !p4;
if (ok)
{
retval = 42;
}
return retval;
as opposed to this?
// precondition checks:
if(!p1) return -ERROR1;
if(p2) return -ERROR2;
if(!p3 && p4) return -ERROR3;
// business logic:
return 42;
Using a retval has the exact problem that you want to avoid: at the point where we do return retval
, we have no idea how retval
was manipulated, or if it was set multiple times by different branches.
It’s mutable state inside the function, so any line from when the variable is defined to when return retval
is hit must now be examined to know why retval
has the value that it has.
Not to mention that the business logic then needs to be guarded with some predicate, because we can’t early return. And if you need to add another precondition check, you need to add another (but inverted) predicate to the business logic check.
You also mentioned resource leaks, and I find that a more compelling argument for having only a single return. Readability and understandability (both of which directly correlate to maintainability) are undeniably better with early returns. But if you hit an early return after you have allocated resources, you have a resource leak.
Still, there are better solutions to the resource leak problem than to clobber your functions into an unreadable mess. Here’s a couple options I can think of.
defer
Example of option 1
// precondition checks
if(!p1) return -ERROR1;
if(p2) return -ERROR2;
if(!p3 && p4) return -ERROR3;
void* pResource = allocResource();
int retval = 0;
// ...
// some business logic, no return allowed
// ...
freeResource(pResource);
return retval; // no leaks
Example of option 2
// same precondition checks with early returns, won't repeat them for brevity
auto Resource = allocResource();
// ...
// some business logic, return allowed, the destructor of Resource will be called when it goes out of scope, freeing the resources. No leaks
// ...
return 42;
Example of option 3
// precondition checks
void* pResource = allocResource();
defer freeResource(pResource);
// ...
// some business logic, return allowed, deferred statements will be executed before return. No leaks
// ...
return 42;
Example of option 4
int freeAndReturn(void* pResource, const int retval)
{
freeResource(pResource);
return retval;
}
int doWork()
{
// precondition checks
void* pResource = allocResource();
// ...
// some business logic, return allowed only in the same form as the following line
// ...
return freeAndReturn(pResource, 42);
}
Bad advice. Early return is way easier to parse and comprehend.
if (p1)
{
if(!p2)
{
if(p3 || !p4)
{
*pOut = 10;
}
}
}
vs
if(!p1) return;
if(p2) return;
if(!p3 && p4) return;
*pOut = 10;
Early out makes the error conditions explicit, which is what one is interested in 90% of the time. After the last if you know that all of the above conditions are false, so you don’t need to keep them in your head.
And this is just a silly example with 3 predicates, imagine how a full function with lots of state looks. You would need to keep the entire decision tree in your head at all times. That’s the opposite of maintainable.
The “or later” is optional, the FSF specifically doesn’t have the power to update the terms of every GPL-licensed software because the wrote the clause in such a way that they don’t.
If I give you software licensed under the GPL3, and a GPL3.1 comes out, it doesn’t apply to your copy of the software. Likewise the copyright holder of the work is also not forced to relicense their software under the GPL3.1. And even if they did, copies of the software distributed under the GPL3 would still be licensed under the GPL3.
The “or later” clause simply means that if I received a copy of a GPL3 software, I can redistribute it under the GPL3.1 if I so wish (where “I” in the previous sentence is everyone with a copy of the work, as the GPL gives everyone with a copy redistribution rights)
Maybe Eidos would love to get another Deus Ex out there but there’s no publisher interest
You know, they could just… Say this, and placate everyone. I’m honestly sick and tired of companies in general, and game companies specifically, being afforded this stupid level of opaqueness.
If you were to talk to someone that would exclusively stonewall you, you’d be quick to stop talking to this person. When it’s game companies though, everyone bends over backwards to try to find justifications for their behavior on their behalf.
TAA has become so common because its’s “free”. Temporal data is required by DLSS and FSR, so if you are implementing those technologies you already have the necessary data to implement TAA, making it a no brainier to include.
Not so fast now! High resolution video only available on edge on windows
If this was cpp, clang-tidy would tell you “do not use else after return”
I don’t know how null works in swift, but assuming it coerces to bool I’d write
if (a) return a;
return b;
Except it is? Instead of cramming 22 new features, 198 bug fixes, and 3 usage changes in the next version, taking 24 months of dev time, one could release the next version with 1 new feature and however many bug fixes fit in the time frame, and release it in 4 to 6 weeks
I was dining out once and ordered a spicy pizza. Had this tiny red chili pepper in the center, maybe the size of the tip of my pinky. I thought nothing of it and popped it whole in my mouth.
I was sweating and crying for 10 minutes, 10/10 would do it again.
Op’s description is legit mouth watering, and now I want a slow-cooked spicy stew with roasted whole chilies.
Interesting. I have more than 1500 hours on it and I think the last few DLCs are way way better than usual. A lot more content, a lot more creativity. However, I also stopped playing after — IIRC — version 1.30. That version made the game something like 3 times less performant (or rather, things took 3 times the time they took previously), and it was already slow to begin with.
That completely killed the game for me.
It can, and it does. It even has a better wsl integration than windows!
So, again, you are either implying that you run pirated windows on your work machine, or you are saying you can’t install Linux on your work machine. Neither is what this is being discussed. Having a boss is completely irrelevant
My IT department likes to install antivirus software that makes it impossible to do your job because it will scan every compiled object file, inflating compilation times by an order of magnitude, even for distributed compilation jobs.
Or stupid “workspace management” software that will randomly uninstall work-related software and / or reboot your machine whenever it pleases.
Luckily I can use Linux at work, otherwise I’d have to either quit or tamper with my work machine to do my job.
And yes, the IT department knows. But they are always “understaffed” to fix stuff. Curiously, they are never understaffed to roll out new stuff that doesn’t work though.
Then why would you need to quit your job if you installed Linux on your personal devices?
You are the one that brought up that installing Linux would require you to quit your job, on a post announcing that one method to pirate windows no longer works, implying that either you use pirated windows at work, or your employer has the right to fire you if you install Linux on your personal devices.
Since the latter is extremely bonkers and, quite frankly, unheard of, assuming the former seems much more reasonable. Especially considering that tons of people do indeed run pirated windows at work, and I myself witnessed as much.
Contact lenses in a nutshell