[sephoric]

Greetings fellow hackers! Author of Autumn here!

I've been writing Autumn on and off for a few months, because there's something really satisfying and rewarding about automating something you do often, and then using that to automate more, and building upward in a cycle.

That, plus I wanted to see how close to building a "legit IDE" I could get while completely faking it with WKWebViews. So Autumn kind of grew from those two principles and I'm really happy with how it turned out.

I'd be glad to answer any questions, I'll be here for a few more hours. (I don't have internet at home so I use the library's wifi for stuff like this, and it closes early today.)

[snek]

I feel like tools like this, which are intended to be used by developers for their own personal use, will have trouble succeeding if they aren't oss.

It would be nice if the documentation was available without having to download this, so people could see what the API is like.

It would also be super duper epic if this supported ESM properly.

[sephoric]

Regarding ESM (ECMAScript modules), I did implement require() and module.exports to the best of my ability, so it should be pretty easy to modularize your scripts. But it doesn't have a Node.js runtime so I didn't focus too much on node_modules support, although in theory many packages should work fine.

Regarding online documentation, good idea, thanks! I'll try to add that this week. Although, the app is so much more than its API, which is what makes it so unique, and I think if people just look at the API itself, they don't quite get to feel the experience of using Autumn to create their own automation workflows, which is what I'm most proud of about Autumn.

[sephoric]

I have updated the website to include the full and complete documentation, I hope this will help you to know whether you want to try Autumn!

[sephoric]

Also, sorry for the terrible website. Web design is not my forte, I'm an app guy, and this was the quickest thing I could hack together in a couple days. Also I'm aware of the issues with the video demo, I'm uploading the file to YouTube so it should be fixed soon!

[kiliancs]

Nothing terrible about the website, in my opinion. It gets the job done without getting in your way. And you can always improve based on experience and feedback.

Things I noticed right a way:

- The logo and the title font. There's nothing wrong about them, but they don't reflect much about the application - Scrolling, there are a few elements that appear over the header bar

[tptacek]

This site is great. It's clean, easy to read, and looks professional.

It's hard for me to evaluate how useful this would be to my workflow without seeing the API, and it looks like I have to actually run the app to do that. It might be worth putting a copy on the website.

[sephoric]

Thank you for the advice, you're the second person to bring that up, and it seems like a fine idea, so I will do that this morning :)

[UPDATE] I have added the full and complete documentation to the website, which I hope will help you decide whether you'd like to try Autumn!

[zsprackett]

Chrome throws up a warning on download. Autumn.zip is not commonly downloaded and may be dangerous. Discard.

https://productforums.google.com/forum/#!topic/webmasters/pV...

[sephoric]

Whoa I got that too! I usually use Safari or Firefox (Google creeps me out) but I have tested the whole site in all three browsers, except this one button in Chrome I guess :D I'll check it out, thank you!

[sephoric]

> Uncommonly downloaded is applied to any download that is new or has been modified/updated until Google has a chance to examine the download using multiple data centers. Once the download has been examined enough times, the warning will be removed.

So apparently we just have to wait until Google's servers decide my app isn't dangerous. Ironic considering I paid the $100 for Apple to notarize the app through Developer ID to remove that same warning from macOS when you first launch the app!