bar VS chrono

$ pass git remote add origin https://github.com/foo/bar.git

git clone https://github.com/foo/bar /some/directory. Even better, set up ssh keypair and clone via ssh, so you don't need to type your username and password each time you push. The correct address will be on GitHub, under green Clone button, just change it from https to ssh.

Yes, just change the URL from https://github.com/foo/bar to https://sourcegraph.com/github.com/foo/bar to be dropped in to a code search for that GH repo.

nchecker. Also, https://github.com/foo/bar/releases.atom

This seems very good.

1. This looks like Notion, which is good. Notion succeeded by being pretty.

2. It feels...I don't know the way to say it, but the appropriately level of solid (I don't accidentally drag and drop stuff), fast, and just easy to use. No non-modal mix of commands and typing makes entering information frustrating. It feels like typing into Notepad. It's frustration-free.

3. I would like if the dashboard showed unscheduled tasks (as a collapsible section at the very bottom, below Completed.)

4. I have TODOs of the form "Deploy XYZ" and ideally they would be "Deploy XYZ - https://github.com/foo/bar/pull/1337" -- but this adds a lot of clutter to the task list. If there were a way to add details or attach notes to tasks, that would be helpful. (It would also add clutter, so be careful. Just a "Details" link next to "Schedule" and the tags might work. Make it open a note on the right, perhaps?)

5. The "Schedule" link below each item makes me think I haven't scheduled the item, but I have. It should say "Today" (when I'm looking at today on the dashboard).

6. The importing of calendars scared me as it populated a giant list, including my coworkers calendars that I've subscribed to (but have set to not display), but turned out fine. Only the ones I have set to display in Google Calendar display in Emery by default. The import UX maaaaybe could be better / less aggressive, but it works.

7. The dichotomy between "schedule this for today" and "add this to a specific time on my calendar" still exists, and frustrates me, but the ability to sort the tasks helps.

8. It's good that this is opinionated. Stay focused and reject most feature requests, including mine.

9. You got me to enter my credit card before I even got to play around with it. That's impressive, but you are definitely cutting your top-of-funnel with that requirement. (Maybe it pays off by increasing conversion at the free trial->paid step, or maybe you only want true believers at the beginning, but the payment form would usually have turned me away.)

10. Can I export my data? In seven days, am I going to have to manually copy-and-paste all my notes and outstanding TODOs back into my old system if I decide this isn't for me? This risk also makes me hesitant to go all-in during the trial period. (An export wouldn't fully solve this, since I'd then have a messy JSON file or something to deal with, but I'd feel a little better about it.)

Thank you, I tested this and it looks very promising. It does in fact change the composer.json accordingly, so I can use this command instead of hand-editing the json file. This means that I have commit to my git repo a `path` repository pointing to my dev package, but in my Dockerfile for production build I can run composer config repositories.foo vcs https://github.com/foo/bar to change "foo" on the fly to something else (e.g. git)

// We have to discard the first read of this sensor because of a know bug // in its firmware. Remove the redundant read after this issue has been resolved: // https://github.com/foo/bar/issues/10 temperatureSensor.read(); let temp = temperatureSensor.read();

$ git clone https://github.com/foo/bar.git

The best thing about the Sourcegraph instance hosted on sourcegraph.com is that you can edit the URL in your browser from https://github.com/foo/bar to https://sourcegraph.com/github.com/foo/bar to be dropped down into a Sourcegraph search for that GH repo. I've been using it for a long time because of this convenience.

(Though it would be even better if the two options for case-sensitivity and regex search were enabled by default instead of needing me to toggle them on every time.)

> I think you can get the wiki with plain old 'git' ? I forget ...

This is correct. The wiki for a repo is accessible as a separate repository named with a suffix of “.wiki”.

So if user foo has a repo bar with an associated wiki, and the repo URL is https://github.com/foo/bar then you can clone the repo and the wiki respectively over SSH by:

    git clone [email protected]:foo/bar.git

The problem is that this effects higher languages too, because they often build on libc. And on some OSes, they don't have a choice, because the system call interface is unstable and/or undocumented).

For example in rust, multiple time libraries were found to be unsound if `std::env::set_env` was ever called from a multi-threaded program. See:

https://github.com/time-rs/time/issues/293 and https://github.com/chronotope/chrono/issues/499

https://github.com/rust-lang/rust/issues/27970

https://github.com/rust-lang/rust/issues/90308

> I think library authors should be more relentless and break compatibility every few years. We just need some conventions to not do so very often.

I indeed did this years ago---I'm the original author of Chrono [1]---and it wasn't well received [2] [3] [4]. To be fair, I knew it was a clear violation of semantic versioning but I didn't see any point of obeying that until we've reached 1.0 so I went ahead. People complained a lot and I had to yank the problematic release. By then I realized many enough people religiously expect semantic versioning (for good reasons though) and it's wiser to avoid useless conflict.

[1] https://github.com/chronotope/chrono

[2] https://github.com/chronotope/chrono/issues/146#issuecomment...

[3] https://github.com/chronotope/chrono/issues/156

[4] https://github.com/chronotope/chrono/blob/main/CHANGELOG.md#...

On that note, it would also be good to configure cargo-deny so that a CI pipeline and any maintainer can easily audit the current dependency versions. Sometimes CVEs require a new major semver (looking at you, time 0.1.x and thus chrono 0.4.x), so it's not enough to rely on people installing the tool with semver-compatible updates. Automatically auditing dependencies is really important, and given how easy cargo-deny makes it, I don't think many projects have any excuse not to configure it.

The example has been randomly taken from the [Chrono][https://github.com/chronotope/chrono/blob/main/src/offset/utc.rs] crate.

libc isn't "just a wrapper". Is a massive legacy codebase filled with hacks, UBs and bugs: https://github.com/chronotope/chrono/issues/499

Would love to have people test this, you can leave feedback here: https://github.com/chronotope/chrono/issues/674.

Security issues? I'm looking at the open issues, but haven't noticed any that seem to be security related (no security related labels either). What am I missing here?