Live data from Hacker News

Move tests to closed source repo

github.com

31–40 of 45 posts

Re: Move tests to closed source repo

#31
post #24

Whether this was a joke or a backtracking, or this dared waste your oh so precious time- You're missing the forest for the trees. There's extreme covert and even overt hostility between how people stand on AI's gluttonous usage of the commons. We're about to waltz into a deep period of tension between developers, and people who, empowered by multimillion dollars corporations, bravely violate developers' copyrights in…

Developers never had "intellectual property". Under capitalism, only billion-dollar corporations do. So the problem with AI isn't that it violated some license. The real problems are that people are losing jobs, that the Internet and our community gets clogged up with more low-effort slop competing for our attention than ever before, and that the products we are all forced to use are becoming worse because corporations are trying to shove AI-features into them and put quotas on engineers to vibe-code as much as possible. There are definitely others. "Copyright" is not even scratching the surface of real problems with LLMs, and many of the people leading the charge in pointing out the evil and hypocrisy of AI companies are themselves copyright abolitionists.

Re: Move tests to closed source repo

#32
post #11

This is interesting because it’s also one of SQLite’s monetizations. SQLite is in the public domain, but you need a commercial license to access their TH3 test harness with 100% branch coverage used to validate SQLite on different platforms.

This has always struck me as such a strange monetization strategy. Do they actually make money off this?

Re: Move tests to closed source repo

#33
post #18
post #8

Earlier quoted context omitted.

That's from this comment here: https://github.com/tldraw/tldraw/issues/8082#issuecomment-39... Well that's embarrassing! I reported it as if it wasn't a joke. I thought the joke issue was this one about translating everything to Chinese: https://github.com/tldraw/tldraw/issues/8092

If it was a joke (the test suite issue), then it was a really shit joke. It reads more like backtracking, I don't think _you_ should feel any embarrassment.

[deleted]

Re: Move tests to closed source repo

#34
post #27
post #21

Earlier quoted context omitted.

Entitled mentality.

Open source is a comittment. It is entitled of companies to grow developer user bases by promising that they will continue to provide their product to consumers and foster an open community, then pull the rug once openness no longer benefits them. The decision to go open source should less often be guided by financial reasons. It is foremost a social system of distributed labour and dependence.

It's not open source, before or after the (hypothetical) change.

Re: Move tests to closed source repo

#35
Why would they go to all the trouble of summarising the test counts in the context and writing out the full removal scope across two comment posts as a "joke"?

I'd believe it was a joke if was a one-liner but this has far more detail then that.

this issue was more of a joke (am I allowed to do that?)

Not really a fan of the qualification here to possibly scare people off from calling them out either.

To clear, I have no problem with them hiding the repo, I have no problem with them changing their mind after the blowback, but it's frustrating when they can't own these decisions and try to hide behind it being a "joke".

Re: Move tests to closed source repo

#36
post #11

This is interesting because it’s also one of SQLite’s monetizations. SQLite is in the public domain, but you need a commercial license to access their TH3 test harness with 100% branch coverage used to validate SQLite on different platforms.

This has always struck me as such a strange monetization strategy. Do they actually make money off this?

It works as a fork deterrent; forks can't easily prove they are still correct without the test suite, so if a company needs to tweak SQLite for any reason, they are better off paying for the tests so they know their tweaks won't break anything.

Re: Move tests to closed source repo

#37
post #35

Why would they go to all the trouble of summarising the test counts in the context and writing out the full removal scope across two comment posts as a "joke"? I'd believe it was a joke if was a one-liner but this has far more detail then that. this issue was more of a joke (am I allowed to do that?) Not really a fan of the qualification here to possibly scare people off from calling them out either. To clear, I have…

the issue was created by claude using this skill https://github.com/tldraw/tldraw/blob/main/.claude/skills/wr...

trust me this was never a serious proposal

Re: Move tests to closed source repo

#38
post #35

Why would they go to all the trouble of summarising the test counts in the context and writing out the full removal scope across two comment posts as a "joke"? I'd believe it was a joke if was a one-liner but this has far more detail then that. this issue was more of a joke (am I allowed to do that?) Not really a fan of the qualification here to possibly scare people off from calling them out either. To clear, I have…

[deleted]

Re: Move tests to closed source repo

#39
post #4

I'm thinking of migrating to ExcaliDraw or Xournal++ next time I need a whiteboard. The performative closing of public contributions citing the slop scare felt disingenuous from the start. You couldn't be bothered to implement _any_ mitigations that leave the community engaged with the project? Writing a contributor karma bot, moving to a non-social or obscure git forge (most slop contributors are resume farming and…

We're in chats with the GitHub team, they're taking it really seriously. I consider our pause on contributions similar to pi's open source vacation, we'll figure it out. https://github.com/badlogic/pi-mono/blob/main/packages/codin...

Re: Move tests to closed source repo

#40
post #8
post #5

Read the thread, it was a joke. "Sorry folks, this issue was more of a joke (am I allowed to do that?) but I'll keep the issue open since there's some discussion here."

That's from this comment here: https://github.com/tldraw/tldraw/issues/8082#issuecomment-39... Well that's embarrassing! I reported it as if it wasn't a joke. I thought the joke issue was this one about translating everything to Chinese: https://github.com/tldraw/tldraw/issues/8092

Sorry Simon, I honestly didn't expect this to be posted anywhere https://x.com/just_be_dev/status/2026419663505072195
Post reply on HN