Thread with 15 posts
jump to expanded post
i do not like google's model of software development and its reckless reliance on CDNs, high-speed internet access and large disks. if dl.google.com ever goes down virtually all android apps will become impossible to build overnight and that should terrify everyone
the most bizarre thing is that you can't even invoke the build system for the first time without internet access, even if there's zero dependencies involved, but i have already screamed at length about how much i hate Gradle and will not repeat that now
retvrn to real sdks
HOW MANY FUCKING STAGES IN THE BUILD PROCESS NEED TO DOWNLOAD RANDOM ZIP FILES FROM DL DOT GOOGLE DOT COM DO YOU GUYS HAVE NO DISCIPLINE AT ALL ARE YOU ALL FUCKING INTELLIGENCE AGENCY PLANTS TRYING TO ENSURE THERE'S AS MANY BACKDOOR OPPORTUNITIES AS POSSIBLE
i am fine with package managers!! i am not opposed to package managers!! but the package manager should only be invoked exactly once! if you cannot even count the number of steps where some kind of package manager might download some kind of stuff something is very very wrong!
And on the pedestal, these words appear:
My name is Google, King of Platforms;
Look on my URLs, ye Mighty, and despair!
Nothing beside remains. Round the dead
Links to countless CDNs, boundless and bare
The lone and level ewastes stretch far away
@hikari I first have to compile my companies build tools before i can use them to build the library this app needs to build its own database schema management tool, and once they're all compiled, i can start running the tests
@EndlessMason @hikari look on the bright side. Our company has internal tools routinely sent around as exe files. You don't have to compile them in that case. :-)
@EndlessMason @hikari If only it were so simple. There is no official NTFS share where the tools are hosted. There are policies against that.
You have to find out about the tools by word of mouth. Then you have to ask where to get them. The answer is I don't know but I can send them to you. Then they send an exe that's been renamed .exxe and you are given instructions to rename it.
In the end everybody has a different exe stored locally. If it doesn't work, the support path is similar.
@EndlessMason @hikari They got rid of the wiki (that was originally hosted on my PC under my desk) because they didn't like that there was no access control. It was replaced by Confluence, which has text formatting capabilities that must share lineage with Microsoft Word's famous ability to adjust picture positions on a page.
But nobody posts .exxe files there, or even writes a description of the tools. Nobody wants a paper-trail proving that these .exxe based tools exist. Word of mouth only.
@EndlessMason @hikari I have an archive of the old wiki I made the day it was ported to Confluence. Mediawiki has a nice export feature. Clean user-facing export features are signs of honest software.
@poleguy @hikari
> Clean user-facing export features are signs of honest software.
There's a particular kind of UI-jank that screams that the applications UI is cut up into rental blocks, so 3rd parties can rent chunks of the screen from the vendor and charge you rent for a plugin that adds a button or a menu or working search or whatever else