447 karma · joined July 2, 2014
But really, any sort of thing that blocks, as the Github README says, "annoying, user-hostile software", is a good piece of software in my book.
The article states,
> An activist group, which claims Coinbase's decision is akin to a brokerage withholding new shares from its investors, ...
which is not at all what it's like. Coinbase isn't the only source to buy/sell BCC. I think it's ridiculous that a company could be sued because they don't offer a new service.
Floor plans are quite useful for staging a burglary.
I agree with this. I always saw pre-orders as a way to reserve your "spot" for a physical object. My first encounter with pre-orders was video games, before platforms like Steam where physical copies of a game aren't limited.
The problem with pre-ordering now is that it's becoming a method of funding incomplete products, with the promise of a finished product. It involves the consumer in the production phase of a project, shifting the risk of "it didn't work out" from the investors to the consumers. And like you mentioned,
> An investor gets a stake of the company. An investor (of certain worth) has a say in what is going on. ... A customer doesn't, they speak only with their desire to buy whatever product is being pitching.
But, at the same time, it looks like they acquired a nice chunk of money ($14m in capital) only after they released their video. Would it have been possible to finish their product, advertise, and start shipping without that $14m, and however much they received from pre-orders? I can't say. To me, it seems like they started advertising to the public and accepting pre-orders before an actual product was ready for the mass market; but if they were running low on funding at the time, it may have been their only option to secure funds. (Take that with a grain of salt; I know next to nothing about business + entrepreneurship)
Here's what `time ls` and `time lc` produced, in a directory with 517 files:
> ls --color=tty -l 0.01s user 0.00s system 93% cpu 0.007 total
> ~/.gem/ruby/2.4.0/bin/lc 0.14s user 0.01s system 98% cpu 0.159 total
It's definitely noticeable, especially if you use `ls` day-in, day-out. But it's nothing debilitating.
But as someone who lives in the terminal, it's not something I would use at all. To me, the fancy fontawesome glyphs PLUS the colors are information overload [1]. It really feels like overkill. I'm not trying to discourage anyone (including the author) from writing these things, and clearly the author is a very good programmer.
If it was an exercise in making something beautiful in the terminal, then the author succeeded in this endeavor. Making a good looking, consistent terminal UI is ridiculously difficult, and each column is pretty and formatted. This program feels like it has had a lot of TLC. Honestly, I hope the author continues to make cool programs in the terminal; they clearly have a knack for it :)
As a minor aside, maybe consider changing the executable name from `lc` to something else; it conflicts with the `lc` executable for Mono (at least on Arch[2], and Ubuntu[3]). But that's just a minor nitpick.
[1] this is my opinion, I want to make this as clear as possible
[2] https://www.archlinux.org/packages/extra/i686/mono/files/
[3] http://manpages.ubuntu.com/manpages/trusty/man1/lc.1.html
If this actually was a config option, I would bet anything the default would inexplicably be set to "true".
>I pay them. My work pays them.
Github is raking in oodles of cash and they STILL can't keep their service up without going down, quoted from OP, "[e]very couple months".
It's not about "making a better one", nor is it about paying for the fancier/premium features; it's about the uninterrupted service, which Github keeps failing to provide.
> the market of dying
is there something about your mortality that you'd like to tell us?