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.
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?
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."
Then again, you can eliminate a lot of that boilerplate. I have a demo app up where I generate UIViews using resultBuillder such that you get a very SwiftUI-like experience using UIKit views.
"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.
I agree with interpol. There are always new info.plist privacy settings and the like that apps need to support. As I recall there were also some relatively recent TLS and https security requirements. Then there are things like dark mode support and... nevermind.
I'd turn the question around. Why wouldn't an Apple customer who buys a product expect it to be up to date, well-maintained, and reflect current best practices in security and privacy?
Saying that it's not convenient for the developer isn't a great answer to that question.
This is the main problem today. Good journalism costs money, and that money can come from ads, but that's usually not enough to pay the freight. Hence paywalls.
Or... it can be free.
But it also costs money to run a site. Especially if you're serving up millions of pages of content and images.
So... someone is paying the bills. The question is who, and why?
Bottom line is that "free" news either comes from someone selling you and your personal information, or it comes from someone with an agenda.
And that's the problem I spoke of earlier. You're either getting information from a recommendation engine designed to promote "engagement" and as such tends towards serving up controversy... or you're getting your information from someone with a specific agenda... which means they're feeding you what they want you to think.
I'm with aoleinik. A long time ago, in a galaxy far, far, away, I had a stand-alone blog that--to put it bluntly--no one visited.
Today I put the same type of content on Medium and get thousands of readers on almost each and every article. So much, in fact, that I've consistently been in the top 1,000 creators on Medium several months running.
Yes, I understand that I'm simply part of their platform. but that's the same for anyone who attempts to create monetized content on Medium, YouTube, Twitch, or any of the many other platforms that pay creators for content.
As far as I can tell, articles and sites like the one above exist because some people simply believe that they should never have to pay for content, and that everything should be free.
Fair enough. And, that being the case, those people are never going to see my work. Also fair.
But Medium drives enough people to my content to make the exchange work for me. Plus it provides enough incentive to get me off my butt and create things that I probably won't have created otherwise.
If anyone who reads this doesn't like Medium. Fine. If you want to go elsewhere... also fine.
But thus far, the value proposition works for me, and it apparently also works for all of the people who read my articles and stories and tutorials each and every day.
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.