I'm looking for features like external terminal, mosh and ipv6 supports which will make a difference from other existing products. Otherwise it doesn't make much sense to migrate from excellent terminals/ssh clients like iterm, putty and mobaxterm.
According to Mozilla, the token is used to analyze download/install rates. This looks something that I'd like to send back to Mozilla for a better browser and market share.
Of course, it's possible to review each individual commit as well, but who does that?
I know that some folks love to mess around as much as they need in their local branches, commit often and then do an interactive rebase, to maybe end up with one or just a few commits that can then be the basis for a pull/merge request, then the difference matter a little bit less.
> At Meta we call an individual set of changes made to the codebase a “diff.”
This statement is definitely a misleading one. A diff itself is always a commit in the history log, and a diff can't be a group of multiple smaller units unless their team submit change set to git first and sync the squashed commit back to fbcode. But even in that case, from fbcode's view the squashed commit is still a diff.
They might get squashed for review or before merge, making the distinction less important. When you are running a monorepo you generally don't get long series of small commits in a batch but rather a singular atomic commit.
Bro there aren't many players that can't do this... This is a fundamental feature of tens of standalone music players. You just need to explore more than Roku or any other streaming service.
If preview is possible, $30 bucks would definitely worth a try (though it's not a very competitive price in the market). But if not, even $5 sounds too much.
I wonder whether you could use a simpler model to do the inference and don't render too much detail to lower the cost of a preview.
$30 is a small amount if we're supporting an open source project but when this comes to be a business...
