gomobile: no Android NDK path is set. Please run gomobile init with the ndk-bundle installed through the Android SDK manager or with the -ndk flag set
Guess what I have done? Fuck you, Google, get your shit together…
After I had cleaned up that Android/Scamsung shit I managed to encounter another pile of shit produced by Go and its gomobile tool. Sigh…
@matigo The documentation says that the service stuff will be run in a worker thread, but apparently on this Android device it is run on the main thread. Yay. Not.
Either I have misunderstood how Android IntentServices are handled or then Samsung has done something fishy changes. Either way, now things should be running smoother.
@matigo I think the source of the vast majority of developer complaints is in messed up tool configurations. I know that people hold back upgrading the OS because some of their essential tools get broken. I would make a bold claim that the fault in those cases is with the tool, not the OS. But it’s easier to blame the OS than the beloved tool that breaks the OS conventions and practices.
@matigo Yep. I installed via Homebrew, which did say something about setting certain shell variables, but those were not enough. But apparently I don't need to deal with the Go part that much, so I can leave that for now.
@matigo I haven't played Go the board game, so I can't say anything about it. But Go the programming language was not the easiest to install, the instructions were very vague at the best.
Today's headache has been brought to me by Go1…
The programming language, not the board game.
Not a particularly efficient work day. But then again, the first day after a long break is always a hard one.
@matigo Never. But I need to work to get money with which I can buy food and stuff for the kiddos. And at the moment my work involves dealing with Scamsung shit.