Jump to page: 1 26  
Page
Thread overview
[Off-Topic] John Carmack's point of view on GC and languages like JavaScript
Aug 07, 2022
Paulo Pinto
Aug 07, 2022
ryuukk_
Aug 07, 2022
ryuukk_
Aug 08, 2022
Nicholas Wilson
Aug 08, 2022
Tejas
Aug 07, 2022
max haughton
Aug 07, 2022
ryuukk_
Aug 07, 2022
Paulo Pinto
Aug 07, 2022
ryuukk_
Aug 08, 2022
Don Allen
Aug 08, 2022
H. S. Teoh
Aug 09, 2022
Patrick Schluter
Aug 09, 2022
ryuukk_
Aug 09, 2022
max haughton
Aug 09, 2022
monkyyy
Aug 09, 2022
ryuukk_
Aug 10, 2022
Paulo Pinto
Aug 09, 2022
max haughton
Aug 10, 2022
monkyyy
Aug 10, 2022
max haughton
Aug 10, 2022
monkyyy
Aug 10, 2022
H. S. Teoh
Aug 10, 2022
monkyyy
Aug 10, 2022
H. S. Teoh
Aug 08, 2022
Meta
Aug 08, 2022
wjoe
Aug 08, 2022
Paul Backus
Aug 08, 2022
wjoe
Aug 08, 2022
Paul Backus
Aug 11, 2022
wjoe
Aug 10, 2022
Johan
Aug 08, 2022
ryuukk_
Aug 11, 2022
wjoe
Aug 11, 2022
rikki cattermole
Aug 11, 2022
wjoe
Aug 11, 2022
rikki cattermole
Aug 11, 2022
Don Allen
Aug 11, 2022
IGotD-
Aug 12, 2022
Paulo Pinto
Aug 08, 2022
Walter Bright
Aug 08, 2022
IGotD-
Aug 08, 2022
jmh530
Aug 08, 2022
IGotD-
Aug 14, 2022
Tejas
Aug 14, 2022
IGotD-
Aug 15, 2022
Walter Bright
Aug 08, 2022
Walter Bright
Aug 08, 2022
Ethan
Aug 09, 2022
rikki cattermole
Aug 09, 2022
Walter Bright
Aug 10, 2022
Jack Stouffer
Aug 10, 2022
Ethan
August 07, 2022

A bit off topic, but worth keeping as reference when someone complains about the GC,

John Carmack's answer regarding how he sees GC question on the Lex Fridman Podcast.

"It is only when you get into the tighest of the real time things that you start saying, no the GC is more cost than it has benefits for, but that is not 99.9+% of all software in the world..."

https://youtu.be/I845O57ZSy4?t=1370

He eventually follows up with a discussion he had about the matter on Twitter, and how some developers cannot let go of the good old days fighting for each byte.

He might know a thing or two about high performance code.

Maybe an interview to bookmark and post on the regular GC discussion threads, as pinned answer.

August 07, 2022

On Sunday, 7 August 2022 at 17:23:52 UTC, Paulo Pinto wrote:

>

A bit off topic, but worth keeping as reference when someone complains about the GC,

John Carmack's answer regarding how he sees GC question on the Lex Fridman Podcast.

"It is only when you get into the tighest of the real time things that you start saying, no the GC is more cost than it has benefits for, but that is not 99.9+% of all software in the world..."

https://youtu.be/I845O57ZSy4?t=1370

He eventually follows up with a discussion he had about the matter on Twitter, and how some developers cannot let go of the good old days fighting for each byte.

He might know a thing or two about high performance code.

Maybe an interview to bookmark and post on the regular GC discussion threads, as pinned answer.

That's kinda bullshit, it depends on the GC implementation

D's GC is not good for 99.99% "of all software in the world", it's wrong to say this, and is misleading

Java's ones are, because they offer multiple implementations that you can configure and the, they cover a wide range of use cases

D's GC is not the panacea, it's nice to have, but it's not something to brag about, specially when it STILL stop the world during collection, and is STILL not scalable

Go did it right by focusing on low latency, and parallelism, we should copy their GC

August 07, 2022

On Sunday, 7 August 2022 at 20:43:32 UTC, ryuukk_ wrote:

>

On Sunday, 7 August 2022 at 17:23:52 UTC, Paulo Pinto wrote:

>

A bit off topic, but worth keeping as reference when someone complains about the GC,

John Carmack's answer regarding how he sees GC question on the Lex Fridman Podcast.

"It is only when you get into the tighest of the real time things that you start saying, no the GC is more cost than it has benefits for, but that is not 99.9+% of all software in the world..."

https://youtu.be/I845O57ZSy4?t=1370

He eventually follows up with a discussion he had about the matter on Twitter, and how some developers cannot let go of the good old days fighting for each byte.

He might know a thing or two about high performance code.

Maybe an interview to bookmark and post on the regular GC discussion threads, as pinned answer.

That's kinda bullshit, it depends on the GC implementation

D's GC is not good for 99.99% "of all software in the world", it's wrong to say this, and is misleading

Java's ones are, because they offer multiple implementations that you can configure and the, they cover a wide range of use cases

D's GC is not the panacea, it's nice to have, but it's not something to brag about, specially when it STILL stop the world during collection, and is STILL not scalable

Go did it right by focusing on low latency, and parallelism, we should copy their GC

What we should promote more about D is the fact that

"GC is here when you need it, but you can also go raw when you need it, pragmatism allows D to be used for 99.9% of traditional softwares, but is also suitable for the remaining 0.1%"

