futharkshill

7 ms·

31.
by futharkshill 5y ago
> they don't want language releases dependent on unicode updates. I'm sorry, what do you mean by this?
32.
by futharkshill 5y ago
A strategy that actually works: read the book through, even if there are many things you do not understand. Do it again and again until you get the majority. Everything you encounter now feels familiar in a sense, and you can go in depth wi
33.
by futharkshill 5y ago
This has nothing to do with C#. The javadoc for this exact problem would have been identical
34.
by futharkshill 5y ago
that seems like a stretch to be honest.
35.
by futharkshill 5y ago
is it just me who cannot find it, or did this article basically only state the hertz of the processors?
36.
by futharkshill 5y ago
maybe, maybe not. The EU is not a single country.
37.
by futharkshill 5y ago
they sell ground fish at every Danish supermarket
38.
by futharkshill 5y ago
Could you tell us, why would you choose to use Bash compared to other programming languages if you are making complex programs?
39.
by futharkshill 5y ago
It is almost as if it was written with people doing a lot of IO and internet :D
40.
by futharkshill 5y ago
I think the only "hard" part about the syntax of C are pointers. Reading e.g. i++ *a->b[0]
41.
by futharkshill 5y ago
Great example, especially considering op found that he added that example as a mistake :D
42.
by futharkshill 5y ago
> Why on Earth would one use malloc in C++? Instead of using ’new’ if explicit allocation is desired. That was the point of my original comment that C++ and C are not the same language :)
43.
by futharkshill 5y ago
> - Why A.B()? Period gets read as a sentence terminator and that function is being called with no parameters, which makes no sense. What C syntax is this referring to?
44.
by futharkshill 5y ago
"monkey patch" is frequently used by Rubyists without anny derogatory meaning.
45.
by futharkshill 5y ago
C and C++ are completely different languages. The arbitrary parsing of data into structs in C is what makes it incredibly suitable for file parsing. Among other things.
46.
by futharkshill 5y ago
You are being overly dramatic. A hundred years ago, workers were treated so bad and had such bad living conditions it makes you sick just to hear about it. THAT lead to some violent revolutions in some countries, most of them young, undemoc
47.
by futharkshill 5y ago
You would be surprised at the skills at the highest level of academia.
48.
by futharkshill 5y ago
alternative: In 2021 we still use C et al. for our backend server, and we get hacked every single day. If I am going to leave a wide open door to my house, I at least want confidence that the house is not made out of cardboard
49.
by futharkshill 5y ago
If you are writing some very important function, you may write it in assembly and it will be faster than e.g. a C implementation (CPU). But how often do you do that? I think of e.g. CUDA as assembly for the GPU as you have to know about bat
50.
by futharkshill 5y ago
I think it will always be slower than hand-optimized GPU code, just like assembly. But for most complex programs, I think the compiler is better than humans. @arthas, the author, at some point made comparisons against implementations and it
51.
by futharkshill 5y ago
Well, yes, but to be honest that code still has to be annotated with bounds and batch sizes etc. In futhark you need to know absolutely zero about GPUs
52.
by futharkshill 5y ago
I cannot overstate the importance of using a programming language targeting GPUs directly like Futhark ( https://github.com/diku-dk/futhark ). In this case, it is a functional, declarative language where you can focus on