Slashdot Mirror

This reminds me of this fascinating Lisp interpreter which is run based on templates during compile time as it seems.

http://209.85.129.104/search?q=cache:Hc_Bsm4QjkAJ:www.prakinf.tu-ilmenau.de/~czarn/meta/metalisp.cpp+metalisp&hl=en&ct=clnk&cd=6

Unfortunately people seem to have lost interest in it and the code is now only in the google cache. This was mentioned in the boost paper:

http://www.cs.ualberta.ca/~graphics/software/boost/libs/mpl/doc/paper/mpl_paper.pdf

I find this totally interesting even though it seems like C++ has been stretched beyond its limits. I think this is a good example for the complexity you complain about. People are producing useful code and even libraries based on obscure features of the compiler which the inventors never thought about. If you need compile time functionality to support programmable code generation you would expect some more explicit language features to be available for this task.

Also I always feel that I must learn about these advanced template mechanisms I have no clue about, to really understand C++. Then I notice that the rest of the world thinks that C++ is outdated and Java or something else sluggish is the language of the future. You can't write high performance code in Java (digital signal processing, image processing, real time stuff, ...) however, so I will continue with C/C++. The DSP and uC environments also never support Java and rarely will they have a good C++ compiler. So I feel a bit left behind. Especially since I don't know what the next best high performance programming language will be.

Well, they have an "expert team" that also collected scenarios and workflows to deal with. Although the site seems to be temporarily offline, it is available through google's cache: http://gui.gimp.org/ (Original Site) http://209.85.129.104/search?q=cache:Zr49_iZjaaoJ:gui.gimp.org/+gimp+ui&hl=de&client=firefox-a&gl=de&strip=1 (Google text-only cache)

Another example is http://thepiratebay.org/user/achim106/.

That one is still in the Google cache: http://209.85.129.104/search?q=cache:B5kqltngQjcJ: thepiratebay.org/user/achim106/+http://thepirateba y.org/user/achim106/&hl=en&ct=clnk&cd=1

The police thought it was, TBP didn't, but deleted things anyway at the request of some users.

Actually, no, they specfically didn't delete these things when users requested it before this big upset. It's only after they got all this unwanted attention that they suddenly started nuking entire user accounts.

Less broken links: http://209.85.129.104/search?q=cache:B5kqltngQjcJ: thepiratebay.org/user/achim106/+http://thepirateba y.org/user/achim106/&hl=en&ct=clnk&cd=1 and http://thepiratebay.org/user/achim106/

That may very well be the case.

However, it's also true. The Pirate Bay has been running (and, I hear, still runs) torrents for very borderline if not outright illegal child porn material. They have refused to remove them (like many other trackers do) until now when it suddenly got worldwide attention, when they started nuking torrents left and right.

Compare http://209.85.129.104/search?q=cache:B5kqltngQjcJ: thepiratebay.org/user/achim106/+http://thepirateba y.org/user/achim106/&hl=en&ct=clnk&cd=1 and http://thepirateba/ y.org/user/achim106/ for instance.

They have removed lots of stuff. They aren't exactly trumpeting that particular fact in their public grandstanding, though.

Try comparing http://thepiratebay.org/user/achim106/ and
http://209.85.129.104/search?q=cache:B5kqltngQjcJ: thepiratebay.org/user/achim106/+http://thepirateba y.org/user/achim106/&hl=en&ct=clnk&cd=1 for instance.

I tried submitting a more balanced third-party article about this earlier, but apparently it's not interesting to Slashdot unless it's spin.

OK, but the lack of an API to disable Vistas indexing isn't what's being contested. In fact, you can read the amicus brief Google submitted to the courts about the issue here.

Here's the key quote:

Google welcomes the efforts of the parties to address Microsoft's violation by taking steps to promote user and OEM choice. At the same time, from what Google understands of the remedies, it appears that more may need to be done to provide a truly unbiased choice of desktop search products in Vista and achieve compliance with the Final Judgment.

