Wrong? You are comparing number of possible values that can be stored not the amount of bits. Drive sizes are specified in bytes not possible combinations it can store.
The antivirus program forced to be installed by my company does not allow .odin file to exist, as there is a ransomware which encrypts files into *.odin.
Of course, git cloning the ALE plugin (linter + languageserver) for VIM also fails as ALE has an .odin file in its repo.
Please explain in detail how alternatives would have worked better for GCC and CUDA. Also, if you could share some historical context about how those alternatives could realistically have been implemented at the time, that would be helpful too.
I love to hear all the "would've" and "should've" scenarios.
To be fair, MSVC has the most C99 stuffs. What is mainly missing for porting (my) programs is the native complex number. But we have Intel compiler for free on Windows, which is fully compatible with the C/C++ standard and produces faster binaries.
The C++ frontend of MSVC handles (the common) compiler-specific language extensions differently than the other compilers. Besides, its pre-processor behaves differently too. It is now good that there is a clang frontend for MSVC.
However, not everything can be well designed at the beginning. Skills of editing will affect efficiency, especially in a try-and-error loop of new ideas/approaches, where only a rough design exists.
Besides, some niche editing tasks (which may involve column editing, macro recording then batched execution, regex based operation, encoding transformation etc.) may otherwise require writing awk/sed or even perl/python scripts as subprojects to achieve, if one does not known the editor well.
I haven't seen any other editor that comes anywhere near the capabilities provided by VIM. I spend a lot of time manipulating data into columnar form and for anything early vim does it effortlessly.
If you’re often doing hardcore text manipulation that’s a bit of a different story, I just personally think the average dev thinks they do that more than they actually do.
Unfortunately, the rendering of fakebold (especially if the factor is not 2) depends on PDF readers and printers.
Some PDF programs handle it well, some fix the factor at 2, some do not implement it at all.
The requirements and constraints depend on the product.
For example, the geometry of your product to accommodate the antenna is not always the same; the (internal and external) environment of the case is also different; there may be requirement of combining various frequency bands into one antenna; etc.
Right. Everything in the near field of the antenna is part of the antenna. Handheld products are an extreme example of this: remember "just avoid holding it in that way"? (after that, Apple built big test chambers and brought journalists in to see them)
