ozzo-validation VS PlatformIO

go-ozzo/ozzo-validation

https://github.com/go-ozzo/ozzo-validation Seems to do what I need but likely will need some convoluted reflection to build out the rules. Also likely some custom rules to be written which is okay since it's a one time cost and reuse in the expressions.

Personally I use ozzo validation: https://github.com/go-ozzo/ozzo-validation

This looks useful, but what differentiates it from something like https://github.com/go-ozzo/ozzo-validation ? Why would I use Valgo over something battle tested that follows a very similar pattern?

This is where it gets spicy: I just don't get at all who ever though this struct-tag based validation library was a good idea https://github.com/go-playground/validator - and yet it's the most mainstream one. Try to implement your own type, you're up to register some global validation tag and repeat it every time you're using that type. I'm grateful https://github.com/go-ozzo/ozzo-validation exists, that's what I use. But it's still way behind the other things I mention, where in general, it's simply not possible to pass around an invalid struct - because it can't be built if it's invalid in the first place.

Gin comes with built-in "validation", while Echo recommends the same validator. I am also not a fan of magic struct tags, so I would probably prefer either writing my own or using something like ozzo.

Other packages of note: https://github.com/uber-go/zap https://github.com/go-ozzo/ozzo-validation

Does https://github.com/go-ozzo/ozzo-validation meet your requirements?

https://github.com/go-ozzo/ozzo-validation/blob/v3.6.0/struct.go#L61

For the ESP32 in read mode, we've successfully developed a project using PlatformIO that accepts the key during build time and stores it in memory.

Check out Zephyr OS and Platform IO. Zephyr is part of the Linux foundation and has similarities to Linux with how it performs hardware abstraction (device tree). Platform IO integrates with other frameworks including mbed and Arduino.

PlatformIO together with avr-stub can be used to do source level debugging but there are some caveats.

Look into https://platformio.org/, it can abstract over a few RTOSes, and can show you which OSes work with which chips/boards.

If the HW looks like it works, you could also try alternate programming software. (e.g. TinyGo or PlatformIO)

You might have better luck with PlatformIO than the Arduino IDE; it's better at automatically choosing the serial port, though I can't say I've used it under Windows.

My other suggestion takes more work but will make your life oh so much better. Professionally I have used and highly recommend. https://platformio.org/ which is free!

Will you be doing embedded Linux? Embedded RTOS? Bare metal? Microcontrollers? SoC (say, FPGA with a hard processor core)?

You can do a lot with QEMU. https://bootlin.com/ has a lot of great, free training material.

https://bootlin.com/doc/training/embedded-linux-qemu/embedde...

is one of my favorites.

Learning to cross-compile, do embedded debugging, the process of booting an embedded system (which varies depending on the answers to the above questions), learning how to read a technical reference for the processor you’re using as well as for peripherals you’re likely to interact with - SPI, i2c, UART, maybe PCIe, are all handy skills. Learn a bit about JTAG, hardware, reading schematics, etc. Even being able solder is helpful.

There may be books (I had a great embedded Linux book when I started) but there are lots of online materials too. Check out https://platformio.org/

There are fun embedded boards and projects for microcontrollers too - micropython on an rpi pico, tinygo, eLua, etc.