Thanks for the link. It's a little disappointing to read, but not at all surprising given Telstra's record. Still, I eagerly hang on to the hope that my exchange will indeed be activated by the end of the month!:-D
Reminds of when I was about 7 and I stuck the 1.5V globe from my Go-Go Gadget Yo-Yo into the 240V power point... As I lent forward and flipped the switch, there was a massive bang and flash. It scared the crap out of me, but nowhere near as much as observing the now blackend wall did. Scared crapless of what my dad would do when he found out, I stack everything I had in the room around the area to hide the damage... Somehow dad figured something was up...;-)
Then there was that time I wanted to see if the 'paper bark' tree burnt like paper....
I love programming in Java. It is simple to program in, simple to understand, and I find it just feels 'clean' compared to say C++. The available API tends to be sufficient for most of my needs, and I find the documentation satisfactory and quick and easy to browse.
If I needed to write a quick, run a few times then throw away, command line application, I would code it in Java every time. For everything else I would unfortunately use something else.
On my aging 4 year old computer, graphical java applications feel slow and clunky to use. Even when the GUI has been coded correctly. Java apps with a poorly coded GUI are just unbearable. Also, the resources the Java VM uses isn't exactly small. Another thing is all graphical Java apps just feel out of place. They always look slightly wrong and feel slightly wrong. This tends to put the user off side from the start, and makes them feel that the application is somewhat substandard.
So basically, I feel that as it currently stands Java isn't suited to serious end user applications. As computer performance increases, and some of Java's future graphical enhancements are available, things may change.
However, while programmers are familiar, comfortable and satisfied with other languages, toolkits and tools, I see little incentive for them to start coding in Java.
I knew I was going to screw something up and someone was going to lynch me for it. I must have spent too long looking for spelling errors and not enough time reading the web site.:-)
Speaking of dodgy maths, before my School Certificate (an exam all high school students do in year 10 in Australia)...
Not wanting to be a pedantic prick, but unless things have changed substantially since my fun filled days of Australian secondary education, not every year 10 student in the country sits this 'School Certificate' thingamo.
Now I'm no expert on the capabilities of telescopes, but it is my understanding that there does not exist a telescope powerful enough to actually do this. In fact, one of the sites you linked to has an article explaining this very fact.
As luck would have it, the same site also has a comment on the yet to be launched SELENE Project. This Japanese probe, which is to be launched in late 2005, should be able to map the surface of the moon in enough detail to see the landing sites. As one who was born more than a decade after the moon landings and had a keen interest in space during my childhood, I eagerly look forward to seeing these images.:)
At the last Wineconf in January, Gavriel State (of Transgaming) showed a short demo of American McGee's Alice with a partial shared memory wineserver, and the increase in the fps was about two fold (yes, double of what it was with the current design).
Just thought I'd mention that this game is one of the corner cases that is drastically affected by reducing the number of context switches. A shared memory wineserver would not automatically give this sort of performance boost to any game/application. Not that you were implying it would, but just so people know.
The Codeweavers code in question is LGPLd. So Project David doesn't need to be concerned that it is proprietary, as it is released under the same license as the WineHQ tree. Infact, all of the Codeweavers Wine code is LGPLd. The code that isn't is things like their installer, and other supporting applications that make using Wine painless.
This doesn't mean the Wine code Codeweavers distributes is the same as the WineHQ code though. There are lots of nasty hacks and work arounds that Alexandre Julliard would never let into the WineHQ tree.
The current version of Wine is released under the LGPL license, not the GPL as most posts so far have been asserting. As a result it is perfectly legal to write code that links to Wine and keep the code proprietary. Any changes to the LGPLd code itself would require the changes to be made available though.
Even if the license were the GPL, there would be nothing stopping them writting seperate proprietary programs/modules to complement any GPLd code, as long as the code doesn't link to or contain anything GPL. For example, in Wine entire DLLs could be written and kept proprietary, without breaking the GPL (if this were the license being used).
To sum up, a project does not have to contain only open source or proprietary code.
Reminds me of GriSoft's AVG Free Edition virus scanner license agreement, which has the following clause:
3. You may not use the Software on a network or more than one PC.
- emphasis mine.
Although these days the intent is somewhat clearer from reading the rest of the agreement, there was a time when it wasn't.
I was helping a strapped for cash organisation legitimise their software, and we decided to see if we could find a free virus scanner before forking out cash for one. So I shot off an email asking them to clarify what they meant by 'a network', pointing out that the internet is a network, and one assumes you can have an internet network connection since the software has an email scanner... After a week they sent an email back repeating the the above clause with the word 'network' capitalised.... Sigh, I don't think they got the point....
We ended up paying for a virus scanner, but didn't end up buying it from them.
Am I the only one who's getting tired of trying to play matchup with GLIBC versions?
No you're not, and since the artical is about Wine, you may be interested in knowing that Alexandre Julliard is also fed up with it.
On Wine Devel he posted this:
Also, frankly, I've spent the last year chasing glibc breakages, and I
don't particularly feel like spending the next year chasing kernel
breakages. I was kind of hoping someone else would pick that fight, so
I could go back to writing some real Wine code for a change...
In some places the Windows API documentation is terribly incomplete, in some other places it is simply wrong. So there is still a large amount of work trying to discover what exactly it is that needs to be implemented.
Also, some parts of the Wine code require specialist knowledge of how Windows does certain things. There may be only one or two people working on Wine who have this knowledge. In some cases no one may presently have the required understanding. So more developers with the necessary skills would likely speed up development.
Furthermore, the goals of Wine are mammoth, as too is the complexity of what is trying to be achieved. Sometimes the translation between Windows and *nix can be very tricky and it can be quite a technical feat to make it happen.
Basically it is a very complex project, and it simply takes time.
I can't recall off the top of my head what steps need to be taken to reach the 1.0 release, but there is an action plan. You could find the answer by google searching the wine-devel mailing list. Dimitrie O. Paun has discussed it in the past, so posts he has made may provide the answer to your question.
One thing for certain is the items currently on the To-Do List must be completed before the 0.9 release. More info can be found on the Wine HQ To Do Lists page.
This seems like a really smart idea. Dont go an get the Ultra-Gigaherz-Processor but a descend, processor that consumes only a low amount of power -> Longer batterylife for laptops -> Silent PCs -> Longer lifetime of the processor
I agree, and it will have the added advantage that no one will be able to run Longhorn if/when it is finally released. Projected 'Average' Longhorn System Is A Whopper
Actually, not letting pirates update their copy of Windows I believe partly works in Microsoft's favour. I personally have 3 friends who have purchased a copy of Windows XP simply because of the hassles of trying to patch their pirated copies.
In a galaxy very, very, very,
very, far away there lived
a ruthless race of beings
known as...Spaceballs.
Chapter Eleven
The evil leaders of Planet
Spaceball, having foolishly
squandered their precious
atmosphere, have devised a
secret plan to take every
breath of air away from
their peace-loving neighbor,
Planet Druidia.
Today is Princess Vespa's
wedding day. Unbeknownst
to the princess but knownst
to us, danger lurks in the
stars above...
The vast majority of people I know wouldn't have a clue what their programs do for them by default. It's been a while since I last used ICQ, but I don't think the logging feature was that obvious unless you knew enough about computer programs to suspect it was there.
Slashdot Mirror
Now all I need is for someone to loan me a Formula 1 race car for the test.
;-)
Well BAR Honda have a couple they won't be needing for a few weeks... Perhaps you should ask them.
Thanks for the link. It's a little disappointing to read, but not at all surprising given Telstra's record. Still, I eagerly hang on to the hope that my exchange will indeed be activated by the end of the month! :-D
> The singer?
yes
Microsoft already loves Linux.
Well I'm not so sure about Microsoft, but I know Bill Gates does. The internet says so, and it never lies!!
---
Reminds of when I was about 7 and I stuck the 1.5V globe from my Go-Go Gadget Yo-Yo into the 240V power point... As I lent forward and flipped the switch, there was a massive bang and flash. It scared the crap out of me, but nowhere near as much as observing the now blackend wall did. Scared crapless of what my dad would do when he found out, I stack everything I had in the room around the area to hide the damage... Somehow dad figured something was up... ;-)
:-)
Then there was that time I wanted to see if the 'paper bark' tree burnt like paper....
Ah good times!
---
I love programming in Java. It is simple to program in, simple to understand, and I find it just feels 'clean' compared to say C++. The available API tends to be sufficient for most of my needs, and I find the documentation satisfactory and quick and easy to browse.
If I needed to write a quick, run a few times then throw away, command line application, I would code it in Java every time. For everything else I would unfortunately use something else.
On my aging 4 year old computer, graphical java applications feel slow and clunky to use. Even when the GUI has been coded correctly. Java apps with a poorly coded GUI are just unbearable. Also, the resources the Java VM uses isn't exactly small. Another thing is all graphical Java apps just feel out of place. They always look slightly wrong and feel slightly wrong. This tends to put the user off side from the start, and makes them feel that the application is somewhat substandard.
So basically, I feel that as it currently stands Java isn't suited to serious end user applications. As computer performance increases, and some of Java's future graphical enhancements are available, things may change.
However, while programmers are familiar, comfortable and satisfied with other languages, toolkits and tools, I see little incentive for them to start coding in Java.
---
Haha, smack down!!
:-)
I knew I was going to screw something up and someone was going to lynch me for it. I must have spent too long looking for spelling errors and not enough time reading the web site.
---
Speaking of dodgy maths, before my School Certificate (an exam all high school students do in year 10 in Australia)...
e ducation.htm
Not wanting to be a pedantic prick, but unless things have changed substantially since my fun filled days of Australian secondary education, not every year 10 student in the country sits this 'School Certificate' thingamo.
In fact, if this web site is to be believed, only students attending high school in the ACT and NSW have the pleasure:
http://www.teachers.ash.org.au/aussieed/secondary
As Australia consists of a further territory and 5 states, for your sake I hope 'Australian Studies' wasn't a component of the exam.
---
Telescopes can see the landing site, for example.
:)
Now I'm no expert on the capabilities of telescopes, but it is my understanding that there does not exist a telescope powerful enough to actually do this. In fact, one of the sites you linked to has an article explaining this very fact.
As luck would have it, the same site also has a comment on the yet to be launched SELENE Project. This Japanese probe, which is to be launched in late 2005, should be able to map the surface of the moon in enough detail to see the landing sites. As one who was born more than a decade after the moon landings and had a keen interest in space during my childhood, I eagerly look forward to seeing these images.
---
At the last Wineconf in January, Gavriel State (of Transgaming) showed a short demo of American McGee's Alice with a partial shared memory wineserver, and the increase in the fps was about two fold (yes, double of what it was with the current design).
Just thought I'd mention that this game is one of the corner cases that is drastically affected by reducing the number of context switches. A shared memory wineserver would not automatically give this sort of performance boost to any game/application. Not that you were implying it would, but just so people know.
---
You can install both. Infact, you can install and run multiple revisions of the WineHQ Wine at the same time.
---
The Codeweavers code in question is LGPLd. So Project David doesn't need to be concerned that it is proprietary, as it is released under the same license as the WineHQ tree. Infact, all of the Codeweavers Wine code is LGPLd. The code that isn't is things like their installer, and other supporting applications that make using Wine painless.
This doesn't mean the Wine code Codeweavers distributes is the same as the WineHQ code though. There are lots of nasty hacks and work arounds that Alexandre Julliard would never let into the WineHQ tree.
---
Yep, it's LGPL.
---
The current version of Wine is released under the LGPL license, not the GPL as most posts so far have been asserting. As a result it is perfectly legal to write code that links to Wine and keep the code proprietary. Any changes to the LGPLd code itself would require the changes to be made available though.
Even if the license were the GPL, there would be nothing stopping them writting seperate proprietary programs/modules to complement any GPLd code, as long as the code doesn't link to or contain anything GPL. For example, in Wine entire DLLs could be written and kept proprietary, without breaking the GPL (if this were the license being used).
To sum up, a project does not have to contain only open source or proprietary code.
---
LOL, that's the sort of answer I was actually expecting, except with a slightly more 'professional' touch! :)
---
Reminds me of GriSoft's AVG Free Edition virus scanner license agreement, which has the following clause:
3. You may not use the Software on a network or more than one PC.
- emphasis mine.
Although these days the intent is somewhat clearer from reading the rest of the agreement, there was a time when it wasn't.
I was helping a strapped for cash organisation legitimise their software, and we decided to see if we could find a free virus scanner before forking out cash for one. So I shot off an email asking them to clarify what they meant by 'a network', pointing out that the internet is a network, and one assumes you can have an internet network connection since the software has an email scanner... After a week they sent an email back repeating the the above clause with the word 'network' capitalised.... Sigh, I don't think they got the point....
We ended up paying for a virus scanner, but didn't end up buying it from them.
---
No you're not, and since the artical is about Wine, you may be interested in knowing that Alexandre Julliard is also fed up with it.
On Wine Devel he posted this:
http://www.winehq.org/hypermail/wine-devel/2003/1
---
In some places the Windows API documentation is terribly incomplete, in some other places it is simply wrong. So there is still a large amount of work trying to discover what exactly it is that needs to be implemented.
Also, some parts of the Wine code require specialist knowledge of how Windows does certain things. There may be only one or two people working on Wine who have this knowledge. In some cases no one may presently have the required understanding. So more developers with the necessary skills would likely speed up development.
Furthermore, the goals of Wine are mammoth, as too is the complexity of what is trying to be achieved. Sometimes the translation between Windows and *nix can be very tricky and it can be quite a technical feat to make it happen.
Basically it is a very complex project, and it simply takes time.
---
I can't recall off the top of my head what steps need to be taken to reach the 1.0 release, but there is an action plan. You could find the answer by google searching the wine-devel mailing list. Dimitrie O. Paun has discussed it in the past, so posts he has made may provide the answer to your question.
One thing for certain is the items currently on the To-Do List must be completed before the 0.9 release. More info can be found on the Wine HQ To Do Lists page.
---
This seems like a really smart idea. Dont go an get the Ultra-Gigaherz-Processor but a descend, processor that consumes only a low amount of power -> Longer batterylife for laptops -> Silent PCs -> Longer lifetime of the processor
I agree, and it will have the added advantage that no one will be able to run Longhorn if/when it is finally released.
Projected 'Average' Longhorn System Is A Whopper
---
Actually, not letting pirates update their copy of Windows I believe partly works in Microsoft's favour. I personally have 3 friends who have purchased a copy of Windows XP simply because of the hassles of trying to patch their pirated copies.
---
SPACEBALLS
:)
Once upon a time warp...
In a galaxy very, very, very,
very, far away there lived
a ruthless race of beings
known as...Spaceballs.
Chapter Eleven
The evil leaders of Planet
Spaceball, having foolishly
squandered their precious
atmosphere, have devised a
secret plan to take every
breath of air away from
their peace-loving neighbor,
Planet Druidia.
Today is Princess Vespa's
wedding day. Unbeknownst
to the princess but knownst
to us, danger lurks in the
stars above...
If you can read this, you
don't need glasses.
----
DVD Details at Amazon
Now, back to work...
---
there is a Spaceballs joke here if anyone can find it :-D
Use the schwartz!
---
Tasmania (a state of .au)...
:) ;)
As a fellow Australian, I find it mildly amusing you felt it necessary to say that!
But I know... It was for all the non-Australians I'm sure....
---
The vast majority of people I know wouldn't have a clue what their programs do for them by default. It's been a while since I last used ICQ, but I don't think the logging feature was that obvious unless you knew enough about computer programs to suspect it was there.
---