Date: Wed, 4 Aug 2021 22:08:25 +0300
On 8/4/21 9:03 PM, Phil Bouchard wrote:
>
> On 8/4/21 1:44 PM, Andrey Semashev via Std-Proposals wrote:
>> On 8/4/21 8:15 PM, Phil Bouchard via Std-Proposals wrote:
>>>
>>> On 8/3/21 11:41 PM, Phil Bouchard via Std-Proposals wrote:
>>>>
>>>>
>>>> On 8/3/21 11:07 PM, Emile Cormier via Std-Proposals wrote:
>>>>> Sorry, but who do you expect to get involved in a C++ language
>>>>> extensions encumbered by patents? Does your "C++ Superset" allow a
>>>>> patent-free, open-source implementation?
>>>>
>>>> Part of what I mentioned is patent pending but I can certainly
>>>> loosen restrictions, but the Root Pointer headers will remain patented.
>>>>
>>> BTW thank God software can now be patented. Here's my anecdote:
>>>
>>> - I was working for Corel Linux back in 2000 until Microsoft
>>> dissolved it;
>>>
>>> - I wrote my own Fornux Powercalc and proposed it to Microsoft but
>>> got silently embraced and extended my Microsoft Powertoys:
>>>
>>> https://github.com/philippeb8/fcalc
>>>
>>> https://upload.wikimedia.org/wikipedia/en/6/6f/Powercalc.PNG
>>>
>>> - Herb Sutter from Microsoft almost embraced and extended the logic
>>> of Root Pointer:
>>>
>>> https://github.com/hsutter/gcpp
>>>
>>>
>>> So sorry for the patent implications but this is the only way to
>>> protect ourselves these days.
>>
>> Patents are a good way to bury your software and ideas in the sand.
>> Sane people will be very cautious about using patented stuff and some
>> won't even touch it with a ten feet pole. IMO, a language (extension)
>> that builds on top of a patented technology is DOA.
>
> Well it depends on the importance of the problem that is being fixed.
> But in no way Microsoft will embrace and extend my efforts anymore.
My point was that people (and companies) embracing code and ideas is
*the* way to achieve adoption.
>> If you want to make profit, that's fine, but creating new programming
>> languages is not the way. You can create tools that make the language
>> safer - compilers, static analyzers, instrumenters, etc. - and sell
>> those. If you want to make the language itself better then you work on
>> that in a way that makes as easy to employ and distribute across the
>> widest possible variety of tools, developers, applications across the
>> industry, and patents are a major blocker in this.
>
> On 8/4/21 1:44 PM, Andrey Semashev via Std-Proposals wrote:
>> On 8/4/21 8:15 PM, Phil Bouchard via Std-Proposals wrote:
>>>
>>> On 8/3/21 11:41 PM, Phil Bouchard via Std-Proposals wrote:
>>>>
>>>>
>>>> On 8/3/21 11:07 PM, Emile Cormier via Std-Proposals wrote:
>>>>> Sorry, but who do you expect to get involved in a C++ language
>>>>> extensions encumbered by patents? Does your "C++ Superset" allow a
>>>>> patent-free, open-source implementation?
>>>>
>>>> Part of what I mentioned is patent pending but I can certainly
>>>> loosen restrictions, but the Root Pointer headers will remain patented.
>>>>
>>> BTW thank God software can now be patented. Here's my anecdote:
>>>
>>> - I was working for Corel Linux back in 2000 until Microsoft
>>> dissolved it;
>>>
>>> - I wrote my own Fornux Powercalc and proposed it to Microsoft but
>>> got silently embraced and extended my Microsoft Powertoys:
>>>
>>> https://github.com/philippeb8/fcalc
>>>
>>> https://upload.wikimedia.org/wikipedia/en/6/6f/Powercalc.PNG
>>>
>>> - Herb Sutter from Microsoft almost embraced and extended the logic
>>> of Root Pointer:
>>>
>>> https://github.com/hsutter/gcpp
>>>
>>>
>>> So sorry for the patent implications but this is the only way to
>>> protect ourselves these days.
>>
>> Patents are a good way to bury your software and ideas in the sand.
>> Sane people will be very cautious about using patented stuff and some
>> won't even touch it with a ten feet pole. IMO, a language (extension)
>> that builds on top of a patented technology is DOA.
>
> Well it depends on the importance of the problem that is being fixed.
> But in no way Microsoft will embrace and extend my efforts anymore.
My point was that people (and companies) embracing code and ideas is
*the* way to achieve adoption.
>> If you want to make profit, that's fine, but creating new programming
>> languages is not the way. You can create tools that make the language
>> safer - compilers, static analyzers, instrumenters, etc. - and sell
>> those. If you want to make the language itself better then you work on
>> that in a way that makes as easy to employ and distribute across the
>> widest possible variety of tools, developers, applications across the
>> industry, and patents are a major blocker in this.
Received on 2021-08-04 14:08:30