The proposed remedial measures regarding user access points are only vaguely described in the status report, and it is not immediately apparent that they will give users and OEMs the rights to which they are entitled under III.H. 1 (a) of the Final Judgment. For example, it appears that Microsoft will continue to show its own desktop search results when users run searches from prominent shortcuts and menu entries throughout the operating system, though users will now be given a mechanism to request results from their chosen desktop search product by taking a second step after they have first viewed results from Microsoft's product.

In addition, although the status report does not mention the fact that one of the menu entries in the Vista Start menu and in various "right-click" menus is the word "Search," Google understands that Microsoft may intend to remove these menu entries from Vista and deprive users of these access points altogether rather than provide the user choice required under III.H. 1 (a) of the Final Judgment. With respect to the automatic invocation of Microsoft's desktop search product following the boot sequence, which implicates III.H. I1(b) of the Final Judgment, it appears that the proposed measures would not result in any changes being made in the operating system. Instead, Microsoft will provide unspecified technical information about indexing to OEMs Independent Software Vendors, and end users.

It seems to me that the complaint is about Microsofts solution either making users jump through hoops (extra clicking for each search) to access the newly installed desktop search engine, or about them possibly just removing UI elements instead of making them configurable. Now you could argue that it's OK for parts of the Vista UI to die or become useless if you disable Vista search on the grounds that you can always create your own UI elsewhere, but I think that would be a bit silly. A key part of the way IE 4 was tied into Windows was via ubiquitous UI integration - whilst users could certainly install an alternative browser, the fact that most parts of the Windows UI still started up IE if you clicked them was a serious problem for Netscape.

My disclaimer is here - I do work for Google but not on anything related to desktop search. I contacted one of our legal/PR people about these Vista Search stories and they told me about this brief, which was released to reporters. As should hopefully be obvious, the opinions I stated here are only my own. As to why this brief is not on our own website, I do not know ....

Or, the original page from Google Cache

It's ironic that Google notified the author of this public Google Notebook, but the content is still available from the same company :)

(I forget how to get the euro symbol)

lol. Kinda depends on where you are... The EC even had a committee on it!! Only the google cache exists now...

http://209.85.129.104/search?q=cache:Vd6E2fXxyDwJ: anubis.dkuug.dk/CEN/TC304/Euro/151.doc

Summary:

If you're in the US it's AltGR-5
It you're in the UK it's AltGR-3
If you're in most of the rest of the world it's AltGR-e otherwise read the document.

True. Sadly his plans for wireless-electricity were completely thwarted, interestingly enough, by a refrigeration company that needed low prices for copper in order to enjoy low-cost production for their cooling systems. The reason copper was cheap, of course, was because wired electricity was in demand at the time.

More on that in here.

Next: An engineer working for Ford will be on the cover of Time magazine hailed as a saint for his invention, the Hydroden Engine. No one will find it conspicuous the article is flanked by a full page ad for BP featuring a woman drinking from a pool of crystal clear alpine water.

Our language is a living thing, you know?

- Justice.gov
http://209.85.129.104/search?q=cache:A5I15OC9_OkJ: www.justice.gov/criminal/cybercrime/mynafSent.htm+ unauthorizedly+site:.gov&hl=en&ct=clnk&cd=1&lr=lan g_en

- NLRB.gov
http://209.85.129.104/search?q=cache:PdlnI1A9aNgJ: www.nlrb.gov/nlrb/shared_files/decisions/280/280-1 378.txt+unauthorizedly+site:.gov&hl=en&ct=clnk&cd= 3&lr=lang_en

- USDoJ.gov
http://209.85.129.104/search?q=cache:yPWeciAou1kJ: www.usdoj.gov/eoir/OcahoMain/publisheddecisions/Ha rdbound/Volume5/735.pdf+unauthorizedly+site:.gov&h l=en&ct=clnk&cd=5&lr=lang_en

