I have to agree here. I love ripgrep, but at times I've had to go back to regular grep because I couldn't figure out what it was ignoring and why, and there were far too many settings to figure it out.
This is going to date me, but I had a t-shirt with basically a code-golf version of DeCSS printed on it and it said "This shirt is illegal" on it or something like that. I never actually wore it in public.
I have a Framework 13, and I'm excited about this. I've been looking forward to moving to RISC-V for years now. I'm one of those weirdos who is willing to pay more for less performance. I guess they know their customers.
Any reasonable person can see that there's much greater danger in allowing a child to ride in a car on a highway--which no doubt would be considered perfectly acceptable by these police. Look at this visualization of cause of death by age: https://wisqars.cdc.gov/data/lcd/home. For those kids, the number one cause of death is "unintentional injury," the biggest component of which is motor vehicle crashes. Unfortunately, these police wield incredible power in our legal system, and, as a lawyer, I don't see any easy fix. It makes me sad that I'll be raising my child in this kind of environment.
I never understood why programmers have such a hard time with time. There are two and only two pieces of information you need to work with time: seconds past the epoch and location. Everything else is applying legal and social context to the actual data.
Here both of those pieces of information are missing on all three questions, so no answers can be given. Any answer to these questions makes assumptions or deductions about those pieces of information.
Nice to hear Russ's name on HN. Not completely forgotten I see. He also opposed the Patriot Act when it was extremely popular which I thought was courageous.
The Times newsroom doesn't posit premises (and certainly not the one you suggest) or debate tax policy, it reports facts. I find the ignorance on the basics of journalism and its role in American society on hacker news to be shocking and embarrassing.
So this response says the story is factually incorrect, but doesn't dispute a single fact. If the story is inaccurate, FedEx should describe what was wrong, in detail, and ask for a correction.
I've dipped my toes into embedded rust from time to time. Can you give me an example or two of how you would use async/await in an embedded environment? I'm just curious about how it would work.
I think carbon emitters should be on the hook to clean up an amount of carbon equivalent to what they emit. There should be nothing controversial about requiring people to clean up after themselves.
This is an amazing achievement for the WebRender team, but users should manage their expectations with regard to performance improvements.
The reality is that Firefox's current rendering engine is highly tuned, and switching to a new engine without major performance regressions is impressive. Keep in mind, there may be performance improvements coming down the line.