It looks like the big thing they are trying to do is simply increase compatability between one user connecting to the other using dcc2.
The point is to let the protocol decide the best way to connect given several options so the user doesn't have to manually try each of the many variants of the DCC command that have been added to the different clients to overcome the problems with DCC (e.g. dealing with NAT).
I do not beleive that dcc2 will have a great difference of quality over the regular dcc but it will have more compatibility.
DCC2 will perform better than DCC in most circumstances. DCC requires ACKs every so often, halting transfer until the ACK is sent from the receiver. Since TCP/IP already guarantees delivery, this part of the protocol is completely redundant, and it can significantly slow down delivery.
They aim to "incorporate new technologies" but I dont see where they are going with this...
DCC2 is both simple and extensible, unlike DCC which, though simple, is not at all extensible. Some functionality that DCC2 could help standardize accross clients are whiteboard sharing, voice/video chat, encryption, IPv6 connections, etc.
A side effect of using XP is that its flexibility makes it impossible to blame the methodology when a project fails; that is, it always comes down to bad choices made by the team members, and all team members share the blame equally. Less competent programmers are afraid of this responsibility. They like the job security of being able to blame a rigid, outdated process or a single team leader when a project fails. If I was not confident in the my own ability or the ability of my team members, I would disparage XP as well.
I think that maybe you are not completely clear about this project. #Smalltalk runs on one particular MS platform: the Common Language Runtime. Currently, the only full CLR comes with the MS.NET Framework for Windows. Rotor (http://msdn.microsoft.com) is a CLR implementation that runs on BSD and Mac OS X, but it is not a complete implementation, and #Smalltalk will not currently compile programs on Rotor.
Interestingly enough, programs that have been compiled with #Smalltalk on MS.NET Framework 1.0.3705 will run on rotor; that is, if you compile the Calculator.sif example with #Smalltalk to produce Calculator.exe, you can run Calculator.exe on Rotor.
Mono (http://go-mono.org) is not complete enough to even run the compiled executables. It pops up a message that says (going from memory here, so don't quote me) "EXECUTION SHOULD NOT REACH THIS POINT", whatever that means...
With your comment about the multi-platform capabilities of Squeak, you are correct. Squeak can run on many more platforms than #Smalltalk. I'll just reiterate that #Smalltalk runs on exactly one platform, which just happens to be a virtual platform. The real advantage is interoperability with the many languages that compile to the CLR. #Smalltalk can use objects defined in any.NET assembly (called a DLL, but much more thatn a simple dynamic link library). If you are, for example, doing contract work for a company that uses.NET languages, you can program your stuff in #Smalltalk and use their classes without worrying about interoperability.
As for your question about communicating with remote.NET objects/services, all of that communication is done using XML/SOAP, so you can theoretically communicate with these services using telnet if you're really feeling up to it.
Under windoze it can also generate.DLL's, but doesn't have to.
The DLLs that it generates are not DLLs in the traditional Windows sense, but they are.NET assemblies meaning that any.NET platform can use them. DLL is a bit of a misnomer, but it's the standard the MS has adopted for naming assemblies.
What would be really awesome is if Linksys could put something on the router's HTML admin pages that would let you check for firmware upgrades and then install them from the browser so it wouldn't matter what OS you used.
You have to download the firmware upgrade manually, but you can use the admin pages to upgrade the firmware as of at least version 1.43. The option is mistakenly hidden under the "Help" tab, though.
If your mobo has a removable cache chip (very common in the time period that I'm guessing your board is from), try removing it. If it's not removable, check your BIOS for an option to diable it. This *might* fix the random rebooting problem.
From the tech experience that I have, a machine that reboots randomly generally has a bad cache. If this is the problem, I'm at a loss to explain why it would show up in kernel 2.4.17. Anyway, it's just an idea.
Oh, and I haven't tried Linux From Scratch, but I use Sorcerer GNU/Linux, and even though I think the spell metaphor is cheesy, my system (475 AMD K6-2, 512MB RAM) is much faster than it is with any of the several binary distos I've tried. I'd be interested to see an in-depth article comparing the "compile everything" distros.
Students are in college for at least 4 years. Four years at the same company is a long time in the IT world, at least so far as I have seen.
You've got a point there, but the students don't necessarily work in the computer center the entire four years. At college I attended (a work-study school), it was rare for a freshman to work in the computer center, and most CS students didn't work there until at least their junior year.
The are only a few real problem that I see (and have seen) with a school IT department with a lot of dependence on student workers.
(1) Students have a very limited amount of time in the department. It's like an IT shop with a really high turnover rate.
(2) The quality of student workers is very hit and miss. If a really talented student comes in and sets up a few good systems then graduates, other students are not always able to step in a maintain or update the system.
(3) The actual full-time IT workers become more paranoid and will spend a lot of time securing the network from their own workers. The high turnover along with the inevitable "bad apples" destroys trust between the full-time staff and the student workers.
That said, I still think that students should definitely have the option (or requirement, even) to work in a school IT department. For many programming students, it could be the only hardware/administration job they ever have, and it will help them understand computers on a different level.
I found my school's computer center to be a great place to gain experience. Unfortunately, since it was my first hardware tech job and it dealt exclusively with networked computers, I learned nothing about modems. Later, I took a job with a local PC shop doing tech work, and a large portion of the problems that I had to deal with were modem problems. It wasn't a big deal because I picked up on the modem stuff in a short amount of time, but it was a definite weakness after my college IT experience.
This patent covers a method to smooth edges seen by the human eye. With this method, sharp edges (or "jaggies") normally seen by the human eye are softened by the process of bending the lens of the eye a small amount so that the focal point of the light passing through the lens is just in front of the retina rather than right on it. Since this is simply a readjustment of a sensory input, no additional processing power is required by the brain to smooth out the "jaggies". This a truly amazing breakthrough for human vision.
(In case you didn't catch it, this is a patent on near-sighted vision.)
...they lost $10.4 million on only $879,000 of revenue.
The ticker symbol has an 'E' added to the end ("XBOXE"). In day-trader lingo, that means the company's in serious trouble. There's a quote in the article that suggests that the company wants MS to just buy the trademark. I wouldn't be surprised if that is their latest business plan revision.
PS. Any info on where I sign up to join the lawsuit? Thanks.
Just click here and click the button at the bottom of the page. Don't forget to tell them how terrible Linux is so they know you're not a spy. Good luck.
I wonder if the lawyers shortened VA Linux Systems, Inc. to "Linux" for a reason (VA Linux Systems, Inc. (``Linux'' or the ``Company''...)) or if the lawyer is just clueless. Wouldn't "VA" have been a better abbreviation? It's more concise and accurate.
Could Linus sue the lawyers for Trademark Infringement(TM)?
IT sounds like some sort of waste disposal that generates power to me. Think Back To The Future when Doc throws some trash into "Mr Fusion" to create power for the time machine.
Change your real info on those sites to bogus info...
I did that with my Amazon site when they had their TOS change a while back. Unfortunately, they can still count it among their accounts, which means that it still looks good on paper to stockholders. Also, if Amazon ever changed their ways and I decided to sign up again, I would have to create a new account. There is no way that their user base can shrink.
From what I understand, they don't even charge to list items. I know the buyer base isn't as large, but if Ebay starts losing customers, then maybe they will stop sending spam.
What he's missing is that in the race to earn profits, corporations have to please people.
Sure they have to please consumers now, but not people in general. A company can piss off everybody in, say, Ghana, but if they're selling to Canadadians, there profits won't be hurt so long as the Canadians are blissfully happy (as Canucks tend to be).
Of course, they only have to keep the consumers happy until they reach "Company Store" status. Wal-Mart is almost there.
Slashdot Mirror
umm...
Why does youtube need ssl?
I could understand logging in needs to be secure, but every page afterwards? They're public pages man!
Just sort of happened *shrug*
Interviewer: Now tell me, what exactly are you doing?
Spotter: Er well, I'm camel spotting. I'm spotting to see if there are any camels that I can spot, and put them down in my camel spotting book.
Interviewer: Good. And how many camels have you spotted so far?
Spotter: Oh, well so far Peter, up to the present moment, I've spotted nearly, ooh, nearly one.
Interviewer: Nearly one?
https://www.youtube.com/watch?v=6RexQLrcqwc
Probably because you didn't look hard enough.
--Riley, dIRC developer, Algenta Technical Staff member
The point is to let the protocol decide the best way to connect given several options so the user doesn't have to manually try each of the many variants of the DCC command that have been added to the different clients to overcome the problems with DCC (e.g. dealing with NAT).
I do not beleive that dcc2 will have a great difference of quality over the regular dcc but it will have more compatibility.
DCC2 will perform better than DCC in most circumstances. DCC requires ACKs every so often, halting transfer until the ACK is sent from the receiver. Since TCP/IP already guarantees delivery, this part of the protocol is completely redundant, and it can significantly slow down delivery.
They aim to "incorporate new technologies" but I dont see where they are going with this...
DCC2 is both simple and extensible, unlike DCC which, though simple, is not at all extensible. Some functionality that DCC2 could help standardize accross clients are whiteboard sharing, voice/video chat, encryption, IPv6 connections, etc.
--Riley, dIRC developer, Algenta Technical Staff member.
A side effect of using XP is that its flexibility makes it impossible to blame the methodology when a project fails; that is, it always comes down to bad choices made by the team members, and all team members share the blame equally. Less competent programmers are afraid of this responsibility. They like the job security of being able to blame a rigid, outdated process or a single team leader when a project fails. If I was not confident in the my own ability or the ability of my team members, I would disparage XP as well.
Whatever.
All you have to do is log in to your neighbors' routers and secure them. I'm sure they left the default passwords.
I think that maybe you are not completely clear about this project. #Smalltalk runs on one particular MS platform: the Common Language Runtime. Currently, the only full CLR comes with the MS .NET Framework for Windows. Rotor (http://msdn.microsoft.com) is a CLR implementation that runs on BSD and Mac OS X, but it is not a complete implementation, and #Smalltalk will not currently compile programs on Rotor.
.NET Framework 1.0.3705 will run on rotor; that is, if you compile the Calculator.sif example with #Smalltalk to produce Calculator.exe, you can run Calculator.exe on Rotor.
.NET assembly (called a DLL, but much more thatn a simple dynamic link library). If you are, for example, doing contract work for a company that uses .NET languages, you can program your stuff in #Smalltalk and use their classes without worrying about interoperability.
.NET objects/services, all of that communication is done using XML/SOAP, so you can theoretically communicate with these services using telnet if you're really feeling up to it.
Interestingly enough, programs that have been compiled with #Smalltalk on MS
Mono (http://go-mono.org) is not complete enough to even run the compiled executables. It pops up a message that says (going from memory here, so don't quote me) "EXECUTION SHOULD NOT REACH THIS POINT", whatever that means...
With your comment about the multi-platform capabilities of Squeak, you are correct. Squeak can run on many more platforms than #Smalltalk. I'll just reiterate that #Smalltalk runs on exactly one platform, which just happens to be a virtual platform. The real advantage is interoperability with the many languages that compile to the CLR. #Smalltalk can use objects defined in any
As for your question about communicating with remote
--Riley
The DLLs that it generates are not DLLs in the traditional Windows sense, but they are .NET assemblies meaning that any .NET platform can use them. DLL is a bit of a misnomer, but it's the standard the MS has adopted for naming assemblies.
--Riley
You have to download the firmware upgrade manually, but you can use the admin pages to upgrade the firmware as of at least version 1.43. The option is mistakenly hidden under the "Help" tab, though.
From the tech experience that I have, a machine that reboots randomly generally has a bad cache. If this is the problem, I'm at a loss to explain why it would show up in kernel 2.4.17. Anyway, it's just an idea.
Oh, and I haven't tried Linux From Scratch, but I use Sorcerer GNU/Linux, and even though I think the spell metaphor is cheesy, my system (475 AMD K6-2, 512MB RAM) is much faster than it is with any of the several binary distos I've tried. I'd be interested to see an in-depth article comparing the "compile everything" distros.
IIRC, Genisis states that light was created on day 1, but the sun, moon, and stars were all created on day 4.
Students are in college for at least 4 years. Four years at the same company is a long time in the IT world, at least so far as I have seen.
You've got a point there, but the students don't necessarily work in the computer center the entire four years. At college I attended (a work-study school), it was rare for a freshman to work in the computer center, and most CS students didn't work there until at least their junior year.
The are only a few real problem that I see (and have seen) with a school IT department with a lot of dependence on student workers.
(1) Students have a very limited amount of time in the department. It's like an IT shop with a really high turnover rate.
(2) The quality of student workers is very hit and miss. If a really talented student comes in and sets up a few good systems then graduates, other students are not always able to step in a maintain or update the system.
(3) The actual full-time IT workers become more paranoid and will spend a lot of time securing the network from their own workers. The high turnover along with the inevitable "bad apples" destroys trust between the full-time staff and the student workers.
That said, I still think that students should definitely have the option (or requirement, even) to work in a school IT department. For many programming students, it could be the only hardware/administration job they ever have, and it will help them understand computers on a different level.
I found my school's computer center to be a great place to gain experience. Unfortunately, since it was my first hardware tech job and it dealt exclusively with networked computers, I learned nothing about modems. Later, I took a job with a local PC shop doing tech work, and a large portion of the problems that I had to deal with were modem problems. It wasn't a big deal because I picked up on the modem stuff in a short amount of time, but it was a definite weakness after my college IT experience.
Full Vision Anti-Aliasing (FVAA) Patent:
This patent covers a method to smooth edges seen by the human eye. With this method, sharp edges (or "jaggies") normally seen by the human eye are softened by the process of bending the lens of the eye a small amount so that the focal point of the light passing through the lens is just in front of the retina rather than right on it. Since this is simply a readjustment of a sensory input, no additional processing power is required by the brain to smooth out the "jaggies". This a truly amazing breakthrough for human vision.
(In case you didn't catch it, this is a patent on near-sighted vision.)
The ticker symbol has an 'E' added to the end ("XBOXE"). In day-trader lingo, that means the company's in serious trouble. There's a quote in the article that suggests that the company wants MS to just buy the trademark. I wouldn't be surprised if that is their latest business plan revision.
PS. Any info on where I sign up to join the lawsuit? Thanks.
Just click here and click the button at the bottom of the page. Don't forget to tell them how terrible Linux is so they know you're not a spy. Good luck.
I wonder if the lawyers shortened VA Linux Systems, Inc. to "Linux" for a reason (VA Linux Systems, Inc. (``Linux'' or the ``Company''...)) or if the lawyer is just clueless. Wouldn't "VA" have been a better abbreviation? It's more concise and accurate.
Could Linus sue the lawyers for Trademark Infringement(TM)?
IT sounds like some sort of waste disposal that generates power to me. Think Back To The Future when Doc throws some trash into "Mr Fusion" to create power for the time machine.
Change your real info on those sites to bogus info...
I did that with my Amazon site when they had their TOS change a while back. Unfortunately, they can still count it among their accounts, which means that it still looks good on paper to stockholders. Also, if Amazon ever changed their ways and I decided to sign up again, I would have to create a new account. There is no way that their user base can shrink.
From what I understand, they don't even charge to list items. I know the buyer base isn't as large, but if Ebay starts losing customers, then maybe they will stop sending spam.
droogie73(210) lost his perfect feedback rating.
I italicized it to draw emphasis to it so that the poster to whom I was replying would not miss it for a second time.
Make that "Congratulations" and "undeniably."
Who said anything about giving a fuck? I'm talking about corporate profits here.
Sure they have to please consumers now, but not people in general. A company can piss off everybody in, say, Ghana, but if they're selling to Canadadians, there profits won't be hurt so long as the Canadians are blissfully happy (as Canucks tend to be).
Of course, they only have to keep the consumers happy until they reach "Company Store" status. Wal-Mart is almost there.