Da wurde groß seit Monaten die Werbetrommel gerührt für den Download Day, da Mozilla mit seinem Firefox 3 in das Guiness Buch der Rekorde möchte, doch am heutigen 17. Juni sind viele User rund um den Globus enttäuscht und erbost über die "amerikanische Arroganz".
So wurde auf der Homepage des Download-Events mal gar kein Datum angekündigt. Erst auf der Übersichtsseite der abgegebenen Versprechen ist nun das Datum zu sehen:
The official date for the launch of Firefox 3 is June 17, 2008. Join our community and this effort by pledging today.
Doch leider bekommt man erst über Umwege mitgeteilt, dass der 17. Juni eben nicht für jedermann in der Welt der 17. Juni ist. Das Mozilla-Team jedenfalls versteht darunter 10:oo Uhr Lokalzeit San Francisco. Und ja, für uns ist der Dienstag, 17. Juni, dann schon fast rum, denn das entspricht in unserer Zeit 19:00 Uhr abends.
Fans in aller Welt haben sich auch entschlossen, zum Download-Day kleinere oder größere Feiern zu veranstalten, doch leider mussten diese in etlichen Ländern der Welt ohne den Download selbst stattfinden. So feiert man also ein wenig, ärgert sich, und geht ins Bett um dann vielleicht morgen noch den Download nachzuholen. Denn dann ist der 17. Juni auch in Amerika angekommen.
Kein Countdown auf der Zentralseite, und selbst wer sich heute vormittag (deutsche Zeit) erst registriert hat, bekommt in der Meldemail keine Informationen darüber, wann es denn los geht.
Man fragt sich schon, wieso im Zeitalter des Internet der modernste aller Browser nicht mit der zentralisierten Weltzeit (UTC) angepriesen wird. Und so gehen inzwischen die ersten potentiellen Download-Teilnehmer schon wieder ins Bett, und wenn sie Mozilla gnädig gesinnt sind, versuchen sie es halt am Mittwoch dem 18. nochmal.
Sorry Ihr Mozillaner, aber um einen Weltrekord mit Weltbeteilung aufzustellen muss man sich auch entsprechend Weltmännisch aufstellen. Da ist ja der Domino-Day besser organisiert!
Links zu Forenthreads:
Posts mit dem Label Computer werden angezeigt. Alle Posts anzeigen
Posts mit dem Label Computer werden angezeigt. Alle Posts anzeigen
2008-06-13
Ach übrigens ....
So ganz nebenbei:
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
Keine Ahnung, was das jetzt soll? Dann google mal:
09:F9:11:02:9D:74:E3:5B:D8:41:56:C5:63:56:88:C0
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
Keine Ahnung, was das jetzt soll? Dann google mal:
09:F9:11:02:9D:74:E3:5B:D8:41:56:C5:63:56:88:C0
2008-06-03
Guiness Buch der Rekorde: Firefox 3 Downloadday 2008
Hallo zusammen, für alle, die es noch nicht wissen:
Das Firefox-Team will mit der Version 3 meines Webbrowser-Lieblings in das Guiness Buch der Rekorde, und zwar mit dem meisten Downloads an einem Tag.
Sie werden dazu einen Downloadday organisieren, dessen Datum aber zur Zeit noch nicht bekannt ist.
Weitere Infos, eine Übersicht der bisher abgegebenen weltweiten Downloadversprechen und mehr gibt es auf der Webseite spreadfirefox.com .
Das Firefox-Team will mit der Version 3 meines Webbrowser-Lieblings in das Guiness Buch der Rekorde, und zwar mit dem meisten Downloads an einem Tag.
Sie werden dazu einen Downloadday organisieren, dessen Datum aber zur Zeit noch nicht bekannt ist.
Weitere Infos, eine Übersicht der bisher abgegebenen weltweiten Downloadversprechen und mehr gibt es auf der Webseite spreadfirefox.com .
2008-04-08
Der Geek am Abend ...
Wann weisst du, dass du dich zuviel mit Computern beschäftigst?
Wenn du das Wort "Hubschrauber" liest und es für einen Kosenamen für den Netzwerktechniker hältst!
Wenn du das Wort "Hubschrauber" liest und es für einen Kosenamen für den Netzwerktechniker hältst!
2008-02-15
Esoteric Programming Language: CopyNPaste
Well, there is just a good bunch of Esoteric Programming Languages on the market, some really serious (means: causing serious damage to your brain), some meant as a joke .
Sigh, would I have more time, I could contribute with an idea for a new one.
What makes modern PLs so successful? It is that they express common programming patterns and paradigms directly on the code level.
A good example is Scala, which incorporates e.g. the singleton pattern with the keyword 'object', or implicit getter/setter generation for a property (you find that in Groovy too).
And here is the new idea, here is one pattern which was never implemented on language level:
Copy and Paste.
Really, a such often used pattern, and no language designed for it ....
And it would be so easy!
Simply take a base language, say: Java.
There you could have a class with a method, say:
In Java, adding a new method which also iterates over its input, but does some other impressing stuff with the elements and does not return a collection would be very annoying. You would copy and paste the above method and change the parts which shall differ from the original version per hand.
But why doing it yourself if your computer can do it for you? So it would be much better to simply tell your computer what to do, and the best way is to make this an integral part of the language itsself.
So the job could be done very easy with CopyNPaste, a language based on Java, but with additional features:
It will indeed become more interesting if the second method will be used as template for a third one ...
The advantages are obvious: You have to think only once about the way the first method doSomething() shall work. Then you are free to concentrate on how the method doSomeOtherThing() differs from that method.
You are free to think in your copy and paste paradigm without leaving this context when doing the new coding.
Thinks can be so easy ...
Sigh, would I have more time, I could contribute with an idea for a new one.
What makes modern PLs so successful? It is that they express common programming patterns and paradigms directly on the code level.
A good example is Scala, which incorporates e.g. the singleton pattern with the keyword 'object', or implicit getter/setter generation for a property (you find that in Groovy too).
And here is the new idea, here is one pattern which was never implemented on language level:
Copy and Paste.
Really, a such often used pattern, and no language designed for it ....
And it would be so easy!
Simply take a base language, say: Java.
There you could have a class with a method, say:
1 public class MyTest {
2 ...
3 public Collection doSomething(Collection input) {
4 Collection newcoll = new SomeCollectionType();
5 Iterator iter = input.iterator();
6 while (iter.hasNext()) {
7 Element elem = (Element) iter.next();
8 Object someNewElem = somethingReallyImpressingDoneWith( elem );
9 newcoll.add( someNewElem );
10 }
11 }
12 }
In Java, adding a new method which also iterates over its input, but does some other impressing stuff with the elements and does not return a collection would be very annoying. You would copy and paste the above method and change the parts which shall differ from the original version per hand.
But why doing it yourself if your computer can do it for you? So it would be much better to simply tell your computer what to do, and the best way is to make this an integral part of the language itsself.
So the job could be done very easy with CopyNPaste, a language based on Java, but with additional features:
1 public class MyTest {
2 ...
3 public Collection doSomething(Collection input) {
4 Collection newcoll = new SomeCollectionType();
5 Iterator iter = input.iterator();
6 while (iter.hasNext()) {
7 Element elem = (Element) iter.next();
8 Object someNewElem = somethingReallyImpressingDoneWith( elem );
9 newcoll.add( someNewElem );
10 }
11 }
12
13 paste:: copy(L:{3-11}) -> {
14 onLine(1): s/Collection/void/ s/doSomething/doSomeOtherThing/ ;
15 delLine(2);
16 delLine(6);
17 onLine(5): delChar({1-21}) ; s/thingReallyImpressing/OtherThing/ ;
18 }
19 }
It will indeed become more interesting if the second method will be used as template for a third one ...
The advantages are obvious: You have to think only once about the way the first method doSomething() shall work. Then you are free to concentrate on how the method doSomeOtherThing() differs from that method.
You are free to think in your copy and paste paradigm without leaving this context when doing the new coding.
Thinks can be so easy ...
2008-02-13
Weisheit aus der Arbeitswelt
Schickte uns ein Kollege:
A train station is where trains stop.
A bus station is where busses stop.
A Work Station is where ...
2007-12-18
How not to use static class members
Recently I came across a new experience which I consider a good example of "How not to use static class members".
Static class members are members (attributes and methods) which are shared between all instances of a class.
I.e.: If one instance changes the value of a static attribute, all other instances know this new value immediately.
Static members -particularly attributes- are shurely useful for configuration purposes, where all instances share a really really common knowledge with each other.
Static members are also indeed necessary for patterns like Singleton or Factory.
They are absolutely necessary to declare constants.
BUT: Static members are fatal if their usage include a runtime aspect.
I experienced that, when I inherited some code which extended the JUnit Framework to do validation on a loaded Model. Each validation was declared as test method of a so called "ValidationCase". As JUnit implicitly creates new instances for each test method to be called as test case.
So when running a specific test class, there are a bunch of instances of this class. For the validation now they had to share the model element to be tested.
The quick answer to this problem was: put it into a static member, all instances will know it then. Advantage: The location where these instances were created was inside the JUnit framework and didn't need to be touched.
BUT:
The error in this notion was: Not all instances of a test class share this model element. (As there are more model elements which are tested later and before by the same test class).
So the rule is: Only all instances of the test class which exist at a given time share this knowledge. At other times the share contains other information, shared by all instances actually existing then.
It worked well as long as only one model element was validated at a time.
The problem of this approach occured when once the validation system was extended to call a validation of one model element out of a validation of the other.
Now there were two groups of instances, one for element A, one for element B. But when B was under test, all instances shared the reference to B. And the reference to A was lost. Overwritten at a point in time.
Even this worked, as long as the validation of B happened to be the last action in the test of A, and the A reference was never needed afterwards.
But it was obvious that this card house once would collapse....
So: Everytime you introduce a static variable into a class, check carefully if its value is really valid for all instances of this class, even over time.
Avoid using static members out of well known pattern (like constants, Singleton, Factory ...).
Static class members are members (attributes and methods) which are shared between all instances of a class.
I.e.: If one instance changes the value of a static attribute, all other instances know this new value immediately.
Static members -particularly attributes- are shurely useful for configuration purposes, where all instances share a really really common knowledge with each other.
Static members are also indeed necessary for patterns like Singleton or Factory.
They are absolutely necessary to declare constants.
BUT: Static members are fatal if their usage include a runtime aspect.
I experienced that, when I inherited some code which extended the JUnit Framework to do validation on a loaded Model. Each validation was declared as test method of a so called "ValidationCase". As JUnit implicitly creates new instances for each test method to be called as test case.
So when running a specific test class, there are a bunch of instances of this class. For the validation now they had to share the model element to be tested.
The quick answer to this problem was: put it into a static member, all instances will know it then. Advantage: The location where these instances were created was inside the JUnit framework and didn't need to be touched.
BUT:
The error in this notion was: Not all instances of a test class share this model element. (As there are more model elements which are tested later and before by the same test class).
So the rule is: Only all instances of the test class which exist at a given time share this knowledge. At other times the share contains other information, shared by all instances actually existing then.
It worked well as long as only one model element was validated at a time.
The problem of this approach occured when once the validation system was extended to call a validation of one model element out of a validation of the other.
Now there were two groups of instances, one for element A, one for element B. But when B was under test, all instances shared the reference to B. And the reference to A was lost. Overwritten at a point in time.
Even this worked, as long as the validation of B happened to be the last action in the test of A, and the A reference was never needed afterwards.
But it was obvious that this card house once would collapse....
So: Everytime you introduce a static variable into a class, check carefully if its value is really valid for all instances of this class, even over time.
Avoid using static members out of well known pattern (like constants, Singleton, Factory ...).
2007-11-08
Hacker's Emblem
So since today you find a new simple little logo on this site:
What is it? What is it about?
Why do I display it here?
I will answer the last question first:
Because I am a software developer, grew up with Unix (and now Linux), saw the upcoming of the Internet and the Hacker culture (see also: History) and strongly sympathise with the paradigm of 'free' like used in 'free software'. This logo symbolises how I now understand life and society, perhaps also the universe and all the rest ;-) .
The other questions are well explained here:
The Hacker Emblem and The Emblem's FAQ
and in german:
Das Hacker Emblem und Häufig gestellte Fragen zum Glider
Daneben: Was ist ein Hacker? - leider sind andere vormals vorhandene deutsche Übersetzungen von ESR's Texten inzwischen nicht mehr verfügbar.
What is it? What is it about?
Why do I display it here?
I will answer the last question first:
Because I am a software developer, grew up with Unix (and now Linux), saw the upcoming of the Internet and the Hacker culture (see also: History) and strongly sympathise with the paradigm of 'free' like used in 'free software'. This logo symbolises how I now understand life and society, perhaps also the universe and all the rest ;-) .
The other questions are well explained here:
The Hacker Emblem and The Emblem's FAQ
and in german:
Das Hacker Emblem und Häufig gestellte Fragen zum Glider
Daneben: Was ist ein Hacker? - leider sind andere vormals vorhandene deutsche Übersetzungen von ESR's Texten inzwischen nicht mehr verfügbar.
2007-10-12
(K)ubuntu und -studio und so....
So, nachdem ich damals mit Suse 6.3 und Debian 3.0 mit Linux in eine Pause gegangen bin, geht's jetzt mal wieder los. Warum?
Vier Gründe:
Nachdem ich Kubuntu nun ohne größere Probleme (nur mit einer durchwarteten Nacht) auf meinem PII 400 MHz mit 128 MB RAM laufen habe und das Dingen ganz locker meinen alten Epson Stylus 400 Printer und meinen HP PSC 1110 all-in-one angesprochen hat, fühlt es sich ganz gut an, das auch auf richtigen Rechnern zu installieren.
Demnächst wird es hier also ein paar Erlebnisberichte zu Linux in Rover's Camp geben.
Vier Gründe:
- Vista kommt mir nicht auf die Platte, und da XP irgendwann doch mal ausläuft, muss ich schauen, was danach kommt. M$ ist es möglichst nicht!
- Ich will mal endlich anfangen, mehr Musik auf meinem Rechner zu basteln, und Ubuntu hat mit der Studio-Version ja nun was passendes für mein Budget auf die Welt losgelassen.
- Ich war durch meinen Unix-geleiteten Werdegang ja immer sehr Linux-affin, jetzt gehe ich also back to the roots.
- ... äh ... hab ich vergessen. Setz einfach was ein ...
Nachdem ich Kubuntu nun ohne größere Probleme (nur mit einer durchwarteten Nacht) auf meinem PII 400 MHz mit 128 MB RAM laufen habe und das Dingen ganz locker meinen alten Epson Stylus 400 Printer und meinen HP PSC 1110 all-in-one angesprochen hat, fühlt es sich ganz gut an, das auch auf richtigen Rechnern zu installieren.
Demnächst wird es hier also ein paar Erlebnisberichte zu Linux in Rover's Camp geben.
Abonnieren
Posts (Atom)
