Help me with my new website!

[FlatAssembler]

I looked at your new phoneme-game page, and its behavior and the code behind it look a lot more like what I'd expect.

There is no point in continuing developing it. It's a failure from its very beginning. I thought it would be fun to play, almost nobody finds it fun to play. I thought I've figured out some algorithm that's relatively easy to implement and that would produce relatively-convincing results, they're convincing to nobody who is into historical linguistics (and I can kind of see why, but I couldn't have seen that before I actually wrote that algorithm and spent days tweaking it). Maybe I'll have better luck next time.

Personally, I'd recommend you start working with server-side code and a database.

I don't know. I mean, the only server-side language 000webhost allows me to use is PHP, which is rather, well, strange to me (It somewhat resembles PERL).
Besides, the server works a lot faster if you just serve HTML files, rather than process them with PHP, right? 000webhost claims my site can take 300 requests per minute, but that's true for WordPress sites, right? If I simply serve unprocessed HTML files, I can serve almost unlimited requests per minute, right?

By the way, what do you guys here think, is it better to work in quirks mode or in standards mode?
I prefer working in quirks mode, because I find it easier to deal with the CSS box-model not working consistently across different browsers (also, the CSS box-model bug doesn't appear in Internet Explorer 11 and other modern browsers even in quirks mode) than having to deal with "document.body.clientHeight" and the likes working differently in various browsers (in quirks mode, they work in all browsers as in Internet Explorer 6). Also, working in quirks mode prevents Internet Explorer 9 from displaying the JavaScript-generated SVGs on my site and therefore hiding the text with them (since it doesn't correctly position them).

Also, what do you think about Facebook? Specifically, do you think its censorship of the deviant political views, such as genocide revisionism, is a good thing? I don't quite see how it can be, in fact, it seems to me it's forcing people into believing something that isn't necessarily true.
I understand that many people might get upset when I say that, for all we know, the conventional narrative of the Genocide of Vukovar may be false. I mean, it's the narrative that our country is built on, it's relatively deeply engrained into our culture, and so on. But, let's face it, the evidence that the genocide happened on the scale accepted by the mainstream history is (at least as far as I am aware) quite vague. The evidence that the Serbian president Slobodan Milosevic had something to do with that? Even more so. The evidence that the Croats were the good guys who did everything they could to prevent the genocide? Non-existent, in fact, even the BBC news noted at the time that the Croatian general Mile Dedakovic apparently let it happen, for which he, in an interview, blamed the Croatian president Franjo Tudman for not sending him enough weapons. Is it possible, if not probable, that they let it happen on purpose, or even made it happen on purpose, and then inflated the numbers and somehow made themselves seem like the good guys?
And Facebook banning me for saying that is forcing the belief, that the mainstream history is correct, on me, isn't it? I mean, that belief is already forced upon people. Hundreds, if not thousands, of people, in both Croatia and in Serbia, have been punished for the things we can't know for certain they did, and thousands of people are being glorified as the good guys by the government, and we cannot be certain they indeed are. People are given that sense of certainty that it happened, and Facebook bans me for even mentioning the possibility that it's false.
I didn't mention that on my website, just so 000webhost doesn't also ban me.

[bennyboy]

re: language
I'm telling you this bluntly. If you don't like .php, then go with ASP.NET CORE MVC. You get to use Visual Studio, you have all the brains of Microsoft behind you, and it uses C#, which I like a lot. A quick google search for something like "best free asp.net CORE host" provides plenty of pages and suggestions. It used to be you needed a full-fledged Windows server to run ASP.NET 4.x, but .NET CORE is different-- it can be deployed almost anywhere. What you REALLY want is a free provider that also allows you a SQL database.

Visual Studio can not only be used to write ASP.NET CORE sites, but you can use it for making Windows apps, or for scripting for Unity games. It's free, and it has the full brainpower of Microsoft behind it.

You can try starting here: https://www.reddit.com/r/csharp/comments...an_aspnet/

re: quirks mode
You should assume that users have a modern browser, or have a client check at the front of your site which screens old browsers out: "This site does not support old technology. Please update your browser." My philosophy is anyone who doesn't have a browser capable of running HTML5 content properly does not deserve to be viewing any internet pages, ever.

re: Facebook
Fuck Facebook. People need to get a life.

[FlatAssembler]

You get to use Visual Studio, you have all the brains of Microsoft behind you, and it uses C#, which I like a lot.

Right now, on the university, they force me to learn AutoCAD. It's very hard (I am not even that good at using a mouse, let alone something more) and, if I want to pass that test, I probably need to dedicate all my free time to that.

My philosophy is anyone who doesn't have a browser capable of running HTML5 content properly does not deserve to be viewing any internet pages, ever.

Then, again, where do you draw the line? Do you support, for example, Internet Explorer 11? It seems to be sort of an immortal browser. On the HTML5 test, it scores about the same as Safari 6.2 or Android Stock Browser 4.1, yet almost all websites work in it, but quite a few websites don't work in Safari 6 or, even worse, Android Stock Browser 4.1. Websites are sort of expected to work in Internet Explorer 11 for some reason.
Android Stock Browser 4.1 is really full of weird bugs, and I didn't fully realize that until I tried to tweak the compiler page to work there. The main difference between Android Stock Browser and Internet Explorer appears to be that Internet Explorer bugs are more documented (Android Stock Browser 4.1 doesn't pass the Acid2 test either). Android Stock Browser appears to completely ignore the "onmouseleave", which I used to close the menu once the user moves their mouse somewhere else, and it works even in Internet Explorer 6. The expected behavior on touch-screens is, as in Mobile Chrome, that a menu gets closed once the user taps somewhere else, right? What's even weirder is that "onmousemove" works as expected. And that buggy mouse-emulation is just a part of the story. It doesn't even appear to support the CSS "z-index" properly. Namely, if you set the "z-index" in CSS, but don't set the position in CSS, then position the element in JavaScript, it somehow brings that element to front (seriously). I've read somewhere that Internet Explorer 6 had some very similar bug, but my code didn't trigger it. I've solved it by changing the "display" property in JavaScript when necessary. And so on.
But, when you think about it, old browser is better than no browser, especially when it comes to JavaScript. Duktape and, even worse, Rhino on Android (on Samsung Galaxy S3 Mini, with 1 GB RAM) appear to execute JavaScript even more slowly than Internet Explorer 6 (on my 11-year-old laptop with 1 GHz Celeron processor and 512 MB RAM) does. It's hard to guess why, Internet Explorer 6 has to, apart from interpreting JavaScript, also interpret CSS and parse HTML.

