Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Search your heart, do you think this story ends similarly if they decide to all do "modern C++" instead?

My guess is that even with initial discipline in the form of code review and style enforcement by one or two people, the C++ descends into a riot of different opinions about, as usual, which are the good bits.

A similar piece of software could be written in C++ but I doubt it gets written successfully, in similar time, by this team. I reckon the post mortem of such an attempt would be written off as "Don't do rewrites, duh"



This is an exceedingly silly conclusion. "Similar pieces of software" are coded in C++ and shipped every single day, without anyone saying "and we managed to do it in C++, too!" The emphasis should be on what the software does well, and how, not on what hoops the developers were jumped through on the way.


> Search your heart, do you think this story ends similarly if they decide to all do "modern C++" instead?

https://github.com/facebook/rocksdb


You might want to take that up with the authors of RocksDB and FAISS. They seem to have shipped some cool stuff.


RocksDB, as I understand it, is a pretty old piece of software, forked from a Google product, which was already a pretty old piece of software, all written in C++. Doesn't seem to have previously been written in Python, doesn't seem to have a team of non-C++ programmers who decided to just learn as they went, and so it's not clear what parallels you expect to draw.

Maybe they're doing a Rust rewrite too? I'd be interested to read about that.


> Search your heart, do you think this story ends similarly if they decide to all do

The main difference would be there wouldn't be a blog article on the front page. :)


> Search your heart, do you think this story ends similarly if they decide to all do "modern C++" instead?

It sounds to me they already had a good chunk of it written in C++ with python glueing it all together.

From a ‘dev velocity’ standpoint one would think having the senior devs learn a new language and rewrite an entire database wouldn’t make sense when they could just systematically replace the python parts with C++, which they already knew.

Or, who knows, maybe all their initial issues stemmed from the locations of semicolons around the else keyword?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: