#batman#dc#dc comics#bruce wayne#dick grayson#batfam#batfamily#tim drake#dc fanart
seen from United States
seen from Sri Lanka
seen from Germany
seen from United States
seen from Pakistan
seen from United States
seen from United States
seen from Germany
seen from United States
seen from Russia
seen from Australia
seen from United States
seen from France
seen from Italy
seen from Yemen
seen from United States
seen from Russia
seen from United States
seen from Canada
seen from Yemen
Oh for the love of pete...
Just discovered that there's a memory leak / crash bug in the editor. This shouldn't wait until I feel like fixing it weeks from now, so guess it's back to code for a bit...
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
I work at a place which uses a lot of tcl for scripting. Tcl is a language no one knows or cares about, for good reason (except python supports tkinter graphics, which use Tk, which is tcl).
A recent version of tcl decided to be all hip and add some functional programming concepts like a map function for lists, named lmap.
Except there's no lambdas.
So you just pass map a blob of code, and it executes it in a for loop in *your* stack frame.
Soo if you call map in your function foo, the little lambda has full access to foo's locals. Just for shits and giggles.
And why would you have a "filter" function when you have map? Just put a 'continue' in the body of your "lambda" and it'll skip that list value. Put a 'break' and it will stop the map.
And if you put a 'return' in your lambda, innocently, well, the calling function will return. That's right you can return from foo while inside a call to map.
And no one complains because tcl just never respects stack frames it pulls this sort of shit all over the place.
For bonus points, "return" actually takes multiple arguments: you can tell it how many stack frames up you want to jump.
The "fun" thing about reviewing and documenting your own code is that you'll occasionally find mistakes caused by small oversights or different portions of the code being made at different times.
So far I've removed like seven files and corrected a dozen little bugs that only existed in rare edge cases that nobody would think about.
To be blunt, this is more exhausting than coding the program in the first place.
Twenty one files done, forty six files to go.
You know what's worse than software by Apple?
Having to develop the code for iOS apps using said software.
It was supposed to be simple: port my work's native Android app onto iOS like we do for many of our apps. This one in particular delt with combining videos and overlaying chosen music over it. Our lead iOS developer had left and found a different job several months back, in retrospect that should've been a warning.
I'm the main Android app developer at our work and got assigned to get better at iOS development for this. But Apple, my fucking god Apple. It's not even a matter of different coding language, this is 100% an abusive relationship.
I need to learn that taking breaks is good because I struggled with something for 2 hours yesterday and I solved it in 3 minutes and half today
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
I've written some code and now I'm too afraid to test it because it took me 5 agonizing days to get to this conclusion ✌️
I know I'm doing a loooot of work by cleaning up the code to get ready to add functionalities but it's still annoying I can't see any progress in the app 😔
I swear figuring out testing an Android app is a bit like playing pillars of eternity 2 on console when you're walking in the city, you do one movement and then 4/5 minutes of wait. And I don't even have the cute elf to flirt with and a cool plot and world, just the pain