Fuck Facebook. People need to get a life.

I couldn't agree more. However, many people, who otherwise have their lives, seem to think Facebook is somehow a reliable source of information about what's going on around them. Quite ironic that those are usually the same people who despise Wikipedia.
Obviously, Facebook has no qualified editors and there is nothing, unlike on Wikipedia, that could replace them, so it has to be full of fake news. And not only is it full of fake news, but if you say that mainstream media might have got some important topic wrong, you will get routinely shut up.
It's quite ironic that that Facebook censorship claims to be anti-racism. Here in Croatia, that story of the Genocide of Vukovar (that the Serbs, the most numerous national minority in Croatia, are genocidal maniacs and that Croats did everything they could to stop them) is used to justify nationalism and racism in the government. Yet, if you say that maybe that story isn't completely true, you get banned from Facebook.
Though, how much a web-page is shared on Facebook is a good predictor to how many views it will get, right?

[bennyboy]

Your whole site doesn't have to support a particular browser. You can do checks for individual features, or you can just check what browser people are using, and warn them when they enter the site. For example, I'm using javascript to get audio permissions, record some mic audio, convert it to .mp3, and upload it in a post request using AJAX. Only the very newest version of Safari supports the required technology. Edge supports it, but IE11 does not. FF and Chrome support it on both Android and Windows, but not (yet) on Apple. I know all those browsers will probably support the technology some time in 2019-- so in my case, I have to check support for the FEATURE, rather than the browser.

If I try to use the recording feature, and there is an error, then I can simply pop up a dialogue: "This page requires functionality which your browser does not support. Please use the newest version of:
-Chrome for Windows
-Firefox for Windows
-Chrome for Android

