You think that schools and businesses are going to give up those deals because they don't like what MS is doing? Communication between businesses, schools, and the rest of the world is important to those instituions. There's no choice.
-- Previous HMD's were very heavy (and unbalancing), and not suitable for long-term use; this is not the case with this implementation.
-- The displays used were relatively low quality, requiring small LCD screens with refresh, brightness, colour depth, and resolution issues; with this new design the only limiting factors are how fast you can modulate the laser intensity and how quickly you can scan the retina. (Colour depth is harder as it requires three seperate lasers of the appropriate wavelengths firing at the same mirror, but is within the bounds of possibility.)
-- Previous HMDs were not portable; they required physical lines back to a power supply and main processing units. Power consumption in this design is substantially reduced, meaning batteries and portables/wireless links can be used to make this design untethered.
Although the improvements may seem relatively minor, collectively they allow the use of HMDs in all kinds of applications that were previously completely untenable.
so you have working flash in mozilla right? and photoshop without mac-on-linux? what about shadows, transparency, and vector scaling all real time? can you stream wmv, rm, and mov all from your web browser flawlessly? do you have video/voice conferencing in gaim?
The point is that anyoen(sic) with a legitimate use for a legitimate tool would get it from a legitimate, trusted source.
Tools are not imbued with some intrinsic legitimacy. That is determined by how they are used -- and who is judging them.
Someone who grabs something they have no clue about from a place they know nothing about, and runs it on their PC without checking what it is: Is clearly thick as pigshit Is up to something they consider illicit.
Your conclusions are wrong and your logic is faulty.
The person who ran that code didn't intend to compromise their machine. Ergo, they trusted the source.
As with tools, legitimacy is determined by the person making the judgement -- one person's legitimate source may be another's evil monopoly-abusing nemesis.
They probably also had some idea of the stated purpose of the tool and thought that it would be useful to them. That implies a basic level of understanding.
It is difficult to know what code to trust and what not. Running binaries downloaded from an unknown user is clearly unwise, but that's not a crime.
Finally, wishing to perform an action in private does not imply that the action is illicit, or believed to be illicit by the person performing that action. Your contention to the contrary is equivilent to saying "If they are commiting no crime, you have nothing to hide/fear."
Which is not always true, in fact it is rarely true.
Imagine someone who packaged up some illegal-to-distribute physical substance in boxes labeled `private, personal and mine, do not touch', then left them around. Can they be done for distributing the substance if someone comes along and steals it?
Your analogy is flawed; there are legitimate non-infringing uses of keygen programs and no-cd patches. It is also legal to distribute these tools.
You've missed the point of the argument. The argument is that intentionally distributing trojan code for installation on machines you don't own or control is a crime; in the UK it would fall under the Computer Misuse Act. That's bad, and you can be charged by the state and put in jail for commiting that crime.
Whether or not the end-user is doing something legally / morally wrong by downloading what they believe to be material under copyright to which they have no permission to use is a completely independent discussion.
I happened to have a quick play with GnomeMeeting yesterday, and I disagree with your comments.
Sure, the low-level configuration screens give you full control and look scary because of it -- but it's not the primary means for users to set up GnomeMeeting. Most users won't even go in here.
Instead, the first time you run the application it leads you through a very simple and well explained wizard which sets up your sound, your webcam, directory details and all the rest. Very straightforward.
Once through, you get the nice simple front-end where you can either tap in the URL for the person you want to call, use the main directory or (if you've got a GM -> landline bridge account) tap in a phone number.
It was astonishingly easy. And I'm not even using the 1.0 release.
This is one package where the user really can be ignorant of a lot of the underlying details and still use the technology.
By the way, the modifications to libiterm required to support Y have already entered Debian Unstable, so you don't have to install that seperately now.
Y-Windows as recently covered on/. is such a GPLed redesign.
However, right at the moment x86-specific speed tweaks are less important than a smarter deisgn that works better irrespective of the platform you're running on.
Externally I think it currently has a dedicated 100Mbit pipe via Thus. I think there may be plans to upgrade that, but I don't know.
SunSITE is certainly quite popular right now, so the increased use explaination is feasible. I'll ask if there's any load monitoring details that can be made available externally.
I understand that argument. It's the only potentially legitimate case that Intel have.
Question: why would a chipset manufacturer, such as Intel, be held liable if a user hacked their driver implementation to exceed local transmission regulations?
Then leave those bits out. If you depend on external functionality that you can't ship implementations for, then just specify the interface that you require.
A new open-source implementation can then be constructed which meets the interface's requirements. Alternatively, depending on the precise circumstances, the internal structure of the driver could be altered to no-longer depend on the missing component.
A development restart has been planned for months; the only reason it hasn't happened sooner is that we've all been settling into new jobs and simply haven't had the spare time to get this going properly until now.
X Windows *does* have issues; I think we can all agree on that. But by the same token, we're not trying to argue that X is not useful; I'm using XFree86 on my production machine right now to good effect. But we think it can be done better.
Linus was just one guy when he started work on Linux. Other people then joined in, and made Linux what it is today.
Mark, myself, and the other chaps who were in the room when the Y concept was born are doing this because we enjoy it. Whether lots of people will join in on our little project remains to be seen.
Sure, it'll be gratifying if we become popular, but that's not what we've set out to do -- write good code.
By the way, you really shouldn't trust random binaries you downloaded from someone else on slashdot. At least validate the MD5SUMS, if you can -- that.exe block is there for a reason.
IBM have used CORBA for many of the internal interfaces in their larger systems; many people in IBM know what CORBA is and what it does.
In this article it's worth mentioning as a means to contrast the whole grid idea with existing RPC designs; otherwise people are likely to think "what's the big deal about web-services as an RPC layer, anyway?"
Slashdot Mirror
How, if it all, could this be related to Janus?
Are MS simply giving up trying to make bits uncopyable on a PC, and instead move to implementing secure tunnels to and from trusted embedded devices?
You think that schools and businesses are going to give up those deals because they don't like what MS is doing?
Communication between businesses, schools, and the rest of the world is important to those instituions. There's no choice.
Long live OpenOffice.org, SMTP.
This is a significant breakthrough because:
-- Previous HMD's were very heavy (and unbalancing), and not suitable for long-term use; this is not the case with this implementation.
-- The displays used were relatively low quality, requiring small LCD screens with refresh, brightness, colour depth, and resolution issues; with this new design the only limiting factors are how fast you can modulate the laser intensity and how quickly you can scan the retina. (Colour depth is harder as it requires three seperate lasers of the appropriate wavelengths firing at the same mirror, but is within the bounds of possibility.)
-- Previous HMDs were not portable; they required physical lines back to a power supply and main processing units. Power consumption in this design is substantially reduced, meaning batteries and portables/wireless links can be used to make this design untethered.
Although the improvements may seem relatively minor, collectively they allow the use of HMDs in all kinds of applications that were previously completely untenable.
That is why this is a big deal.
so you have working flash in mozilla right? and photoshop without mac-on-linux? what about shadows, transparency, and vector scaling all real time? can you stream wmv, rm, and mov all from your web browser flawlessly? do you have video/voice conferencing in gaim?
:)
I don't need those things.
Linux on my iBook is faster and does what I want.
I even get better screensavers.
So I use Linux.
23 March 2003
A year old?
Tools are not imbued with some intrinsic legitimacy. That is determined by how they are used -- and who is judging them.
Your conclusions are wrong and your logic is faulty.
The person who ran that code didn't intend to compromise their machine. Ergo, they trusted the source.
As with tools, legitimacy is determined by the person making the judgement -- one person's legitimate source may be another's evil monopoly-abusing nemesis.
They probably also had some idea of the stated purpose of the tool and thought that it would be useful to them. That implies a basic level of understanding.
It is difficult to know what code to trust and what not. Running binaries downloaded from an unknown user is clearly unwise, but that's not a crime.
Finally, wishing to perform an action in private does not imply that the action is illicit, or believed to be illicit by the person performing that action. Your contention to the contrary is equivilent to saying "If they are commiting no crime, you have nothing to hide/fear."
Which is not always true, in fact it is rarely true.
Imagine someone who packaged up some illegal-to-distribute physical substance in boxes labeled `private, personal and mine, do not touch', then left them around. Can they be done for distributing the substance if someone comes along and steals it?
Your analogy is flawed; there are legitimate non-infringing uses of keygen programs and no-cd patches. It is also legal to distribute these tools.
You've missed the point of the argument. The argument is that intentionally distributing trojan code for installation on machines you don't own or control is a crime; in the UK it would fall under the Computer Misuse Act. That's bad, and you can be charged by the state and put in jail for commiting that crime.
Whether or not the end-user is doing something legally / morally wrong by downloading what they believe to be material under copyright to which they have no permission to use is a completely independent discussion.
Because you don't see the posts which actually *are* modded down..
Until he manages to get it in his mouth.
I happened to have a quick play with GnomeMeeting yesterday, and I disagree with your comments.
Sure, the low-level configuration screens give you full control and look scary because of it -- but it's not the primary means for users to set up GnomeMeeting. Most users won't even go in here.
Instead, the first time you run the application it leads you through a very simple and well explained wizard which sets up your sound, your webcam, directory details and all the rest. Very straightforward.
Once through, you get the nice simple front-end where you can either tap in the URL for the person you want to call, use the main directory or (if you've got a GM -> landline bridge account) tap in a phone number.
It was astonishingly easy. And I'm not even using the 1.0 release.
This is one package where the user really can be ignorant of a lot of the underlying details and still use the technology.
You probably mean the Y server, not X. And we're using Arch, not CVS.
Andy Suffield has been working on the project; he's got some stuff up at http://people.debian.org/~asuffield/.
By the way, the modifications to libiterm required to support Y have already entered Debian Unstable, so you don't have to install that seperately now.
Y-Windows as recently covered on /. is such a GPLed redesign.
However, right at the moment x86-specific speed tweaks are less important than a smarter deisgn that works better irrespective of the platform you're running on.
Y Windows is currently under heavy development and not yet suited for end-users -- and is unlikely to be so for a while.
Externally I think it currently has a dedicated 100Mbit pipe via Thus. I think there may be plans to upgrade that, but I don't know.
SunSITE is certainly quite popular right now, so the increased use explaination is feasible. I'll ask if there's any load monitoring details that can be made available externally.
I understand that argument. It's the only potentially legitimate case that Intel have.
Question: why would a chipset manufacturer, such as Intel, be held liable if a user hacked their driver implementation to exceed local transmission regulations?
Then leave those bits out. If you depend on external functionality that you can't ship implementations for, then just specify the interface that you require.
A new open-source implementation can then be constructed which meets the interface's requirements. Alternatively, depending on the precise circumstances, the internal structure of the driver could be altered to no-longer depend on the missing component.
The Department of Computing (where I'm sitting) is even better. Then it's dock-ick-ack-uck.
And SunSITE Northern Europe got a massive upgrade recently.
http://www.sunsite.org.uk/
Cheers,
David
Howdy,
The official line is 'We Really Don't Give a Damn'.
Cheers,
David
Howdy.
You make some reasonable points.
A development restart has been planned for months; the only reason it hasn't happened sooner is that we've all been settling into new jobs and simply haven't had the spare time to get this going properly until now.
X Windows *does* have issues; I think we can all agree on that. But by the same token, we're not trying to argue that X is not useful; I'm using XFree86 on my production machine right now to good effect. But we think it can be done better.
Linus was just one guy when he started work on Linux. Other people then joined in, and made Linux what it is today.
Mark, myself, and the other chaps who were in the room when the Y concept was born are doing this because we enjoy it. Whether lots of people will join in on our little project remains to be seen.
Sure, it'll be gratifying if we become popular, but that's not what we've set out to do -- write good code.
Cheers,
David
Apache2's default configuration doesn't scale gracefully to the load generated by a slashdotting.
I've upped various magic numbers in poolsize.conf and it appears to now be responding much faster.
Cheers,
David
Strictly speaking, we were doing a four-year undergraduate degree which resulted in a Masters award at the end.
http://www.doc.ic.ac.uk/~dwm99/slashdot/FirefoxSet up-0.8.exe.not.
.exe block is there for a reason.
By the way, you really shouldn't trust random binaries you downloaded from someone else on slashdot. At least validate the MD5SUMS, if you can -- that
I would disagree.
IBM have used CORBA for many of the internal interfaces in their larger systems; many people in IBM know what CORBA is and what it does.
In this article it's worth mentioning as a means to contrast the whole grid idea with existing RPC designs; otherwise people are likely to think "what's the big deal about web-services as an RPC layer, anyway?"
We updated our mozilla.org mirror this morning in anticipation of a slashdotting.
http://www.sunsite.org.uk/package/mozilla.
Hmm, I'll have to update our summary...