But ye, you have to deal with some sub-optimal 'out-of-the-box' experience and privacy isn't really there (though let's be honest, on stock android google also look at your hands constantly)
870 karma · joined July 14, 2022
But ye, you have to deal with some sub-optimal 'out-of-the-box' experience and privacy isn't really there (though let's be honest, on stock android google also look at your hands constantly)
Not that it's a good feature, just an FYI
To much.
But it's not, it's exactly the same shovelware that any other OEMs push at You, except people give it a pass because "it's from google". My phone app should be my phone app, not google contacts.
And sure, GMS integration are de facto 'the android experience', but let's not pretend like Google’s version of calendar being preloaded is crucial for GMS to work.
I don't see how it would even be feasible to share this data with non-installed stores, not to mention it being completely ridiculous.
But yea, I find this point to be weirdest from all the ones that epic proposed.
Ofcouse Epic wants to make more. So?
Good changes are good changes, we should judge them on their own merit regardless of who are pushing them.
Being 'sceptical' because the underdog is still a massive company thus we should give current leader (who is many times larger) a free pass, isn't really a skepticism, it's just irrational.
Yea sure, apps stores are 'free to compete' but Google store HAS TO be installed out of the box if you want to have access to GMS services (alongside the entire suite of Google apps).
Let's not play dumb here and pretend like current status quo isn't heavily favorable for Google
If an app has permissions to work as an app stores, it should already be able to query installed packages, no? So Epic's proposal wouldn't expose information about whether or not app is installed, but only about the source of installation.
You can ofcourse still think it's unreasonable to give this information to 3rd parties, but that's different then exposing just the fact of having an app installed, which is what Google implies here (imo)
It's a bit confusing to have a 'thing' mention one mechanism in its name, but actually being valuable by ensuring some other mechanism
The question is whether or not the fact of it not being implemented comes from problem difficulty, or designers explicit refusal to do so
Which isn't really a good aproach to structuring codebase, it's just to appeal to borrow checker inflexibility.
Lack of global scope. Lack of function overloading.
And while you can technically prototype in a other language, speed of iteration is always a bottleneck.
The only way to escape it is if You are an about master of language, the project you are working on and even the feature you are adding.
But that's a verry rare case scenario
Again, the former are fine, it's the latter I have a problem with.
At some point you just disallow horses to go onto the high-speed road, and aren't waiting for literally every last farmer to sell their horse over a car.
Unfortunately you can't just have Rust's safety checks, without opting into restrictions that Rust designers force onto You that aren't inherent to safety checks, but more because 'that's a better practice (according to us)'.
And also, easy and fast iteration just isn't there, both because of borrow checker restrictions and compile times
This is just false. Sure, they probably are 'close enough', but you can't claim the performance is 'the same' simply because those languages inherently do more to achieve the same results.
Games.
Big/specialiased games to be precise, as for smaller projects managed language offer good enough performance.
But for all the crazy optimizations modern compiler do, I don't see how marking pointers for more then couple of them in a raw is that crazy
And it's not like the companies arent trying this idea (again, M1 exploit). But for whatever reason they want to keep cpus as black box, perfect abstract machines, even though we know they aren't
From my understanding this is what led to the recent 'unpatchable' exploit in Apple's M1, but rather then trying to guess it by some heuristic, why not just give compilers option to make that optimization?
What I meant is “we (as in) the c/c++ community (or rather the specification committee)” could tomorrow decide that, lets say, all null pointer dereferences should lead to program exit. Existence of UB is a choice.
Every UB could verry well be wrapped in error checking and we could have 0 UB out there. We don't do that, but that's because of (our) choice, not some superficial entity that poses machine when running into UB.
What happens is: Compilers sees unreachable and assumes that this codepath will never run, so it just yeet it out of existence. For example, maybe it will remove the preceding if-statement and rather then check its condition, just insert true or false. Afterall, why waste computing on checking condition if we know it will never resolve to the unreachable path.
In Rust, the same if-statement won't be optimized away, and if the code happens to go for the unreachable path, it will call panic.
Now, the example is a simplification, but it's just to demonstrate that UB comes from compilers (verry aggressively) assuming UB will never happen, and not because someone decided to "add it".