tumblr dot com
Three Goblin Art
KIROKAZE
h

@theartofmadeline
Not today Justin

祝日 / Permanent Vacation
2025 on Tumblr: Trends That Defined the Year

★
i don't do bad sauce passes

#extradirty

titsay
"I'm Dorothy Gale from Kansas"

roma★
Mike Driver
Show & Tell

tannertan36
Stranger Things
One Nice Bug Per Day
Lint Roller? I Barely Know Her

seen from Ireland

seen from Canada

seen from Malaysia

seen from Malaysia
seen from Canada
seen from Austria
seen from Germany
seen from Italy

seen from Taiwan
seen from United States

seen from United States
seen from Germany

seen from Malaysia

seen from Malaysia
seen from United States
seen from Italy
seen from United States
seen from Italy
seen from Germany

seen from United States
@entangledloops
PALM BEACH GARDENS, FL—Saying it provides a pleasant and rewarding diversion from the quietness of living alone, local grandmother Rosemary Burke confirmed Wednesday that she has been enjoying a thriving correspondence with Mailer-Daemon.
No more pre-installed 3rd-party apps, please! IMHO, amongst the worst are the android apps that can't be installed.
How it feels to work on phone-related code.
“Configuration on demand is an incubating feature.”
Or as I like to call it, pretentious beta.
Do we really need to keep reinventing new phrases for old concepts? Doesn’t gradle already set the entry barrier high enough without needing this kind of language to confuse everyone?
Ugh. Talk about putting the BS in build system.
The more I use gradle, the more I feel inducted into an API-cult with the sole intent to drive all users slowly (but just tolerably slowly) insane while consuming their harddrives. Off the top of my head:
Constantly changing buildscript configurations (see the confusing history and use of the Android plugin, or the gradle plugin concept in general)
More and more blackbox behavior accompanied by a debug log so thick I’d need to invest my weekend into reading and parsing it (and a month into the accompanying documentation)
Half of the useful examples exist spread across StackOverflow instead of in the documentation (or don’t exist). Also, half the time I find a properly behaving solution, it’s barely received any praise or has negative reputation---because it’s often unreadable, to minimal fault of the author.
Complex examples of real-world behavior mostly missing. Even the “not-simplest-possible-example” is often absent and leaving me frustrated. Granted, nobody has time to write an example for everything, but often gradle outlines difficult semantics and doesn’t follow through, like task overwriting or dynamic task name generation (docs are soooo weak).
Useful examples are unreadable. Take this gem for example, which logs everything somewhere useful. It’s absolutely hideous.
And I still use it because it’s a fundamentally good idea...but come on.
I could go on, but enough ink and effort on my part has been spilled on account of gradle already today alone.
Okay, I’m tired and a being a little pessimistic here, but anyone I’ve met who’s put the real time into gradle like I have has a long list of their own complaints. Gradle developers: let’s try some more planning-phase, or at least community polling for how we’d like certain things handled before pulling the rug out beneath us.
I still hold deep hopes that something like the following is relevant:
systemd vs gradle
Your guess as to which project consumes the other’s scope first is as good as mine.
I love you, so you can’t die, Google Wallet!
Cue solemn music as I make the final transfer…*sniffle*….
Google RSS reader, Google answers, Google code, Google labs, and now THIS?
What’s next, Google search?
Favorite Line of the Day
“This section explains and lists the Video API as it was available when this document is written.”
Seems to imply the documentation is never updated, or that the code and the API are not synchronized? (Kidding.)
Found in the pjsip API: https://trac.pjsip.org/repos/wiki/Video_Users_Guide
A sample app should not be 10.4k lines and broken up into 3 levels of hierarchy. That is exactly what the Amazon Voice Service sample is. Plus the services.
Tim Harris (developer, SetemTech)
The reason gradle drives me insane: it should not take 44 chapters to reach this point.
Sneaky runtime quirks
Latest stable android doesn’t implement Float.isFinite(), but if you use an IDE such as IntelliJ and have a project sdk set to a Java 1.8 JDK in a multi-project build (with android sdk set appropriately for that module), it will happily build, dex, and generate an APK that produces unexpected behavior. This is also true if you run retrolambda on the project to get 1.7 comparability. Figured it out when I set the whole project to build against Android as an experiment. No crash to indicate failure, just spurious return values of “true” when the float is set to positive infinity. Thanks, Obama!
Reason for the exception java.lang.VerifyError: Bad type on operand stack
Encountered this gem today. It produces a hideous runtime crash from the JVM indicating something about mis-compiled bytecode.
Turns out the cause was a non-static inner class that calls super() passing along a Runnable. There isn’t anything inherently wrong with the practice, but the Runnable referred to enclosing class members! Before super() completes, the instance doesn’t exist, and therefore has no access to the enclosing this pointer.
Solution:
Provide a member function to accept the Runnable after super() is called, don’t refer to enclosing members, receive the necessary members as parameters to the inner class constructor, and/or carefully use a custom workaround (like static vars or a FunctionalInterface to substitute for Runnable that can handle the situation.)