7 ms·

https://github.com/williamcotton/webdsl https://github.com/williamcotton/webdsl Made almost entirely with Cursor and Claude 3.5 Sonnet. 11k lines of C and cou

https://github.com/williamcotton/webdsl https://github.com/williamcotton/webdsl Made almost entirely with Cursor and Claude 3.5 Sonnet. 11k lines of C and counting.

andix 2y ago
Thanks, that's exactly what I'm looking for.
thomasfromcdnjs 2y ago
I used Windsurf mostly on a feature to build out user authentication and then another tool to generate the PR documentation entirely. https://github.com/jsonresume/jsonresume.org/pull/176 https://github.com/jsonresume/jsonresume.org/pull/176 Meets my good enough standards fo sure
BeefWellington 2y ago
It's funny that this is MIT licensed, expecting credit for uncopyrightable work.
- williamcotton 2y ago
  I work in copyright law. Familiarize yourself with the AFC test concept and I'm willing to have a conversation about what would be copyrightable in this project of mine. https://en.wikipedia.org/wiki/Abstraction-Filtration-Comparison_test https://en.wikipedia.org/wiki/Abstraction-Filtration-Compari...
  - BeefWellington 2y ago
    You misunderstand, the repo lists an MIT license which requires attribution. You want people to give you credit if they use this LLM-generated code. LLMs which were trained on the works of thousands of other developers with similar licenses, who are offered no similar credit here. It also claims copyright of the code as though you have authored it, but you're claiming here to have used LLMs to generate it. Seems like trying to have it both ways.
    - williamcotton 2y ago
      I want people to give me attribution for the parts of my project that are copyrightable. From the article, The second step is to remove from consideration aspects of the program which are not legally protectable by copyright. The analysis is done at each level of abstraction identified in the previous step. The court identifies three factors to consider during this step: elements dictated by efficiency, elements dictated by external factors, and elements taken from the public domain. This means that the code written for interfacing with an external API, eg, GitHub OAuth, would not be covered by any sort of copyright as the expression is dictated by requirements of the API itself. The overall structure and organization of the code was not generated by LLMs and is fully covered by copyright. LLMs are in fact very good at writing code that would probably not be copyrightable in the first place and are pretty bad at writing the overall expressive systems structures that would be covered by copyright.
      - BeefWellington 2y ago
        > I want people to give me attribution for the parts of my project that are copyrightable. A requirement not extended to the open source developers whose code you are using essentially a copyright and licensing laundering engine to get around.
        deleted 2y ago
        [deleted]
        deleted 2y ago
        [deleted]
gray_-_wolf 2y ago
What I find interesting is that the project claims MIT license, but if it is "almost entirely" AI generated, I am not sure it even is copyrightable. So either the licensing terms deserve some large disclaimers, or it is not "almost entirely" made with AI. Based on the name I assume it is your project, could you shed some light on which of those two options is correct?
- williamcotton 2y ago
  There are differing levels of abstraction when considering copyright.
- andix 2y ago
  I guess copyright laws treat AIs as tools. If you paint a picture with a brush it's also almost entirely "brush created", and still you can claim copyright for it.
imtringued 2y ago
I like the concept, but honestly I don't see myself writing an entire webapp with this. Here is some feedback: There are a bunch of libraries that need to expose an http API. There is a niche for providing an embeddable http server that comes batteries included with all the features such as rate limiting, authentication, access control, etc. Things that constantly have to be reimplemented from scratch, but would not warrant adding a large framework by themselves. That's where I think the idea of a "WebDSL" would shine the most.
- williamcotton 2y ago
  Thank you for the feedback. I also don't see myself writing an entire webapp with this either - perhaps small sites or simple API endpoints? I was mainly scratching an itch I've had for a couple of years. I also really like tuning C code just for the fun of it!

https://github.com/williamcotton/webdsl https://github.com/williamcotton/webdsl Made almost entirely with Cursor and Claude 3.5 Sonnet. 11k lines of C and counting.

andix 2y ago

Thanks, that's exactly what I'm looking for.

thomasfromcdnjs 2y ago

I used Windsurf mostly on a feature to build out user authentication and then another tool to generate the PR documentation entirely. https://github.com/jsonresume/jsonresume.org/pull/176 https://github.com/jsonresume/jsonresume.org/pull/176 Meets my good enough standards fo sure

BeefWellington 2y ago

It's funny that this is MIT licensed, expecting credit for uncopyrightable work.

williamcotton 2y ago
I work in copyright law. Familiarize yourself with the AFC test concept and I'm willing to have a conversation about what would be copyrightable in this project of mine. https://en.wikipedia.org/wiki/Abstraction-Filtration-Comparison_test https://en.wikipedia.org/wiki/Abstraction-Filtration-Compari...
- BeefWellington 2y ago
  You misunderstand, the repo lists an MIT license which requires attribution. You want people to give you credit if they use this LLM-generated code. LLMs which were trained on the works of thousands of other developers with similar licenses, who are offered no similar credit here. It also claims copyright of the code as though you have authored it, but you're claiming here to have used LLMs to generate it. Seems like trying to have it both ways.
  - williamcotton 2y ago
    I want people to give me attribution for the parts of my project that are copyrightable. From the article, The second step is to remove from consideration aspects of the program which are not legally protectable by copyright. The analysis is done at each level of abstraction identified in the previous step. The court identifies three factors to consider during this step: elements dictated by efficiency, elements dictated by external factors, and elements taken from the public domain. This means that the code written for interfacing with an external API, eg, GitHub OAuth, would not be covered by any sort of copyright as the expression is dictated by requirements of the API itself. The overall structure and organization of the code was not generated by LLMs and is fully covered by copyright. LLMs are in fact very good at writing code that would probably not be copyrightable in the first place and are pretty bad at writing the overall expressive systems structures that would be covered by copyright.
    - BeefWellington 2y ago
      > I want people to give me attribution for the parts of my project that are copyrightable. A requirement not extended to the open source developers whose code you are using essentially a copyright and licensing laundering engine to get around.
      - deleted 2y ago
        [deleted]
      - deleted 2y ago
        [deleted]

gray_-_wolf 2y ago

What I find interesting is that the project claims MIT license, but if it is "almost entirely" AI generated, I am not sure it even is copyrightable. So either the licensing terms deserve some large disclaimers, or it is not "almost entirely" made with AI. Based on the name I assume it is your project, could you shed some light on which of those two options is correct?

williamcotton 2y ago
There are differing levels of abstraction when considering copyright.
andix 2y ago
I guess copyright laws treat AIs as tools. If you paint a picture with a brush it's also almost entirely "brush created", and still you can claim copyright for it.

imtringued 2y ago

I like the concept, but honestly I don't see myself writing an entire webapp with this. Here is some feedback: There are a bunch of libraries that need to expose an http API. There is a niche for providing an embeddable http server that comes batteries included with all the features such as rate limiting, authentication, access control, etc. Things that constantly have to be reimplemented from scratch, but would not warrant adding a large framework by themselves. That's where I think the idea of a "WebDSL" would shine the most.

williamcotton 2y ago
Thank you for the feedback. I also don't see myself writing an entire webapp with this either - perhaps small sites or simple API endpoints? I was mainly scratching an itch I've had for a couple of years. I also really like tuning C code just for the fun of it!