General > General Technical Chat
I feel.... Dirty...
james_s:
--- Quote from: daqq on April 29, 2023, 03:04:34 pm ---I know that there are areas where they are a great fit, consumer IoT in particular, but overall they leave a sour taste in my mouth. We actually use them in a bunch of stuff. The stuff I don't like:
- ADC parameters, linearity and overall ADC WTF
- requires a lot of support components, external memory in particular is annoying
- documentation is not exactly awesome
- some pinout choices that I don't like
This is not to say that I won't use one where it's appropriate, but unless something really requires BLE/wifi then no way.
--- End quote ---
You'd have to be a masochist, or really need something as compact as possible to use a bare chip, I use the modules that have all the RF stuff all ready to go with a metal shielding can, it's much easier than fussing around with the RF stuff, unless that's your thing.
MarkS:
--- Quote from: james_s on April 30, 2023, 12:57:27 am ---... Snip...
--- End quote ---
I answered this a few posts back.
daqq:
--- Quote from: james_s on April 30, 2023, 12:57:27 am ---You'd have to be a masochist, or really need something as compact as possible to use a bare chip, I use the modules that have all the RF stuff all ready to go with a metal shielding can, it's much easier than fussing around with the RF stuff, unless that's your thing.
--- End quote ---
A lot of the stuff we do needs to be crazy compact. One of my boards was 8mm wide and used an STM32WB5MMG module for everything. For an ESP32 I had a 15mm wide board that was chock full of goodies, so no space for anything extra.
artag:
--- Quote from: tooki on April 29, 2023, 10:31:20 pm ---
I guess that argument just makes NO sense to me whatsoever. Every IDE attempts to "do everything" because that's literally the point of an integrated development environment. First-party IDEs (MPLAB X, Cube MX, Keil, etc.) do all the same things, sometimes more...
Are you sure you're not actually annoyed at Visual Studio Code, which merely happens to be the most common host for PlatformIO? But you can use it in other IDEs, or use just the CLI version.
--- End quote ---
Platform i/o makes it worse by trying to do everything for every processor. This might be a strength but usually isn't. Proprietary IDEs are sometimes saved
by at least limiting the damage to one.
I don't need an IDE, I've got Unix. The entire OS is an IDE and does indeed do everything - and does it well. Not in a half-arsed way like most job-specific IDEs. That makes even less of a use-case for platform i/o : it fails to have processor-specific goodness by being all-encompassing and fails to be universal by trying to integrate less and poorer tools than you need. But that's not why I dislike it as that applies to many IDEs.
Yes, the default editor doesn't help. It's possibly not as bad as the previous default editor.
What I don't like about the 'you can change the editor' argument is that you tend to have to dig in pretty deep to change it. By which time you've learnt the wretched thing. Idk if this is the case for PIO, as I said, I was put off it by my first encounter and have avoided it like the plague ever since.
Brumby:
Don't beat yourself up too much.
I had a project offered to me (through the EEVblog no less) to provide a custom mod to a digital scale. I was supplied with a number of units of a typical scale and found an Arduino Nano clone board fitted perfectly in a space within the case. It had more than enough memory, adequate performance and just enough ports to do the job and once built, no-one would ever know unless they opened it up.
Sometimes getting something already built and tested is a more sensible choice.
Just don't ask me to share the source code though - so ugly :-[ - as it was my second effort in an embedded project (the first effort is still under development, you know - one of those projects that depends on a tuit of the circular form ;D )
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version