Quote:No, it's not that. Media features are in a transition state right now. Specifically, OS / browser support for media recording.Sorry, I know nothing about those things.
Quote:No, I never use any kind of software in designing a page.Well, I've used some a few times.
For example, on the toponyms page, it was a lot easier to use LibreOffice Writer to edit the text with so many linguistic symbols than to attempt to configure some text-editor to do that, and LibreOffice Writer correctly converts linguistic symbols to HTML (which I simply copied onto my template).
Also, in the Duktape-ZIP, I used Cocoa TextEdit to have the ReadMe file in both HTML and RTF (I've edited the HTML and CSS it outputted and added some JavaScript to set up the layout, of course).
Regardless, my question was not about using the tools to design a page, but about using things like CoffeeScript or Emscripten. They are supposed to help with client-side scripting, that you can write your client-side scripts in some language that would be more appropriate for the problem you are trying to solve, and it gets transpiled into JavaScript.
Quote: It's a lack of implementation for media queriesI don't know, I don't use them. Basic media queries support is allegedly present since Safari 3. I use JavaScript instead, since it's more familiar.
Quote:My understanding is that 3rd-party browser on iPhone are essentially cosmetic-- they are required to run Apple's native web browser under the hood, and cannot replace it.Basically, yes, they all need to use WebKit for HTML and CSS. But it's a good engine, some versions of Opera and Chrome based themselves on it on all platforms. Android Stock Browser 4.1 is also based on an old version of WebKit, and, yes, it's buggy, but it's from the Internet Explorer 9-era, other browsers from that era were way worse. It's not like Apple is forcing people to use Trident.
From my limited experience, I'd say it's the Gecko-based browsers that lead to many compatibility problems today, perhaps just as many as Internet Explorer 11 does. I mean, like, "document.body.clientWidth" returning different results if called consecutively in the same "onresize" handler... It took me hours to diagnose the problem and do some weird hack to fix that.
As far as I know, browser vendors can use their own JavaScript engines on iOS. Embedding, for instance, Duktape into an Objective-C program should be trivial, as Duktape is praised not to use inline assembly and not to attempt to output assembly and compile it on the fly (which is what's forbidden on iOS for some reason). WebKitCore is in the vast majority of cases faster than Duktape, but Duktape is somewhat easier to use, and, if you use Duktape, you can use the same JavaScript engine on all platforms (including those that don't have nearly enough processing power to run something like WebKitCore).
Quote:Voice recording is a huge feature and a big priority.Like I've said before, if I had to implement something like that, I wouldn't even know where to start.
By the way, what do you think, was Facebook right to ban me when I posted, on a day of an anniversary of the Genocide of Vukovar, that it's not worth crying about Vukovar because, for all we know, it could be just a myth?
