250 karma · joined February 15, 2011
And you wonder why I haven't commented here in the past eight years.
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.
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!
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.
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.
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.
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.
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.
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.
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.
Only other nitpick: How many copies of Photoshop magazine does that apartment dweller need to own? ;)
Think of your web site as your business card -- it's how people get in touch with you once they've already been introduced; it seldom works as the introduction itself.
If you have a laptop and smartphone, chances are you don't "need" an iPad -- but once you figure out exactly what you CAN use it best for, it quickly becomes your "go to" device for certain tasks. I have all three within easy reach, but when I need ebooks, Facebook, Reddit or other leisurely entertainment, the iPad experience is far superior to that available on either of the other two devices. Meanwhile, my wife, who couldn't care less about Reddit or ebooks, finds it's the best platform for recipes, Pinterest, etc.
So yeah, developer's names, addresses and emails are not secrets by any means. Why would anyone buy an app from someone they had no means of identifying?
Why would the FIRE button be immune to a bug in the browser? Any chance this is a timing issue in your own code, rather than a bug in the browser?