to_the_sun

is-it-ok-to-use-cyclings-abstractions-in-projects-i-plan-to-sell-later

If it isn't ok with Cycling74 to use their abstractions, I will hurt them for you O_o

(just kidding, i only said that because i'm a coward who already knows it's ok and it makes me feel brave to post idle threats)

If it isn't ok with Cycling74 to use their abstractions, I will hurt them for you O_o
(just kidding, i only said that because i'm a coward who already knows it's ok and it makes me feel brave to post idle threats)


Very good very good. I just keep finding new reasons to love Max

oh wait, sorry! i shouldn't be so blanketly humorous...

you would want to check for copyright notices and licenses... in the js code itself it has a copyright notice with jeremy's email... so in this case, i'd recommend emailing him or cycling to get permission(but generally speaking about object-only 'abstractions', things like 'grooveduck' for example, should be ok).

Because there's no reason to reinvent the wheel.

I swear, if I had to re-write m4l.bal2~ and all that shit then I'd ragequit so hard.

Because there's no reason to reinvent the wheel. 

I swear, if I had to re-write m4l.bal2~ and all that shit then I'd ragequit so hard.


(hehe, if it were me, i'd write my own as well: i'd rewrite the code line by line if i had to, learn each line, then see what i could change to make it my own... if i were to sell something which utilized it, making my own would also make me the most familiar with it i could be, and would ensure that i could actually offer proper support/fixes to that same code. there's a strange sense of loyalty i'm trying to describe here that ensues as a result... not just from customers because they can trust you know what you're doing, not just your loyalty to the product either, but rather... loyalty from the code itself: my own stuff works more predictably for me than other people's stuff, even when my stuff is buggy and their stuff is bug-free, there's more freedom and integrity when i travel right here on my own two feet than from there, standing on their shoulders...

nah, screw it, i failed yet again to describe what i'm trying to say, heeheEE!... ;p)

(hehe, if it were me, i'd write my own as well: i'd rewrite the code line by line if i had to, learn each line, then see what i could change to make it my own... if i were to sell something which utilized it, making my own would also make me the most familiar with it i could be, and would ensure that i could actually offer proper support/fixes to that same code. there's a strange sense of loyalty i'm trying to describe here that ensues as a result... not just from customers because they can trust you know what you're doing, not just your loyalty to the product either, but rather... loyalty from the code itself: my own stuff works more predictably for me than other people's stuff, even when my stuff is buggy and their stuff is bug-free, there's more freedom and integrity when i travel right here on my own two feet than from there, standing on their shoulders...
nah, screw it, i failed yet again to describe what i'm trying to say, heeheEE!... ;p)


excuse my ignorance, but if you write your own you can make it better, then it is like inventing a new wheel.

btw, first of all, if you write your owwn, it is easier to remember its name!

(my highly busy supervisors might chastise me for reinventing the wheel instead of downloading and re-purposing an existing one. But I share in that boundless joy and freedom and creativity and pride and exploration that re-imagining the wheel brings, of which raja speaks. In my own humble experiments. When I can be bothered and have the time).

"In my own humble experiments. When I can be bothered and have the time"

I agree. Those would all three be indicators of a "NON-commercial" project, like, not for a client or some such.

to me time is most important, including the long-run, and in the long-run, rolling my own makes it faster for me to think in general mathematical terms for other things too... but rolling my own also includes studying other people's stuff very carefully. (we also live embedded in capitalism everywhere, so there is 'competition' to think about: learning from other people's stuff well enough to roll your own keeps you that closer to staying ahead of the competition...

but most of all, hehe, if i die, i can't take max with me, so i'd rather my soul did remember the math,

muaahaahahaAHAHAAHAHAAH*cough* *wheeeeze* heeehaa- *cough* haHA! >;D)

but also for the commercial realm too:
to me time is most important, including the long-run, and in the long-run, rolling my own makes it faster for me to think in general mathematical terms for other things too... but rolling my own also includes studying other people's stuff very carefully. (we also live embedded in capitalism everywhere, so there is 'competition' to think about: learning from other people's stuff well enough to roll your own keeps you that closer to staying ahead of the competition...
but most of all, hehe, if i die, i can't take max with me, so i'd rather my soul did remember the math,
 muaahaahahaAHAHAAHAHAAH*cough* *wheeeeze* heeehaa- *cough* haHA! >;D)


Is it ok to use Cycling's abstractions in projects i plan to sell later?