They're usually not accessible, or very expensive to do so.
Also, why should the infrastructure be vehicle-focussed like you describe? There's no reason other than people are so used to it.
4,311 karma · joined January 6, 2016
They're usually not accessible, or very expensive to do so.
Also, why should the infrastructure be vehicle-focussed like you describe? There's no reason other than people are so used to it.
(If Okta was zero-dayed, IMO we'd have heard about it. Great way to shift blame.)
Seems to me giving people a shock at the checkout is a particularly evil way of making taxes explicit. It isn't like the taxes aren't broken down on EU receipts for those who care; in fact it's quite explicit.
And that matters if you have to be careful about spending. Also, "everyone knows about them", really? If it's so easy to "know" the local tax rate for various things, why isn't it easy to label them?
See the rest of the world, where even young kids can go shopping. If you give them 5 <amount of currency>, and the item they want is less than 5, or they want five of something that is 1, they can buy it.
I wouldn't necessarily expect a demo; but not mentioning it at all seems like it could lead readers down a path where they choose the "most performant" option presented (FFI + ctypes). The post has a "To go further:" link section where even a quick link to PyO3 would go a long way. So I thought I'd mention the downsides and an alternative on HN.
The benefit is that you only need to ship the CPython extension, you can build it with cargo, and everything's in one place. I've maintained bindings for Python and C# to native libraries, and it's usually a pain for various reasons.
The C API might be able to be used anywhere, but that doesn't mean it's ergonomic, easy to use, or safe.
Also, there is no ctypes involved, as the result is a CPython extension that just loads on the Python side.
Instead PyO3 [1] lets you "write a native Python module in Rust", and it works great. A much better choice IMO.
obviously this is the case if you are a normal citizen. imagine how fast they'd access the recordings if a police officer was hurt, or to identify protesters, etc
So would you for example agree to be extradited to Russia for saying there's a war with Ukraine? Or to China for mentioning the Uyghur genocide? It's a secret after all.
Also, just being able to threaten journalists with court in general would have a chilling effect - especially in a place like the US where it costs so much money.
By the way, the first and sealed indictment of Assange was not for leaking secrets. Make of that what you will.
No, it isn't tall people, as I already said.
Along those lines, a quick way to drive adoption could be a huge "how do i do x" or recipes page to Ctrl+F through. If I have to search the internet for how to do x in nushell/fish/etc, I might as well stick to arcane bash - at least you know someone has had the same problem before.
Make it easy for me to get stuff done by showing me how to get stuff done, and I'll grok the shell bit by bit.
I did see https://www.nushell.sh/cookbook/ , but it isn't really a searchable reference. There's some setup stuff, other short pages with basic tutorials (?), a link to a repo with example scripts, and for one-liners you are instructed to join a discord. None of these are easily searchable.
Nope. If you're lucky, you get a segfault.
> imagine you're making a game
Actually, I would love to be making games. The benefits Rust provides aren't huge benefits in Game Dev, we get it. In fact, isn't this whole thing just a rehash of Jonathan Blow's ECS critique? But most of us aren't making games.
Imagine instead you're a not making a game, and you see CVE after CVE because of memory safety. Customer data gets stolen, things like SSNs. People's lives are impacted. I suppose a game crash is annoying, but way less annoying than someone's/my personal info being leaked.
Sure, we could go on as usual, blame "human error" and say everybody needs to do better. Or, we could accept better over perfect, and try to mitigate common errors that seem to happen often. You can still use `unsafe`. I guess by this argument, seat belts are useless, too, because they don't stop traffic fatalities completely. And so are all aviation safety improvements.
We're still here having the "Rust offers no/marginal benefits (to game dev and other niches)". Ok.
That's so pedantic, I'm inclined to disagree - if it's even correct. Not everything that's unsolicited is spam. An unsolicited thank you note isn't spam.
More components of spam are traditionally a large, indiscriminate number of receivers, and low quality messaging. Irrelevancy does partially capture both of these.
I can convert from UTC to my timezone (TZ) in my head, since logs are usually UTC. I know other engineers can do this, too. What I cannot do is convert from a random TZ to my TZ without looking it up. Clearly, the author knew this, which is why EST was added for an American audience.
Note the Datadog post-mortem is UTC [0], but the status page isn't [1]; even the EU one is ET [2].
So why are time stamps not being in UTC a thing?
Reasons I can think of:
* Status pages and post-mortems are not for engineers, but for management?
* Certain US-based companies use ET (i.e. EST or EDT) or PT (i.e. PST or PDT), and everybody else has cargo-culted it.
[0] https://www.datadoghq.com/blog/2023-03-08-multiregion-infras...