hmlongco

Really? Did my toggling on an 8e that ran as a controller for a COM (Computer Output Microfilm) "printer".

Not saying that I could write code directly in octal... but I was pretty darn close. Of course, it helps when your assembly language consists of just eight instructions.

Things happen. But what I often tell people is that I'd probably be sitting in front of a computer anyway. Might as well get paid for it.

So honest question. I presume you spent months on those LC questions.

Do you feel that they were beneficial in terms of making you a better developer, or did you simply learn a bunch of solutions to puzzles that have no bearing on real world development?

I've been playing... (I mean, I've been) working with computers for decades.

My basic philosophy is that I'd probably be sitting in front of the silly thing anyway. Might as well be paid for it.

Weather changes. It's when enough weather changes that the overall climate changes where we begin to have issues.

Try reading for comprehension. The parent said, "You lucking out in which country you’re born in..."

You were lucky in that YOU were born in the US. Your parents could have lived in India. Or China. Or Chad. Or the Ukraine. Just so happens they lived in the US and, as a lucky consequence, you were born in the US.

But unless you're Native American your ancestors weren't born here. They were immigrants too. America is a huge multi-cultural melting pot spanning generations. 97% of the population are immigrants or the descendants of immigrants.

Getting tired of the folk that move in and then say, "Hey, I've got mine. Now it's time to close the door on everyone else."

Yeah, let's exclude the numbers for those over 70. Not like they're actually people or anything...

"Vendors accepting cryptocurrency can always choose their own level of risk by deciding how many blocks to wait before accepting a transaction. This allows them to "wait out" temporary attacks."

And introduces even more inefficiencies into the entire system as now we have to spend that time waiting for transactions to clear

Uhh... because I can see what was captured? If I'm overly concerned that a given callback might be held somewhere for all time I'll simply capture a weak reference and be done with it.

Umm... but isn't the refcounting GC more deterministic? If I create a chain of 10 object and then release the head, I run through 10 allocations and then 10 release cycles on those 10 objects. Period.

"No doubt straight up ARC with refcounting bumps on every function call,etc..."

Yeah, but in Swift you don't do that. From what I'm told, the compiler's static analysis has gotten a lot smarter in determining when a ref-count bump is needed, and the increased use of struct-based value types in the language leads more and more to situations where a refcount bump isn't needed at all since there's no object reference in the first place.

"it may not be the GC that's to blame, or not entirely: it's all the bloated crap they are pulling into the image"

Again, you keep waving your hands in the air and saying if you don't do that, you'll be fine.

Uh... I can solve entire batches of problems by just saying, "don't do that and you're good."

Unfortunately, real-world constraints always seem to get in the way...

"They're giving you 30 days' notice to show that you're still maintaining the app, and then it stays up."

Which would have been more than enough time... if the app had in fact been maintained.

And which doesn't change the fact that the developer agreement clearly states that apps must stay current and maintain compatibility.