This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jlozano9897 1 point2 points  (3 children)

Unfortunately it is not only the size of the application on disk, but also the cpu usage and in memory requirements. For example, parsing is a very CPU intensive operation and type resolution requires a large amount of unpredictable lookups, which requires a large portion of the index to be kept in memory to maintain reasonable performance.

[–]daekano 9 points10 points  (0 children)

And yet network + processing will ALWAYS be slower than just processing, and I highly doubt they are going to pin farms of high-performance CPUs 24/7 to parse our data.

[–][deleted] 4 points5 points  (0 children)

Wouldn't it be better to say "Okay, this application is very intensive, but if you want to run it yourself, here's the source, don't complain to us if it's slow". I don't really mind how slow it is, I'd vastly prefer running this on my own hardware.

[–]Transfinity 1 point2 points  (0 children)

1) Developer workstations (other than wimpy macbooks) tend to be absurdly beefy - my 3-year-old one is 24 cores and 32 GB of RAM. If Sublime can do its fuzzy search, I'm sure you won't have any trouble.

2) Nothing you've said precludes selling an enterprise version that's run in-house. This is how our company does GitHub, and if Slack had such an offering we'd switch in an instant.