Live data from Hacker News

Fast

patrickcollison.com

191–200 of 306 posts

Re: Fast

#191
post #143

Earlier quoted context omitted.

That's a good point. But Git was initially written by one cranky Finn, in ten days. It totally changed the way we all work.

JavaScript was also famously built in 10 days. I'd say that internally git is more consistent %)

> JavaScript was also famously built in 10 days

And boy does it show!

Re: Fast

#192
post #146
post #56

Earlier quoted context omitted.

Not to knock the success of git, or the amazing effort under pressure, but the cohesiveness / understandability could be better.

Most of the inconsistencies, like "checkout" having three different functions, were added much later, in attempts to make UX niftier locally, without thinking about the product as a whole.

Checkout can move your head to different commit and it can copy files to your working tree from a non-checked-out commit. What's it's third function?

Re: Fast

#194
post #146

Earlier quoted context omitted.

Most of the inconsistencies, like "checkout" having three different functions, were added much later, in attempts to make UX niftier locally, without thinking about the product as a whole.

Checkout can move your head to different commit and it can copy files to your working tree from a non-checked-out commit. What's it's third function?

It can create a branch with -b, based on a branch of your choice (not necessarily current).

I constantly use this, having created an alias:

  [some other branch]$ git cob feature/foo123 main

Re: Fast

#195

This reminds me of when I interviewed at Stripe, a few years back. It was a surreal experience. We were in a small conference room. I sat at the table on one side, Patrick and Edwin sat on the other side. They asked me questions, I answered them. It was a good discussion. Then there was a brief pause in the conversation. Suddenly, Patrick let off the most absurdly loud fart. I chuckled in surprise. Patrick and Edwin…

lol looking through my recruiting notes... no such thing has ever happened

Oh snap, called out by the man himself! Good story though

Re: Fast

#196

This reminds me of when I interviewed at Stripe, a few years back. It was a surreal experience. We were in a small conference room. I sat at the table on one side, Patrick and Edwin sat on the other side. They asked me questions, I answered them. It was a good discussion. Then there was a brief pause in the conversation. Suddenly, Patrick let off the most absurdly loud fart. I chuckled in surprise. Patrick and Edwin…

lol looking through my recruiting notes... no such thing has ever happened

history is written by the victors!

Re: Fast

#197

Major one missing: China built 5,000 miles of high speed rail in 6 years. In California, it's been 15 years and we have 0 miles complete. Also built numerous hospitals during pandemic in a couple weeks. Demolished and replaced a bridge in 43 hours: https://www.popularmechanics.com/technology/infrastructure/a... . General pattern of completing infrastructure projects at a blistering pace - and they work. Also landed a…

At least California's infrastructure will last the test of time. If China's railways are anything like there global infrastructure then it will probably fall apart in less then 10 years.

Autocracy gets shit work done.

Re: Fast

#198
post #153

Earlier quoted context omitted.

That's a good point. But Git was initially written by one cranky Finn, in ten days. It totally changed the way we all work.

> But Git was initially written by one cranky Finn, in ten days. It totally changed the way we all work. To be fair, Linus was trying to replace Bitkeeper, a proprietary DVCS which he'd been using to maintain the kernel for several years at that point. Mercurial, which runs on similar principles, was around at the time too. He didn't just make a quantum conceptual leap straight from SVM to git on his own in 10 days;…

I see this as kinda the flipside of "how to draw an owl" [1]. A smarter programmer than me once described software as "do 90%, then do the other 90%" - the mvp, first functional prototype, heck, even the first deliverable is great and all, but then it's time for the thing to live and breathe and go out in the real world and learn all about what it'll become someday. Thus was born semantic versioning.

On the other end of that, like what you're talking about, you have the artist who answers "how long did it take you to paint that?" with: "my whole life". I think this holds true in most disciplines and especially in software. The actual code that makes a thing work is trivial - but you have to know which of the 9 gazillion ways of doing it is the one you want, which only comes from experience.

1 - https://imgur.com/RadSf

Re: Fast

#199
post #186

Earlier quoted context omitted.

JS on the list is quite interesting, since it being rushed and a prototype ending up getting shipped often gets cited as an explanation for why JS has issues. Given how widespread it is, this is a project I wish had gotten a lot more time. An argument could be made that it succeeded, so it must be good, but given it's the only built-in, full language in the browser just says that it was good enough and now we are kin…

Indeed, there was no choice. Good thing we ended up with a small language that has easy objects, first-class functions, and compact syntax. We could have got something like ABAP were we really unlucky.

As much as I couldn't live without complaining about Javascript's shortcomings, I have to agree with this. At the time, many of the features you mention were hardly necessary - no one was considering using it to build giant web apps, let alone servers! The fact that people decided they could do those things and the language was sufficiently flexible to grow along those lines would probably be very surprising to the original developer. For having such a chaotic evolution, it's becoming a much better language than anyone would have a right to expect.

Kind of like English, which is also a terrible choice for a global language, it's shown a fairly powerful ability to incorporate new idioms.

Re: Fast

#200

This reminds me of when I interviewed at Stripe, a few years back. It was a surreal experience. We were in a small conference room. I sat at the table on one side, Patrick and Edwin sat on the other side. They asked me questions, I answered them. It was a good discussion. Then there was a brief pause in the conversation. Suddenly, Patrick let off the most absurdly loud fart. I chuckled in surprise. Patrick and Edwin…

Sounds arrogant. Not cool at all.
Post reply on HN