"I consider garbage collection a last choice and an imperfect way of handling for resource management." #C++ bit.ly/17pQCxf
1
2
@ewolff "How do I deal with memory leaks? By writing code that doesn't have any." Pure, rhetorical genius. stroustrup.com/bs_faq2.html#…
1
1
@h_schreiber Without garbage collection it is easier to avoid memory leaks - as you are used to care about memory.... ;-)
2
@ewolff @h_schreiber he makes a good point in that GC is not the only alternative to the old-style C way of doing things (cf. RAII pattern)
1
@stilkov @h_schreiber I used to think GC was obviously better. Less errors. Some performance benefits. However, read bit.ly/1wfAA53
2
1
Replying to @ewolff
@ewolff @h_schreiber Very thoroughly researched article that misses the point completely :)

Feb 23, 2015 · 1:16 PM UTC

2
Replying to @stilkov
@stilkov @h_schreiber Misses the point in what way?
1
@ewolff @h_schreiber It assumes mobile web apps are 100% JS, and ignores HTML & CSS – basically DSLs for hardware-accelerated graphics
1
Replying to @stilkov
@stilkov @ewolff Hm. Has more to do with UI performance and less with memory management or related costs, like debugging and maintenance.