If folks have spare time that they want to donate, how about helping out in your own backyard first?
How about, "Because the need there isn't generally as great"? Anyway, even if this software is bespoke, it's going to be available under the GPL, so anybody who has a use for it (and can get the source) can benefit from it.
Traffic congestion is still a problem at intersections, as parking them. I'd also like to see how it handles routing through the city.
You have the relatively cheap option of doing it in 3D. No intersection, no problem. Not sure about parking, but I guess that you just have sidings big enough for one car every twenty metres (in busy areas). You get out, it leaves to pick someone else up. Routing will be a very interesting programming problem.
Also, now we're talking about tracks. What happens when one jumps the tracks? It just sit there hold up everything else behind it?
Presumably. That'd be the same as trains and cars...
How are we going to accomodate for all these tracks in existing cities? It's grossly expensive and takes up space.
Hmm. Tear up some of the roads and stop subsidising drivers would be my knee-jerk response. Alternatively, since you won't need to accommodate any forty tonne trucks, just build them all as flyovers to existing roads. It is expensive, true, but so is purchasing new land for more roads, maintaining roads, and dealing with the adverse affects of motor vehicle over-use.
James
background -
I attend an English university of no distinction, and I'm completing a master's degree in CS. It's not a first CS degree, but a conversion for those who did a different subject for their undergrad.
coding -
We've done some x86 assembler, C and Java, which I think is reasonable mix. Some people on the course seem to hate programming. Personally, I wish there was more, but that's by-the-by.
question -
Of the above, the Java project was collaborative. Makes sense, given the increased orthogonality of code units versus C or assembler. I wrote most of the code, someone designed the (optional) database, someone else did most of the worrying, and betwen them they produced vast amounts of documentation. I know for a fact that our code was not read over, despite the fact that implementation was supposed to be fifty per cent of the marks. We could not have been, as far as I can see, marked fairly. I like my code - it's the thing I do best. I'm not particularly interested in documentation &c. Does anyone else think that code is overlooked in marking, to the advantage of less core CS skills? How common is it for markers to skip looking at code? Has anyone often had their code looked over in great detail by their lecturers?
I wonder how many people have tried compiling their code, then decompiling it and handing in the tidied up decompiled code? Don't know much about decompilers, but I'd imagine they make the code look pretty terse, if the initial compile was any good.
I was at Nottingham University 1995-98. When I arrived, there can't have been much demand for bandwidth, and I received strange looks when I asked about a connection on my room.
By the time I left, the three thousand plus rooms on campus had connections, although take up was relatively slow. The network cost then was thirty pounds for the year (thirty weeks).
When QW Vindaloo Duel Servers #5 and #6 joined started operating out of the student union's web server, the authorities were actually quite intolerant. They were not nearly as busy as the Vindaloo servers in Oxford, and a QW client only sucks up two or three kilobits per second at worst anyway. Given that the Computing Service housed the local SuperJANet hub anyway, their insistence on its removal seemed rather draconian. Moreover, thet couldn't at the time monitor they type of traffic students were generating. A couple of servers on campus might have reduced the amount of QW traffic going through their gateways to other JANet sites.
James
Given the lack of attention paid by cyclists, pedestrians and motorists to each other, I can only predict certain death. Still, at 80 mph you might take out some other people when they pull out / step out on front of you.
As my Geography teacher never tired of telling us, climate != weather.
Climate is big and long-term. Weather is here and now. Not even the people who built that machine think it can predict world weather for one thousand years. There's just been a bit of a misunderstanding.
Slashdot Mirror
If folks have spare time that they want to donate, how about helping out in your own backyard first?
How about, "Because the need there isn't generally as great"?
Anyway, even if this software is bespoke, it's going to be available under the GPL, so anybody who has a use for it (and can get the source) can benefit from it.
Traffic congestion is still a problem at intersections, as parking them. I'd also like to see how it handles routing through the city.
You have the relatively cheap option of doing it in 3D. No intersection, no problem. Not sure about parking, but I guess that you just have sidings big enough for one car every twenty metres (in busy areas). You get out, it leaves to pick someone else up. Routing will be a very interesting programming problem.
Also, now we're talking about tracks. What happens when one jumps the tracks? It just sit there hold up everything else behind it?
Presumably. That'd be the same as trains and cars...
How are we going to accomodate for all these tracks in existing cities? It's grossly expensive and takes up space.
Hmm. Tear up some of the roads and stop subsidising drivers would be my knee-jerk response. Alternatively, since you won't need to accommodate any forty tonne trucks, just build them all as flyovers to existing roads. It is expensive, true, but so is purchasing new land for more roads, maintaining roads, and dealing with the adverse affects of motor vehicle over-use.
James
background -
I attend an English university of no distinction, and I'm completing a master's degree in CS. It's not a first CS degree, but a conversion for those who did a different subject for their undergrad.
coding -
We've done some x86 assembler, C and Java, which I think is reasonable mix. Some people on the course seem to hate programming. Personally, I wish there was more, but that's by-the-by.
question -
Of the above, the Java project was collaborative. Makes sense, given the increased orthogonality of code units versus C or assembler. I wrote most of the code, someone designed the (optional) database, someone else did most of the worrying, and betwen them they produced vast amounts of documentation. I know for a fact that our code was not read over, despite the fact that implementation was supposed to be fifty per cent of the marks. We could not have been, as far as I can see, marked fairly. I like my code - it's the thing I do best. I'm not particularly interested in documentation &c. Does anyone else think that code is overlooked in marking, to the advantage of less core CS skills? How common is it for markers to skip looking at code? Has anyone often had their code looked over in great detail by their lecturers?
I wonder how many people have tried compiling their code, then decompiling it and handing in the tidied up decompiled code? Don't know much about decompilers, but I'd imagine they make the code look pretty terse, if the initial compile was any good.
I was at Nottingham University 1995-98. When I arrived, there can't have been much demand for bandwidth, and I received strange looks when I asked about a connection on my room.
By the time I left, the three thousand plus rooms on campus had connections, although take up was relatively slow. The network cost then was thirty pounds for the year (thirty weeks).
When QW Vindaloo Duel Servers #5 and #6 joined started operating out of the student union's web server, the authorities were actually quite intolerant. They were not nearly as busy as the Vindaloo servers in Oxford, and a QW client only sucks up two or three kilobits per second at worst anyway. Given that the Computing Service housed the local SuperJANet hub anyway, their insistence on its removal seemed rather draconian. Moreover, thet couldn't at the time monitor they type of traffic students were generating. A couple of servers on campus might have reduced the amount of QW traffic going through their gateways to other JANet sites.
James
This is Orwell not Huxley...
telephong?(http://www.alphabet-soup.net/dir6/eleph ant.html)
Given the lack of attention paid by cyclists, pedestrians and motorists to each other, I can only predict certain death. Still, at 80 mph you might take out some other people when they pull out / step out on front of you.
As my Geography teacher never tired of telling us, climate != weather.
Climate is big and long-term. Weather is here and now. Not even the people who built that machine think it can predict world weather for one thousand years. There's just been a bit of a misunderstanding.