I've recently started a side project for the N64, and this is very relatable! Working within such tight constraints is most of the fun.

Something similar here: https://github.com/lmcd/EasyAnchors

Yep, around 1fps on a 2017 15" MacBook Pro. I'm seeing similar issues with some of my own WebGL work on this new machine :(

* A pixel-perfect WebGL/JavaScript implementation of UIKit/QuartzCore that runs basic iOS apps in a web-based simulator at 60fps

* A Swift 3 -> JavaScript compiler with many language features, full type inference and more

* Many interesting ways of combining the above to form interesting new development/learning/prototyping tools

* One such tool/product has a full WYSIWYG app builder, with drag/drop UI components, auto layout, etc (think Interface Builder but with pluggable logic). I have a backend supporting this that can generate an .xcodeproj, compile, codesign, etc on the fly to a real, fully native app

Started as a browser-based version of Reveal (https://revealapp.com/), and spiralled out of control from there.

One of the spin offs: http://shopmo.co (not fully live)

> A pixel-perfect WebGL/JavaScript implementation of UIKit/QuartzCore that runs basic iOS apps in a web-based simulator at 60fps

That sounds really interesting. Do you have a demo URL or (60fps :D) video of this in action?

How's about this: https://www.youtube.com/watch?v=BD15ncn7KQw

Note: this video is 100% real, but I trimmed out some frames here and there (during keypresses and Shopify auth) to make for a seamless pitch.

Now I kinda understand why no URL yet; this is amazing, and I imagine you don't want to leak how you're doing it quite yet. (How ARE you doing it?)

Is the homescreen part of your system, or is that a synthetic simulation?

I wish I had a practical reason to ask to use this. I definitely want to learn if there's ever a demo I can play with :D

Thx, appreciate it! Pop me an email and I'll keep you in the loop: [email protected]

Here's one approach you could use if you had a reliable zero-day at your disposal. I've been out of the jailbreak scene for a while, so I might be way off the mark:

1) Have zero-day ([0]) that can be used to deliver executable payload over SMS (think Stagefright). iOS devices can receive text messages before the filesystem is decrypted. Perhaps Apple should close this vector.

2) Deploy dylib that patches the SpringBoard UI (where the lock screen lives), disabling the code that counts incorrect passcode attempts

3) Brute force the passcode

[0] http://www.wired.com/2015/11/hackers-claim-million-dollar-bo...

> Perhaps Apple should close this vector.

Perhaps. However, it's very likely that receiving SMS before decryption is not a bug, but a feature.