Often I complain that GTK+ documentation (non-reference) is non-existent. The few GTK+ books that were ever written are now old and most of their included source code does not even compile anymore. All hail "Foundations of GTK+ Development" by Andrew Krause.
Permalink for comment 242720
To read all comments associated with this story, please click here.
>GTK# is extremely dangerous. It's inviting lawsuit,
>or intimidation and/or extortion from Microsoft.
Why? Come on, that's FUD. GTK# is NOT copying a Microsoft product. If GTK+ itself is NOT threatened, then why is a thin wrapper using a de jure standardised language threatened?
If there are any problems, it will be in the WindowsForms or ASP.Net side or other stuff that isn't in the ECMA standard.
Give Microsoft *some* credit for open standardisation where they've done it.
> The recent Fortune magazine article, which contains
> MS's latest patent threats, makes this crystal clear.
Go-one, be specific. MS can threaten wherever they have patents, but GTK# is no more and no less likely to be infringing than any random bit of code, so far as I can see.
Member since:
2006-02-20
>GTK# is extremely dangerous. It's inviting lawsuit,
>or intimidation and/or extortion from Microsoft.
Why? Come on, that's FUD. GTK# is NOT copying a Microsoft product. If GTK+ itself is NOT threatened, then why is a thin wrapper using a de jure standardised language threatened?
If there are any problems, it will be in the WindowsForms or ASP.Net side or other stuff that isn't in the ECMA standard.
Give Microsoft *some* credit for open standardisation where they've done it.
> The recent Fortune magazine article, which contains
> MS's latest patent threats, makes this crystal clear.
Go-one, be specific. MS can threaten wherever they have patents, but GTK# is no more and no less likely to be infringing than any random bit of code, so far as I can see.
James