Replying to
@RickiTarr@beige.party hell, I’ve vented about a problem, then realized in the middle that I’m the problem.
Remote
tjw
@tjw@haxe.social
akkoma 3.16.0Programmer, I really like Haxe and Rust but get stuck doing a lot of stuff in C++. I work on the @grig@haxe.social audio libs in Haxe.
🦀
Alt of @thomasjwebb@mastodon.social
🦀Alt of @thomasjwebb@mastodon.social
0 Followers
0 Following
13 Posts
pronouns:
they/them
codeberg:
github:
gitlab:
portfolio:
LinkedIn:
personal:
consulting company:
Replying to
I'm also researching ways of taking advantage of Claude where I'm not even using it to generate anything that gets checked in. If it's just doing research for me and code reviews, that might be better anyway. If this proves fruitful I could end up going more restrictive. As long as the above post is pinned, I will update it with any changes.
Now, to be clear, I am and have always been interested in serving the niche market that is musicians and the yet more niche market that is tools for people who want to get into music. But you have to have the “I already decided to ruin my life with music” mindset. If you’re expecting to pay off investors, proceed with caution.
The problem with getting trapped by dependence on a *heavily subsidized, obviously pre-enshittification* cloud service for your workflow is that not only can it increase friction for reverting back to your old workflow, it also could also make it more difficult to switch to something better that is yet to come. Even from the most pro-AI perspective, the current approach seems unlikely to be the best we can do. Our old instincts about avoiding vendor lock-in are more relevant than ever.
The rule I’ve always followed if I want to make my own software, I won’t even look at code that’s under a more restrictive license. There are many cases where it would have helped me to look at proprietary or copyleft code, but I refrained. Because whatever the law says, the intent of the original authors matter. When you release something copycenter, that’s an assurance to users of it that what they’re using or putting into their projects is safe to do so. If it’s even heavily inspired by anything not copycenter or public domain, then a fundamental contract with them is broken.
In some ways, the LLM is just a red herring with the whole chardet situation. If a long-term contributor to the GPLed project wrote something new by hand and contributed to the same repo, then it would be clear that they’re at least violating the spirit of the original project. Whether or not an agent is involved, it has to be a cleanroom reimplementation, which means someone else has to do it. There is a philosophical question of whether or not an LLM even can do cleanroom implementations and we’ll find out whether that’s possible from a legal perspective as soon as MIT-licensed clones of proprietary software lead to lawsuits.
But the open source community has never just been code. The persons behind the software matter. Pissing off copyleft people to appease corporate overlords and signalling that there are people in the OSS community who will stab you in the back will definitely harm the community and thereby the general public. In a time when tech companies are just getting more and more evil, OSS is more important and if unethical or antisocial behavior gets accepted, then everyone’s worse off.
I’ve always been more on the copycenter side of the divide, but the rule is we can’t be jerks to each other. That’s why I’ve always been careful about even the spirit of the copyleft licenses. Sometimes maintainers of copyleft projects will let you relicense part of it if you fucking ask. Being an asshole just encourages people to close ranks and see each other as the enemy. (Also think about how petty it is to attempt a relicense into copycenter when the original was already lGPL, admittedly kind of an odd license to choose for python, but probably compatible with non-copyleft projects).
I just hibernated my LinkedIn account. One of the better places to follow me for work/dev stuff is this account, on the fediverse as @tjw@haxe.social and on bsky at https://bsky.app/profile/tjw.haxe.social. Due to bugs on the Akkoma side, the account’s main handle isn’t tjw.haxe.social yet. Catch me at the #GDC next week!
I'm going to be at as many #GameAudioGDC events as I can this year. Hit me up if you're going to be at the GDC!
I just uploaded a livestream from last month onto youtube about making #Bitwig extensions (and eventually, extensions for other DAWs) in #haxe using my grig.controller lib and how to help improve it.
https://youtu.be/BBxYIquf7OU
https://youtu.be/BBxYIquf7OU
Replying to on haxe.social
I've also been meaning to ask. I pitch my voice up an octave to sound cartoony and match the aesthetic of my pngtuber avatar. Do you find it annoying?
Replying to on haxe.social
Oh and also one that I have to do:
- Migrate my fediverse instances to a new machine