TexasMick

They have the source code on their website: https://www.microchip.com/en-us/tools-resources/archives/mpl...

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 company folds? You're left with some proprietary repo that you suddenly have to workout how to self host.

It just doesn't make sense when compared to just learning git which is definitely the most fruitful thing a developer could learn at the start of their career.

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 in a long time.

Why do you think there's issues with merging and revising, pretty much all cloud solutions have a button to do both for you.

Tbh they should really just learn it. It's super simple and powerful

It reminds of when someone told me git submodules are slow.

They just forgot about shallow clones..

It's kinda crazy argument, I think data loss is way more likely with a centralised system than a decentralised system.

It's a problem with anything after USB3 in general, bandwidth is very unpredictable.

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, dealing with 50,000 things per second means we need to avoid kernel context switches.

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 heavily.