don’t really have to be one to know how past reverse engineering cases have gone

oh nooooo whatever would we dooooo

not ones that involve pasting the gpl into files.

companies have been sued over using the same names for functions. this is absolutely not clean room.

what made it easier for me was to think of it as design by contract. if you start by describing the interfaces, you can basically autocomplete the functionality.

i wrote a driver for an i2c device in rust because i needed to sanity check my c implementation, and after defining the types of each register i wanted to use i could just ignore types entirely because it all became implicit.

not saying i particularly like how much magic there is in rust, just that i get it.

they brag about reimplementing software from companies they were laid off from with llms. llms are trained on shittons of source code both open and proprietary, which they are known to be able to regurgitate verbatim. also, if you’ve worked with a proprietary codebase at all, you can not be let even close to a reimplementation or it’s legally not clean-room, no matter how much you pinkie promise to not use any of what you learned at your former workplace.

these people wouldn’t know what a “clean-room” was if it swallowed them whole

need it to be a hierarchical thing? otherwise just cp -vur src/ dst/ >> files.txt && sort -bdufo files.txt files.txt and look in the file.

…yeeeees? that’s what i said that started this entire thread.

…compiled? it’s all written in x86-specific assembly language. you’d have to rewrite it from scratch.

source available != open source. unless explicitly rejected by the creator through a license or waiver, all the immaterial rights of any work still rest with them.

i get that it’s terry, but just saying “it’s open source” feels a lot like the “i declare bankruptcy” bit. he didn’t actually waive any rights there.

odd non-sequitur. is it still leaky?

https://opensource.org/blog/public-domain-is-not-open-source

preaching to the choir. useful for newbies though

yeah mit requires attribution, fair.

the entire reason the osi got started was because they (mainly esr) felt the gpl was too restrictive.

you can if it’s mit, cc0, or unlicense.

it’s a cult. i was more hoping it had gone.

• https://github.com/vlang/v/issues/35
• https://xeiaso.net/blog/v-vaporware-2019-06-23/
• https://xeiaso.net/blog/vlang-update-2020-06-17/
• https://n-skvortsov-1997.github.io/reviews/
• https://justinas.org/the-bizarre-world-of-v

public domain generally means you can’t relicense or copyright works using it. the osi doesn’t like that. the gpl is also not open source for the same reason.