The significance of this is Elon Musk, who is the self-driving Uber of dot.com billionaires and is the hero of our times.
Well, I knew Steve Jobs well enough, and have met a few civilian astronauts and a bunch of other rich people. None of the others seem to have done so much for the long-term future of the human race as Musk has in leading the path to more affordable spaceflight.
Well, it beats making them into the world's most complicated airplanes as with the space shuttle. SpaceX has proven that they can do vertical landings of the first stage intact onto both land and a seagoing barge; after a trip out of the atmosphere and to about 1/5 of orbital velocity but not into orbit. They plan to do a parachute-less vertical landing of the Dragon capsule after a heat-shield re-entry. That turns out to be far less expensive and complicated than a space plane. It does turn out we need a lifting body for much larger vehicles. It still doesn't have to be a plane, though.
We don't need wings.
It's never Apple's problem. It's always "you're doing it wrong".
Bullshit. The single time I had a hardware issue with an iPhone (stuck sleep/wake button), I took it to the store, showed them the issue, had my SIM transferred to a new unit and was walking out the door 15 minutes later.
I can't tell if you are serious or not, but their Zen architecture should be dropping soon, and they at least in theory have caught up with the Intel CPUs of a generation or two ago.
If they have a good price point, they might start actually giving Intel some competition, which is good, since Intel has done next to nothing very interesting since the Ivy/Sandy Bridge days.
I teach classes using the Raspberry Pi 2 (soon to be switching to 3, I hope) in a variety of contexts, such as with students wanting to learn ARM assembly and to K-12 teachers who want to do physical computing in their science classrooms.
It feels to me like the RPi is focused a little too much on Python and Scratch. I understand that it's called the Pi because of Python, but ARM assembly is my favorite assembly language, and bare metal assembly in particular is just a really natural fit for physical computing due to how easy it is to turn GPIO pins on and off. But the lack of documentation for the newer Broadcom SoCs has made it difficult for my students to write bare metal projects. So this leads to my question for you: are there any plans on rolling out better documentation / support / code examples for assembly on the RPi 2 and 3?
Despite this sounding like grousing, I would like to assure you that I love everything you've done with the Raspberry Pi and the notion of physical computing in general. Everyone who takes an assembly class or science technology workshop with me this year will get a free RPI3 and a bunch of sensors, wires, and motors to do hands-on, open ended projects. And I've been doing this for a while and it works really well. Thanks again for all of your vision and tireless effort you've spent in this arena.
>A lot of tech people tend to forget that for most people, a computer is not an end unto itself. It's just another tool for getting their real work done. Why "advocate" a desktop if people can get their work done on a tablet or phone? A desktop system has a lot of complexity that, for most people, probably tends to get in the way of actually getting their work done as much as it helps them.
Tablets and phones are consumption devices, not creation devices. They are a hideously bad match for trying to do any sort of serious development work, or even your bog standard PowerPoint deck. A Surface is about as tablet-y as you can get while still being able to do reasonable work, but a Surface is still a real computer under the hood. Anyone who works with touch-only systems could probably give you a long list of design decisions that slow them down when trying to do anything serious.
>I'd argue that very few people's productivity is measured in how efficient their file operations are. It's sort of like believing you're going to be vastly more efficient as a programmer if you memorize a bunch of keyboard shortcuts or type 60wpm instead of 30. Unlike the movies, programming isn't about how fast you type.
I think his point isn't just doing file operations, but rather that everything from the CLI is going to be faster and more powerful than a GUI when you know what you're doing. GUIs are great when doing graphical stuff, but for text-based work, text-based interfaces work better. UNIX is an operating system that is also an integrated development environment.
And typing fast really does make a difference. I mean, sure, Amdahl's Law and everything, but when you know what you're going to do, your typing speed will linearly translate into productivity.