Hacker Newsnew | past | comments | ask | show | jobs | submit | UkiahSmith's commentslogin

I much prefer lsd over exa, as lsd has better backwards compatibility with the flags. Specifically `-t` for sorting by time, exa has it specify the time field used.


This is exactly why I switched some months back to lsd after years of using exa.

The muscle memory of `ls -alt` and `ls -alrt` was too powerful for me to switch to `-snew`, even after literal years.


Where did you read that license can be revoked after 35 years?

Does this include licenses that say "irreversible" in them?


In the US, it's part of the Copyright Act and it applies regardless of the license. Per 17 USC 203(a)(5):

"Termination of the grant may be effected notwithstanding any agreement to the contrary, including an agreement to make a will or to make any future grant."

More info on terminations/transfers generally: https://www.copyright.gov/docs/203.html


That section is part of Chapter 2, which is about /transfer/ of copyright, in whole or in part. The “license” it refers to is a license that provides for /complete transfer/ of a part of the bundle of rights that is normally encompassed in copyright. So, frex, someone could use a “license” to transfer their right to authorize derivative works based on their copyrighted work to, say, their kid. The original author would no longer have any say about authorizing derivative works—only the licensee (their kid) would.

It is these transfers of copyright or partial copyright that the author can terminate after ~35 years.

AFAIK, none of the OSS licenses involve transferring copyright, in whole or in part. The original software creator still retains full copyright of their code. They have merely granted a license to others to use that code in certain ways. I just double-checked and GPL v3.0, frex, explicitly says that this license is built on top of copyright and only has effect for the duration of that copyright, and that the author of the code retains their copyright. The fact that the programmer retains their copyrights is why they can license the code under multiple OSS licenses if they want, or both license the code under an OSS and have a separate commercial agreement with someone else for use of the code in a way that the OSS license wouldn’t allow.

And since people licensing their code under the terms of an OSS license never transferred any part of their copyright to someone else as defined by 17 USC 201, there’s nothing for them to terminate under the terms of 17 USC 203. 17 USC 203(b)(5) explicitly says that these termination rules only apply to chapter 2 transfers, not to other sorts of licenses.


I found a legal article discussing this as it relates to software. https://news.ycombinator.com/item?id=34444646


Have you ever merged onto an expressway behind someone doing 20mpg? It's terrifying.

Acceleration makes merging onto expressways safer.


You should try writing with a fountain pen, if you already haven't. It's a different experience than popular ball pens.


Not any old fountain pen, though. A cheap one snags on the paper, and isn't at all pleasant. A good pen (on good paper - like, a nice laid) is certainly a pleasure. But who writes personal letters with a pen, these days?

I've never tried to write with a quill. That must have been a real pain in the wazoo - constantly whipping out a penknife to trim the nib.


Absolutely. This is how I survived handwriting.

Pens would just physically hurt to type with. Fountain pens, no force required, they just glide on the paper.


Oh, I have. I love fountain pens and writing with them a lot. But those things get ink everywhere, I've never had it when they didn't, so I haven't had one in a while. But I love fountain pens, I've had many of them.



I prefer lsd over exa because the flags are more compatible with standard ls


Agreed. I gave up on exa because `ls -tr` doesn’t work.


You mean like this? https://i.imgur.com/g4hl1Rg.png

alias ls="exa -h --group-directories-first --icons -g $@ --git --color always"


That seems different than sorting by time?

My minor exa gripe is described here: https://github.com/ogham/exa/issues/519

Lots of workarounds, even more available now, but I ended up switching to lsd and love it. I like the file type icons.


I think that's what OP means by “easier to alias”


> Unlike in every single one of those other languages, this Golang decision means that you can't pin to a specific minor version

Yes, it is possible to pin to minor version.

The version is specified in the `go.mod` file.

Look at this [go.mod example](https://github.com/ukiahsmith/modbin1/blob/main/go.mod).

The upstream `modlib1` library at v4 has tagged versions for v4.0.0 and v4.1.0. The go.mod file pins the version to the _older_ v4.0.0.


git restore


+1 this.

It's not just better name for doing "git checkout -- path". "git checkout" has this stupid behavior of restoring files to worktree and index. "git restore" by default doesn't touch index (I wrote SO answer that explains this a bit more: https://stackoverflow.com/a/60855504/350384)

there is also "git switch" but I just kept using "git checkout" because there is nothing "git switch" can do that "git checkout" can (it's just a shorter name but I had aliased "checkout" to "ch" anyway, as many people do)



Apple is including 1 year of service free with new hardware. That is going to be a very strong push and get a lot of people using it.


The $5/month price is probably going to ensure no one cancels after the year.


Exactly, even if people are not using it heavily the price is so low that it makes sense for them to just keep it.


A genius move to get their service going and give it exposure.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: