justin = {
main feed
,
music
,
code
= {
cockos
,
reaper
,
wdl
,
ninjam
,
jsfx
,
more
}
,
askjf
,
pubkey
};
Ask Justin Frankel
No reasonable question unanswered since 2009!
Suggested topics: programming, music, sleep, coffee, etc.
Note: please do not ask questions about REAPER features, bugs or scheduling, use the
forums
instead.
Name:
Ask:
Human (enter yes):
[
back to index
] | [
unreplied
] | [
replied
] | [
recent comments
] | [
all
]
Question:
What’s one design decision or technical problem in REAPER that users probably take for granted, but that you’re personally most proud of solving? Oh, and thank you for all your hard work and for keeping such a down-to-earth attitude while building something so nice.
Asked by shrike (145.53.x.y) on September 17 2026, 10:10am
Reply on September 17 2026, 3:08pm:
There have been a ton of challenges over the last 20+ years where you spend a ton of time figuring out a solution to a difficult problem, and you're really satisfied with it, and then a week after it ships and there's no egg-on-face moment, you forget about it and move on to the next things, and you yourself take it for granted!
Comments:
Posted by shrike (145.53.x.y) on September 17 2026, 4:13pm:
Yeah, that's great. I can only imagine how complex it can get sometimes. I bet putting out the releases is at least a little nerve wracking when handling for difficult problems is added. I am really impressed just how much backward compatibility you guys must have been carrying around. And how everything is still so snappy despite all that!
Posted by Mespotine (82.135.x.y) on September 17 2026, 4:56pm:
Do you have some strategies for how you develop to prevent yourself from "painting yourself into the corner" codewise? Or is it something you do intuitively nowadays with so much experience?
Comment:
Your Name:
-- Site Owner's Name:
(for human-verification) Comment:
[
back to index
] | [
unreplied
] | [
replied
] | [
recent comments
] | [
all
]
Copyright 2026 Justin Frankel
.
|
RSS