Then you are wrong, since we're already talking about arrays of sizes known at compile time. Indeed, otherwise we would also need to remember the size in the runtime.
I do not agree. When you benchmark you usually measure the differences between times needed to complete. This is because it is highly non-obvious that if you increase workload twice, the time increases also twice. Perhaps the algorithm is not linear. Perhaps if you have more data, you suddenly need to swap memory. Perhaps something (like disk access in parallel) means that actually it takes less than 2x time. This means that a concept of speed per unit of work is undefined. So the only reasonable interpretation of "70% faster" means "spends 30% time of original".
Yes, this approach is followed as well, but now you're at the problem of writing a memory allocator by yourself (which might of course turn out to be better for your usecase). So the issue of writing code that avoids allocation still prevails, as now you probably want to know what to allocate memory for, since if you were supposed to make a general purpose allocator, it is likely it won't overperform libc malloc.
I'm not sure how it's counted, but in Poland we initially get 20 days and 26 after you work several years. Maybe the 4 weeks include national holidays, which don't count into the limit I mentioned.
Well, in Polish, Monday is poniedziałek, which means "after Sunday" (Sunday is "niedziela") and not "start of the week" and it looks analogous in Russian...
I believe that it is in spirit of this website that you are encouraged to explain poorness of a joke, if you find it poor. After all, if it inspires curiosity what's the issue?
Imo that's a bit of a failed analogy. More appropriate would be, imagine coffee is something very precious and Starbucks suddenly stopped selling to women. In this case, women need to go to other cafes, increasing their competition over coffee there. But in that case it doesn't seem to be so absurd any more - perhaps it's not the case that the coffee resources are so scarce (just as it's the case with crypto - does 3x miners of some currency mean that each of them makes 3x less? I don't think so).
Also, is it true that 80% of revenue was from Ethereum, or it's dummy data?
- free large file upload (max 2GB),
- native (non-electron) app for all the desktop platforms,
- custom stickers (and not so limited as reactions on Discord, anybody can use any sticker set anywhere)
- nice bot api (discord offers quite good experience as well)
- works well when on shaggy mobile network. Doesn't send duplicate messages/etc (Messenger does)
- doesn't censor messages. I'm free to send link to any website, upload any file type (again, looking at you, messenger)
- you can quickly summarize different media shared in a given conversation, view all photos, movies, files, URLs, etc
- search actually finds stuff (looking at you again, messenger)
- you can be logged in on any number of devices (phew, WhatsApp)
Probably there are more. I'm so happy that most of my friends switched.
Well, if you know anonymous function, it should be easy to understand what happens. Functions are first-class objects here. Q is a procedure that takes an arbitrary procedure. It's not that you run the procedure. In fact, it's another way around, you want to say something about the source code of the function, not the result of applying it.
I think that the website tells you to provide yearly income in yens, but it treats the number as if it was USD. I got the info that I'm in top 1.2% when I input my salary in PLN.
C++ adds a few time-consuming stuff, like templates, however my belief was that what uses the most time is optimization passes, which won't be much faster for C. The actual benchmarks should be done however.
Kernel has thousands of compilation units. Each of them is compiled by a separate compiler process. Only the linking at the end doesn't parallelise, however it should take a much smaller part of the time.
The proportions change of course, if you develop kernel and do incremental builds lots of times. Then the linking stage might become a bottleneck.
The above statement should also relate to most other C/C++ projects.
C mandates that arrays have positive size. It's not really a discussion about what the target platform does, rather it's what the abstract C machine mandates.
It becomes even funnier with a dual-boot setup. My headphones think they are connected with my laptop, but either the pairing was with Linux or Windows, in which case I need to disconnect and connect again.