HN user

cleeus

239 karma
Posts1
Comments68
View on HN

I replaced a handwritten lexer of a proprietary PDF library with a re2c generated lexer. Besides fixing a bunch of dormant bugs, the resulting lexer was much faster. Also the state of c++ std regex implementations is pretty sad (at least it was the last time I checked) and if you just need to match with a few compile-time-known regexes, re2c is there for you to solve the problems.

Company Update 8 years ago

Things I don't understand about the US ... why does not most advanced western nation not have a socially fair health care system.

E.g. in germany, the price of health care is proportional to income.

Planet Shadertoy 8 years ago

Remember that WebGL is also a security nightmare. Shaders are fed to the GPU driver. The driver contains a compiler and compiles the shaders into the GPU specific ISA. The GPU that runs that code is a PCIe device with full DMA access. What could possibly go wrong?

(I'm aware that at least Chrome does some syntactic checks on the shader syntax)

So they want to build seamless interop with MS Exchange including all calendar features, oh and compat with that plugin the workers' council really needs? ... let the investor money burn ...

Google Memory Loss 9 years ago

My men­tal mod­el of the Web is as a per­ma­nen­t, long-lived store of humanity’s in­tel­lec­tu­al her­itage.

My mental model of the Web is a human brain with all kinds of weird mechanisms - one that forgets things, makes things up, mixes memories. Google is like an "association cortex" - take it away and all the memories are still there but access to them is much harder and needs to go through more indirections (links).

Increasing the ISO is just a multiplication of the raw sensor value - it doesn't lead to more noise - it just makes it visible to the human eye. Also on my DSLR I can see all kinds of stripes and cross patterns in the noise, so a lot of it is not really random but based on static sensor properties.

It's not that simple.

Some years ago I used an analog TV card tuned to an empty channel that was giving seemingly white noise and captured frames to generate entropy. I only used the least significant bit of each RGB value of each pixel.

When I supplied the bits to the diehard testsuite, it complained about a number of patterns and failing tests.

The hash function will of course save you, but it's hard to tell the amount of real randomness that's coming from the sensor.

update: Oh, I may have misunderstood. If the whole images changes in random ways and is secret, then of course this is fine.

The Nintendo Switch is basically a nVidia Jetson TX1 (4xA57@1GHz) with some additional parts and a nice plastic packaging. That's comparable to a RasPi 3 except for the GPU. The costs are probably a bit more then 30$ of a raspi but it's not 1000$.

I bought an AMD card for my Linux desktop this year, because they have better open source drivers then nVidia :) Before that, I bought nVidia or Intel. It's a good feeling to run without that ugly nvidia-drivers blob.

If you want to see this in action, just visit the CCC event. People regularly manage to DoS (or just overload, I don't know) even the DHCP servers. So at some point all you will get from the network is a little wooden peg with a number. :)

Your are right, of course.

Maybe what I wanted to express was more like this: TP-Link has a sloppy attitude towards the security of their stock firmware. It might work, but it is full of security holes. HTTPS and checksums/signatures wouldn't change that.

Maybe they could do everything right with their firmware and provide top notch security and updates. But then their firmware would be a factor for market differentiation and at that point they would be incentivized to put effective code signing schemes in place. Other market players do that. Look at AVM Fritz Box products - nice hardware, security updates for many years and the result is: they are known GPL offenders and have strong code signing in place.

Instead TP-Link delivers you crap firmware on nice and cheap hardware and they don't care what you run on it.

I had to work with a lot of open and close source. From my experience there is an equal amount of good and bad code on both sides of the fence. It depends more on the age of the codebase and the respective engineering techniques.

I'll chime in: Thank you Audacity (-team) for always being there when I need you (aka consistent quality and maintenance).

I have not looked deeply at mmhash3 (I guess it means murmurhash3), but wikipedia says:

[...] When using 128-bits, the x86 and x64 versions do not produce the same values [...]

which will make it unsuitable for cross-platform applications. I was talking about a usecase where you could also choose CRC32 from a security standpoint but want more collision resistance. How does blake2 performance compare to MD5?

As a dev you should take a look at the difference of hashes/s of the different algorithms. Some are measured in GH/s, some in MH/s, some only kH/s. E.g. MD5 is way faster then SHA256. So if you only use a strong hash for ensuring data integrity in the absence of adversaries and performance matters, you may prefer MD5 even in these days.

If you’re making a native app, your tech stack choices are pretty limited. On the macOS side, you’ll use Xcode, Swift, and AppKit. On Windows, you’ll use Visual Studio, C#, and WPF or UWP.

Or you could use C++ and Qt and suddenly have Windows,Mac and Linux support in one codebase. And the Qt mobile story is looking better with every release.