Note that this was most likely written by his facilitator, not by him. It was written via a technique called "Rapid Prompting Method", which appears to be a variant of facilitated communication, a method that has been debunked as simply being the facilitator guiding the child, either consciously or subconsciously, to type things that the facilitator is thinking, not that the child is thinking.
A lot of people who believe in FC and it's variants believe that there's a big conspiracy to silence the voices of their children. They don't think it's relevant that there was a facilitator who was just "supporting his arm" or "providing contact" or something of the sort. So they are unlikely to do this; they want to promote a notion that the child is producing the text, not the facilitator.
I didn't realise this kind of thing applied to people with enough motion control to hold a cup of coffee as seen in the photo. Surely they can type on an iPad themselves at that point, without the need for an interpreter or go-between?
it is actually not about motion control. It is a fundamental inability to communicate. I don't know much about this specific case, but it is quite possible he could accurately hit arbitrary buttons, but cannot map those actions to a meaning to be communicated.
That doesn't sound like a terribly hostile tone. Yes, there was a little bit of hostility, but nowhere near the level that would lead a support person to give up on helping you.
Remember, people in support are used to a somewhat hostile tone. People get in touch when something is wrong, and so it's fairly common for people to be frustrated. If they just responded with "sorry, can't help you" to every support query with a slightly hostile tone, they wouldn't be providing much support.
And yes, it is also good to try and assume good faith and not vent your frustration at a support person who had nothing to do with whatever issue it is that you're frustrated about. But it's a fact of life in support that you'll have to deal with some unhappy people, so you need to be able to deal with it.
> The other alternative is you download source, at which point the Makefile or any other piece of the build that you execute can do whatever the shell script would have done
Part of the problem with this is that since it's a bootstrapped compiler, and the only one for the language so far, "downloading source" mean you need a binary to compile it with, which devolves to the same problem.
Rust was bootstrapped with an OCaml based compiler. Alas I don't think it has been kept up to date, so you won't be able to use it to compile the v1.0 source. Not sure how many generations in between the last OCaml compilable rust and the current rust you'd need to compile to bootstrap, probably quite a few.
A while back, somebody got Cargo running on an unsupported platform, but bootstrapping was a major problem. The compiler had to bootstrap newer versions of itself tens of times, and that was only for a few weeks of breaking changes …
Yep, the dropping of the sigils was a big help in my actually giving the language a chance. It's been on my radar for a while, but went through a pretty ugly period for a while before coming out much better than before.
There was also just a sense of "OK, I get what these things do, but when should I us an @ vs an ~ vs a & in my API", and now I feel like it's much more clear what you use the different reference types for.
It is possible, with a little manual hacking of the linker and some trickery with storing strings in ELF headers, to get Rust to produces 151-byte executable.
Yes, a simple "Hello World" winds up statically linking a fairly sizeable standard library, in particular anything dealing with strings has to involve a certain amount of UTF-8 manipulation and the formatting and I/O have a lot of features and thus likely fairly large code size. But for the most part that's just fixed overhead, and you can opt out of using the standard library if you want and produce smaller executables.
There has been some discussion of adding some language support for something like async/await/yield from other languages, but nothing concrete in the near future on the language front.
So, there's usable third-party libraries for it (at least, if you're on a Unix like platform), language support is in the realm of "it would be nice someday".
You can clone the repository, modify it locally, and build and test the docs (yes, the docs get tested, most of the code samples are actually executable tests), or you can just edit them online in GitHub's editor and send a pull request that way if you're just making documentation suggestions that won't need any tests.
The reason that you see so many multicopters for the smaller ones is that they are much mechanically simpler, and thus cheaper to manufacture. All you need mechanically for a multicopter is a number of independent rotors that you can vary the speed on.
A traditional helicopter has a very complicated assembly to allow powering a rotor that can tilt forward, backwards, and to the sides, as well as change the angle of the blades. This is a lot more expensive to produce.
It is more efficient, in a power to weight ratio sense, to have only a single motor, which is why you see this design on full-sized helicopters. But for smaller, cheaper drones, you don't need as good of a power to weight ratio to make it worthwhile, and the cheaper simpler design makes them easier to mass-produce and sell to amateurs or professionals on a budget.
The things that probably have led to an explosion of them recently include electronics getting cheaper, and control systems getting better. Regular helicopters can be piloted by a skilled operator with some training. A mutlicopter needs a automated control system to keep it balanced. As electronics for the control systems have gotten cheaper, as well as MEMS sensors (accelerometers and gyroscopes built into ICs), these control systems have become cheap and easy to integrate into mass produced products.
In addition, battery technology has been improving, as has electric motor technology. While previously only the single big fossil fuel engine was the only viable power source, as battery capacity has increased and electric motors have gotten more efficient, it's more viable to have small electric copters.
Another thing that makes these more accessible to casual amateurs, and again makes mass production more viable, is that most people now carry around a flexible input device with wireless control capabilities. That means that you can sell devices without a dedicated controller, can do things like streaming video back from the drone, and so on, increasing the range of things that you can do with one.
Other technological improvements also help feed into this. Having widely available, small, light HD and 4K cameras means that you can actually do something useful with these drones; back when to do any real filming you needed a big, bulky camera, they weren't as efficient for getting aerial shots, but once there are small, light, high quality cameras, it becomes feasible.
The title currently reads "Ripple fined for acting as a money services business without registration", and the complaint says "Ripple Labs willfully violated several requirements of the Bank Secrecy Act (BSA) by acting as a money services business (MSB)and selling its virtual currency, known as XRP, without registering with FinCEN".
That looks like the title matches the contents. Did the title change since you wrote the question? It is important on Hacker News, when addressing anything about the title of a submission (or about the precise URL of the submission), to quote the title or URL you are talking about, as moderators sometimes silently change the title or update the URL to point to the actual underlying story rather than blogspam.
It's also been done in actual reality. For example, one of Sweden's largest supermarket chain is the consumer co-operative Coop [1]. Their own line of budget private-label products had a very minimal "no-brand" design, though in 1979 they started using the name "Blåvitt", referring to the blue-white colors of the minimal design. I found a picture [2] of some of their products (coffee, detergent, tooth paste, tea, soap, bread, etc).
The Japanese retailer Muji also has a no logo or no brand approach to their products. Somewhat ironically, their 'brand' appeal (and company recognition) is due in large part to their minimal, unbranded design.
See https://en.wikipedia.org/wiki/Facilitated_communication for more information. I also recommend the PBS Frontline documentary "Prisoners of Silence" (transcript: http://www.pbs.org/wgbh/pages/frontline/programs/transcripts..., video: https://www.youtube.com/watch?v=HXw8Ksvyt5Y), which does a good job both debunking it, and demonstrating why facilitated communication can be quite harmful; there was a rash of incidents in which facilitators imagined sexual abuse allegations from children, leading to substantial repercussions for innocent parents.