Tortoisehg tag vs bookmark8/28/2023 ![]() I want a UI optimized for high-efficiency GTD-like triage of incoming stuff, with easy auto-triaging for things like "new YouTube video" notifications.A properly unified folders/tags system with the arrival source being stored as metadata instead.) It shouldn't matter what protocol something arrived through.It's an idea for a unified e-mail/RSS/calendar/TODO/bookmarking tool with a UI paradigm I wasn't able to find outside of various academic papers touching on the need for some of the solutions I reinvented. Once I get my other stuff caught up, I want to complete what I started as my degree project for my bachelor's degree. (The latter of which, I'm planning to replace.) I'm only just now starting to prepare to install my first SSD, and I'm very careful about designing my desktop loadout so the only things I need to curse are browsers and Thunderbird. and, of course, the other big reason I chose git back when I decided to migrate off Subversion and my flirtation with bzr. maybe I'm just an odd duck in actually wanting to follow the "understand the conceptual model first" approach the git devs espoused? That sort of thing is what puzzles me about people saying Mercurial is easier. I found the conceptual model off-puttingly complex and didn't feel like setting up some kind of hacky "take FS-level snapshots of the repo in case Mercurial's internal Undo isn't comprehensive enough" system. ![]() now I remember the other reason I avoided Mercurial. On that front, I worry that Mercurial is going to have a fight on its hands, purely from git's network effects.Īhh yes. but my plan for resolving the bus factor issue is to pre-pay my domains for 10 years and set up automatic mirroring of everything between GitHub, Gitlab, BitBucket, and possibly SourceForge, to ensure that if keel over, the worst that can happen is that the executor of my will neglects to keep up the domains and people have to go to the github.io version or the Gitlab/BitBucket/SourceForge mirror instead. especially as a solution for what I said about phases. That does remind me, however, that I need to build a habit of setting up a system of branches where I can have master separate from "this is much further along, but as part of the development process, half the documentation is aspirational/brainstorming, not actually descriptive of the codebase" instead of just stopping pushing for months on end. I like this idea in theory but, in practice, I mainly use git push -f because I was too eager to push something, so I'd just be too eager to mark something public instead under that paradigm. We'll do our best to keep these links up to date, but if we fall behind please don't hesitate to shoot us a modmail. This is not an official Rust forum, and cannot fulfill feature requests. Err on the side of giving others the benefit of the doubt.Īvoid re-treading topics that have been long-settled or utterly exhausted. Please create a read-only mirror and link that instead.Ī programming language is rarely worth getting worked up over.īe charitable in intent. If criticizing a project on GitHub, you may not link directly to the project's issue tracker. Post titles should include useful context.įor Rust questions, use the stickied Q&A thread.Īrts-and-crafts posts are permitted on weekends.Ĭriticism is encouraged, though it must be constructive, useful and actionable. For content that does not, use a text post to explain its relevance. Posts must reference Rust or relate to things using Rust. We observe the Rust Project Code of Conduct. ![]() Strive to treat others with respect, patience, kindness, and empathy. ![]() Please read The Rust Community Code of Conduct The Rust Programming LanguageĪ place for all things related to the Rust programming language-an open-source systems language that emphasizes performance, reliability, and productivity. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |