Android BTFO

Based Apple

Other urls found in this thread:

coinbase.com/join/5a304f4aafa4460139b4b37d
github.com/apple/swift-evolution/blob/master/proposals/0004-remove-pre-post-inc-decrement.md
twitter.com/NSFWRedditImage

Garbage collecting > Reference counting

Reference counting never works with object oriented languages, because often you have to employ some pattern consisting of circular references through interfaces - in which case, you get memory leaks because the reference count never reaches zero.

> never reaches zer
wut???
> what are weak references?

*constantly overheats and thermal throttle*

> t. brainlet

hey it's that language that runs like shit unless you disable safety checks, generics, and managed references

Reference counting still isn't high development as garbage collectors.

And mark & sweep or generational garbage collection fixes that problem how?

Garbage collectors are kinda neat in that they can compact memory. Other schemes usually don't do anything like that.

On the other hand, garbage collection is stupid in how it has to traverse through all kinds of data structures to know whether something can be deallocated or not. With manual memory magement you just know in advance when you can free it, whereas the garbage collector may have to traverse through some linked list 100 times in vain during the lifetime of some program.

Garbage Collectors are literal garbage. That's one of the reasons Android performs like shit and has the worst memory management of any mainstrem OS.

It just werks

Swift is a good language. But whoever wrote the API are fucking idiots.

coinbase.com/join/5a304f4aafa4460139b4b37d

Which API are you talking about?

Kotlin native had ARC too.

My 6gb of ddr3 doesn't need this

github.com/apple/swift-evolution/blob/master/proposals/0004-remove-pre-post-inc-decrement.md

try again.

Java programming language is garbage too

...

>iBrainlets

>and has the worst memory management of any mainstrem OS.
I think you'll find that the app memory usage is actually quite reasonable.

makes perfect sense. ++ results in ugly code that doesn’t make sense for beginners.

Just use:
a += 1

It’s just 1 character longer, and makes much more sense

>It’s just 1 character longer, and makes much more sense

it makes no more sense than a++, fuck off shill

The two operations are not equivalent.
++ can be used inline.

Swift? That sounds like a language you wipe your ass with.

>> what are weak references?
Something that a programmer has to go out of their way to do. If you're using a library that doesn't do it internally when they should, you're completely SOL. It also means you end up relying on implementation details of classes you use, as you need to know whether you have to strongly or weakly reference a particular object in order to not get circular references.

Wow so you're saying Apple has invented a technology to automatically collect all the garbage that isn't being referenced anymore? Incredible!

Why doesn't it just throw itself out, then? Sounds like some shitty programming.

Isn't reference counting the least efficient way of garbage collection? Automic operations are quite expensive. Especially at language level.