Hey this looks cool but wanted to highlight a bug. I opened the bot, tapped on sample video and I got the “translating a sample Turkish drama…” message twice. Then it said “your first translation is ready” so I press view in the app and the recent list shows the duplication. It says the first one is ready but the second was in progress. I close the app and see a “our whale friend is gathering video” with a progress bar. So I guess it’s not ready? Then I get a failure message which looks like the second video failed? Anyway, cool idea but it seems buggy and I think the app UX could be simplified, good luck!
Because it's developed by JetBrains (with Google contributions), a company whose main business is writing really good IDEs. Apple on contrary is a hardware company that happens to build software. If they had delegated the XCode development to JetBrains, we would have had a great IDE for macOS/iOS development too. AppCode was damn good with zero support from Apple side, and despite the fact that JetBrains always needed to catch-up with Apple's breaking changes.
I've not found Android Studio to be particularly amazing for those kinds of features either. Sometimes they work, sometimes they half-work, and on occasion I've had them do the wrong thing entirely.
A lot of refactoring work across both platforms ends up being manual one way or another.
Subclasing and overriding is not a good idea. There is no compilation failure if you forget to override a function which can lead to flakey tests at best and prod data impact at worst.
Credentials should only be provided at the application root, which is going to be a different root for a test harness.
Mockito shouldn't change whether or not this is possible; the code shouldn't have the prod creds (or any external resource references) hard coded in the compiled bytecode.
I totally agree, I’m being tongue in cheek, but given how poor some codebases can be, the more precautions the better ie compilation failures on non-mocked functions.
reply