HN user
1. Larger vehicles pose a much greater threat to pedestrians and cyclists, both from frequency and consequence of incidents.
2. Tire emissions are more toxic than exhaust [1] and tire wear is dramatically greater on heavier vehicles. This is about air pollution in the city, not climate change globally.
[1] https://www.theguardian.com/environment/2022/jun/03/car-tyre...
Passwords need to be sent both with the request, and to the requestor. I think GP is referring to sending credentials to the service making the request.
It is far better to give service XYZ a time-bound and scope limited token to perform a request than a user's username and password.
This is challenging to answer with the nonspecific, "regular ones?"
What, to you, is a "regular tax?"
Payroll taxes? Income taxes? Property taxes? Sales taxes? Carbon taxes? Gas taxes? Cigarette taxes?
All are as dissimilar to recycling taxes as they are to each other.
I think in this case "better" reduces to convincing the upstream data source to not use json.
Putting that frustration on jq seems like a case of transference.
Few people have screens as high resolution as even a mediocre phone camera.
Before someone brings up future screen tech, there are additional reasons that's not a trivial workaround. Additionally there's a higher benefit to having high resolution cameras which have a wide field of view and the user may want to zoom in on the physical data vs a screen where the zooming happens in software.
Only 19% of electricity generated today in the US is from coal, trending toward 0. Then consider larger fossil fuel power plants are far more efficient than the tiny engines in vehicles.
"Coal is used to power electric vehicles," is an argument that is more noise than signal.
There's an off by one error in the above statement. Not sure if it's the right or left hand side.
This has given me a brilliant idea: deferring maintenance downtime until some larger user-visible service is down.
This is terrible for many reasons, but I wouldn't be surprised to hear someone has done this.
I disagree. In both cases the observer benefits from reaching beyond their current knowledge. They have the same solution.
Not treated as, only backed by byte sequences. If you range over them you get a series of rune values that can be multi-byte code points.
There's a few other differences, strings cannot be directly mutated or have the address of their elements taken.
I'm going to nit this for several reasons:
1. Walking on the moon implied a return trip which requires an extra ~3km/s.
2. Under the rocket equation the fuel requirements for more delta v grows superlinearly, which then awkwardly makes your rocket bigger, which requires more fuel...
3. 22 years prior a metal can went to space. The scale of a manned moon mission in comparison is absolutely nuts, even basic things like having rocket motors that can be relit is a large technical challenge.
11 cubic meters seems like a fairly small amount of water for a car fire. That's less than the capacity of a typical water truck. What, "applied directly to the battery," means raises questions in my mind. Is this a calculation based on the exothermic potential of the entire battery pack?
A PCIe 4.0 x16 link is 32GB/s in one direction. Capital B. Quite a bit faster.
It's also fully bidirectional, allowing for the same speed in the other direction at the same time. Thunderbolt is capped at 40Gb/s total bandwidth.
Well, the US federal government thinks this is fine. Citizens still have to file, and often pay taxes if they move out of the country. If one renounces their citizenship they are liable for up to 10 years of exit taxes.
To have this analogy encompass the full situation, you're also a residential landlord who owns 50% of all residential housing in the US. Your tenants are only allowed to have things in their home that came from the market you control. Things bought in the market also cannot be placed in housing you do not control.
You argue you don't have a monopoly because your tenants can always move, even though most of their possessions cannot be moved to other housing.
Reasoning by analogy is bad, but I think it's important to note that most people's phones are their digital home. It is not a low friction situation to just "shop elsewhere" for a single product when it wouldn't be compatible with your home.
Huh, so they did. TIL.
Intel's fault? Uhm, they've had some misses recently, but your statement about RAM support is incorrect.
The 7200u supports 32GB or RAM. That chip is over 4 years old and nothing special. Not sure how long that's been supported, I didn't feel like looking further back.
https://ark.intel.com/content/www/us/en/ark/products/95443/i...
The issue is your defect rate for larger chips. If a small laptop CPU only has 25% of chips being fully functional, a 4x the size server chip will only yield 0.39% of chips being defect free.
I say this having no idea what Intel's defect rate is right now, and I acknowledge fusing of bad sections can mitigate this a bit.
That is a problem that has not been thoroughly explored. What has been motivational historically, and what is necessary to motivate in the future, do not have to be the same.
And even looking at history, the motivations of scientific development seems quite varied. War has been a key promoter of many fields of science, which has in turn lifted may people out of poverty. So we should have more world wars?
That could equally be a consequence of technological and scientific development than any particular economic structure.
If the client doesn't trust the server, the crypto protocol is a little irrelevant.
I otherwise agree that we (ostensibly) are in a better place now with pre-defined curves.
Giant Magellen and Thirty Meter Telescope are both $billion+ projects.
So, no.
Yes it does. If you capture the authentication handshake, it's as straightforward as putting the passphrase into Wireshark.
It's worth noting that this guarantee also only applies to messages between a client and broker. The protocol does not guarantee messages are consumed, only that they reached the broker. So if guaranteed delivery of a specific message to consumers is something you need MQTT tends not to be a good fit as you have to build application layer acknowledgements on everything.
Does not.
What it should and should not do is a subjective matter.
Maximum non-commercial penalty for copyright infringement in Canada is $5000 (about $3700 USD today).
I don't think taking people to court has a great cost-benefit ratio.
How do you mean? The formal disclosure was supposed to be earlier this month.
[Edit] I see, link implies the problem is that the 6 month disclosure process lacked urgency, and many affected parties were notified late in the cycle. Perhaps this is an argument against agreements to keep vulnerabilities secret for a long time, as an attitude of, "there's enough time to address this," can be counterproductive.
That's like saying there's no difference between 99.9℅ the speed of light and going all the way there, from an engineer perspective. Turns out, one of these requires an infinite more expenditure of energy than the other. Similarly, if you're evacuating a tube by removing gave the gas at a time, 1/1000 is attainable. 0? Not so much.
Well, maybe not Bash, but it seems a dozen years ago referring to Perl as a systems language would not have caused anybody to blink ;)
I apologize for how glib my remark above was, it didn't add much to the conversation, and was more a knee jerk response to the notion that "Systems Language" is now, or ever has been, well defined.
I brought up the handling of signals, because process management is, in practice, a pretty big deal in what I would consider systems programming. But I don't think it's important to all systems programming. Much like I don't think avoiding garbage collection is necessary for all systems programming, though it's clearly an issue for some applications.
What I do find odd is the notion that it is necessary to not have garbage collection, but not having a solid story behind handling signals from the OS receives a pass.
Rust can handle signals, but its implementation is very platform specific (even the currently recommended crate lacks Windows support), and ultimately calls out the FFI. So it seems that saying Rust has support for signals is like saying Go supports manual memory management because you can call C.malloc and C.free...