Shaving 40% Off Google’s B-Tree Implementation with Go Generics

Re:Shaving 40% Off Google’s B-Tree Implementation with Go Ge... by Pannoniae on Tuesday September 19, 2023 @10:31PM (#37579775)

I didn't do it properly on purpose, because that wouldn't have been fair towards Go. Ultimately, many things which aren't even common yet today have already existed in the 70s.

I have picked 20 years specifically since it was around 2003-2005 when Java and C# got generics. Obviously, they were also more than 20 years late but I compared it to mainstream languages people are more likely to know about or more likely to compare it with.

I wanted to be fair and compare Go to some other mainstream languages which are big today, not niche ones.

[ Parent | on HN ]

Re:Shaving 40% Off Google’s B-Tree Implementation with Go Ge... by fooster on Tuesday September 19, 2023 @11:29PM (#37580091)

It’s so frustrating that every post on go brings out the same tired tropes. It just ruins any sensible discussion on any changes. Why do you do it? Are you trying to troll and actively make HN a worse place because that is for me what you are doing.

If you don’t like go don’t read the posts it’s not hard. Just stop.

[ Parent | on HN ]

Re:Shaving 40% Off Google’s B-Tree Implementation with Go Ge... by sharts on Wednesday September 20, 2023 @01:57AM (#37580841)

Aren’t you doing the same by replying to their comment?

[ Parent | on HN ]

Re:Shaving 40% Off Google’s B-Tree Implementation with Go Ge... by thfuran on Wednesday September 20, 2023 @04:09AM (#37581698)

How so?

[ Parent | on HN ]