HNHacker News
TopNewBestAskShowJobs

Xeamek

870 karma · joined July 14, 2022

submissionscomments
Xeamek··on We're ending our Samsung collaboration
Samsung's skin for android is actually incredibly customizable (to the point you can individually pick color for each UI element separately), as well as including quite a few QoL upgrades that are missing on stock android.

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)

Xeamek··on We're ending our Samsung collaboration
You can change that buttons behavior.

Not that it's a good feature, just an FYI

Xeamek··on We're ending our Samsung collaboration
There are a lot of valid cricotisms, but claiming Samsung products are 'the worse' is just....

To much.

Xeamek··on Epic's proposed remedies are bad for everyone but Epic
If "google stuff" was part of (open source) android OS, then sure.

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.

Xeamek··on Epic's proposed remedies are bad for everyone but Epic
>They say "any and all third party app stores." Does that include app stores the user hasn't installed

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.

Xeamek··on Epic's proposed remedies are bad for everyone but Epic
I mean, technically 3rd parties can already scrap packages from Google and repost them through various channels.

But yea, I find this point to be weirdest from all the ones that epic proposed.

Xeamek··on Epic's proposed remedies are bad for everyone but Epic
I don't understand this aproach.

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.

Xeamek··on Epic's proposed remedies are bad for everyone but Epic
>Epic’s proposal hurts device manufacturers: Part of the State AG settlement ensures that any app store is free to compete for placement on an Android device. But Epic’s proposal would cut Google Play out of this process, reducing competition and therefore enabling rival app stores to underbid. This would reduce what OEMs can earn from pre-installation and placement on their devices, cutting into already narrow OEM margins in a way that could raise consumer prices.

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

Xeamek··on Epic's proposed remedies are bad for everyone but Epic
>Epic’s proposal hurts the privacy of Android users: Under Epic’s proposal, Google would be forced to tell any and all third party app stores which apps a user has installed on their phone through Google Play. It would wrongly expose a person’s personal apps usage – even for topics like religion, politics, or health — for Epic’s gain. This is a clear violation of user privacy.

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)

Xeamek··on Why not just do simple C++ RAII in C?
Is RAII even wanted? I mean, in the name, 'Resource acquisition is initialization' it talks about the initialization part. But while not super versed in cpp, it looks like what everybody wants is actually the de-initialization part, which doesn't seem to be inherent to RAII, no?

It's a bit confusing to have a 'thing' mention one mechanism in its name, but actually being valuable by ensuring some other mechanism

Xeamek··on "No way to prevent this" say users of only language where this regularly happens
That's truism, ofcourse there is no way to do something that is not impemented.

The question is whether or not the fact of it not being implemented comes from problem difficulty, or designers explicit refusal to do so

Xeamek··on "No way to prevent this" say users of only language where this regularly happens
Comment above, mentioned borrowing while structs instead of borrowing memory. I believe this was once discussed under term 'partial borrows', but the "idiomatic" aproach is to 'just split your structs'.

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.

Xeamek··on "No way to prevent this" say users of only language where this regularly happens
Except Rust's unsafe is even worse then any other 'unsafe' languages.

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

Xeamek··on "No way to prevent this" say users of only language where this regularly happens
There are restrictions out on You by the borrow checker to ensure safety, and then there are restrictions put on You by rust design team 'just because'.

Again, the former are fine, it's the latter I have a problem with.

Xeamek··on "No way to prevent this" say users of only language where this regularly happens
Again, restrictions that are forced you for a price of safety are one thing. But what I'm complaining about are restrictions that don't have to be there to get borrowchecker working, but rather are there because designers arbitrary decided "it's better this way".
Xeamek··on "No way to prevent this" say users of only language where this regularly happens
That's not how society progress.

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.

Xeamek··on "No way to prevent this" say users of only language where this regularly happens
Eh, Rust would be fine if not for the fact that it's too opinionated.

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

Xeamek··on "No way to prevent this" say users of only language where this regularly happens
>I am sorry but my observarion is that Nim and LLVM and dare I say even GC-less Java all achieve the same performance as C

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.

Xeamek··on "No way to prevent this" say users of only language where this regularly happens
>What projects need manual memory management

Games.

Big/specialiased games to be precise, as for smaller projects managed language offer good enough performance.

Xeamek··on Fast linked lists
For everything? Obviously no.

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

Xeamek··on Fast linked lists
Apparently Apple and Intel do, since they introduced those changes into their silicon
Xeamek··on Fast linked lists
I mean sure, I don't doubt 99% of end-user programmers wouldn't look twice at something like this, but compilers designers probably would care.

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

Xeamek··on Fast linked lists
Why cant we 'simply' get processor extension to mark data as pointer so that the prefetcher would actually know what to fetch.

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?

Xeamek··on Upstreaming Linux kernel support for the Snapdragon X Elite
What device was this benchmark run on?
Xeamek··on The C++ Iceberg
It's unsafe to do that, but it's not UB
Xeamek··on The C++ Iceberg
Yes, I know it's not possible for a specific c++ dev to do such checks, as compilers can optimize them away.

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.

Xeamek··on The C++ Iceberg
Like?
Xeamek··on The C++ Iceberg
What do you mean? Just check if it's not null?
Xeamek··on The C++ Iceberg
It's not like UB is some magic functions that gets called when encountering UB.

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.

Xeamek··on The C++ Iceberg
It doesn't 'invoke' undefined behavior in the sense that it calls some function 'doRandomShit()'.

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".

← PreviousPage 3 of 14Next →