SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 15 submissions in the queue.
SoylentNews
Submitted via IRC for TheMightyBuzzard
The results are in: The Raspberry Pi 3 is the most desired maker SBC by a 4-to-1 margin. In other trends: x86 SBCs and Linux/Arduino hybrids get a boost.
More than ever, it's a Raspberry Pi world, and other Linux hacker boards are just living in it. Our 2017 hacker board survey gives the Raspberry Pi 3 a total of 2,583 votes — four times the number of the second-ranked board, the Raspberry Pi Zero W.
[...] Note that by "votes" we are referring to Borda rankings that combine 1st, 2nd, and 3rd choice rankings [...]
So, which if any credit-card-sized computers are you lot playing around with?
Source: http://linuxgizmos.com/2017-hacker-board-survey-raspberry-pi-still-rules-but-x86-sbcs-make-gains/
This discussion has been archived.
No new comments can be posted.
2017 Hacker Board Survey: Raspberry Pi Still Rules, but x86 SBCs Make Gains
|
Log In/Create an Account
| Top
| 60 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
* m2 stares at the monitor... it looks like a hamburger...
m2 - that's a bad sign
(Score: 3, Funny) by DannyB on Thursday June 22 2017, @04:49PM (3 children)
Task:
To blink an LED.
A blinking LED is required on a control panel to indicate a warning condition.
Hardware engineer:
Easy, I'll use a 555 chip, a few resistors and a capacitor.
Done. Did I win a prize?
DIY Maker:
Easy. I'll use an Arduino with the blink sketch and a resistor.
Done. I have more billable hours than the first guy.
Senior Software Engineer:
You guys have it all wrong.
Such a system would never be flexible enough for a real application where a blinking LED indicator is required.
Consider the inflexibility of the 555 approach. What if the marketing people change the requirements from a simple on/off blink to a different blink pattern. The simplest example would be the double blink.
Blink, Blink, long pause, Blink, Blink, etc.
Then consider the lack of sophistication that the Arduino has. With a simple microcontroller you can't have a web interface to configure the LED's blink rate. You would have to re flash the firmware.
With a more sophisticated controller, like a Raspberry PI, or even better, a Beagle Bone, the system could automatically check on the internet for software updates; and automatically download and apply them. For security, downloads could be signed with 4096 bit keys using private certificates from the manufacturer. (This also ensures ongoing contracts since no other vendor would have the private certificates.)
Higher end boards provide more flexibility. The LED controller could have it's own WiFI connection to not burden the rest of the system to provide its internet access.
Since the specification is a blinking LED for a warning condition. Extreme reliability is required. Therefore we might consider abandoning Linux for an RTOS running on a Raspberry Pi.
Imagine the inflexibility the project would be saddled with if we had used a 555 or an LM3909.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 3, Touché) by kaszz on Thursday June 22 2017, @05:03PM
My solution: Buy a pre-made blinking LED. They do exist.
(Score: 2) by LoRdTAW on Thursday June 22 2017, @07:57PM
You have senior software engineer confused with DIY maker.
(Score: 2) by JoeMerchant on Friday June 23 2017, @02:59AM
So, if you need a few lights controlled via network commands, I think the Pi is the way to go.
If the lights just need to blink stupidly in response to a switch closure or something, then, yeah, 555 will do the trick.
🌻🌻 [google.com]