TexasMick

6 ms·

1.
by TexasMick 1mo ago
It's Clacton, farage chose it for a reason. It's full of retirees and Brexit voters It's hard to explain what seaside towns are like if not from the UK but I can tell you that this is the end of farage and reform. He didn&#x2
2.
by TexasMick 1y ago
They have the source code on their website: https://www.microchip.com/en-us/tools-resources/archives/mpl...
3.
by TexasMick 3y ago
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.
4.
by TexasMick 3y ago
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
5.
by TexasMick 3y ago
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
6.
by TexasMick 3y ago
You can always merge feature branches together to check for conflicts
7.
by TexasMick 3y ago
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 l
8.
by TexasMick 3y ago
Tbh they should really just learn it. It's super simple and powerful
9.
by TexasMick 3y ago
It reminds of when someone told me git submodules are slow. They just forgot about shallow clones..
10.
by TexasMick 3y ago
It's kinda crazy argument, I think data loss is way more likely with a centralised system than a decentralised system.
11.
by TexasMick 3y ago
It's a problem with anything after USB3 in general, bandwidth is very unpredictable.
12.
by TexasMick 3y ago
Bulk has bus error detection and so you shouldn't get errors
13.
by TexasMick 3y ago
I basically refuse to fix other people's git issues because 99% of the time they don't know how the basics.
14.
by TexasMick 3y ago
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 t
15.
by TexasMick 3y ago
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.