austinmccoy6251

5 ms·

1.
by austinmccoy6251 4y ago
Great question! This does not require any dependency whatsoever -- adding comments and running the tool is sufficient. This was important, as our core mission is to ensure that integrating Artemis into your code does not require you to bend
2.
by austinmccoy6251 4y ago
Great suggestion! I am actively pushing to try to make small decisions like this to make it flow with one's current documentation format as much as possible. I will definitely add this to the to-do list.
3.
by austinmccoy6251 4y ago
These are some great suggestions! We definitely are excited to try to eventually branch out and allow people to configure the actual layout of their interface through some sort of nesting approach like the one you provided. Great idea!
4.
by austinmccoy6251 4y ago
Thank you! I appreciate the support! We're focusing hard on covering applications, languages, and challenges that lack coverage from existing products like Jupyter Notebook.
5.
by austinmccoy6251 4y ago
Yes! That's actually one of the primary motivations behind why we made this "comment-based." The caveat of course is that we presently only support Python at the moment, but you can expect to see C++ and Java support rolled
6.
by austinmccoy6251 4y ago
Thank you for the compliment! How funny! The inspiration for this project actually came from my work in a lab during my undergraduate work. Being constantly emailed mega-scripts with no context wears down the soul, haha. You can see traces
7.
by austinmccoy6251 4y ago
Thank you for taking a look at it! Great question! Funnily enough, we actually pursued this approach initially for the same reasoning you provided. I absolutely agree with your point regarding highlighting. However, we pivoted to using pure
8.
by austinmccoy6251 4y ago
Not to mention NASA's Artemis -- looks like we both have an uphill SEO battle ahead of us!
9.
Launch HN: Artemis (YC S22) – Use comments to give code an interactive interface
90 points by austinmccoy6251 4y ago|30 comments