I benchmarked protobuf encoding and nanopb was very good. Even though our schema was huge, it still did serialisation in a time that was surprisingly small for our underpowered chip.
I've ran into this too, the feedback hub seems to be populated by first line support types. I also found a bug in a win32 API and the feedback hub told me to reboot my PC
People have lost data on GitHub from repositories being copyright striked for example. At least with git, every developer has a copy of the full history so full data loss is impossible really. What happens if this…
You can always merge feature branches together to check for conflicts
2-3 people daily I would be completely surprised there's any issues. It suggests they're working on the same files and on the same lines, why??. My current project has 40+ developers and I haven't seen a merge conflict…
Tbh they should really just learn it. It's super simple and powerful
Bulk has bus error detection and so you shouldn't get errors
I basically refuse to fix other people's git issues because 99% of the time they don't know how the basics.
I write software for FPGA soft cores. Even with all this acceleration around the soft core, we need some sort of scheduling and kernel context switches are really a big killer. We have the same issue as web developers,…
I have seen context switches be a killer in some embedded contexts. Especially on FPGA soft core applications where you often are dealing with heavy I/O, if you just naively spin up threads for I/O then you will suffer…
I benchmarked protobuf encoding and nanopb was very good. Even though our schema was huge, it still did serialisation in a time that was surprisingly small for our underpowered chip.
I've ran into this too, the feedback hub seems to be populated by first line support types. I also found a bug in a win32 API and the feedback hub told me to reboot my PC
People have lost data on GitHub from repositories being copyright striked for example. At least with git, every developer has a copy of the full history so full data loss is impossible really. What happens if this…
You can always merge feature branches together to check for conflicts
2-3 people daily I would be completely surprised there's any issues. It suggests they're working on the same files and on the same lines, why??. My current project has 40+ developers and I haven't seen a merge conflict…
Tbh they should really just learn it. It's super simple and powerful
Bulk has bus error detection and so you shouldn't get errors
I basically refuse to fix other people's git issues because 99% of the time they don't know how the basics.
I write software for FPGA soft cores. Even with all this acceleration around the soft core, we need some sort of scheduling and kernel context switches are really a big killer. We have the same issue as web developers,…
I have seen context switches be a killer in some embedded contexts. Especially on FPGA soft core applications where you often are dealing with heavy I/O, if you just naively spin up threads for I/O then you will suffer…