My case is special, though-- my users are existing customers, and they will feel left out if they can't use the functionality. In other words, I can count on them to take the effort to go find a better browser and try again. Obviously, not all sites will be able to do that.

---

Obviously, Facebook has no qualified editors and there is nothing, unlike on Wikipedia, that could replace them, so it has to be full of fake news. And not only is it full of fake news, but if you say that mainstream media might have got some important topic wrong, you will get routinely shut up.
It's quite ironic that that Facebook censorship claims to be anti-racism. Here in Croatia, that story of the Genocide of Vukovar (that the Serbs, the most numerous national minority in Croatia, are genocidal maniacs and that Croats did everything they could to stop them) is used to justify nationalism and racism in the government. Yet, if you say that maybe that story isn't completely true, you get banned from Facebook.
Though, how much a web-page is shared on Facebook is a good predictor to how many views it will get, right?

I suspect that the WAY you said things might have been part of your banning, not only your political position. At the risk of minimizing the importance of your country in the global community, I seriously doubt a huge company like Facebook cares enough about the politics to police and ban people based on their positions.

But if you say "fucking lying serb pieces of shit" or "fucking Croat pieces of shit," then while you might feel justified in your position, you are very likely to get red-flagged and removed.

I had this problem in the game League of Legends. One team mate over and over let his laner roam and attack me, and never listened to pings. He then blamed me for dying to his laner, and I said "Dude, stfu. You let that guy fucking rape me in the jungle." I instantly got banned for using offensive language, even though in the context I felt perfectly justified in cursing at that guy.

Remember that-- these days, you have to play a victim card: "Oh. . . my feelings aren't being heard. My humanity is under attack. These guys are violating my sense of cultural and national identity!" Then you're fine. They are likely to be the ones banned.

[FlatAssembler]

I have to check support for the FEATURE, rather than the browser.

Well, in the compiler web-app, I abstained from browser-sniffing as much as possible. Sometimes detecting a lack of particular feature and mitigating it is easy to do, like here:

Code:

if ((typeof document != "undefined") && !document.getElementsByClassName)
    document.getElementsByClassName=function(str)
    {
        var niz=document.getElementsByTagName("*");
        var ret=[];
        for (var i=0; i<niz.length; i++)
            if (eval("/(\\s|^)"+str+"(\\s|$)/").test(niz[i].className))
                ret.push(niz[i]);
        return ret;
    }

or here:

Code:

if (!Array.prototype.includes)
    Array.prototype.includes = function (x)
    {
        for (var i = 0; i < this.length; i++)
            if (this[i] == x)
                return true;
        return false;
    }

Detecting and mitigating the inconsistent implementations of "innerText" (which are probably unintentional bugs in browsers) also wasn't very hard, all I had to do was this:

Code:

var kod = document.getElementById("assembly").innerText;
if (!kod)
{
    alerted = 1;
    alert("Emitter error: Your browser doesn't appear to support the JavaScript 'innerText' directive. Can't send the assembly code to the server. Please use either Internet Explorer or some modern browser.");
    document.getElementById("AJAXmessage").style.display = "none";
    return;
}
if (/\n\n/.test(kod))
    kod = kod.replace(/\n\n*/g, '\n');
if (!/\n$/.test(kod))
    kod+='\n';

However, sometimes detecting a particular feature isn't easy. For instance, the code I've used to detect SVG support is this:

Code:

if (!document.createElementNS)
{
    alert("Diagram error: Can't access the SVG elements from JavaScript. You appear to be using a browser that doesn't support that. If you are using Internet Explorer 11, make sure it isn't running in the compatibility mode.")
    alerted = 1
    return
}

Is that correct? It's conceivable that some particular browser supports "createElementNS", but can't render JavaScript-generated SVGs, right?
The CSS Box-Model bug in Internet Explorer 6 also isn't trivial to detect. The code I ended up using, after lot of experimenting, is this:

Code:

if ((document.getElementById("zatvori").offsetWidth<18 || document.getElementById("zatvori").style.width=="21px") && document.getElementById("zatvori").style.display!="none") ie6=true;

The "onmouseleave"-bug in Android Stock Browser 4.1 doesn't appear to be detectible via JavaScript, does it? Neither is the Android Stock Browser itself easy to detect via JavaScript, since it uses almost the same user agent as Safari (which doesn't suffer from that bug). I mean, the work-arounds I've ended up using look like this:

Code:

if ((typeof navigator != "undefined") && /(M|m)obile/.test(navigator.userAgent))
   document.getElementById("content").onclick = function () {
      document.getElementsByTagName("nav")[0].style.display = "none";
};

That assumes all mobile browsers suffer from that bug, this is not true and it will be even less true in the future.
The "z-index"-bug in Android Stock Browser 4.1 also appears not to be easily detectible via JavaScript. I've mitigated it similarly, but I suppose that if I managed to find a reliable way of detecting Android Stock Browser, my web-app would run smoother in other mobile browsers.
And, the only work-around around Internet Explorer 11 ignoring the CSS "overflow" property on the JavaScript-generated SVG elements on my homepage is browser-sniffing, right?

Code:

if (!(navigator.userAgent.indexOf("Trident")+1))
    crtanje.appendChild(krug);

OK, maybe using SVG polylines would be slightly better, but this is far easier to do, isn't it?

I suspect that the WAY you said things might have been part of your banning, not only your political position.

If I remember correctly, I posted the following on a day of an anniversary of the Genocide of Vukovar: "Čemu plakati za Vukovarem? Po svemu što znamo, Bitka za Vukovar mogla bi biti samo mit!". That means: "What's the point of crying about Vukovar? For all we know, the Battle of Vukovar may be just a myth!".

---

By the way, which browser do you think will become the most hated among web-developers once Internet Explorer, Microsoft Edge and Android Stock Browser (all of which are either deprecated or about to become deprecated) disappear? I think it's going to be Firefox. I've had to mitigate Firefox-specific behavior two times in the compiler web-app:

Code:

if (document.getElementById("zatvori").style.left.substring(0,document.getElementById("zatvori").style.left.length-2)
-document.getElementById("content").style.width.substring(0,document.getElementById("content").style.width.length-2)>10)
    document.getElementById("content").style.width=
        document.getElementById("zatvori").style.left.substring(0,document.getElementById("zatvori").style.left.length-2)-3+"px";

Code:

if (!window.event) {
    isFirefox=true;
    window.event=new Object();
}
if (isFirefox)
{
    window.event.clientX=e.clientX;
    window.event.clientY=e.clientY;
}

For comparison, I've had to mitigate Opera-specific behavior once, and I've never had to mitigate Chrome-specific behavior (I was developing in Safari).

[bennyboy]

If you are trying to support older browsers, this is your life. For me, it doesn't matter, because I use HTML5 a lot, and older browsers don't support those tags anyway-- I simply do not care whether they are supported. I would never bother directly manipulating so much code like you have, because I need to roll features into production for real-life customers, and I can't dick around for a year with all that stuff.

IE11 and the Apple browsers are currently a problem, since a lot of people use both of them. But in my case, I will just give users of those browsers the capability of uploading their own sounds instead of direct recording. Doing that will save me potentially hundreds of hours of coding, and let me work on other features of my site.

[FlatAssembler]

I use HTML5 a lot, and older browsers don't support those tags anyway

Using an unsupported tag won't cause a parser error. You use the "main" tag, right? Internet Explorer 11 doesn't support the "main" tag, yet it becomes a part of the DOM and you can manipulate it using JavaScript and CSS. In Internet Explorer 6, the same is true for other HTML5 tags.

I simply do not care whether they are supported.

Now that I see making the page render correctly in Internet Explorer 6 doesn't make it render correctly in all modern browsers, I don't care too much either.

I would never bother directly manipulating so much code like you have,

Well, it was relatively easy to do for me since I was hand-writing all the JavaScript. Are you using CoffeeScript or something like that?
With CoffeeScript, it should be even easier to support older browsers since it transpiles to ES3, so I guess you are not using CoffeeScript, but something similar.
Do you think such things really help? I think they probably help a little if you find the time to learn them (CoffeeScript, for example, has a very weird syntax to me, but I can see how some of its features can come useful), but we cannot compare hand-writing JavaScript to hand-writing Assembly.

IE11 and the Apple browsers are currently a problem, since a lot of people use both of them.

Apple browsers are a problem?
Well, I can see how Safari on iPhone could be a problem, it has a somewhat quirky font rendering (but that appears to be true not just for Safari, but for entire iOS, since similar problems appear in Objective-C), and it appears to execute JavaScript slightly slower than Mobile Chrome or Android Stock Browser (my SVG PacMan is barely playable on iPhones because of that).
But Safari on MacOS appears to be an excellent browser. I don't even have Chrome installed either on my 12-year-old PC or on my 5-year-old MacAir, but every time I test my website in Chrome on someone's computer, it works exactly the same as in Safari on Mac (apart from maybe taking slightly longer to load). Are you saying it's not like that the other way around (that what works in Chrome needs to be tweaked to work in Safari on Mac)?

By the way, I've managed to tweak almost the entire JavaScript on the compiler page to work in Duktape. Now it's trivial for me to process entire files and output assembly to some other file. You can download the Duktape-compatible version as well as the customized C stub required to run it on the compiler page (there is a link to a ZIP archive containing the source files there). This was my first program written in my own programming language (I call that programming language AEC, "Arithmetic Expression Compiler"):

Code:

AsmStart ;This part of code is Windows-dependent, so it has to be done in inline assembly.
    debug=0
    format PE console
    entry start

    include 'win32a.inc'

    section '.text' code executable
    start:
AsmEnd
i:=1
j:=1
While i<101
    j:=1
    While j<101
       AsmStart
           if debug=1 ;Invoking FlatAssembler preprocessor.
                fld dword [j]
                fstp qword [esp+12]
                fld dword [i]
                fstp qword [esp+4]
                mov dword [esp],_debugOutput1
                call [printf]
            end if
       AsmEnd
        If i>j
            a:=i
            b:=j
        Else
            a:=j
            b:=i
        EndIf
       While (b>1/100)&(a>1/100) ;Modified version of the Euclid's algorithm.
            If a>b
                a:=mod(a,b)
            Else
                b:=mod(b,a)
            EndIf
       EndWhile ;There is a reason why BASIC used different keywords for "EndIf" and "EndWhile", because they are trivial to translate to Assembly :-).
        subscript:=i*101+j
        If a>1/100
           gcd[subscript]:=a ;Warning: Arrays are write-only in this version of AEC, they have to be read in inline Assembly. Hopefully that's not too hard.
        Else
            gcd[subscript]:=b
        EndIf
       AsmStart
            if debug=1
                fld dword [a]
                fstp qword [esp+20]
                fld dword [j]
                fstp qword [esp+12]
                fld dword [i]
                fstp qword [esp+4]
                mov dword [esp],_debugOutput2
                call [printf]
                mov dword [esp],_pause
                call [system]
            end if
       AsmEnd
        j:=j+1
    EndWhile
    i:=i+1
EndWhile
AsmStart
mov dword [esp],_output1
call [printf]
mov dword [esp+4],firstNumber
mov dword [esp],_input1
call [scanf]

mov dword [esp],_output2
call [printf]
mov dword [esp+4],secondNumber
mov dword [esp],_input1
call [scanf]

fild dword [firstNumber]
fstp dword [a]
fild dword [secondNumber]
fstp dword [b]
AsmEnd
subscript:=4*(a*101+b) ;While you need to use inline Assembly to read arrays, you can still calculate subscripts in AEC.
AsmStart
fld dword [subscript]
fistp dword [subscript]
mov ebx,[subscript]
fld dword [gcd+ebx]
fst qword [esp+4]
mov dword [esp],_output3
call [printf]
invoke system,_pause
invoke exit,0

_debugOutput1 db "DEBUG: Attempting to calculate the GCD of %f and %f.",10,0
_debugOutput2 db "DEBUG: GCD of %f and %f is %f.",10,0
_output1 db "Enter the first number (whole number 1-100): ",0
_input1 db "%d",0
_output2 db "Enter the second number (whole number 1-100): ",0
_pause db "PAUSE",0
_output3 db "Their greatest common divisor is: %f",10,0

section '.rdata' readable writable ;Yes, you are expected to declare the variables yourself in inline assembly, as the way it's done varies greatly from one operating system to another.
result dd ?
a dd ?
b dd ?
i dd ?
j dd ?
firstNumber dd ?
secondNumber dd ?
subscript dd ?
gcd dd 101*101 dup(?)

section '.idata' data readable import ;Those functions can't be called from this version of AEC (as the way to call them in Assembly varies from one operating system to another), they have to be called from inline Assembly.
library msvcrt,'msvcrt.dll'
import msvcrt,printf,'printf',system,'system',exit,'exit',scanf,'scanf'
AsmEnd

I don't have the time to continue developing it, though.

[bennyboy]

Using an unsupported tag won't cause a parser error. You use the "main" tag, right? Internet Explorer 11 doesn't support the "main" tag, yet it becomes a part of the DOM and you can manipulate it using JavaScript and CSS. In Internet Explorer 6, the same is true for other HTML5 tags.

No, it's not that. Media features are in a transition state right now. Specifically, OS / browser support for media recording.

Well, it was relatively easy to do for me since I was hand-writing all the JavaScript. Are you using CoffeeScript or something like that?
With CoffeeScript, it should be even easier to support older browsers since it transpiles to ES3, so I guess you are not using CoffeeScript, but something similar.
Do you thing such things really help? I think they probably help a little if you find the time to learn them (CoffeeScript, for example, has a very weird syntax to me, but I can see how some of its features can come useful), but we cannot compare hand-writing JavaScript to hand-writing Assembly.

No, I never use any kind of software in designing a page.

IE11 and the Apple browsers are currently a problem, since a lot of people use both of them.

Apple browsers are a problem?
Well, I can see how Safari on iPhone could be a problem, it has a somewhat quirky font rendering (but that appears to be true not just for Safari, but for entire iOS, since similar problems appear in Objective-C), and it appears to execute JavaScript slightly slower than Mobile Chrome or Android Stock Browser (my SVG PacMan is barely playable on iPhones because of that).

It's not a performance issue. It's a lack of implementation for media queries-- no Apple device pre iOS11 supports the libraries I'm using, and even in iOS11, it's poor support, and cannot be implemented in 3rd-party browsers (like Chrome). 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.

In my case, I'm programming a massive site with a really long to-do list. Voice recording is a huge feature and a big priority, but there are a lot of other things I need to do-- optimizing database searches, creating GUI elements for graphing test results, and so on. I also have to generate huge amounts of content-- new reading materials, audio recordings, tutorials and so on. So I have to ask myself-- what's the maximal use of my time, in terms of the end-user experience?

Fucking around with Apple isn't it, at least not right now.

[FlatAssembler]

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.

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.

It's a lack of implementation for media queries

I 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.

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).

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?

[FlatAssembler]

By the way, here is the second program I've written in my own programming language:

Code:

;So, this is my second program in my own programming language.
AsmStart
    debug=0
    format PE console
    entry start

    include 'win32a.inc'

    section '.text' code executable
    start:

    mov dword [esp],_output1
    call [printf]
    mov dword [esp+4],n
    mov dword [esp],_input1
    call [scanf]
AsmEnd
fib(0):=0
fib(1):=1
i:=2
While i<n+1
    fib(i):=fib(i-1)+fib(i-2) ;Good idea, QBASIC! Treating Assembly arrays as functions, I would have never thought of that! It's really easy to program.
    i:=i+1
EndWhile
subscript:=(i-1)*4
AsmStart
    fld dword [subscript]
    fistp dword [subscript]
    mov ebx,[subscript]
    fld dword [fib+ebx]
    fstp qword [esp+4]
    mov dword [esp],_output2
    call [printf]
    mov dword [esp],_pause
    call [system]
    mov dword [esp],0
    call [exit]

_output1 db "Enter n (0-100): ",0
_output2 db "The n-th Fibonacci number is: %f",10,0
_input1 db "%f",0
_pause db "PAUSE",0

section '.rdata' readable writable
result dd ? ;Yes, you need to declare it to be used internally by AEC. Hope you don't mind! :-)
n dd ?
i dd ?
subscript dd ?
fib dd 100 dup(?)

section '.idata' data readable import
library msvcrt,'msvcrt.dll'
import msvcrt,printf,'printf',system,'system',exit,'exit',scanf,'scanf'
AsmEnd

I really need to stop with that now and start learning for the university!