From another independent language developer, good luck to you. I know this may not feel constructive but I'm going to say it anyway: the name of the language is a huge turnoff for me. I try to avoid janky things and use the word as a pejorative. It isn't that different to me than naming the language crap.
I quit my job to work on my programming language
11–20 of 35 posts
Re: I quit my job to work on my programming language
#12From another independent language developer, good luck to you. I know this may not feel constructive but I'm going to say it anyway: the name of the language is a huge turnoff for me. I try to avoid janky things and use the word as a pejorative. It isn't that different to me than naming the language crap.
Re: I quit my job to work on my programming language
#13Giving up part time with benefits? Why? Surely those 15-20 hours per week don’t make a significant difference.
Previously, Mon->Wed nights and all of Thur->Sun would be for jank dev, since I felt like I didn't have enough time. Now I can focus a more normal Mon->Fri and more easily have space on the weekends to unwind and rejuvenate.
What could you do with 15-20 hours per week? A lot, I reckon'.
Re: I quit my job to work on my programming language
#14From another independent language developer, good luck to you. I know this may not feel constructive but I'm going to say it anyway: the name of the language is a huge turnoff for me. I try to avoid janky things and use the word as a pejorative. It isn't that different to me than naming the language crap.
Yeah. Jank sounds like Junk. OP should consider changing it into some short form like J.
Re: I quit my job to work on my programming language
#15I'll be blunt here, I see it as just a proloned phase. You wanted something, we all wanted that something at some point. You're not the only one who sees problems and thinks "it could be done differently, if", that's why you gather auditory. You'll end up realizing that no language can replace all these years, and that the amount of real useful work that could be done in that time with boring tools is mind-boggling compared to what will ever come out of this optimistically. Every new real job brings some new insight into what could make it less job-y and more fun. These problems never end and most solutions do not fit together. Feeling that something is not right and it could be done more is just part of the job. If you truly believe in it and have a reasonable source of financial stability, godspeed. But I think you might be living an illusion that almost every programming enthusiast had at some point.
Re: I quit my job to work on my programming language
#16From another independent language developer, good luck to you. I know this may not feel constructive but I'm going to say it anyway: the name of the language is a huge turnoff for me. I try to avoid janky things and use the word as a pejorative. It isn't that different to me than naming the language crap.
Re: I quit my job to work on my programming language
#17Are you going to build an engine in Jank after you release the language? I think you could do some really interesting things with server-side multiplayer in a clojure-y way.
Re: I quit my job to work on my programming language
#18From another independent language developer, good luck to you. I know this may not feel constructive but I'm going to say it anyway: the name of the language is a huge turnoff for me. I try to avoid janky things and use the word as a pejorative. It isn't that different to me than naming the language crap.
Like CockroachDB? Such names are memorable--you've already memorized it.
As far as I know, "jank" only has negative connotations, and a quick glance at the website did not provide an alternate interpretation of the name.
Also, if the author is looking for sponsors, some companies might be reluctant to be a proud sponsor of jank.
Re: I quit my job to work on my programming language
#19I love it. Send it! Are you going to build an engine in Jank after you release the language? I think you could do some really interesting things with server-side multiplayer in a clojure-y way.
Re: I quit my job to work on my programming language
#20I rewrote jank several times, during these eight years, with a different design each time, trying to find something which felt right. I wanted something I'll be blunt here, I see it as just a proloned phase. You wanted something , we all wanted that something at some point. You're not the only one who sees problems and thinks "it could be done differently, if", that's why you gather auditory. You'll end up realizing…