aslatter's comments

On: Start all of your commands with a comma (2009)

[aslatter]

I didn't invent this, but I have a headless "config" checkout, and have a git-alias which sets my home-directory as the work-tree:

   git init --bare $HOME/.config/repo
   alias config='/usr/bin/git --git-dir=$HOME/.config/repo --work-tree=$HOME'
   config config --local status.showUntrackedFiles no

Then I can do things like "config add", "config commit", and "config push".

On: Did a 1997 merger ruin Boeing?

[aslatter]

I keep this clip open in a browser tab so I can go back to it from time-to-time: https://www.youtube.com/watch?v=X3NASGb5m8s

It's the same basic message from Jobs, but this time about Xerox.

[epistasis → aslatter]

I'm curious when this was recorded, but my guess is early 2000s or maybe late 1990s?

With how Apple has avoided ever becoming a monopoly in pretty much any area, and instead tries to just take the top most profitable customers, it really meshes well with this idea of not becoming a monopoly and having the company rot.

Edit: looks like this might be from Triumph of the Nerds, a series released on PBS in 1996. So before Jobs' return to Apple and Apple's turn around.

[bee_rider → epistasis]

That’s an interesting thought. I always assumed they went for the upscale market because that’s where the profit margin is. But also, it does seem to let them pull in a ton of profit while not ever becoming a monopoly or the dominant player.

I think they are only the majority in tablets, right? And tablets seem to be, oddly enough, a bit stagnant.

[epistasis → bee_rider]

Yes, it's more than simply going for the most profitable customers, it's about avoiding the least profitable customers so that there's still a forcing function on the company to stay on top. And also direct immediate feedback trhough loss of the high profit margin customers, when starting to fail.

Of course, this could be overthinking a plate of beans, maybe Apple just aims for a high price point and high profit margin. But if you did want to take most of the current profits, and most of the future profits, you'd ensure you got enough feedback to not become a monopoly. You'd aim to take only the high profit margin customers and intentionally ignore the lower profit margin customers to let some form of competition continue to push on you.

[RVuRnvbM2e → aslatter]

Wow. I had not seen this clip before. What an insightful couple of minutes.

Thanks for sharing!

[arcfour → aslatter]

How does this apply to e.g. the Bell System?

From what I understand, their network was overengineered and they generally put out a very high quality product, and didn't need to do a lot of marketing.

[bronson → arcfour]

They put out a high quality, overengineered, extremely expensive product that, by government mandate, had no competition. After deregulation it was clear that customers wanted a little less quality for a lot less money.

[kelnos → arcfour]

You don't need to do any marketing when you're a government-protected monopoly and customers have a choice between having phone service with you, or no phone service at all.

[arcfour → kelnos]

But why put out a quality product then?

[kelnos → arcfour]

You can still feel pride in your work while being granted a monopoly.

[AceyMan → arcfour]

Bronson said what is intended with my now deleted post.

And considering the landfills that are filled with things that replaced "expensive" goods like a Bell phone—maybe the tradeoff isn't worth it?

I doubt any consumers then had heard about 'economic externalities' (in fact, I'm not sure enough have heard about it now).

[djmips → aslatter]

Don't be a tonerhead!

On: Email and Git = <3

[aslatter]

That is a pain, but the --update-refs argument to git-rebase helps somewhat: https://git-scm.com/docs/git-rebase#Documentation/git-rebase...

On: ZSTD 1.5.5 is released with a corruption fix found...

[aslatter]

From my fopen(2) docs:

m (since glibc 2.3)

Attempt to access the file using mmap(2), rather than I/O system calls (read(2), write(2)). Currently, use of mmap(2) is attempted only for a file opened for reading.

[eklitzke → aslatter]

I'm very skeptical that this actually makes things faster. For one, zstd is definitely going to be CPU bound rather than I/O bound. But even if it wasn't, there shouldn't be a performance benefit to reading a file sequentially using mmap compared to reading it sequentially using read, which you can easily verify yourself by writing a small program that just reads files both ways.

[dikei → eklitzke]

I think for clear linux, it might be for memory saving in constraint devices rather than for speed optimization.

On: Emotionless chatbots are taking over customer serv...

[aslatter]

I was able to down-grade my subscription over email, which isn't as good as an on-line form, but better than a phone-call.