@ctbeiser I guess by 'file type' ownership you mean 'which program shows the initial representation/UI?' Either politics or task context.
-
This Tweet is unavailable.
-
-
Replying to @nouswaves
@ctbeiser I'm still trapped in my mindset from a month ago when I was building a command line app. This seems connected to that.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@ctbeiser Representing a basic UI for a file is actually something that is missing from the command line.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@ctbeiser There is nothing to guide the selection of an app that can operate on the data from a file type.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@ctbeiser It's the user's job to think 'grep' when with a string; 'cat' when with a file; 'spark' when with a string of delimited numbers.1 reply 1 retweet 0 likes -
Replying to @nouswaves
.
@ctbeiser Solution there, it seems to me, is to ensure that every program has a function signature that describes its use to the OS.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@ctbeiser Given this your UI would be a nice visual representation of the data types and the function signatures that can operate upon them.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@ctbeiser I really like your idea. Document windows belonging to files -> no monolithic programs -> compositions of small programs.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@ctbeiser The best part of the CLI is its compositional nature (pipes, etc). But it conceals its utility through its lack of document views.2 replies 0 retweets 0 likes
@ctbeiser Create a UX that has document views as described as well as being high-fidelity and easy-to-use and I think it'd be a winner.
-
This Tweet is unavailable.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.