What you're missing is that these guys act as a go-between for a large number of takeout restaurants. It effectively gives you up to date access to all takeout menus for all your local restaurants from one central site.
but if you think copyright related crimes, especially ones where nobody profits from the crime and the only loss is a theoretical and arguable one at best, are in the same ballpark as the other examples you gave... well... you need to get out more often.
I disagree. If he doesn't know the difference between rape, burglary and arson and copyright theft, then I think he should definitely stay in! We don't need any more sociopathic nutters on the streets!
This may not be quite as vaporware as some might think. Certainly it seems to be true that Adann Osmani did win the prize with a browser that speeds up internet usage by 400%. See this link:
http://www.rte.ie/news/2003/0110/youngscientist.ht ml for the news report and the 9.00 video link below the article to see the presentation.
Don't quite know about the claims though. Some of the reporters may have got quite confused. It's possible that he has just modified an open source browser and added some intelligent precaching. Which might have taken him 2 years and he might just have told them how many lines of code there were in the whole app and not how many of them he wrote:-)
Still seems like there's something fishy about it, but if it's a hoax, it's an elaborate one and the judges were fooled.
MVC helps here, but it's still annyoing - instead of the simple "MyApp::toolbar_visible = true;" you end up writing something like "MyApp::toolbar_visible = true; MyApp::notify_toolbar_change();" Ideally you should only need the "= true" part, and the language runtime should figure out that the toolbar needs to be shown.
What you should write is MyApp::setToolbarVisible(true);
And the implementation of MyApp::setToolbarVisible(bool visible) should do the notifying. Then your toolbar should be a change listener to MyApp and will show or hide itself as necessary. That way you'd be a lot closer to MVC. The way you have it, it is much too easy to forget to call MyApp::notify_toolbar_change() and have a broken application. Having an accessor method do that for you means that the line only appears once and will always get called at the right time.
Slashdot Mirror
What you're missing is that these guys act as a go-between for a large number of takeout restaurants. It effectively gives you up to date access to all takeout menus for all your local restaurants from one central site.
Frankly it's a brilliant idea.
Wow that was a fast slashdot effect. I don't suppose anyone managed to get a mirror of it before the site went down?
This may not be quite as vaporware as some might think. Certainly it seems to be true that Adann Osmani did win the prize with a browser that speeds up internet usage by 400%. See this link: http://www.rte.ie/news/2003/0110/youngscientist.ht ml for the news report and the 9.00 video link below the article to see the presentation.
:-)
Still seems like there's something fishy about it, but if it's a hoax, it's an elaborate one and the judges were fooled.
Don't quite know about the claims though. Some of the reporters may have got quite confused. It's possible that he has just modified an open source browser and added some intelligent precaching. Which might have taken him 2 years and he might just have told them how many lines of code there were in the whole app and not how many of them he wrote
MVC helps here, but it's still annyoing - instead of the simple "MyApp::toolbar_visible = true;" you end up writing something like "MyApp::toolbar_visible = true; MyApp::notify_toolbar_change();" Ideally you should only need the "= true" part, and the language runtime should figure out that the toolbar needs to be shown.
What you should write is MyApp::setToolbarVisible(true);
And the implementation of MyApp::setToolbarVisible(bool visible) should do the notifying. Then your toolbar should be a change listener to MyApp and will show or hide itself as necessary. That way you'd be a lot closer to MVC. The way you have it, it is much too easy to forget to call MyApp::notify_toolbar_change() and have a broken application. Having an accessor method do that for you means that the line only appears once and will always get called at the right time.