Originally posted by starshipeleven
View Post
I have been making home automation projects and other stuff where I deploy these things around, meanwhile you are just arguing over definitions or ifs and buts.
No, these devices offer these interfaces on marked pins on the board, there is no need to hack up shit or try to reverse-engineer the system or whatever and risk instability or hardware damage.
And? Consumer devboards do their best to look cooler and better than competition, so they try to offer more and more stuff that in real life isn't really needed in most cases.
You know about phones with octacore processors, x86 mobos with large amounts of PCIe/Sata/whatever that are not going to be used by 90% of the userbase (seriously, when is someone going to fill 10 Sata ports like in the modern mobos?)
You know about phones with octacore processors, x86 mobos with large amounts of PCIe/Sata/whatever that are not going to be used by 90% of the userbase (seriously, when is someone going to fill 10 Sata ports like in the modern mobos?)
But on the note of 10 SATA ports, the caveat to that is capabilities of the controller. I have a mobo with 10 SATA ports, but 4 of them are SATA II and are used for things like eSATA and can be configured in IDE mode, which Windows seems to prefer when reading some DVDs. It tends to be more difficult to change the behavior of a single SATA controller.
It's not personal anecdotes, it's experience in the field.
The fact that you don't find anything better than dismissing my experience as "anectodes" because lulz means you have 0 experience in the field to counteract mine.
The fact that you don't find anything better than dismissing my experience as "anectodes" because lulz means you have 0 experience in the field to counteract mine.
Yeah, and I'm saying that the people that REALLY need so many pins are a tiny minority of the ones making embedded projects. Because I have experience and I know others too.
The entire point of embedded projects is dropping many sensors/switches/stuff all around where they are needed. So yeah, saving 5$ per device isn't that bad when you need to buy 10 or more.
No for dimensions, ok for bluetooth, shields are kinda large on average and they are not usually the best choice for a serious embedded project.
Shields are for rapid prototyping, then you just solder stuff on a smaller board or whatever. Also to save quite a bit of $$.
Shields are for rapid prototyping, then you just solder stuff on a smaller board or whatever. Also to save quite a bit of $$.
Around the same (I'm including the daughterboard)
Yeah, Raspi zero is a devboard for experimentation and learning just like raspi, while actual IoT stuff and minirouters are more suited for actual headless embedded use.
I'm just saying that for the average headless embedded usage it's usually far better to get a different class of devices that don't have a GPU but give you something else more suited for the target use.
Leave a comment: