Quote: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.
Quote: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.
Quote: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?
