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...

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.

https://github.com/hmlongco/Builder

"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.

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.

Especially for people who can't be bothered to develop native applications.

Yeah, but we shouldn't have a double standard. If we could get an AI to reduce the number of deaths in half it would still be worthwhile.

Besides, non-fatal ACCIDENTS per mile are much more common, and we should be able to determine if those are reducing a lot faster.

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.

To them, thanks.

Writes an individual who strongly suggests Hugo and who just happens to create Hugo themes.

Dark patterns are tricks, like making you click on something that you thought did one thing but does something else. Asking you to sign in/up is hardly a dark pattern.

And I've yet to see Medium "fill the screen" with annoying banners. In fact, from what I've just seen, Medium just displayed a web page with the article's bottom half telling you you've read all of your free articles and asking you to sign up.

Too much hyperbole on the internet these days...

Started writing on Medium a year or so ago, mostly on Swift, RxSwift, SwiftUI, Combine, dependency injection, iOS application architecture, and so on. Will probably make $5-6K this year, which is a heck of lot more I ever made trying to monetize standalone blogs. And since it's cumulative I'll probably do better next year.

Probably the fact that while you listed your preferences you and most everyone else wouldn't bother to pay. Primarily since it would mean making a credit card transaction to an unknown site.

Your options are clearly biased towards the fact that you don't want really to pay anything, either in terms of money or ads/attention.

Took a quick look. If you want my take, your basic tutorials are, well... too basic. They describe fundamental language principles in a well-established programming language for which there's already a wealth of material available. Frankly, there's already a million articles and books that cover that.

IMHO, you need to write about some cool hot or esoteric feature that solves a specific problem in a new way. Or about how a particular crash bug ended being based on something that everyone else thinks works one way when in fact it works the other way.

Do a search on a topic. Are there already thousands of pages that cover the same thing? If so, write on something else.

Trust me. It's possible to do a lot better than $1.50 an article.

What's your solution?

Like it or not, websites cost money to run. The more popular they are, the more money it takes.

So... what? Spend your own money? Ads? Paywalls? Sell t-shirts? Try Patreon and hope enough people throw a dollar or two into your hat?

So you read some articles, and apparently find them useful... except for that fact that Medium would like you to... create an account????

OMG! The horror of it all. ;)

So... it's a "dark pattern" to give you access to some articles for free and then, should you like them and want to read more, ask you to pay for them?

IDK, but that seems pretty straightforward to me.

Conventional wisdom holds that we’ll see ARM-based Macs first on the low end… but what happens if high-end Macs running advanced Neural Engine chips are the real target?