- PBR.Ohio.gov
http://209.85.129.104/search?q=cache:heyK-Buv_mEJ: pbr.ohio.gov/pdf/1991/91-REM-04-0224.pdf+unauthori zedly+site:.gov&hl=en&ct=clnk&cd=9&lr=lang_en

Our language is a living thing, you know?

- Justice.gov
http://209.85.129.104/search?q=cache:A5I15OC9_OkJ: www.justice.gov/criminal/cybercrime/mynafSent.htm+ unauthorizedly+site:.gov&hl=en&ct=clnk&cd=1&lr=lan g_en

- NLRB.gov
http://209.85.129.104/search?q=cache:PdlnI1A9aNgJ: www.nlrb.gov/nlrb/shared_files/decisions/280/280-1 378.txt+unauthorizedly+site:.gov&hl=en&ct=clnk&cd= 3&lr=lang_en

- USDoJ.gov
http://209.85.129.104/search?q=cache:yPWeciAou1kJ: www.usdoj.gov/eoir/OcahoMain/publisheddecisions/Ha rdbound/Volume5/735.pdf+unauthorizedly+site:.gov&h l=en&ct=clnk&cd=5&lr=lang_en

- PBR.Ohio.gov
http://209.85.129.104/search?q=cache:heyK-Buv_mEJ: pbr.ohio.gov/pdf/1991/91-REM-04-0224.pdf+unauthori zedly+site:.gov&hl=en&ct=clnk&cd=9&lr=lang_en

Our language is a living thing, you know?

- Justice.gov
http://209.85.129.104/search?q=cache:A5I15OC9_OkJ: www.justice.gov/criminal/cybercrime/mynafSent.htm+ unauthorizedly+site:.gov&hl=en&ct=clnk&cd=1&lr=lan g_en

- NLRB.gov
http://209.85.129.104/search?q=cache:PdlnI1A9aNgJ: www.nlrb.gov/nlrb/shared_files/decisions/280/280-1 378.txt+unauthorizedly+site:.gov&hl=en&ct=clnk&cd= 3&lr=lang_en

- USDoJ.gov
http://209.85.129.104/search?q=cache:yPWeciAou1kJ: www.usdoj.gov/eoir/OcahoMain/publisheddecisions/Ha rdbound/Volume5/735.pdf+unauthorizedly+site:.gov&h l=en&ct=clnk&cd=5&lr=lang_en

- PBR.Ohio.gov
http://209.85.129.104/search?q=cache:heyK-Buv_mEJ: pbr.ohio.gov/pdf/1991/91-REM-04-0224.pdf+unauthori zedly+site:.gov&hl=en&ct=clnk&cd=9&lr=lang_en

Our language is a living thing, you know?

- Justice.gov
http://209.85.129.104/search?q=cache:A5I15OC9_OkJ: www.justice.gov/criminal/cybercrime/mynafSent.htm+ unauthorizedly+site:.gov&hl=en&ct=clnk&cd=1&lr=lan g_en

- NLRB.gov
http://209.85.129.104/search?q=cache:PdlnI1A9aNgJ: www.nlrb.gov/nlrb/shared_files/decisions/280/280-1 378.txt+unauthorizedly+site:.gov&hl=en&ct=clnk&cd= 3&lr=lang_en

- USDoJ.gov
http://209.85.129.104/search?q=cache:yPWeciAou1kJ: www.usdoj.gov/eoir/OcahoMain/publisheddecisions/Ha rdbound/Volume5/735.pdf+unauthorizedly+site:.gov&h l=en&ct=clnk&cd=5&lr=lang_en

- PBR.Ohio.gov
http://209.85.129.104/search?q=cache:heyK-Buv_mEJ: pbr.ohio.gov/pdf/1991/91-REM-04-0224.pdf+unauthori zedly+site:.gov&hl=en&ct=clnk&cd=9&lr=lang_en