And not just "We have a GC too, who needs to manage memory manually LOL"

August 07, 2022

On Sunday, 7 August 2022 at 20:43:32 UTC, ryuukk_ wrote:

>

On Sunday, 7 August 2022 at 17:23:52 UTC, Paulo Pinto wrote:

>

[...]

That's kinda bullshit, it depends on the GC implementation

D's GC is not good for 99.99% "of all software in the world", it's wrong to say this, and is misleading

Java's ones are, because they offer multiple implementations that you can configure and the, they cover a wide range of use cases

D's GC is not the panacea, it's nice to have, but it's not something to brag about, specially when it STILL stop the world during collection, and is STILL not scalable

Go did it right by focusing on low latency, and parallelism, we should copy their GC

It's actually 69.420% of all software in the world

August 07, 2022

On Sunday, 7 August 2022 at 21:17:50 UTC, max haughton wrote:

>

On Sunday, 7 August 2022 at 20:43:32 UTC, ryuukk_ wrote:

>

On Sunday, 7 August 2022 at 17:23:52 UTC, Paulo Pinto wrote:

>

[...]

That's kinda bullshit, it depends on the GC implementation

D's GC is not good for 99.99% "of all software in the world", it's wrong to say this, and is misleading

Java's ones are, because they offer multiple implementations that you can configure and the, they cover a wide range of use cases

D's GC is not the panacea, it's nice to have, but it's not something to brag about, specially when it STILL stop the world during collection, and is STILL not scalable

Go did it right by focusing on low latency, and parallelism, we should copy their GC

It's actually 69.420% of all software in the world

Exactly, hence why this quote is bullshit

But nobody wants to understand the problems anymore

https://discord.com/blog/why-discord-is-switching-from-go-to-rust

Let's miss every opportunities to catch market shares

August 07, 2022

On Sunday, 7 August 2022 at 21:25:57 UTC, ryuukk_ wrote:

>

On Sunday, 7 August 2022 at 21:17:50 UTC, max haughton wrote:

>

On Sunday, 7 August 2022 at 20:43:32 UTC, ryuukk_ wrote:

>

[...]

It's actually 69.420% of all software in the world

Exactly, hence why this quote is bullshit

But nobody wants to understand the problems anymore

https://discord.com/blog/why-discord-is-switching-from-go-to-rust

Let's miss every opportunities to catch market shares

Discord switched to Rust, because they wanted to work in cool new toys, that was the actual reason, while they use Electron for their "desktop" app.

Meanwhile companies ship production quality firmware for IoT secure keys written in Go.

August 07, 2022

On Sunday, 7 August 2022 at 22:39:24 UTC, Paulo Pinto wrote:

>

On Sunday, 7 August 2022 at 21:25:57 UTC, ryuukk_ wrote:

>

On Sunday, 7 August 2022 at 21:17:50 UTC, max haughton wrote:

>

On Sunday, 7 August 2022 at 20:43:32 UTC, ryuukk_ wrote:

>

[...]

It's actually 69.420% of all software in the world

Exactly, hence why this quote is bullshit

But nobody wants to understand the problems anymore

https://discord.com/blog/why-discord-is-switching-from-go-to-rust

Let's miss every opportunities to catch market shares

Discord switched to Rust, because they wanted to work in cool new toys, that was the actual reason, while they use Electron for their "desktop" app.

Meanwhile companies ship production quality firmware for IoT secure keys written in Go.

Or maybe they wanted to reduce the servers bill?

August 07, 2022
I expected Carmack's view to be practical and make perfect sense. I'm pleased to be right!

Anything he has to say about writing code is worth listening too.
August 07, 2022
On 8/7/2022 1:43 PM, ryuukk_ wrote:
> That's kinda bullshit, it depends on the GC implementation

I expect his opinions on the GC to reflect the implementations he's used, not ours.


> D's GC is not the panacea, it's nice to have, but it's not something to brag about, specially when it STILL stop the world during collection, and is STILL not scalable

Any implementation strategy is based on tradeoffs. D's are:

1. To run in mixed language instances, must work with C code with a frictionless interface.

2. To coexist peacefully with code that extensively use other allocation strategies

3. To have zero parasitic overhead

The requirements of Go and Java are quite different, which drives their different strategies.
August 08, 2022

On Sunday, 7 August 2022 at 20:48:02 UTC, ryuukk_ wrote:

>

On Sunday, 7 August 2022 at 20:43:32 UTC, ryuukk_ wrote:

>

That's kinda bullshit, it depends on the GC implementation

D's GC is not good for 99.99% "of all software in the world", it's wrong to say this, and is misleading

Java's ones are, because they offer multiple implementations that you can configure and the, they cover a wide range of use cases

D's GC is not the panacea, it's nice to have, but it's not something to brag about, specially when it STILL stop the world during collection, and is STILL not scalable

Go did it right by focusing on low latency, and parallelism, we should copy their GC

What we should promote more about D is the fact that

"GC is here when you need it, but you can also go raw when you need it, pragmatism allows D to be used for 99.9% of traditional softwares, but is also suitable for the remaining 0.1%"

And not just "We have a GC too, who needs to manage memory manually LOL"

You seem to be unaware that D does have more than one GC available.
Specifically, there is a fork based GC available for linux that is not stop-the-world, and is usable fro real time applications.

Perhaps we should advertise that more. Its only real downside is that it is linux only.

« First   ‹ Prev
1 2 3 4 5 6