938 karma · joined May 16, 2012
https://www.twitter.com/antcatel http://www.github.com/paraboul
e-mail: [username] at gmail
That is, you can trace coins, not owners, unless you're always using the same source address.
And you still want to access the old value if reallocation failed.
Reading through large source code can be very discouraging for someone that want to start programming. Things like this show that with a little bit of Math and few libraries you can bootstrap a little universe.
It's just crazy how the standard is slow to come up with new basic APIs.
I mean, you can make a P2P video streaming application since 1995 using straightforward architecture in a desktop App using less cpu, less middleware and less engineering.
"Streaming video through WebSocket (thus over http upgrade) through a plain-tcp-to-websocket-proxy on top of...".
It feels over-engineered and like TCP-Sockets are a revolution. I know, we can't easily expose plain-socket because of security but still... What's next? UDP for 2018? Socket-binding for 2022?
(Nice work though)
In the teaser video all visible parts are direct screen recordings of:
(1) existing 2D canvas or WebGL demos ported to NiDIUM engine
(2) shots and images from the native embedded UI Framework
Do not expect NiDIUM to read HTML pages or to compete with any existing browser.
Instead, expect a solution to build (and browse) applications, with a fast and unified look and feel.
So:
* Yes, it's a browser, in a sense that it can loads remote "apps/code" via HTTP using URLs (and somehow link them)
* Almost everything is integrated and highly customizable (like the integrated UI Framework)
* Cool APIs like plain-socket UDP/TCP (client and server), GLSL postprocessing on every canvas, layer, etc...
* We've made our best to be compliant with existing APIs (context2D, webgl, commonjs, etc...)
* It ditches HTML & CSS in favor of new things (NML and NSS, we will communicate on this later)
* Low Latency Audio and DSP (and yes, one of us come from the demo scene, hence the poor soundchip music ;-) )
We designed almost everything from scratch, but the whole thing is still at an early stage.
And to relate with tranding topics today about "english accent", we made this video a bit "old school" because we're not native english speaker (french) and a bit afraid of making "talkative" videos.
We will post updates as soon as possible!
Source : Close friend and : https://twitter.com/magicaltux
I guess that most of the DOM API (end user level) has yet to be done along with the javascript API (binding) controlling it (e.g. XHR, Websocket, DOM manipulation, domain security control, etc...).
Next : the browser itself (chrome, modules, tabs, external interfaces, UI, ...).
So, no, not 90%. But I would attribute 50% for starting the project itself and having created something as awesome as Rust.
Did you mean with emscripten to asm.js
You are just saying that C is not clean. (IMHO) nginx code-base is doing a really good job dealing with micro-optimization.
>code looks like if it uses trillions of mutable state
Actually, that's a very good approach. e.g. : nginx parser get optimized out as a big jump table (http://en.wikipedia.org/wiki/Branch_table)
In the first case, comparing 2 integer (4x 8bit) is faster than omitting one byte.
That's is, using ngx_str3Ocmp with c1 != 'O' would be a usage error.
Edit: sltkr, sorry didn't see your reply.
FTFY.
Seriously, I don't get it.