futharkshill

> they don't want language releases dependent on unicode updates.

I'm sorry, what do you mean by this?

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 with the literature

This has nothing to do with C#. The javadoc for this exact problem would have been identical

that seems like a stretch to be honest.

is it just me who cannot find it, or did this article basically only state the hertz of the processors?

maybe, maybe not. The EU is not a single country.

they sell ground fish at every Danish supermarket

Could you tell us, why would you choose to use Bash compared to other programming languages if you are making complex programs?

It is almost as if it was written with people doing a lot of IO and internet :D

I think the only "hard" part about the syntax of C are pointers. Reading e.g. i++ *a->b[0]

Great example, especially considering op found that he added that example as a mistake :D

> 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 :)

> - 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?

"monkey patch" is frequently used by Rubyists without anny derogatory meaning.

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.

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, undemocratic, or unstable. Some of them migrated 2,000 km from their home.

People have food, shelter, entertainment.

You would be surprised at the skills at the highest level of academia.

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

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 batch size, and special operations and annotations, but Futhark is like writing C or Java for the GPU (it actually compiles to CPUs as well), and it is just a much nicer experience, and I think 99.9% of all people will write faster code because GPUs are simply so complex

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 was a most twice as slow, but often faster.

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

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 the why, not the how. Just like CPUs are incredibly complex, higher level abstractions are very important.

If you were a pro GPU programmer and had 10 years, Futhark would be maybe 10x slower. But just like we do not program in assembly when making critically fast software, most non-simple things are easier written in this.