News for hackers. Stuff that matters.
Re:How we rolled out one of the largest Python 3 migrations by thijsvandien on Tuesday September 25, 2018 @03:22PM (#18069583)
Interesting write-up, though it leaves me terrified how a relatively small, more or less single purpose application like the Dropbox client has over 1 million lines of code in Python alone.
Re:How we rolled out one of the largest Python 3 migrations by fermienrico on Tuesday September 25, 2018 @04:49PM (#18070352)
I found the Dropbox lecture [1] at Stanford one of the most riveting things ever. There is just so much technology behind Dropbox, it is staggering.

There is a reason why it is so much better than iCloud sync, Google Drive, Box or OneDrive.

[1] https://www.youtube.com/watch?v=PE4gwstWhmc

Re:How we rolled out one of the largest Python 3 migrations by travbrack on Tuesday September 25, 2018 @11:19PM (#18072466)
This led me to find another loosely related but very entertaining piece of dropbox history. The original "Show HN" post: [1]. It's funny to see so much skepticism knowing now what the company became.

[1] https://news.ycombinator.com/item?id=8863

Re:How we rolled out one of the largest Python 3 migrations by billforsternz on Tuesday September 25, 2018 @11:44PM (#18072610)
Yes, this is one of the classics - right up there with the "less space than a Nomad, no wireless, lame" comment (which wasn't on HN I don't think - but we all know it could have been :)

Edit: I see the motherlode is in place earlier in the thread "Especially when you could build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem"

Re:How we rolled out one of the largest Python 3 migrations by anentropic on Wednesday September 26, 2018 @07:36AM (#18074836)
ha, that's a nice counterpart to the 'trivial' thread above https://news.ycombinator.com/item?id=18071820
Re:How we rolled out one of the largest Python 3 migrations by mixmastamyk on Wednesday September 26, 2018 @12:59AM (#18072899)
The iPod comment was from slashdot, if memory serves.
Re:How we rolled out one of the largest Python 3 migrations by wiredfool on Wednesday September 26, 2018 @06:42AM (#18074567)
Yes. CmdrTaco, when posting to the home page:

https://slashdot.org/story/01/10/23/1816257/Apple-releases-i...

(that post is old enough to vote in this year's election).

Re:How we rolled out one of the largest Python 3 migrations by chubot on Tuesday September 25, 2018 @07:20PM (#18071391)
You might only use a small part of Dropbox, but I bet there is a lot of functionality that you don't care about but which is critcial to Dropbox as a business/product for others.

The fact that you think it's small means they're probably doing something right!

Relevant: https://danluu.com/sounds-easy/

(FWIW I don't use Dropbox myself, but I definitely had people ask me why Google needed 3,000 employees back in the day. Apparently it now has nearly 90K employees.)

Re:How we rolled out one of the largest Python 3 migrations by carlmr on Wednesday September 26, 2018 @04:06AM (#18073779)
From the article

>There's also a wide body of research that's found that decreasing latency has a roughly linear effect on revenue over a pretty wide range of latencies for some businesses. Increasing performance also has the benefit of reducing costs.

I wish he cited some of that research, because Google doesn't show much except for this amazon study with the 100ms.

I'm especially interested if there's any research on engineering tools and their latency (long build times) etc., which are chronically under addressed in quite a few large corporations. I'm just wondering if there's some studies that would make the case for me if I were to present this to management.

Re:How we rolled out one of the largest Python 3 migrations by PascLeRasc on Tuesday September 25, 2018 @07:46PM (#18071521)
Especially when you could build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem!
Re:How we rolled out one of the largest Python 3 migrations by orf on Tuesday September 25, 2018 @09:06PM (#18071856)
Sarcasm doesn't translate well on the internet, so I'm really not sure if suggesting using CVS (of all things) over a mounted FTP share as a replacement for Dropbox is a joke!
Re:How we rolled out one of the largest Python 3 migrations by blerb795 on Tuesday September 25, 2018 @09:15PM (#18071897)
Re:How we rolled out one of the largest Python 3 migrations by zbentley on Tuesday September 25, 2018 @10:24PM (#18072214)
> Sarcasm doesn't translate well on the internet

Given what you're replying to, I'd say irony sure does.

Re:How we rolled out one of the largest Python 3 migrations by panic on Tuesday September 25, 2018 @05:46PM (#18070781)
The size of a codebase is less about its function and more about the number of people adding code to it.
Re:How we rolled out one of the largest Python 3 migrations by flukus on Tuesday September 25, 2018 @08:33PM (#18071704)
In turn this becomes the number of people required to maintain a codebase.
Re:How we rolled out one of the largest Python 3 migrations by thijsvandien on Tuesday September 25, 2018 @06:39PM (#18071155)
What would you consider the main cause(s) of that?
Re:How we rolled out one of the largest Python 3 migrations by panic on Tuesday September 25, 2018 @07:23PM (#18071407)
The job of a programmer is to write code, so that’s what they do. I doubt there are very many people at Dropbox whose job it is to remove code!
Re:How we rolled out one of the largest Python 3 migrations by maltalex on Tuesday September 25, 2018 @07:39PM (#18071488)
That’s an extremely narrow definition of a programmer’s job.

I think that in terms of lines if code, my contribution to many projects was net negative.

Re:How we rolled out one of the largest Python 3 migrations by icebraining on Wednesday September 26, 2018 @04:00PM (#18079684)
Re:How we rolled out one of the largest Python 3 migrations by MisterOctober on Tuesday September 25, 2018 @08:54PM (#18071808)
I dunno - refactoring often involves removal of a fair bit of code
Re:How we rolled out one of the largest Python 3 migrations by larrik on Tuesday September 25, 2018 @04:17PM (#18070128)
Dropbox doesn't feel that small or "single purpose" to me anymore.
Re:How we rolled out one of the largest Python 3 migrations by thijsvandien on Tuesday September 25, 2018 @06:28PM (#18071091)
What does the Dropbox client do for me other than syncing files and exposing a bit of the online functionality such as generating share links? (Serious question...)
Re:How we rolled out one of the largest Python 3 migrations by iscrewyou on Tuesday September 25, 2018 @06:38PM (#18071148)
We can simply start by asking what does “syncing files” include?

Watching files. Keeping backup of files. Keeping conflicts resolved. Watching Selective Sync files and folders. Watching Smart Sync files and folders. Notifications for synced files. Etc. etc.

There’s way more the client does than what I mention.

Re:How we rolled out one of the largest Python 3 migrations by PurpleRamen on Wednesday September 26, 2018 @02:22AM (#18073206)
I don't think there is much code for conflict-resolving in dropbox. Usually in case of conflicts it renames one of the involved files and add a message about conflict and the date to the name and moves on.
Re:How we rolled out one of the largest Python 3 migrations by varenc on Friday September 28, 2018 @06:58PM (#18097721)
Perhaps there's lots of code to minimize the number of times a real conflict occurs?
Re:How we rolled out one of the largest Python 3 migrations by thijsvandien on Tuesday September 25, 2018 @06:44PM (#18071183)
I agree that syncing is far from trivial, but that doesn't change it's a single purpose.
Re:How we rolled out one of the largest Python 3 migrations by kiriakasis on Tuesday September 25, 2018 @07:13PM (#18071354)
Not to build a straw man but by this logic also a browser is a single purpose application
Re:How we rolled out one of the largest Python 3 migrations by paulddraper on Tuesday September 25, 2018 @07:36PM (#18071477)
A rocket ship is also "single purpose."
Re:How we rolled out one of the largest Python 3 migrations by Marazan on Wednesday September 26, 2018 @03:59AM (#18073741)
It might be single purpose but that single purpose is a reallllllly difficult problem.
Re:How we rolled out one of the largest Python 3 migrations by _ZeD_ on Tuesday September 25, 2018 @11:41PM (#18072586)
You have no idea how web development is different from desktop one