[flagged]
[dead]
Formatting a 25M-line codebase overnight
11–20 of 115 posts
Re: Formatting a 25M-line codebase overnight
#12[flagged]
I’d hardly call Sorbet Ruby :)
Re: Formatting a 25M-line codebase overnight
#13[flagged]
The systems have to be written in some kind of programming language, and I think Ruby is a perfectly fine choice.
Not denying that Ruby is a perfectly fine choice but within the article itself it says that Stripe runs the world's largest Ruby codebase so certainly it might be testing the constraints of the language.
The thing I am interested is that I don't suppose that Stripe always had these many LOC's and so I would be curious to know if at any point as the codebase was increasing, were they looking at other new languages which were coming like golang or rust which was more suited for their work or not and what were there decisions/thinking process to continue using ruby.
Re: Formatting a 25M-line codebase overnight
#14[flagged]
This ought to change your mind about Ruby!
Re: Formatting a 25M-line codebase overnight
#15I’m shocked at the 25M line part! That is a completely unfathomable amount of code for one codebase. I really want to know more about that.
They're up to 42 million now, as per the article
That sounds even more insane to me, but I guess most of that code does not really touch financial transactions, otherwise it would be a nightmare being responsible to verify that.
Re: Formatting a 25M-line codebase overnight
#16Now it makes me wonder, are those 45M LoC are untyped ?
Re: Formatting a 25M-line codebase overnight
#17[flagged]
Things can always be worse. It could be PHP, for example.
Re: Formatting a 25M-line codebase overnight
#18Now it makes me wonder, are those 45M LoC are untyped ?
Re: Formatting a 25M-line codebase overnight
#19The floating spiral thing is so distracting I spent more time deleting it in Inspector than reading the article. I feel like they hate their readers. Awful.
Re: Formatting a 25M-line codebase overnight
#20One of my first jobs was a small software company writing software for a small number of clients, in MS basic PDS.
The lead developer didn't like to bother with formatting code, so I wrote a tool called makenice to format his nasty spaghetti gibberish into something with good indents and layout to make it easier for us normal people to parse.
He was furious, literally spun in circles about it right in the office in front of everyone, so I wrote makenasty to format code into the way he appeared to like.
I only shared makenasty/nice with a couple of the team, who loved it, as it allowed easy conversion between something readable and something the team lead like.
He never knew about makenasty.