You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
The D language group has an article claiming programs with GC can be faster than manually managed ones at times (https://dlang.org/spec/garbage.html …). Does this only apply against programs doing RAII + ref counting, or is there no merit at all to this?
Everyone always says this. Java people said this and still do. They are always comparing against slow programs because they don’t really know what fast is.
Jon, you don't understand. Garbage collectors are faster because humans don't know all the secret opcodes that the GC and the CPU whisper to each other when humans aren't listening.
People are being ruled by their abstractions. They don't know what's in them, how they work, and can't say sensible things about them.
i was reading a thread recently where people were talking about all the weird workarounds they had to do to get UI stuff in unity to not cause huge GC spikes every few seconds and it just baffles me that people think its worth it.
my c++ UI stuff which I didnt even bother to optimize makes no dent whatsoever in my frame time
In that case, I'm glad nogc and betterC are becoming more well-supported for D...
John Carmack said something in 2013 about how you could do moving compaction on your mutable game state at the end of every frame (or maybe at the end of every few frames idk); would you consider that to be GC? And would it be fast?
In java memory allocation doesn't take time. Because, it takes memory from an already allocated block, i.e heap. Grabage collection is the slow part. And, java has different garbage collectors for different use cases. But, none of them can be used for real time apps like fortnit
Java garbage collection can take from few milliseconds to minutes during garbage collection. Garbage collection is one way or the other is a stop the world event, in java. That means "Your entire application is stopped, or you can say as good as hanged".
One of the biggest issue in java application in production is tuning your heap memory for minimum garabage collection and least amount of pause time.. Not to forget it crashes your entire application due to out of memory error. There are memory leaks in java, eg db connection.
java applications are not fast, they are just fast enough for most of the real world applications. I am a java developer, whenever I need something that's fast with low memory usage, I use rust for that. System programming languages with garbage collector is dumb.
I have been a java developer for 16 years and totally agree, it's fast enough for writing the backend of a web service, it shouldn't touch systems or games.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
