HNHacker News
TopNewBestAskShowJobs

wizzard0

306 karma · joined October 17, 2013

submissionscomments
wizzard0··on Akka, Haskell, Erlang, Go and .NET Core compared on 1M threads
.NET version has 2 variants for exactly this reason :) Single-thread version is fastest of course.
wizzard0··on Akka, Haskell, Erlang, Go and .NET Core compared on 1M threads
.NET core impl has 2 versions, async and sync. Task.FromResult is synchronous, yes. Look closer :)
wizzard0··on Akka, Haskell, Erlang, Go and .NET Core compared on 1M threads
> I would imagine a for loop would put all of those to shame.

Indeed, see ".net sync" version. The point is to measure process spawn/message passing performance.

wizzard0··on Akka, Haskell, Erlang, Go and .NET Core compared on 1M threads
Added Erlang on Windows numbers, added .NET synchronous numbers.
wizzard0··on Akka, Haskell, Erlang, Go and .NET Core compared on 1M threads
(dotnetcore version author here)

Please note that Windows and OS X is benchmarked on different CPUs!

You're welcome to re-test at dual-boot MacBook together so we can meaningfully compare OS X/Windows

wizzard0··on JavaScript to Lua translator
Yep, *nix support is definitely part of the plan.
wizzard0··on JavaScript to Lua translator
Author here. Tessel uses modified eLua, I want to use Node modules in vanilla Lua, so naturally that approach was not viable to me.
wizzard0··on JavaScript to Lua translator
Take a look what happens if you write something simple, like "a[5]=1": http://es5.github.io/#x15.4.5.1

Or "a > b": http://es5.github.io/#x11.8.5

This, in turn, causes all sorts of weird behavior nicely described at https://www.destroyallsoftware.com/talks/wat

wizzard0··on JavaScript to Lua translator
Author here. Actually, I wanted to do exactly the reverse - ability to use tons of Node.js modules in Lua, while coding in Lua. Think of it :)
wizzard0··on DMND: A gamma-correct, energy-preserving, subpixel image resizer
Take a closer look at the enlarged fragment: https://tvori.info/jit/subpixel-resize/halos4x.png

What I am trying to avoid are the black rings around white-on-gray lines, which sharpening causes to images.

Oh, and your display _might_ try sharpening everything by itself, so you can't see any difference at 1:1 size :)

wizzard0··on DMND: A gamma-correct, energy-preserving, subpixel image resizer
Added the 'antialias' option for you - check it out. There is a ton of knobs under the hood :)
wizzard0··on DMND: A gamma-correct, energy-preserving, subpixel image resizer
Well, just applying textbook signal processing algorithms properly, without optimizations commonly done to speed things up.
wizzard0··on DMND: A gamma-correct, energy-preserving, subpixel image resizer
That is, of course, subjective. There are ppl out there who like it clean and sharp - but without "ringing", and there are ppl who prefer smooth lines and hate aliasing.

But most imaging software only offers the second option, that's why I have made the other one :)

wizzard0··on DMND: A gamma-correct, energy-preserving, subpixel image resizer
Update: Changed color for transparent images from bright magenta to white %)
← PreviousPage 5 of 5