2 comments

[ 3.4 ms ] story [ 21.7 ms ] thread
Alt-Text: There was a schism in 2007, when a sect advocating OpenOffice created a fork of Sunday.xlsx and maintained it independently for several months. The efforts to reconcile the conflicting schedules led to the reinvention, within the cells of the spreadsheet, of modern version control.
It's interesting where the bounds of a "do one thing, and do it well" are for a sufficiently advanced command-line interface (CLI) tool, while web apps seem to require a minimum of capabilities along with its "reason for being"--not limited to authentication, authorization, routes, logging, and database driver.

I wonder if there is a way to categorize apps according to "workflow paths": actions taken to accomplish something, specialized for that use case, with just a few branches.

Then again, maybe any sufficiently advanced web app implements a Jenkins instance with several dozen plugins. Not that this is good, just a possibility.

Because users don't want to go to seventeen different corporate apps to get things done, but how do you break down those silos?

But yeah: the app has some core algorithm, and lots of supporting elements around it.

From that perspective, we do allow some necessary pieces around it. An algorithm by itself won't suffice.

Maybe it's a spin like "show me the data structures, and I don't need the algorithm" [1].

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