Vyxal
Why Did You Join Vyxal? #1
Replies: 7 comments
-
|
a) What brought you into the language? b) What made you stay and use Vyxal for code golf? c) What made you switch from purely golfing to contributing code/information/ideas? |
Beta Was this translation helpful? Give feedback.
-
|
a) What brought you into the language? b) What made you stay and use Vyxal for code golf? c) What made you switch from purely golfing to contributing code/information/ideas? |
Beta Was this translation helpful? Give feedback.
-
|
TL;DR It's mainly the community. It's not too big, not too small, and quite helpful and friendly. a) What brought you into the language? I'm not sure how I was first introduced to Vyxal. Maybe I saw it mentioned somewhere as being easy to use? I think I then saw the documentation and was mildly annoyed that it was a text file. I converted it to Markdown (manually, with regex) and later made a Python script for doing that. That was my first contribution to Vyxal, and I didn't actually add anything more for a while. I did occasionally hang out in the chat room, though, because it was a somewhat nice place even back then, when there weren't as many active contributors. b) What made you stay and use Vyxal for code golf? When the rewrite happened, I really got into it because there were a lot of people around and it was fun working with others on a medium-sized project. I haven't actually worked on too many big projects, so it was nice getting to practice Git stuff, writing docs, reviewing PRs, writing tests, automating stuff. I think it's that that made me stay and contribute. Oh, and I was bored out of my mind last school year because it was virtual. Despite not using Vyxal much myself, I liked that it was a thing several people were working on and I liked occasionally implementing elements (lazylists are painful but it's so satisfying when you get a builtin working). I also wanted to help improve the tooling, because most golflangs are kinda lacking in that. At some point, Razetime linked to Stax in chat, and I think that was the first time I saw that a golfing language could be just as fancy as (or at least, somewhat close to) practical languages. I decided then that I wanted to make a debugger for Vyxal. c) What made you switch from purely golfing to contributing code/information/ideas? NA, I guess. |
Beta Was this translation helpful? Give feedback.
-
|
a) What brought you into the language? I joined because of the bounties. My first answer was pretty terrible (I wrote it like JS), but as I learned I improved. b) What made you stay and use Vyxal for code golf? I initially stayed because all my Vyxal answers seemed to get upvotes. I kept improving and eventually got to the point where writing stuff in Vyxal was easier than in other languages. c) What made you switch from purely golfing to contributing code/information/ideas? Found a bug and fixed it. Also TIL that I've created a quarter of Vyxal's issues |
Beta Was this translation helpful? Give feedback.
-
|
a) What brought you into the language? b) What made you stay and use Vyxal for code golf? c) What made you switch from purely golfing to contributing code/information/ideas? |
Beta Was this translation helpful? Give feedback.
-
|
a) What brought you into the language? b) What made you stay and use Vyxal for code golf? c) What made you switch from purely golfing to contributing code/information/ideas? |
Beta Was this translation helpful? Give feedback.
-
|
a) What brought you into the language? Partly the 5-answer bounty, and also I was seeing people answering in it, and once I tried it, and hey, it was cool. Also, I found that Jelly was quite hard to understand, and could never figure it out. And Vyxal was... readable. b) What made you stay and use Vyxal for code golf? Well... I liked the language. It was easy to learn, easy to read, and also, the the online interpreter was so awesome. I could just click stuff in the keyboard instead of having to copy from the docs, like in Jelly or 05AB1E. c) What made you switch from purely golfing to contributing code/information/ideas? Well, it started when these typos in the docs kept bugging me. I PRed. Then I found more typos. I PRed. And then... I found elements I wanted. I opened an issue. Someone added a label. And... well, it stayed quiet. So, I thought, well, let's see how bad the code is. To my surprise, it was quite easy to understand. So... well, I added an element. And... well, that's how it started. |
Beta Was this translation helpful? Give feedback.
-
Seeing as how I'm considering writing a blog post on how to manage community contributions and community expansion, I'm interested in knowing why you personally decided to come aboard this language and organisation.
More specifically:
a) What brought you into the language?
Was it the community ad? Or the 5-answer bounty? Language of the Month? Or was it just plain curiosity from exploring the ecosystem of code golf? What was it that you saw that led you here?
b) What made you stay and use Vyxal for code golf?
Anyone can investigate and look at a language, but it takes commitment and dedication to learn and use a new language. What convinced you to invest in getting to know Vyxal as a language?
c) What made you switch from purely golfing to contributing code/information/ideas?
Understanding a language and using it is hard enough. Wading into the code-base for that language is considerably harder, as you need to become familiar with the intricacies and styles of the code. As is coming up with innovative and cutting-edge ideas. What made you decide to start writing code or making other forms of community contribution?
Answer as many questions as you want, and feel free to add extra information that you want to share about your experience here.
Beta Was this translation helpful? Give feedback.
All reactions