3 ms·

Starting to pretty much desire tools that can do nothing but are just fast at their core competency. Looking at PRs in github and then when toggling to the "fi

Starting to pretty much desire tools that can do nothing but are just fast at their core competency. Looking at PRs in github and then when toggling to the "files" tab it chocking up or being like "I don't want to display this file because its more than 100 lines" is like wtf you're whole point is to show me modified files.

FredPret 1y ago
Like the Unix philosophy, but for businesses. Come to think of it, this might be great advice for life in general: do one thing very well, and be modular (aka play well with others)
- Analemma_ 1y ago
  I wish the world worked this way, but I don't think it does, especially in tech. If you "do one thing well", the cloud hyperscalers will use their billions to copy whatever that is, and add your "one good thing" into their bundled subscriptions or cloud plans. At which point, any rational CTO will go "why should we pay for this, when we're already getting it via AWS/O365/whatever, and with better integration with our existing tooling to boot?" I don't think "do one thing well" can succeed in this world, which is why Atlassian, Dropbox, etc. keep on launching things like office suites even though that makes no sense considering their core competencies. It's the only way not be streamrolled by FAANG.
  - MoreQARespect 1y ago
    It works with Keiretsu. Ive long thought that this is how Europe should play catch up and build its own equivalent(s) of AWS, GCP and Azure.
    - FredPret 1y ago
      I've seen it mentioned in the context of smaller countries competing with the big guys using industrial policy, and one example mentioned in that article (I don't have a link - it was long ago) they specifically mention Sweden and Volvo.
agloe_dreams 1y ago
I'm about to sound crazy. Github's problem is that it isn't a SPA. It is a massive Ruby on rails project that is all server-rendered. Everything you do needs to be synchronous and almost everything requires a reload. A react or angular app with great restraint would be dramatically faster at all of this as viewing a file is just an API call - not a page reload. They are stuck with their hands tied as loading large data would cause the whole page load to be delayed - thus silly limits. Many things should not be webapps... but an app on the web like this...probably should.
- lpapez 1y ago
  You can have parts of the web app rendered on the client, and still keep the rest of the app the same. Rewrite the diffs and previews, keep the rest as-is. There is no excuse for possibly the most used feature of Github to suck so badly.
- cyrilou242 1y ago
  > Everything you do needs to be synchronous and almost everything requires a reload. this is pretty incorrect, you may want to look into the concept of "partials" in SSR. maybe you meant everything requires a roundtrip ? but SPA would not solve most of the roundtrips necessary in github given many interactions in the github app require authn/authz checks. would you care getting into more details ? Also, 'old' github was known to be very fast an reliable and was indeed a ruby on rails SSR app. Since a few years ago github started to introduce react and more client side logic and it correlates with more issues and more slowness in the frontend. It only correlates, but still.
kirici 1y ago
I am increasingly in favor of inspecting/diffing branches from MRs locally.
- raxxorraxor 1y ago
  We use so many cloud services and SaaS products that it will be quite a shock how fast systems can be. You don't even need to use a local service, just hook up a minimal server somewhere that pulls from slow services here and there. Technically cloud, but not as shitty. I think modern wait times are crushing for productivity, it is really demotivating and wears you down. Either just skip to another task and get overwhelmed by context switches or you wait and degenerate to a non-thinking troglodyte.

FredPret 1y ago

Like the Unix philosophy, but for businesses. Come to think of it, this might be great advice for life in general: do one thing very well, and be modular (aka play well with others)

Analemma_ 1y ago
I wish the world worked this way, but I don't think it does, especially in tech. If you "do one thing well", the cloud hyperscalers will use their billions to copy whatever that is, and add your "one good thing" into their bundled subscriptions or cloud plans. At which point, any rational CTO will go "why should we pay for this, when we're already getting it via AWS/O365/whatever, and with better integration with our existing tooling to boot?" I don't think "do one thing well" can succeed in this world, which is why Atlassian, Dropbox, etc. keep on launching things like office suites even though that makes no sense considering their core competencies. It's the only way not be streamrolled by FAANG.
- MoreQARespect 1y ago
  It works with Keiretsu. Ive long thought that this is how Europe should play catch up and build its own equivalent(s) of AWS, GCP and Azure.
  - FredPret 1y ago
    I've seen it mentioned in the context of smaller countries competing with the big guys using industrial policy, and one example mentioned in that article (I don't have a link - it was long ago) they specifically mention Sweden and Volvo.

agloe_dreams 1y ago

I'm about to sound crazy. Github's problem is that it isn't a SPA. It is a massive Ruby on rails project that is all server-rendered. Everything you do needs to be synchronous and almost everything requires a reload. A react or angular app with great restraint would be dramatically faster at all of this as viewing a file is just an API call - not a page reload. They are stuck with their hands tied as loading large data would cause the whole page load to be delayed - thus silly limits. Many things should not be webapps... but an app on the web like this...probably should.

lpapez 1y ago
You can have parts of the web app rendered on the client, and still keep the rest of the app the same. Rewrite the diffs and previews, keep the rest as-is. There is no excuse for possibly the most used feature of Github to suck so badly.
cyrilou242 1y ago
> Everything you do needs to be synchronous and almost everything requires a reload. this is pretty incorrect, you may want to look into the concept of "partials" in SSR. maybe you meant everything requires a roundtrip ? but SPA would not solve most of the roundtrips necessary in github given many interactions in the github app require authn/authz checks. would you care getting into more details ? Also, 'old' github was known to be very fast an reliable and was indeed a ruby on rails SSR app. Since a few years ago github started to introduce react and more client side logic and it correlates with more issues and more slowness in the frontend. It only correlates, but still.

kirici 1y ago

I am increasingly in favor of inspecting/diffing branches from MRs locally.

raxxorraxor 1y ago
We use so many cloud services and SaaS products that it will be quite a shock how fast systems can be. You don't even need to use a local service, just hook up a minimal server somewhere that pulls from slow services here and there. Technically cloud, but not as shitty. I think modern wait times are crushing for productivity, it is really demotivating and wears you down. Either just skip to another task and get overwhelmed by context switches or you wait and degenerate to a non-thinking troglodyte.