veltas

48 ms·

661.
by veltas 5y ago
It seems to me like the author focuses on the Taliban's seizure of such data as a way of bringing absolutely everyone onto the page of "data can be misused", maybe aimed at the field that was cautiously optimistic about the t
662.
by veltas 5y ago
>maybe Google how to build an EMP Sounds like a good way to get on a list.
663.
by veltas 5y ago
> Clang. Not only handwritten but the same file handles parsing C, Objective-C and C++. And it's under 3000 lines! https://github.com/llvm/llvm-project/blob/llvmorg-12.0.1/cla...
664.
by veltas 5y ago
> No, there is nothing to understand: the rule to minimize a variable's scope is mechanical. I tried to explain my answer to this in my third paragraph. > It's impossible to assume that even the very best programmer writes g
665.
by veltas 5y ago
Your C compiler is probably a very large C++ program written over many years and with millions of dollars worth of time poured into it. The C compiler I use takes up hundreds of megabytes of space in a minimal build. So in my opinion it&#x2
666.
by veltas 5y ago
Maybe one has been optimised more than the other, because one is more 'important' or has higher adoption?
667.
by veltas 5y ago
In my own experience writing and reviewing professional or wild code, a variable called 'i' that gets used for different loops in a function is pretty harmless, if it's reused in a consistent manner, such as only being used a
668.
by veltas 5y ago
I don't see how it is "actively harmful" to use this style. I'll defend the style and say I think either is fine from an objective standpoint, the advantage of declaring near the top and leaving uninitialised is that it
669.
by veltas 5y ago
Just trying thinking about one thing you forget a bit longer each time you encounter it, and trying to rationalise why the syntax is as it is. Slowly build it up. You don't need to remember the whole thing at once.
670.
by veltas 5y ago
It's not just an Old-Sk00l convention, but the main convention for C programming, alongside avoiding C++ comments. It's cultural and I think C programmers are now trained to worry when you don't write code like this because t
671.
by veltas 5y ago
I used to use const everywhere and then one day I realised it clutters code and it's never caught a bug for me. I don't personally find it worth the extra time. (Of course, I use const with pointers on interfaces for read-only ref
672.
by veltas 5y ago
> Lack of high quality decoders and absolutely terrible performance are what kept it back. Isn't that also a symptom of lack of adoption?
673.
by veltas 5y ago
But significant compared to time to load the source in the first place? Or any processing that will come after?
674.
by veltas 5y ago
>CSV is actually horrible at parse-time vs. other data formats I find this really hard to believe given it's a simple enough syntax. And parsing is usually not the limiting factor, usually fast enough to not be noticed alongside int
675.
by veltas 5y ago
Declarators (the name along with pointer, array, etc annotations) in C are written parallel to how they are used, I have always assumed this was to make defining/explaining the language simpler (even though it often defies new learner&
676.
by veltas 5y ago
What you actually need to do is keep your prices the same while everyone else raises their prices and collect all their business, then you can afford to pay your workers more. But the end effect is the same, less work for people.
677.
by veltas 5y ago
IA-64 is Itanium
678.
by veltas 5y ago
I malign Netburst because I owned one (actually still own it) and it was slower than the previous generation of processors (under certain loads) despite costing more.
679.
by veltas 5y ago
For those of you distracted by the office chatter, me too: https://mynoise.net/NoiseMachines/whiteNoiseGenerator.php?l=... I use this speech noise-jamming page a lot at work, someone walks over near my desk and starts
680.
by veltas 5y ago
That's not my experience. I've seen the more productive engineers prefer WFH and not WFH. I didn't really notice a correlation in my office.
681.
by veltas 5y ago
B doesn't have these issues because it only has one integer size, take that C.
682.
by veltas 5y ago
On a normal readline terminal like bash you already are basically using a text editor.
683.
by veltas 5y ago
Apologies by the way, re-reading my post it comes across overly dismissive. I didn't intend it that way.
684.
by veltas 5y ago
Correct, you're not a lawyer. IANAL either but I know enough to know people can't generally waive their rights. If they could then every website would just say "you are waiving your GDPR rights if you continue using this site
685.
by veltas 5y ago
You're right, sorry.
686.
by veltas 5y ago
Oh right. Also hi siraben didn't notice it was you.
687.
by veltas 5y ago
Why does AoC implying LEM mean you can't use LEM in constructive maths? EDIT: misread
688.
by veltas 5y ago
I think you can already pick an element. But what does it mean to pick an element infinitely many times? You have to be very careful about your assumptions there, an inductive proof would only prove you can pick an arbitrarily large number
689.
by veltas 5y ago
I enjoy the prospect of finding out what novels you think are better or more suitable.
690.
by veltas 5y ago
My experience in 8-bit is you can write 80% in C and then just focus and optimise the bits that need it in assembly. The rule is the same as ever, don't prematurely optimise (i.e. by writing everything in assembly), but the amount that

More ›