Haha. People have already said what is Vulkan in practice - it's very convoluted low-level API, in which you have to write pretty complicated 200+LoC just to have simplest stuff running. Also doing compute on NVIDIA in Vulkan is fun if you believe the specs word for word. If you don't, you switch a purely compute pipeline into a graphical mode with a window and a swapchain, and instantly get roughly +20% of performance out of that. I don't know if this was a bug or an intended behavior (to protect CUDA), but this how it was a couple years ago.
HN user
Arech
That's what I thought of too. Given their task formulation (they basically said - "check these binaries with these tools at your disposal" - and that's it!) their results are already super impressive. With a proper guidance and professional oversight it's a tremendous force multiplier.
Thanks, this is a very interesting topic.
What I personally would like to see is some kind of quantization of how the biases that the author talks about (such as insufficient seed volume of a PRNG) affects computed p-values. Specifically, why there must no "cancellation of errors" happen? So far, IIUC, the author only shows theoretical possibility of errors, but what's more interesting is a real effect. When it all boils down to a p-value being less than a certain threshold (choosing which is another pita), it might not matter whether a true p-value is within, say, 2^-16 from the computed.
I had been Windows user since Windows3.1. More than 3 decades straight. After a few years of working with Linux, installed Debian on home PC about a year ago and couldn't be more happier since then.
Is it a normal mic, or bluetooth? I think, Trixie have some regressions in bluetooth stack of Cinnamon - it worked nicely in Bookworm, but I had weird issues on Trixie that just disappeared once I switched to KDE (didn't try Gnome).
and sometimes a total unbelievable junk...
My dog (Briard) isn't just addicted to play fetch with balls.. Since he knows that when another dog enters the dog park, the ball will be removed/hidden from him (to prevent the dogs clashing trying to get the ball), he becomes hostile to the dog entering the park, actively trying to prevent them from doing so! This happens only if we started to play with balls. If not, he'll be totally friendly... What an ass!
Your don't need noexcept on it, complier sees it on its own without a potential noexcept overhead... Other than that - agree.
Exactly this.
In most cases (and this was the case of Mozilla I referred to) it's only a matter of compiling code that already have all support necessary. They are using some upstream component that works perfectly fine on my architecture. They just decided to drop it, because they could.
Ah, com'on, spare me from these strawman arguments. Good enought is good enough. If F-Droid wasn't worried about that, you definitely have no reasons to do that for them.
"A tiny group is holding back everyone" is another silly strawman argument - all decent packaging/installation systems support providing different binaries for different architectures. It's just a matter of compiling just another binary and putting it into a package. Nobody is being hold back by anyone, you just can't make a more silly argument than that...
This is super annoying how SW vendors forcefully deprecate good enough hardware.
Genuinely hate that, as Mozilla has deprived me from Firefox's translation feature because of that.
It's not clear how the author controlled for HW caching. Without this, the results are, unfortunately, meaningless, even though some good work has been gone
Please don't pretend you don't understand that risks of Google/Apple maybe even Samsung getting the information is just "a tiny bit different".
TBH, such a low price for so many working (!) features is an amazing achievement if not subsidized! What bothers me here, however, is...a provenance. Let me guess, it asks from your smartphone access to your location, contacts, calendar, SMS archive, email, medical records and political views and attitude towards CCP and then does some shady syncs with .cn servers "just to keep you data safe in case a meteor hits you"... Sad.
ADDED: Oh, seems like some people like to pretend that the results of "some other" companies getting this information are totally, totally the same.
I absolutely love 3 dimensional nature of the game and how carefully many images are chosen to allow for a precise spacetime localization with a bit of a research. Super enjoyable experience in startling contrast with geogessr, which I don't even want to open. Thanks a ton!
I don't want to rant, but I don't a tiny bit like the UI they have made for tab groups, and I won't use it.
They should have just paid lavishly to the developer of Simple Tab Groups, and incorporate that extension into the master. Fast, cheap and perfect result. Instead they made....this :(
That's likely because it offloads most of the job to GPU. On a potato it's also very choppy, but CPU fans stays quiet indeed. Gate's notes seems to put the most strain on CPU instead.
Hhhmmm, interesting, thanks for reply!
That would be fairly interesting to look at the actual code you've used, and have a look at the codegen. By a chance, is it viable for you to open-source it? I'd guess it should bear lots of interest for Hana author/s.
What compiler/version did you use? For example, MSVC isn't (at least wasn't) good at always evaluating `constexpr` in compile-time...
hana::while creates lambda functions, so perhaps a simple function optimization becomes a cross-unit affair if it calls hana::while. (speculating)
Hmm, I'd say it (LTO) shouldn't influence, as these lambdas are already fully visible to a compiler.
Boost Hana (which still has some runtime overhead compared to the same logic with hardcoded values)
Can you elaborate on that? What was your use-case for which this was true?
Haha, yeah, that crap adds indeed
While I don't disagree with that, in my experience all Windows instability on WinNT family (and I tightly worked with all end user versions of Win from 16 bit W3.11 to the recent Win11 with a very few exceptions) are caused by faulty hardware and/or bad drivers that can't handle it. I don't think I could remember any issue that I can't attribute to bad HW/3rd party driver.
Wrt Win95 & it's kind - all processes in that family essentially run in a single address space, and data "isolation" were "achieved" only through obscurity. If you knew some magic constants that were easily obtainable from disassembly, you could do anything there. So no wonder it was as bad as the worst program you've installed..
Overall, the whole logic "A is written in X, but B is written in Y, hence it is faster" is so deeply flawed, that one has to consider a possibility that the author doesn't understand the mere basics of computer program engineering. There are so much nuances that I don't even want to start untangling it.
Disproportionally more if you divide it on the user base to get the cost of targeting 1 user when you want them all (and most of evildoers want that exactly).
[emotions redacted]
Long ago there was XPrivacy project for Android that allowed to granularly set permissions for each app & system service and ensure they won't get the real private data. It's no longer alive these days, I guess. Can someone share their experience with the alternatives for the modern latest Android?
The problem with these weaknesses is that they are different in each human being. For me listening an mp3 is like a sanding an ear, while some don't even hear the difference between it and a live performance.
I wonder why this isn't inbuilt into the program..
this is a gem, thanks for sharing!
Exactly this. Somewhat an issue here though, that this is essentially a matter of a person's culture. What you've said is most likely true for WEIRD (acronym) people, but for other cultures where retailiation is quite possible, one either have to dance that silly dances, or indeed polish their CV.
Honestly, I was expecting to see suggestions for testing for numerical stability. This might be a super annoying issue if the data is just right to hit certain peculiarities of floating point numbers representation.