5. A multipaned layout for documentation. Possible panes: what you're reading, tangential stuff (glossary, footnotes) so you don't lose your place, history of clicks, bookmarks, things to check out later, personal notes Basically an IDE just for reading hypertext
-
Show this thread
-
6. A standardized sqlite-based configuration format so I can actually encode relationships and comment my config and not have to deal with all the YAML footguns
4 replies 1 retweet 14 likesShow this thread -
7. A tool for persistently annotating code in-line without using comments, a la Google docs, the bare minimum of editing features, so I can say "hey do we want this line" without it being a comment or a github pull request
2 replies 2 retweets 26 likesShow this thread -
Oooh oooh we can also make it multimedia, so I can annotate a function with a stack trace that includes it, or a set of other functions that call it, or an uptime graph, or a picture of cats
1 reply 0 retweets 15 likesShow this thread -
8. Tablet integration I want to have a tablet displaying a file graph and if I touch a file the editor on my desktop jumps to that file More variety in input methods in general would be cool
1 reply 0 retweets 19 likesShow this thread -
Uhhh folks I might only have 8 half-baked ideas Really reaching to find a ninth
3 replies 0 retweets 8 likesShow this thread -
9. A way to specify additional information in versions of libraries about what's different in this version, like saying "3.4.3 -> 3.5.0, cause: security vulnerability, added public api: foo bar baz"
2 replies 0 retweets 4 likesShow this thread -
10. Portable file metadata, because right now the only metadata you got is the file extension, and that's barely any info at all. Might have to be stored in a different file to be backwards compatible, lol
7 replies 0 retweets 5 likesShow this thread -
Okay now we're getting into quarter-baked ideas 11. A profiler that tells you how much money you'd save by making your code faster, either by reduced machine time or by better customer retention
6 replies 0 retweets 22 likesShow this thread -
Replying to @hillelogram
I often build tools that do this! When I don't have tools that output a dollar value, I keep mind the TCO ratio between CPU, RAM, network, disk, etc., but I don't think it's reasonable to expect devs working on services to know that ratio off the top of their head...
1 reply 0 retweets 4 likes
...since that changes all the time, can vary because someone negotiated a great deal, etc. Also, having a dollar value is nice because you can compare to non-hardware costs, like headcount. If that's quarter-baked, I wonder what you'd think of ideas that I consider half baked?
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.