Talk:Herb Sutter
This article was nominated for deletion on 12 September 2023. The result of the discussion was keep. |
This article must adhere to the biographies of living persons (BLP) policy, even if it is not a biography, because it contains material about living persons. Contentious material about living persons that is unsourced or poorly sourced must be removed immediately from the article and its talk page, especially if potentially libellous. If such material is repeatedly inserted, or if you have other concerns, please report the issue to this noticeboard.If you are a subject of this article, or acting on behalf of one, and you need help, please see this help page. |
This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||
|
Untitled
editHerb Sutter is my uncle! He is a real cool guy. Keep reading his books!
- Will do... actually his website has awesome info as well for those curious :) RN 12:53, 3 September 2006 (UTC)
Patent controversy
editSutter's name is on US Patent 7496889, "Whitespace Keywords". On reading this document, there are countless nonsensical statements (the whole premise of keywords with a space in them is trivial). At one point it goes into
(LAN) and wide-area networks (WAN). LAN technologies include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet, Token Ring and the like. WANtechnologies include, but are not limited to, point-to-point links, circuit switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet switching networks, and Digital Subscriber Lines (DSL).
Any compiler developer would write this work off, but the article suggests some pre-eminence. What's the deal? —Preceding unsigned comment added by 86.142.179.118 (talk) 04:23, 23 November 2009 (UTC)
Patent controversy continued
editIf I remember correctly: In the process of developing Microsofts variant of Visual Basic they had a problem making it compatible with existing implementations due to a (as I remember it) keyword and a patent. Microsoft could not make the languages compatible. I am sure someone knows more about it, and can correct my wrongs. I think it is something similar we see with this patent. Here Microsoft is trying to protect their Common Language Runtime (CLR) (or C++ .NET) from being copied. That no one should be able to make a system compatible to the .NET C++ version of Microsoft. That's at least my theory. 2001:4643:E6E3:0:F12E:681B:A94D:9196 (talk) 12:12, 1 December 2017 (UTC)
Why the redirect from 'free lunch'?
edit>(Redirected from The Free Lunch Is Over (computing))
Why does this direct exist? I came here from that topic and having read this page I still have no idea why I'm here. MEMark (talk) 03:20, 10 July 2023 (UTC)
- Apparently he wrote an article in 2005 entitled "The Free Lunch is Over". At the time the redirect was created there was a section in this article discussing it, but it was removed in this edit in October of 2022. ~ ONUnicorn(Talk|Contribs)problem solving 18:17, 12 September 2023 (UTC)
- I've restored discussion of the free lunch paper to this article. ~ ONUnicorn(Talk|Contribs)problem solving 21:23, 12 September 2023 (UTC)