7 ms·
Before adding the newest fad features, maybe the should go back and add old fads that they missed. One big fad from 50+ years ago that I'd welcome is folders.
by tzs 6y ago
Before adding the newest fad features, maybe the should go back and add old fads that they missed.
One big fad from 50+ years ago that I'd welcome is folders. I don't want to just have all my repositories appear in a flat list ordered by time since last update. I want to make folders so I can organize repositories by topic--just like I have my repositories organized in my computer.
- kerng 6y agoThe modern version is tags, but they lack good sorting/viewing for tags
- raxxorrax 6y agoNot wanting to start a discussion about graphs vs trees for organizing, but in my opinion simple folders are great to fulfill basic needs. I cannot imagine a book having no table of contents and just a list of tags with numbers indicating relevant page numbers. That is just dumbing yourself down in favor of machine classification or search algorithms while a simple solution exists for this problem for higher order classification and context, which tags alone fail to provide, even with sorting.
- 6510 6y agoWith limited entries of text or code you can just have them all on one page. Slightly more requires a folder or category system. If you have even more you need tags you should also keep the categories (everything must sit in a single category), If you have even more you need categories, tags and search. Trying to use one of those for the wrong volume just creates clutter.
- rytis 6y agoDepends on a book type I suppose. Most have "index" section, which is just a list of tags. In recipe books I find it more useful than ToC actually.
- 6510 6y agoAl entry should go in a single category, chapter or folder. The index should provide a useful overview. Tags you may have in any amount. More is usually better. A tag with a single entry is useful. Chapters should never have a single entry.
- l72 6y agoI think it depends on your goal. If I want to browse new chicken recipes, I am going to open the table of contents, find the section on poultry and start flipping through recipes. On the other hand, if I want to cook a chicken curry, I am going to go to the index and look up curry, then find the relevant page. Folders are great for when you don't know what you want and just want to browse or explore based on broad topics. Tags/indexes are better when you know basically what you want, and you just need a way to find it or items similar to it.
- prepend 6y agoIt’s surprising to me that they don’t just do a folder based view using tags and relationships among tags. I don’t like being restricted to single folders, but I’d love to symlink projects into multiple folders. This would work out well if they just added some graph functionality among tags.
- throwaway8941 6y agoJFYI, they have those in gitlab. Here's an example. https://gitlab.com/gitlab-org https://gitlab.com/gitlab-org
- threeseed 6y agoMy favourite fad of the last few decades is: sorting. You know because in Github you can't even sort your list of repositories.
- 6510 6y agoHTML cant even sort
- Wingy 6y agoJS can though, so can Ruby.
- 6510 6y agoIt doesn't belong there in my view. We started out not knowing what anything should look like, we didn't even know what computers were suppose to do. Everything had to be envisioned and implemented. Different approaches were taken for a lot of things. Eventually we just know how something should work. At that point it can be abstracted away. Similarly lots of things should stay in JS. If we've experimented and evolved to the point where we know how something should work we should grow beyond modules and have build in methods for it. It is happening but much to slow in my opinion. Say, we have a Date API, are week numbers a thing or not? Are they an unpredictable poorly understood thing? Does it bother anyone if the API supports it? Everything should be able to migrate up and down from the metal to the highest level of abstraction depending on how much we use it. edit: There is no point shipping [table] sort magic to the client on every page view that needs it.
- chipotle_coyote 6y agoIt seems like you're simultaneously saying "sorting doesn't belong as a language function in JavaScript" and "we shouldn't ship a sorting routine to the client," which seems...odd. If the page view needs sorting, then isn't that the use case where we can most say that there is, in fact, a point to "shipping sort magic to the client"? (Also, you can do an HTML table sort in about 10 pretty short lines of code[1], so this seems like a kind of weird hill to die on.) [1]: https://stackoverflow.com/questions/14267781/sorting-html-table-with-javascript#14268260 https://stackoverflow.com/questions/14267781/sorting-html-ta...
- atq2119 6y agoThis so much. Another pet peeve of mine: GitHub is terrible for the workflow that Git was originally designed for. Specifically, the issue that there's no good way to review patch series. The key here is presenting a series of patches as a whole, but allowing reviews on individual commits of the series.
- infinitezest 6y agoAssuming that we're talking about the same thing, this is possible in GH from the `Files` tab on the PR screen.
- u801e 6y agoNot really. You cannot comment on the commit message itself. And, if I'm not mistaken, changes made in one commit that are undone in a subsequent commit won't show up even if the files view if filtered by commit. Also, it's difficult to tell which comment is associated with which commit.
- conradludgate 6y agoI don't think I ever factor in commit messages into my code reviews. I may look at the commit history if I want to see how they experimented implementing the feature, but I only care about the end goal and the code I will be merging in at the end.
- u801e 6y agoThe issue is that Github actually discourages reviewing by commit because it makes it difficult to do so. Though there are those who are only interested in the overall diff, there are others who want to be able to maintain a clean and informative history via version control. When the review system makes it difficult to ensure that's the case, then then version control history cannot be maintained.
- atq2119 6y ago
- mbeex 6y agoSo, something like https://docs.gitlab.com/ee/user/group/ https://docs.gitlab.com/ee/user/group/ ? But this is gitlab.
- ashtonkem 6y agoI’ve recently switched from GitLab to Github enterprise due to a job switch. I am shocked at how bad Github enterprise is to navigate. It seems like I regularly have to depend on the search function to find the repo I want.
- kreddor 6y agoI agree completely. I miss folders for YouTube subscriptions as well. It seems folders are on the way out in most modern tools and apps.