Hey! That's exactly what Apple did when they came out with their third party repair programs! It's like the only difference between all these companies is how shit they are, not that they are shit.
Traister101
joined 1 year ago
It's complicated. Paul isn't really a good guy, but he's not really a bad guy either. He's just a dude. He's a dude who has limited vision into the future from which he cannot escape. He's not using his future vision to pick the bad choices he's trying to pick the best ones he can and the hand he's dealt kinda just sucks.
It erases the type of what your pointing at. All you have is a memory location, in contrast to int* which is a memory location of an int
Sounds like the same shit those rare metal guys are always yapping about but with extra scams...
Nah bro that's just the memory leaks, your supposed to force close and reopen it every so often so the OS cleans up after their shitty application
Smart pointers model ownership. Instead of (maybe) a comment telling you if you have to free/delete a returned pointer this information is encoded into the type itself. But that's not all, this special type even handles the whole deleting part once it goes away.
Since they model ownership you should only use them when ownership should be expressed. Namely something that returns a pointer to a newly allocated thing should be a std::unique_ptr because the Callie has ownership of that memory. If they want to share it (multiple ownership of the object) there's a cheap conversion to std::shared_ptr.
How about a function that takes in an object cause it wants to look at it? Well that doesn't have anything to do with ownership so make it a raw pointer, or better yet a reference to avoid nullability.
What about when you've got a member function that wants to return a pointer to some memory the object owns? You guessed it baby raw pointer (or again reference if it'll never be null).
There's most certainly residuals, I've accidentally deleted then installed Windows on top of a bunch of my game saves. I found some random file recovery application and let it run for awhile. Guess what? Nearly everything was readable despite the fact it got wiped and then had a whole windows install.
NAND also experiences minor permanent damage on writes. Actually clearing the NAND involves a write as the charge has to be forced out (a write of 0s)
Um what? I didn't like hide extra meaning in what I said. High quality code doesn't imply all that extra shit you added. It's code that's easy to read and modify. Typically this just means you name stuff well and document things that aren't obvious. Usually my docs explain why something exists since thinking it's unnecessary cause you don't remember what the original problem was a common occurrence before I started doing so.
Is high quality code ran through a formatter? I'd hope so yeah. There should be a consistent code style across the entire project. Doesn't matter what it it long as it's consistent.
100% code coverage is meaningless and as such a pointless metric. Also 100% coverage is explicitly tied to the implimentaion as all code paths have to be reached which is obviously not a good idea (tests have to change when the implimentaion changes as you're testing the implimentaion not the api).
Really a lot of this is just meaningless buzz words as an attempt at some sort of gotcha. Really don't understand how you even interpreted a statement so simple in this way.
Ah sure, like scripts and stuff. I have some absolutely atrocious python hanging out to help me do shit. I don't have like any actual projects that are just a trash fire though
I don't really get the code point. Like your own code written for personal projects is probably gonna be pretty high quality I'd hope? Sometimes we just write trash to get something finished but soon as I've had to change it... hell yeah I'm unfucking that mess, no way do I want to figure out what it does a second time.
The availability of guns and the mental health of the members in our society?
Semantic whitespace is awful because whitespace (something that you can't actually see) has meaning in how the program runs. Braces
{}for scopes gives you the ability to easily tell at a glance where a scope ends. Whitespace doesn't allow for that. Especially, especially when you can accidentally exit a scope (two new lines in a row with Python) and it's not actually an error (Pythons global scope). Yeah formatters and linters make this less of an issue but it sucks... Languages with legible symbols for scoping are significantly easier to reason about, seeendsymbols in Lua.