flafla2

O(m log^2/3 n) !!! What a triumph.

One of my favorite ever papers and very ahead of its time. Thanks for the share :)

This is so awesome. There’s a lot to geek out about here, but I was personally enamored with the extra effort to make good renders/visualizations in software. Thanks for the read!

Agreed. Bugs happen, bug fixes don’t always happen (especially quickly)

That being said, we could all do with a bit more input sanitization, and I hope Cox learned their lesson here.

Cloudflare does a pretty good job of managing it, at the cost of some centralization.

It would be pretty cool if there was a way to DDOS-harden at the protocol layer. Not sure if that’s even possible though

Oh neat I’ve never heard of NativeAOT. I’ve only used Unity’s AOT compiler “Burst” for C# (I assume that is something different?).

Cool stuff.

edit: Actually I meant to say Unity’s IL2CPP, which transpiles IR to C++. Burst is a different tool with similar goals—it compiles IR straight down to native via LLVM.

Oh got it. So like c# but compiles to native a la Swift?

Superficially this language appears to be very similar to Swift. Beyond the syntax, it also has first class refcounting, C language binding, and no external runtime (compiles straight to binary).

I wonder, does Vala have a stable ABI, or native compatibility with other higher-level languages like C++ or ObjC? These are other difficult challenges which Swift attempts to tackle (and depending on who you ask, with varying levels of success).

In any case this is an interesting language. Thanks for sharing

I agree with the sentiment but in practice I’ve found that most C++ STL exceptions throw in a “fatal error” type of scenario like a bad allocation and generally not an “expected error”. For example, basic_ifstream::open() sets a fail bit on error, and doesn’t throw an exception.

This is in contrast to python or Swift for example, their standard libraries are more “throw-prone”. Building off the previous example Swift’s String.init(contentsOf:encoding:) throws on error on failure.

So in practice, IMO it is usually safe to disable exceptions in C++. Though, I have run into tricky ABI breaks when you link multiple libraries in a chain of exceptions->noexcept->exceptions and so on! You’re of course at the mercy of nonstandard behavior so buyer-beware. I definitely wouldn’t advocate for turning them off -just- for a binary size reduction.

Indeed, it’s more accurate to say that C was designed around common asm calling conventions of its day, than the other way around.

Matlab is awesome. I had to learn it for a class in Computational Photography back in school. The matrix-centric language design is an interesting change from traditional languages and the amazing linear solvers available give you a shocking amount of power sometimes. For example, the language has really good SIMD/parallelism support out of the box, because you are steered towards making all of your variables into vectors and performing batch processing. Backslash is also an incredibly powerful tool in the right hands, and lends itself to some beautiful oneliners (it’s sort of like a shell language in that way).

Same. I’m honestly kind of stunned

Very happy that Aras is fighting the good fight, doing some great OSS work after his departure from Unity. The speed up numbers are quite impressive!

I remember when I was first getting into shader programming 10+ years ago, I asked a question on the Unity forums and Aras was one of the first to respond. Even then he was a titanic figure behind Unity’s graphics stack. I never forgot how kind he was to help a kid like me out, I’m sure he was quite busy!

Complete yet succinct explanation — bravo and i might steal this way of explaining it!

> this type of AI is not getting us any closer to that.

That is not obvious at all.