If I may make an observation here: I think the vast majority of all programs benefit in productivity from a GC. In the sense, that the GC is an adequate solution at the least, and a more efficient solution in many cases, especially if you factor in development time. Managing memory manually, especially in concurrent settings, is going to take some attention to detail, and is likely to slow down how fast you can get a system working.
What you are likely to be looking at here is good old selection bias. The problems that doesn't fare well under a current generation of GCs are likely to bubble to the top of syndication sites, simply for the fact that they are interesting outliers. My experience, over the last, say 20-40 years, is that GCs are slowly eating more and more of the cake. As they improve, it definitely converges toward more viability, not less. There will always be programs for which they fare badly. But as they are detected, so are GCs improved. On Wed, Feb 12, 2020 at 4:11 PM Henrik Johansson <dahankz...@gmail.com> wrote: > Well, Cassandra has a rewrite in C++ ScyllaDB hat performs many times > better so that particular example isn't really helping the GC case. > > I don't mind the GC myself but I hear the "GC is actually faster" often > and it seems not to be true in the wild although I am sure theoretical > cases can be envisioned. > > On Wed, 12 Feb 2020, 16:06 Kevin Chadwick, <m8il1i...@gmail.com> wrote: > >> On 2020-02-12 14:02, Robert Engels wrote: >> > Most of that is because their codebase predates Java. There are more >> modern dbs >> > like Cassandra that are in Java. Certainly Hadoop is probably the >> largest >> > distributed database in the world and it’s written in Java. >> >> Bound to use more cpu cycles and memory than a c equivalent. Of course >> postgres >> is more capable. >> >> >> https://blog.timescale.com/blog/time-series-data-cassandra-vs-timescaledb-postgresql-7c2cc50a89ce/ >> >> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golang-nuts+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/f388606c-7f52-78bc-f59c-776688114e4f%40gmail.com >> . >> > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/CAKOF695amjn_FvHrh1S2x41knXOQ9Dq-yX2%2Bfh5jDL_dDJenaA%40mail.gmail.com > <https://groups.google.com/d/msgid/golang-nuts/CAKOF695amjn_FvHrh1S2x41knXOQ9Dq-yX2%2Bfh5jDL_dDJenaA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- J. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAGrdgiWTDKpdX3tMAecRf770YWDsFHbvjY%2BTcMAxQ5A3LZMe6w%40mail.gmail.com.
