My comment wasn't about any specific platform - it was about things taking 15+ minutes to compile. As far as I can tell, those days are far from gone! Some of the code I work with takes an hour or two to compile (luckily I usually only have to do that once a day or so, and do single component compiles the rest of the time).
Still, my point remains that if you can cut down a 2 hour compile to a 1 hour compile, that buys you extra productivity time. I would consider it a worthy investment to get a cost effective machine with more power than a Mac mini for serious development - aka a PC running some flavor of Unix (Solaris or BSD work well) - or Windows if necessary.
I have been a fan of Apple software for a long time now, but I refuse to buy Apple hardware to run it on because it is in many situations cost ineffective for my uses, and because Apple refuses to open up some of their standards or use other people's standards, it remains isolated from the PC world in terms of software compatibility.
I see the switch to x86 processors a big step in the right direction, but only time will tell if it turns out to be a move that threatens the WinTel world seriously.
I'd like to see the Mac box that does justice to BF2
I'll bet that the Power Mac G5 would do the trick, especially the high end one. However, I could build a PC with similar specs for half the price, which was my point...
Tell you what: ou work on Microsoft, I'll work on Apple.:)
You say this as if Microsoft has a soul. I have hope for Apple, but I use Microsoft out of necessity:( (I dual boot Linux of course, but I find myself using Windows most of the time just because Linux lacks the convenience of direct support from most software)
I would like to see you play Battlefield 2 on a Mac Mini (if it were released for Macs).
Or better yet, watch you sit around and wait for 2 million lines of code to compile on a Mac Mini.
Or, do anything computationally expensive. 1.25 GHz, 256MB of RAM, and an ATI Radeon 9200 just doesn't cut it for me. My 4 year old laptop beats those specs.
I think that may be by design, to get you to "switch".
It's going to take more than a rough-around-the-edges music player to get me to switch to Apple hardware. Specifically, it would take about a $500-$1000 price drop as well as more software companies releasing games with support for Mac OS X (Battlefield 2 anyone?)
Is anyone else annoyed that their is no real Windows "updater" for iTunes, and each update basically requires iTunes to reinstall, sometimes clobbering my settings that tell Quicktime to stop bothering me?
I really wish that if Apple releases software for Windows that they actually put the work necessary into it to make it a good product. (Don't get me wrong, I still like iTunes, it just seems very unpolished in Windows).
Actually, the patent covers the specific method in which iTunes organizes it's database, which is a bit different from other methods. Claims 1 and 2 patent the interface of having multiple data field boxes, such as genre, artist, and album. Each of these boxes at the top enumerates the total list of possible values for that data field, until you select an item for that field - then the other fields are updated to only include values consistent with the item chosen. If you've used iTunes, you should be familiar with this selection and search system - otherwise it would help to go poke around some screenshots.
It was in the United States. Miles were used for the same reason they are used on road signs and in cars - it is standard here right now, even if metrics is "better".
It utilizes scanning radar, stereo vision, and scanning laser ranging. Position and orientation are estimated by six-axis inertial sensing and axle encoding that are fused with GPS by an Applanix pose estimator. Additionally, position is sensed by OmniStar GPS.
Generating models from digital sensor data is not simple. Integrating sensor data with machine intelligence is a profound challenge for navigating rough terrain. Sensor data is imperfect due to sensor calibration errors, visual glare, unusual surface properties, and error induced by vibration. Navigation computers must utilize this data while moving at high speed across rough terrain. It must continually make decisions with limited and imperfect information.
As for using 2D images to build a 3D map, if you really did try to implement disparity maps with webcams you should know the limitations in this. The time taken to calculate the disparity map, the semipoor resolution, noise, and lack of data in uniform areas make it only somewhat useful.
Laser range-finding is good, but keep in mind this is a laser. This means that you can really only check a range at one data point at a time. Granted, there are ways of dealing with this, such as scanning, or using prisms/mirrors to spread the laser into a plane, or a combination of the two, but it is still a limited technology.
Neither technique you mentioned is new nor the holy grail to robotic sensing. I would like to see you implement a machine vision system capable of picking out rocks in sand and small pits and other dangers while traveling at 50 mph.
They linked to that story in this story so I would hope you got the connection. The new "news" is Linus responding to the claim that he didn't invent linux. His humurous response was the source of this stories title.
His actual response was in the PPS:
"I don't think the Alexis de Tocqueville institute ever had humor (they certainly used to take themselves very seriously), but their site today is filled with jokes.
Maybe they forgot to pay their DNS registration fee, and some enterprising person decided to play a joke on them? Or maybe their clocks are running a month-and-a-half late?"
From what I can see this project doesn't do much against protect lazy coders. The features listed are easily protected against by writing non-sloppy code.
I'm not sure that this project is a good thing, as if someone gets used to it and switches to a server without it they might be in trouble.
I am curious to see how this will play out with big US companies like Microsoft and Apple, specifically with foreign competitors cloning their products.
Will Microsoft be able to prevent Windows clones from being sold in the US by US patents, even though they may be legal in Europe?
I actually read somewhere where they (i dont remember who they is) were doing something like that with the wooly mammoth - they were mixing wooly mammoth dna with elephant dna, and taking the dna from the resulting animal and mixing that with elephant dna, and continuing until they had close to 100% wooly mammoth. sorta like cloning dinosaurs lol
Slashdot Mirror
My comment wasn't about any specific platform - it was about things taking 15+ minutes to compile. As far as I can tell, those days are far from gone! Some of the code I work with takes an hour or two to compile (luckily I usually only have to do that once a day or so, and do single component compiles the rest of the time).
Still, my point remains that if you can cut down a 2 hour compile to a 1 hour compile, that buys you extra productivity time. I would consider it a worthy investment to get a cost effective machine with more power than a Mac mini for serious development - aka a PC running some flavor of Unix (Solaris or BSD work well) - or Windows if necessary.
I have been a fan of Apple software for a long time now, but I refuse to buy Apple hardware to run it on because it is in many situations cost ineffective for my uses, and because Apple refuses to open up some of their standards or use other people's standards, it remains isolated from the PC world in terms of software compatibility.
I see the switch to x86 processors a big step in the right direction, but only time will tell if it turns out to be a move that threatens the WinTel world seriously.
I remember well when it took 15 minutes to compile and link my Unix-based BBS software on a 286. Thank goodness those days are long gone!
I see you have never compiled Gnome. Or perhaps on some machines a Linux kernel.
I'd like to see the Mac box that does justice to BF2
...
I'll bet that the Power Mac G5 would do the trick, especially the high end one. However, I could build a PC with similar specs for half the price, which was my point
Tell you what: ou work on Microsoft, I'll work on Apple. :)
:( (I dual boot Linux of course, but I find myself using Windows most of the time just because Linux lacks the convenience of direct support from most software)
You say this as if Microsoft has a soul. I have hope for Apple, but I use Microsoft out of necessity
I would like to see you play Battlefield 2 on a Mac Mini (if it were released for Macs).
Or better yet, watch you sit around and wait for 2 million lines of code to compile on a Mac Mini.
Or, do anything computationally expensive. 1.25 GHz, 256MB of RAM, and an ATI Radeon 9200 just doesn't cut it for me. My 4 year old laptop beats those specs.
I think that may be by design, to get you to "switch".
It's going to take more than a rough-around-the-edges music player to get me to switch to Apple hardware. Specifically, it would take about a $500-$1000 price drop as well as more software companies releasing games with support for Mac OS X (Battlefield 2 anyone?)
Is anyone else annoyed that their is no real Windows "updater" for iTunes, and each update basically requires iTunes to reinstall, sometimes clobbering my settings that tell Quicktime to stop bothering me?
I really wish that if Apple releases software for Windows that they actually put the work necessary into it to make it a good product. (Don't get me wrong, I still like iTunes, it just seems very unpolished in Windows).
Actually, the patent covers the specific method in which iTunes organizes it's database, which is a bit different from other methods. Claims 1 and 2 patent the interface of having multiple data field boxes, such as genre, artist, and album. Each of these boxes at the top enumerates the total list of possible values for that data field, until you select an item for that field - then the other fields are updated to only include values consistent with the item chosen. If you've used iTunes, you should be familiar with this selection and search system - otherwise it would help to go poke around some screenshots.
It was in the United States. Miles were used for the same reason they are used on road signs and in cars - it is standard here right now, even if metrics is "better".
one step foreword
He sure isn't a spelling major
The fuel cell burns methane
In other news, baked bean stocks triple!
Nice try to sound smart, but its not like your the first to think that robots should have sensors.
Red team's sensors
It utilizes scanning radar, stereo vision, and scanning laser ranging. Position and orientation are estimated by six-axis inertial sensing and axle encoding that are fused with GPS by an Applanix pose estimator. Additionally, position is sensed by OmniStar GPS.
Generating models from digital sensor data is not simple. Integrating sensor data with machine intelligence is a profound challenge for navigating rough terrain. Sensor data is imperfect due to sensor calibration errors, visual glare, unusual surface properties, and error induced by vibration. Navigation computers must utilize this data while moving at high speed across rough terrain. It must continually make decisions with limited and imperfect information.
As for using 2D images to build a 3D map, if you really did try to implement disparity maps with webcams you should know the limitations in this. The time taken to calculate the disparity map, the semipoor resolution, noise, and lack of data in uniform areas make it only somewhat useful.
Laser range-finding is good, but keep in mind this is a laser. This means that you can really only check a range at one data point at a time. Granted, there are ways of dealing with this, such as scanning, or using prisms/mirrors to spread the laser into a plane, or a combination of the two, but it is still a limited technology.
Neither technique you mentioned is new nor the holy grail to robotic sensing. I would like to see you implement a machine vision system capable of picking out rocks in sand and small pits and other dangers while traveling at 50 mph.
Wouldn't the tooth fairy be a mother?
They linked to that story in this story so I would hope you got the connection. The new "news" is Linus responding to the claim that he didn't invent linux. His humurous response was the source of this stories title.
His actual response was in the PPS:
"I don't think the Alexis de Tocqueville institute ever had humor (they certainly used to take themselves very seriously), but their site today is filled with jokes.
Maybe they forgot to pay their DNS registration fee, and some enterprising person decided to play a joke on them? Or maybe their clocks are running a month-and-a-half late?"
From what I can see this project doesn't do much against protect lazy coders. The features listed are easily protected against by writing non-sloppy code.
I'm not sure that this project is a good thing, as if someone gets used to it and switches to a server without it they might be in trouble.
I am curious to see how this will play out with big US companies like Microsoft and Apple, specifically with foreign competitors cloning their products.
Will Microsoft be able to prevent Windows clones from being sold in the US by US patents, even though they may be legal in Europe?
I can think of a few good applications for this much storage ...
fp!
I actually read somewhere where they (i dont remember who they is) were doing something like that with the wooly mammoth - they were mixing wooly mammoth dna with elephant dna, and taking the dna from the resulting animal and mixing that with elephant dna, and continuing until they had close to 100% wooly mammoth. sorta like cloning dinosaurs lol