> But I still used the up/down arrow keys for years or scrolled up when I was looking for a previous command
It's not even that bad of a habit with zsh either where it will only scroll through history matching a substring in your history, for instance if I type "rg -i" and then start pressing up arrow, it will only cycle through history entries starting with "rg -i".
if you enable history substring search in zsh you can get that feature anywhere in the command and not just the start. it's very useful if you remember some snippet of the command like it had the word debug in it etc. in fish that is built in and on by default.
though one function that i recently added will narrow your history down based on a space separated set of filters which i found useful
function hgrep
set -l cmd history
for pattern in $argv
set cmd "$cmd | grep -- "(string escape "$pattern")
end
eval $cmd | cat
end
use `hgrep ruby debug foo` would filter for a line that contained all the words ruby, debug and foo.
The company could have rejected the government deal if they cared about the moral aspect of spying on citizens instead of money; by accepting the deal and executing the contract they are complicit.
HN does not use markdown code block formatting so this is hard to read. Formatting code blocks is simple, two blank spaces before any line to make it a code block and no need for extra newlines (unlike between paragraphs):
double deposit(double amount)
in (amount > 0, "Deposit amount must be positive")
out (result; result == balance)
{
balance += amount;
return balance;
}
I'm not asking about the syntax, I'm asking about the logic where a value can be equal to itself plus another value when the pre-condition is that it must be > 0.
This is such a disingenuous comment. People are allowed to be displeased with how these very wealthy people have spent their money without being told "hrmm, well maybe you should vote with your dollar!!"
No, it's their money, they may as well burn it. Why should we care, we didn't earn it and we have no right to it.
It'd be different if we were talking about government funding. Companies and individuals can and should be able to do with their assets as they please.
This is some Randian "no society, only individuals" level of commentary. I dont have to have a "right" to their money to find how they spend it objectionable, and I sure as hell don't need to act like their actions won't have second and third order effects. Everything is connected, and the sooner we get away from this idea that individuals operate in a bubble, the sooner we will all benefit.
They are the right abstraction for people that do not want to relocate terabytes of their existing data and filesystem structure to migrate to some sort of an esoteric filesystem just so they can let a tool work "properly" according to some tech purists. I don't wanna worry about it at all, it just works behind the scenes.
Unless the highly-optimized parts are wrapped by an interface that looks similar to the non-optimized version.
In the case of a tagged object in Rust, depending on how well the compiler can wrangle through it, you might even be able to add a `.unpack()` method that returns a pretty enum from a packed value, that you can pattern-match on or whatever, and let the compiler remove all the code of unpacking unused cases.
(using that directly for the addition example would end up less efficient of course, but still most likely beneficial. It's after this when there's a potential true readability vs performance tradeoff)
Not necessarily, in C++ you'd still drop from smart pointers to raw pointers, from virtual dispatch to switches/computed gotos, from std::function to function pointers and so on. These abstractions all come at a cost.
We're in a reply chain discussing a mob of digital artists exercising verbal violence against a digital painting software author who used LLM to assist with the code. This is literally an analogous situation.
What does verbal violence mean non-hyperbolically to you?
>Verbal abuse (also known as [...] verbal violence [...]) is a type of psychological abuse that involves the use of oral or written language directed to a victim. Verbal abuse can include the act of harassing, labeling, insulting, scolding, rebuking, or excessive yelling towards an individual.
I'm sorry for this verbal abuse you'll now receive, as I'm disagreeing with you, but it's really hard to see "rebuking" as verbal abuse, I think that page might need a pass or two to make it a bit more objective.
On the contrary I think that's an apt comparison. Look up the history of e.g. the Luddites. This isn't the first time this sort of thing has happened in human history.
Graduated and figured I should get a job. Honestly wasn't enthusiastic about the idea. Saw an ad in the paper. It may have mentioned C programming. I went and interviewed with two senior engineers. All they asked was do I know how to do TCP/IP. I said that I did and was working the next week. Honestly the coolest job I've had in my career. Colleagues were all engineers - mostly nuclear.
That's good to know, I'd usually go about it in a roundabout way: soft reset the commit then git add --patch to stage the hunks to split it into multiple commits.
I think you'll find your workflow is still required. `git history split` is really only focused on turning a commit into 2 commits, so if you wanted multiple, you would need to run the command multiple times.
Add to that, it's patch functionality isn't as robust as `git add --patch`. For example, you cannot edit a hunk, so if you intended to tease out atomic changes, you won't be able to.
It's not that roundabout compared to what `git history split` is doing. It's sort of the missing tool in a lot of the rebase discussions (in the Stack Overflow answers). Basically `git history split` is most useful for "split an older commit in this branch", so it's a higher level complex dance of, essentially:
- `git rebase -i`
- Change the TODO list to `edit` the chosen commit (everything else to `pick`)
That "simplified" `git add -p` in the middle and that assumption that everything else not selected is the "other patch" is fine for quick splits, but there's still power user super powers in knowing the full rebase workflow and `git add -p`.
Yeah, I've been using git for nearly 20 years. I still rely on `git gui`. It's my crutch. I know you can do all of that in a terminal, but staging different hunks (or individual lines) is super easy.
Which gui? I’m on Mac and somehow I could never really be happy with gui‘s for git. Gitkraken is the last I tried and I found it too much cluttering. Paid choices weren’t that great aswell either (yet)
Also age plays a pretty significant role. I know older asians who regularly walk who still got T2D. You could argue that walking isn't physically active enough... but they'd argue otherwise. It's all relative.
At the risk of being argumentative I had a horrible diet for the past ~10 years and carried 50 extra pounds. However I also exercised a lot as a hobby and to my shock my glucose and other bloods always came out in the normal range.
This year I started Mounjaro and dropped the 50 pounds. Curious to see what my next checkup shows.
People kick around the idea of the "personal fat threshold". E.g. caucasians seem to be better at carrying fat than, say, Southeast Asians. White people seem to be able to better store fat without metabolic side effects; SEA seems to get T2D at a much lower bodyfat percentage.
Possibly maybe, but plenty of caucasian friends at my old bodyweight/fat percentage had/have horrible markers. I lean more towards the protective effect of exercise.
Look at Figure 2C in particular. The hazard ratio of smoking is 1.41. The hazard ratio between "Low" (<25th percentile) and "Below Average" (25th-49th percentile) cardiovascular health is 1.95.
In other words, it is better to be a smoker than in the lower 25% of non-exercisers. By far. It's not even close.
It's not even that bad of a habit with zsh either where it will only scroll through history matching a substring in your history, for instance if I type "rg -i" and then start pressing up arrow, it will only cycle through history entries starting with "rg -i".
reply