Kernel modules have definitely been a contentious issue vis-a-vis the GPL. That being said I believe you are 100% correct. Although MadWifi is dual license, in this case linking to the kernel provides the GPL infection to force the decision. Well again they have not yet replied to me as of yet so let's hope they also come to this conclusion and release this code.
I have noted in the last few days the release of the various bits of source code and am happy to see Asus ensure that they are in compliance. Now I would love for them to go the extra mile and release the code changes to MadWifi to support the wireless. I know this is released under a BSD style license and they are not obligated but one of the biggest weaknesses of the Eee right now for me is the inability of their wpa_supplicant to offer enterprise encryption support. Something that is hard to change without the MadWifi source or switching to use NDISWrapper. The Eee is the best gadget but I want my wireless @ work.
NOTE: I have asked Asus about enterprise encryption support and they have said it may be coming. I have also asked about the madwifi source but received no definitive answer yet.
Yes I would have to agree. The method of programming being discussed is more akin to a Finite State Machine (FSM) in which you describe various states, events which cause state transitions and of course the define what all happens during the transition. It is a valid programming methodology and is used in telephony and other places. One popular application for working with such code was Rational ObjecTime which became part of the Rational Rose product before Rational was bought by IBM. Where FSM has troubles is with switch statements as they become quite complex (switch is the same as many IF and IF ELSE in many ways) which may be why the author was so negative to IF statements. As for games size, yes games have gotten bigger, this is however more to do with all the artwork and sounds that accompany the games and not the software driving them. As for the developer's of comment "nearly everything is created procedurally" this would explain the smaller size not because of "procedural programming" but because rather then grabbing an image or sound from artwork on a CD they are creating it in code. For example I can write some code to render a sphere, with the API allowing for color, material, lighting and others to be defined, now I can write small bits of code to call the API and create a thousand spheres all with unique characteristics, all with minimal amount of CD space being used (lets say 1K for the API definition and 100bytes per sphere = 1K+(100B*1000) = 98.6Kb). Now if I was to have 1000 unique spheres using artwork you would have 1000 unique images saved on CD plus a smaller API to load them (0.2Kb API, 100Kb per image = 0.2Kb + 100Kb *100 = 12.2Mb). Even if you were to do some optimization, which you would, the difference is clearly visible.
I am surprised that UK parents and teachers are so up in arms about WiFi when they so don't give a damn about the food that is killing their kids as The Naked Chef points out here. I think the number one culprit is called a "Twizler" (mechanically processed sausage thingy), not WiFi.
I thought I had seen this sort of device already and a quick search shows that I rememberred correctly. Check out Ripesense and here and Juicy Idea and I am sure many more. Can a professor get in trouble for plagiarism???
Slashdot Mirror
This has proved useful at an industrial level http://www.fifthlight.com/ . Kind of neat when combined with the capability to dim florescent lights.
Did I hear that right? Google has GAS?
Kernel modules have definitely been a contentious issue vis-a-vis the GPL. That being said I believe you are 100% correct. Although MadWifi is dual license, in this case linking to the kernel provides the GPL infection to force the decision. Well again they have not yet replied to me as of yet so let's hope they also come to this conclusion and release this code.
NOTE: I have asked Asus about enterprise encryption support and they have said it may be coming. I have also asked about the madwifi source but received no definitive answer yet.
Yes I would have to agree. The method of programming being discussed is more akin to a Finite State Machine (FSM) in which you describe various states, events which cause state transitions and of course the define what all happens during the transition. It is a valid programming methodology and is used in telephony and other places. One popular application for working with such code was Rational ObjecTime which became part of the Rational Rose product before Rational was bought by IBM. Where FSM has troubles is with switch statements as they become quite complex (switch is the same as many IF and IF ELSE in many ways) which may be why the author was so negative to IF statements. As for games size, yes games have gotten bigger, this is however more to do with all the artwork and sounds that accompany the games and not the software driving them. As for the developer's of comment "nearly everything is created procedurally" this would explain the smaller size not because of "procedural programming" but because rather then grabbing an image or sound from artwork on a CD they are creating it in code. For example I can write some code to render a sphere, with the API allowing for color, material, lighting and others to be defined, now I can write small bits of code to call the API and create a thousand spheres all with unique characteristics, all with minimal amount of CD space being used (lets say 1K for the API definition and 100bytes per sphere = 1K+(100B*1000) = 98.6Kb). Now if I was to have 1000 unique spheres using artwork you would have 1000 unique images saved on CD plus a smaller API to load them (0.2Kb API, 100Kb per image = 0.2Kb + 100Kb *100 = 12.2Mb). Even if you were to do some optimization, which you would, the difference is clearly visible.
I am surprised that UK parents and teachers are so up in arms about WiFi when they so don't give a damn about the food that is killing their kids as The Naked Chef points out here. I think the number one culprit is called a "Twizler" (mechanically processed sausage thingy), not WiFi.
I thought I had seen this sort of device already and a quick search shows that I rememberred correctly. Check out Ripesense and here and Juicy Idea and I am sure many more. Can a professor get in trouble for plagiarism???