VeryVito

I don't know what to tell you, but I use the tool and think others might find it useful. If an appraisal from a user isn't welcomed here -- or somehow makes you less inclined to use it -- then I'm not even sure this site is all about.

And you wonder why I haven't commented here in the past eight years.

Thanks! I have to admit that I wasn't able to make heads nor tails of Resterm. It may be above my pay grade.

I'm all for more text-based API docs tools, though, and from the README, Resterm does look well thought out and certainly capable! But it gave me flashbacks to my first days trying to learn Emacs.

Nope. I found the tool in a web search a few months ago, and I've been filing bug reports and keeping up with the project for the past few months. I knew they were open-sourcing it and announcing it here today, so yes, I wanted to put my two cents in.

You're right, I don't post much here (or anywhere these days, really), and knee-jerk accusations like this are part of the reason. But sometimes I like to share things I find useful with other developers. I certainly don't make a living doing so, though.

Enjoy your day!

> Overall, it appears this tool is in the same space as Postman, Insomina, etc. which has been plagued with rug-pulls and everything I've seen says it's likely to happen here too.

How so? Even without the tool itself, you've still got a collection of useful markdown files that perfectly describe your APIS. They're not magic nor proprietary, and now this tool makes them even more useful: If the developers are trying to rip anybody off, they're doing a terrible job.

This tool is for those who DON'T want to be locked into yet another cloud service: Its power lies in the formatted Markdown files which can be thought of us as a collection of souped-up `curl` statements that you may already be collecting anyway. This just lets you use them without copying and pasting them into yet another proprietary tool or platform -- and now that it's open-sourced, perhaps we'll see its magic spread to other tools, too. This format-over-product concept is ideal for development teams that already keep their projects in git repositories.

By open-sourcing the project, the creators have made the rug-pull scenario all but impossible (which is the point of today's announcement, I think). Regardless, it's in the wild now, and there's no pricing page because the tool is free and open source.

I read over this post before submitting and realize it sounds like I'm shilling here, but bear with me: I just REALLY like what Voiden is doing here, and I'm thrilled to see it open-sourced now.

Every other API-testing tool seems to have evolved into a bloated, cloud-first, subscription-based "service" (Yes, I'm looking at you, Postman, Paw/RapidAPI, etc), and I'd been looking for just this type of thing when I stumbled across this project a few months ago. Finally, somebody gets it!

It works different, and it may still have a few rough edges, but now every developer with access to our projects has access to the relevant APIs and instructions on how best to use them -- while the credentials remain safely off the cloud and on their own machines.

It's been exhilarating to finally have full testing and documentation right in our code bases, and the fact that it's now open source means our team can fully embrace Voiden without fear of once again having the rug pulled out from under its feet.

Thanks for going this route! I predict Voiden is going to be the sleeper hit for developers this year.

Honestly, the best way to see the advantages of the toolset is to complete the "Get started" section of flutter.io.

I develop iOS, Android, Web and Mac apps, and I was honestly blown away by the quality of the intelliJ and VSCode plugins available for Flutter. In fact, they've kinda ruined me for other language SDKs now.

Granted, the lack of material, demos and discussions makes it difficult to tackle some problems, but that seems to be changing these days. It's hard NOT to enjoy coding in Flutter, though, and I think that end up being its biggest strength.

Sweet Volvo 240.

I doubt there's a soccer mom in the world who didn't know this had happened already; my wife had been expecting it for months when it finally switched.

Other manufacturers are doing similar things. In fact, Trix Cereal has quietly switched away from artificial colors recently, and other General Mills "kids" cereals are expected to follow suit soon.

I always opt for open-source when available, but after having used JetBrains' PHPStorm for PHP/CSS/JS/etc, I can't even pretend Eclipse is still a viable solution.

Although the community version of IntelliJ at PHPStorm's core is open-sourced, PHPStorm itself is not. Regardless, the productivity gain it provides is WELL worth the cost and inconvenience.

I'm glad to see successful apps exiting The Mac App Store, and I hope others will follow. Unlike its iOS counterpart, which is great in many ways (new app discovery not being one of them), the MAS has unfortunately done more harm than good to the once-thriving indy Mac app-development scene.

It offers a low cost of entry, but also encourages "pump-and-dump" development, in which developers are actively (though surely not intentionally) discouraged from updating their apps once they launch.

It's designed to be the "anti-professional" means of app distribution, and it never reaches any higher.

This "study" seems flawed in so many ways (or the article describing it doesn't do it justice).

According to the article, the people who did not get a job were the ones who "indicated on their resumes they were cancer survivors AND WORE A HAT that read 'cancer survivor' when applying for a job."

NEWS FLASH: Wearing a novelty baseball cap to a job interview may not be the best idea -- cancer or not.

We have promo codes available, if anyone is interested. Reply here, and we'll get 'em to you. Thanks!

This is really nice, and it's great to see a non-Chrome version, too (working great in Firefox so far). Chrome often gets all the love (and is a great choice) for new dev tool extensions, but many of our clients -- for one reason or another -- can't/won't use Google's browser on intranet-based solutions. It's nice to be able to test/debug on more than one browser (Some of us still have to party like it's 1999).