Thank you for introducing me to the fact that a collection of ferrets is called a "business".
1,315 karma · joined March 4, 2015
(Although since Rust can compile to WASM, it might be possible to write Rust, compile it to WASM, load that WASM in Node and run that on Lambda@Edge.)
To your second point, I think the author is making an argument that it can perhaps even be earlier than that: the bug is introduced when the programmer's model of the behavior differs from reality. That is to say, the "bug" exists purely in the developer's mind. After that it's a matter of course for the bug to be transferred from there to the codebase.
If the developer chooses to interrogate their model before committing it to code, there is the possibility of the bug being caught before it ever makes it into the codebase. But perhaps it is still correct to say the bug still existed, for a short time, at least.
From the docs:
> PostgreSQL does not protect against correctable memory errors and it is assumed you will operate using RAM that uses industry standard Error Correcting Codes (ECC) or better protection.
https://www.postgresql.org/docs/11/wal-reliability.html
Re: IS ECC RAM really needed?
https://www.postgresql.org/message-id/20070526145214.GA21290...
I don't know enough about Linux to verify that the Keybase package does everything right; I delegate that to the Debian packagers and don't install anything as root unless it's from the Debian package repositories. Any software that I need that isn't in the distro is installed to a folder inside my home folder, where it might conflict with other custom installed software, but at least it won't break the entire system.
2. WASM is designed from the ground up as a compile target, not a language. We already see many languages with support for building to WASM. C, C++, Rust, and eventually when WASM supports garbage collection we'll probably see Python, JS, Go, all with support for compiling to WASM.
Yes, of course we all want our tools to the best they can be, but that involves making tradeoffs in features because the maintainers don't have an infinite pool of time.
Postgres is a sufficiently advanced tool that if you're using it for any serious work you need to read the documentation for it. Ideally cover to cover, but at least skim the whole thing and pick out the important parts. The Postgres "Routine Database Maintenance Tasks" documentation [1] describes in great detail everything you need to do to keep your database working well.
The ring doorbell is installed at your front door. It records pretty much all movement to and from your house. It records audio at the doorstep, so if you're having a conversation with anyone at your doorstep, that gets recorded too. If you have a porch and are sitting on it and speaking with people, etc etc etc.
Thanks for all your hard work on Rust, Steve, and good luck with the future!
You very well could be right, but those sources are not scientific. If you want to show me that magnesium helps people sleep, show me a PubMed article on the subject.
There's a pretty good song about how the moon's day/night cycle would affect a lunar mining colony: https://www.youtube.com/watch?v=GDPUdUGJpjc
I don't know all the fancy names for logical fallacies but this seems to be deliberately misrepresenting the argument. The website clearly states that the problem with the Latin alphabet is that it has to be able to be written efficiently as well as read. Your trillions of humans over a few thousand years have had to both read and write this alphabet. In the past few hundred years we've had technology that allows someone who made a huge investment to produce massive amounts of text without writing, and in the past few decades the ability to produce text without writing has become completely ubiquitous. Does it still make sense for this alphabet to optimize for hand writing? Are you arguing that the constraints that made the Latin (or any handwritten) alphabet have remained unchanged over thousands of years? They want to redesign an alphabet to fit modern constraints. We consume a lot of text on devices that need to have screens that fit in our pockets. Perhaps a two-thousand year old alphabet isn't still the optimal solution?
I also don't think the authors necessarily expect to disrupt anything. They just made something cool and put it on the internet. I'm happy people like this exist.
Once I actually picked up a volume of Plato's works I was surprised how approachable it was to me, a complete layman of philosophy.
Regardless, I don't see how this satire could be considered dangerous.
I'm still waiting for another manufacturer to even come close to the physical design of yubikeys.
I'm not sure I understand what you mean by this, especially since you go on to say that artist communes in the US qualify. Surely these artist communes exist within our centralized political and cultural system as well? These communes presumably refer crimes such as murder to the centralized authority, the police, rather than lynch mob.
I actually suspect that any significant regulation of Mastodon would in fact increase decentralization. Since the software itself is open source, it will be hard to regulate, if not impossible (is code speech?). That means regulators have to go after hosts of instances. Perhaps some instances will comply with regulation, but I suspect many will not. The largest of the non-complying instances will be shut down.
If the complying instances are seen as inferior to non-complying instances, instead of flocking to the complying instances, the users of the instances that were shut down should distribute themselves amongst the remaining non-compliant instances. Some of these instances will be outside of the centralized authority's jurisdiction (for example, after SESTA, many sex workers flocked to a mastodon instance that was specifically set up for them; this instance is hosted outside the jurisdiction of the US).
Direct link: https://www.youtube.com/watch?v=sbNv9MP27xE
Amazon already collects tax in Colorado, but a few smaller retailers will send you a letter at the end of the year totaling up your untaxed purchases. Since different counties and localities collect different rates, it's hard to get the total tax right at the time of sale.
Is this true if you're a developer? I've stayed away from macs because you need xcode to get any sort of dev tools and xcode is only available on the App store (at least this was the case the last time I tried to develop on a mac).