HN user

varajelle

886 karma
Posts0
Comments341
View on HN
No posts found.

If I'm not mistaken, especially with x11, it is trivial to install a keylogger without root password. Just a process in the background that listen to your keys and send them over the wire. (And you can add that program in the list of program to run while logging in)

I was thinking the same. But then I thought about it more and wondered why you need to enter your own password if you're already logged on. If an attacker is already in the system, it can install key logger and whatnot without the root password. And the xn--ts9h program can have the Unix permission so that only the user can run it.

I don't understand this website and why it always get linked. It's just a list of a bunch of crates unsorted. Most of them are unmaintained, or just early prototypes. There isn't a good comparison of all these crates

I don't even understand how is that possible, since Qt Creator is GPL3.

Because doing so would be violating the terms of the commercial Qt license you paid for.

I mean, there might be effect, but do you have a quantification of these. Like maybe you get 0.1% more likely to catch cancer if you eat these mushroom, but when you compare that to the 300% more likely if you smoke then I think you're safe.

Why do we allow smoking but are scared of low dose radiations?

For GUI programming, you can use a toolkit that have a preview extension that updates in real time as you type. For example, Slint does that.

Sorting with SIMD 4 years ago

Nice article, but there are many errors or typo that makes it hard to follow. (Is it a typo or do I not understand that part) For example, his use of 'unsafe': why functions that don't take pointer are declared as unsafe? Also taking a pointer of an array shouldn't need unsafe. Is 4 > 8 ? Missing close ']'. And that's just the one I see.

I haven't tried compiling the code example, but I don't think they do.

Does it inline? 4 years ago

'comptime' only works if all arguments are known at compile time and the function can be evaluated at compile time. This is not the same as inlining, which puts the body of the function in the caller and remove the call. (And then do further optimisations such as const propagation)

With BSD, you're giving every company the right to take your code and use it without returning any favour at all.

With the CLA it's the same. But at least Signal give back by still providing libsignal as free software.

It depends on your motivations for contributing. If you don't like the CLA or any other things, you can still fork. Even if it may not be compatible with your own motivations, it is still in the spirit of free software.

Yeah, but the compiler need to see through all the functions to find out that there is no const_cast and therefore makes const useless because it could as well see it is not modified. Also it needs to be good at alias analysis.

This may come down to how good the language is at capturing desired semantics in a library. Rust still has a long way to go to catch up with C++ on this axis, and C++ is not waiting around.

What catch up does Rust need to do?

Rust has slice that know the size of its data built in the language, while C++ doesn't. And Rust has stricter const and mutability rules that facilitates optimizations.

As for the implementation, Rust use LLVM which is also the backend used by one of the popular C++ compiler.

I take your code and I compress it in a tar.gz file. Il call that file "the model". Then I ask an algorithm (Gzip) to infer some code using "the model". The algorithm (gzip) just learned how to code by reading your code. It just happened to have it memorized in its model.