Hacker News new | ask | show | jobs
by knappador 4155 days ago
In javascript in javascript in javascript... The time when concern seemed actionable has passed; It's clear that the infinite recursion is well underway, and because the arguments are just returns passed in-register, that the call stack will never overflow. I can't tell if there's any logic or reachable return pathways. Is the only way back to reverse time and to have never entered the fractal in the first place? Save yourselves. We can never see the fate of matter that has passed into the event horizon already. The big picture can't be found in the smaller imitations. We can't say that it's over, but we must hold it within our culture that using javascript within javascript is a warning sign, such as curiosity about death or whether the world is a projection of our minds. We must remember that ineffability is effable rather than attempting to reach that effability in all except analytic proofs; even computation of lowly derivatives or irrational numbers cannot be perfectly calculated via machine. Friends don't let friends implement javascript or vehicles for javascript within javascript. It hasn't been proven that there is a conclusion to such exercises. Meanwhile, many have perished chasing truths we can only imagine may be ever even slightly distinguishable from within this universe.
1 comments

There is no recursion. Just some parts which have been implemented in C++/ObjC before (like most of the UI) is now implemented in JS.

Besides, the main engine, i.e. the rendering engine, the JS engine and other core low-level parts (all of Blink and V8) are all still implemented in C++.

I'm fooling around. I'm sure everyone on the project rightfully will get a ton of return on their investment. I'm actually working on a browser UI myself. It's only because of platform OS integration that I'm using Java, but one thing I did learn using a lot of Kivy is how much of a pain it is to be far from the platform libraries.

Unlike Kivy, which is Python, you've chosen JS, so at least your UI is on a more naturally portable layer given that you have a browser runtime right there. Documenting your plumbing into the system libraries will be really critical. The JS community will hack every other piece of the system on their own, but user after user will shy away from the system plumbing because it's not what attracted them initially, so I would prioritize there.

Writing cross-platform UI's may be a pipe dream for now. OpenGL is headed towards a weird place with Mantle and Metal etc while OpenGL Next comes together. The HSA Alliance (Notably missing Nvidia and Intel) might offer some hope that CPU architectures and graphics API's (and GPGPU) will converge again, but right now, HTML5 with JS is probably the best we have for sheer everywhere.

Probably where I would diverge most sharply (and somewhat irreconcilably) with the web community and perhaps even the high-minded ideals of Mozilla is HTML/CSS, but the "superior" tools I find in Android are themselves relatively new. Do I wish that HTML/CSS/JS would go away? Yes, but without need of burial. A technology will displace it someday through sheer elegance that unicorns had not yet fathomed. If it's at all recognizable in what I'm using today, it's an early stage experiment.

> Just some parts which have been implemented in C++/ObjC before (like most of the UI) is now implemented in JS.

Then again it's been implemented in JS before: http://en.wikipedia.org/wiki/XUL