unoptimized

I'll charitably believe that you read the article, but if you're still complaining that the code is unoptimized when the author clearly said it was unoptimized then you didn't understand the article.

The function is called 'Optimize', perhaps it just calculates a more optimal dataset, and then does nothing with it, leaving the unoptimized data in there.

It was totally unoptimized, and used select() instead of the more modern, faster alternatives.

Early access game devs pushing unoptimized releases should set up their release system betterer.

Right now the speed issues we have are solely due to unoptimized algorithms and not due to hardware limitations.

And the original, unoptimized, declarative query would now be able to run faster.

The amount of unoptimized crap they generate in a few weeks (in some cases) is quite depressive too I'm afraid.

I have some go code with a trivial, completely unoptimized blog, rendering a couple of articles.

I was able to eliminated 2 to 50k in 81ms in completely unoptimized C# just now.

But Apple has left their drivers buggy, unoptimized, and just bad.

At worst they avoided a stack and made an implementation that was unoptimized in an entirely unrelated manner, not because it unimplemented anything on top.

Was quite a performance hit but unoptimized and with many protections.

That doesn't compute well if we were to assume that you are writing some compute-intensive tasks for which (unoptimized non-C language can be "slower".