Wie steht es denn eigentlich um unser Bildungssystem? Heute, in der Zeit von Google und Wikipedia? Wie viel Wissen brauchen wir noch und lernen unsere Kinder richtig bzw. das richtige? Wie könnte es sein? Gunter Dueck gibt einen sehr guten Einblick in wie es seiner Meinung nach aussehen könnte:
Jetzt hoffe ich noch dass sich unsere Bildungsministerin das auch ansieht….
I need to rant about this… the Dojo documentation is simply in very very bad shape… For example the superb description of the dojo.subscribe feature:
This is one of the major features, available since Dojo 0.9. And there is NO documentation available. And I’m even not going to talk about the fact that there are tons of broken links in the documentation or examples do not work on their own site… (if samples are available at all).
“Unbeatable JavaScript Tools” – I agree to this slogan 100%. Unbeaten in performance, bugs and documentation.
</rant>
IPv6 wird dieser Tage 15 Jahre alt… Ja, ein Protokoll welches noch gar nicht wirklich verwendet wird…. und aufgrund seines Alters im aktuellen Internet einige Probleme haben wird.
Und so kommen auf die Internet-Nutzer einige sehr unschöne Erfahrungen zu. Damit sie dann trotz der Fehler von Herstellern und Betreibern ins Internet kommen, müssen sie viel mehr über IPv6 lernen, als sie je wissen sollten. Denn schließlich handelt es sich um ein Protokoll einer recht tiefen Netzwerkebene, also ein technisches Detail. Wer das Internet benutzt, sollte darüber eigentlich gar nichts wissen müssen.
Dem kann ich nur zustimmen… es wird sich aber leider nicht vermeiden lassen… die Umstellung wird der Horror!
Der ganze Geburtstagsartikel zu den kommenden Problemen mit IPv6 ist auf heise Netze zu finden.
Oh yeah! This blog post perfectly describes the awesome and the horrible about working from home…. Especially the one on degration of social skills (click on the thumbnail to the right to see it larger) is super-funny and of course a bit true….
Don’t get me wrong, working from home is great (as you can see in the first “awesome” comics), that’s what friends usually notice first…. however I think it should be a good mix between being in the office (and hopefully meeting someone there!) and staying at home to focus on programming….
Be sure to check out the full comic, highly recommended!
After complaining about Dojo taking so long fixing bugs I found another quite interesting bug report this morning:
Yes, fixing the dojo.back in IE8 is definitely harder than the 1/2 line fix for 8546, but in the end dojo.back is “supported” since Dojo 1.0, so I’d expect that Dojo is tested against new browsers and bugs are fixed in a timely manner…
And the saga continues… I reported a Dojo bug about scheme-less URLs in March (filed against 1.4.2)… now the brand new 1.5 has been released and the (simple-to-fix bug)… was not fixed.
Why? Well, I don’t know. Maybe because they don’t care? The comment in bug 8546 is:
It’s been open for 18 months, and it was pointed out to me as a bug by a large user of Dojo and jQuery. They reported the issue to jQuery, and it was fixed in 2 weeks, and we’re going on 18 months.
Sorry dojo, speed-wise you already lost, no matter what you do!
Kleinanleger, die über Online-Broker im Markt mitmischen wollen, scheiden selbstredend aus. Sie sind in diesem Spiel die geborenen Verlierer.
Leider sieht es genauso aus. Warum? Ist hier nachzulesen.
Sometimes I have the feeling that the only large Web site that uses scheme-less URLs is the one I work with during office hours… because not a lot of Web sites use this handy feature which allows to include resources independent of the protocol (i.e. <link type=”text/css” rel=”stylesheet” media=”all” href=”//www.domain.com/styles/main.css” /> – note the missing protocol). This works cross browser and is perfectly valid – and saves the hassle of security warnings in IE in case of secure Web sites.
Anyhow, when I used the jQuery library it turned out that these scheme-less URLs confused the .getScript function. The bug was easy to find and report and after some whining it got fixed. I mean, how hard is it? Fix the simple bug, add a test case to the unit tests (you do unit test, don’t you?), run the tests done.
Does not seem to be the case with Dojo, which experiences the same bug (already reported here and here). Not only that the bug is open since 14 month, this simple bug was reported in version 1.2.3 and won’t be fixed until version 2.0? Come on, you must be kidding! Signing up and submitting a comment or patch (1/2 line of code: || relpath.indexOf(‘//’) === 0 appended to the first if in the function _xdIsXDomainPath) is also not possible because the user sign-up leads to a 404 page. Uuups.
So I’ll end up with maintaining my local patch file, and hopefully I remember to apply the patch in case there is a future Dojo upgrade…
During the beginning of the iPhone Apps area a lot of multi-protocol messengers came out. They allowed the users to use one application to chat via MSN, ICQ, Jabber and others. For most of these clients a new account had to be created – the service provider would then store the username/password of the IM services.
So far, so good.
Now, after testing some different applications for a while, I decided I don’t need some of them so I removed the applications from the iPhone. But the Websites still have an account which stores all my MSN, ICQ, … passwords, right?
For most providers it was not a big deal to remove or delete the account – the “hardest” was to write a mail to the support to get a hidden URL where I could request removal.
Not so for eBuddy. They simply don’t offer any way to remove an account. Yes, I can remove all IM service accounts from the eBuddy-account, but I cannot remove the eBuddy account itself. I also tried sending various mails to feedback@ebuddy.com, pr@ebuddy.com or privacy@ebuddy.com – all unanswered, even after several reminders.
So I can only recommend to think twice before creating an account with eBuddy – there is no way to opt out and it seems there there is no support at all!
Today I stumbled across a very strange IE issue. Again. Basically the code that was working fine in all real browsers – the code loaded some HTML fragment containing script tags using AJAX and added it to the page. Nothing complicated, except that those script tags require some special handling in Internet Explorer, as they do not execute automatically when being added to the page:
if(IE) {
var scripttags = NewlyAddedDomViaAjax.getElementsByTagName(“SCRIPT”);
var head = document.getElementsByTagName(“head”)[0];
for(var i=0, j=scripttags.length; i < j; i++)
{
var scripttag = document.createElement(“SCRIPT”);
scripttag.src = scripttags[i].src;
head.appendChild(scripttag);
}
}
No big magic and works fine. Except for the case that the script tag comes as first element in the newly inserted HTML code. In this case the getElementsByTagName is *not* returning the script node at all – it just returns an empty result set. This means that the JavaScript code is not executed in IE….
Luckily this problem is quite easy to solve – just move some other HTML code in front of the HTML snippet that is returned via AJAX – place all the script tags at its end and everything will work fine!
btw, how about Google? Not of great help, the closest I could find was this unanswered forum post.