Hi, I'm the author of the blog post. I didn't have any concerns about it doing things I didn't intend, because I was careful to review the diffs every time it made a change. There's a lot of hype about no-code AI app generators, and while that may work well some day, for now, I believe that these tools are most useful for maximizing the output of an experienced engineer who can understand the code being written by the model.
Thanks for taking the time to respond. I'm a decent enough programmer and have noticed weird, unnecessary code sometimes being added along the way as I've worked with AI during coding, so I was curious if you had any concerns about leaning on a tool that has the ability to write code that you might not understand. Sounds like you do not have that concern, and I'm glad it worked for you.
Specto is building a cloud-based mobile performance monitoring platform to power the next generation of performant mobile app experiences. We're hiring a senior Android engineer to lead the development of our Android SDK. You will be responsible for building state of the art technology for collecting and analyzing Android performance data from real user devices in production, and working with our most important customers to help them get the most out of the platform.
We're aware of performance issues with larger buddy lists (which tends to happen when Facebook accounts are connected) and an update will be submitted to the MAS soon that fixes this.
Hi there, I'm the developer of Flamingo. This is something that I considered during the development process but with the Mac App Store, sandboxing, and the overall difficulty of designing a good plugin API, this didn't make the cut for 1.0. Once things stabilize a bit I'll have more time to experiment with things like this. It's only 1.0 :)
When I first read the features, I assumed the Facebook/Hangouts and XMPP were essentially 3 different modules, which would probably make extending it to third party plugins fairly easy. But I realised that all of the services are XMPP at the moment, and therefore I suppose this would mean adding lots more abstraction to internal APIs and stuff.
I've heard about issues with sandboxing and plugins before, but as far as I can tell they are mostly for when plugins need access to the filesystem, as they have a different bundle ID and therefore don't get permissions from the main application? I might be completely wrong there though. As long as the plugins for Flamingo don't need filesystem access, or other privileged access, I would have thought it would be fine. RapidWeaver, for example, has a large plugin community, but is distributed on the App Store.
We're gauging the demand for a trial version at the moment and may decide to offer one if we find that many users are surprised by things not working as expected after purchasing the app (e.g. certain accounts not working, things that were unclear in the marketing, etc.)
To add a data point, I'm not going to give a chat app (a small utility, but an important one that I'd be willing to pay for) a second thought at $10 without a trial.
Echoing a third time - for any consideration on my machine, I'm going to need to take it for a test drive. $10 is non-trivial, and Adium is still more functional and already on my machine (oh, and free). I really do want to take your app for a drive, though. Please, please release a trial. Make it as short as three days - I'll use it enough to know if it's worth the money by then.
I'm the developer of Flamingo. There's understandably a lot of opinions on how exactly this should work, but we believe we made the best decision in removing something that most people rarely use to realize our vision for what a modern instant messaging client should be like. It's an opinionated decision, and we realize that many will not agree with it.
That's unfortunate. I know it's just one example but I was planning on recommending this to my company of several hundred people. But it's essential for people at a company, especially one with a lot of remote workers, to specify when they're away and when they might be back.
