Hacker Newsnew | past | comments | ask | show | jobs | submit | ccgus's commentslogin

There's no JIT for WebAssembly on iOS (at least last time I looked last year), so it's going to be much slower than it could otherwise be.


Are you sure about that? Why wouldn't WebAssembly in Safari support JIT?


Make sure to send me the images that crashed it (support at flyingmeat.com)! I'd love to get that fixed, as I'm not aware of any cases right now where this happens.


Hey! Thanks for reaching out in HN comments! Unfortunately I'm not sure I have them any more I'm afraid, I've been dealing with a lot of images.

I was very diligent about submitting the crash reports, so you should have 10-20 examples. Not sure if you can see who they come from, but if you can hopefully you find them.


A cordite stone will work well against the broiler. But as with any stone, you're going to want to hit it up slowly to reduce breakage. I'd recommend at least 40m heat up to whatever your oven's top temp is (probably 550), then switching to broiler after that point.


It doesn't have to be a WFO (wood fired oven), but you will get slightly different results depending on wood/gas/electric.

I used to have a WFO, but after I moved houses I've switched to all electric. It's different and more convenient, but I do miss my old WFO at times. Still makes great pizza though, and most folks won't be able to tell the difference.


I 100% endorse these recommendations (I say this as someone who makes 3-6 pizzas a weekend, with an oven that does 900+ degrees as well).

I'll also put in a little plug for my dough calculator here: http://maybepizza.com/calc/ , which is a bit more accessible on hand held devices.

I like that you're keeping a historical record on your spreadsheet- that's a neat idea.


OOoooO I like your style mister!

Let people post their results, correlated with their location and time to pull humidity from the local weather and give them a place to store results and we can crowd source our way to some serious pizza! :P


The towns around Seattle are also building up quite a bit, unlike around SF where a lot of places just refuse to.


You're aware of the application_id pragma? That's what this guy was created for: http://www.sqlite.org/pragma.html#pragma_application_id


Hah, I read that and thought "Hmmm, I wonder if Gus knows about this? He should use it in Acorn". Then I read your username :)


That's good, but is not enough. A metadata support would be useful!

e.g. It's like with photos (JPG) were you would only know it was shoot with a Canon camera, or a music file (MP3) that only stores the application name media player.

Most common file formats support metadata formarts like JPEG with its EXIV, ITPC, XMP and MP3 with ID3 v1 & v2, etc.

So for SQLite4 a very simple key value format would be great, with some predefined key-fields.


You can always embed a "metadata" table in your schema. Not ideal but would probably do the job in a lot of cases.


Ah, no I wasn't. The file format page simply marks that region as reserved. http://www.sqlite.org/fileformat.html


One of the reasons it's slow is because CG bitmap contexts are pre-multiplied, but the Canvas spec requires things to be not-premultiplied, so there's a bit of extra math that needs to happen w/ Canvas vs. straight CG/Quartz.


> the Canvas spec requires things to be not-premultiplied

It does, but unfortunately neither Webkit nor Gecko respect this. Take a PNG with an alpha channel and draw it to a canvas over a white div then read back the pixels; you get the pixels premultiplied by the white behind it. Same with other backing colors. There are cases where it won't premultiply, but unfortunately they're a minority.

(The reason I ran across this particular case is that I use PNGs to compress data, and using the alpha channel to store data is impossible because of the premultiplication.)


Looks like this is from The Architecture of Open Source Applications: http://www.aosabook.org/en/llvm.html

There's some other good stuff (and a book) on the site as well.


I was wondering why the Dr. Dobbs article looked familiar. Thanks for noticing and remembering the original.


That also explains why it references LLVM 2.8, while the dateline says it's from May 29, 2012.


And it makes you wonder why AppCode isn't written in AppCode. At least the Xcode engineers use Xcode to write it…


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: