News for hackers. Stuff that matters.

bobdobbs666

Re:Tesla to run reduced output in Shanghai in January on Wednesday December 28, 2022 @03:26AM (#34158834)
https://pubmed.ncbi.nlm.nih.gov/35027728/

https://pubmed.ncbi.nlm.nih.gov/33884644/

here are a couple studies showing that covid can cause immune system deregulation effects.

there are plenty more if you go and look.

even mild cases have been shown to cause last impact to the immune system.

There are several preprints that speculate this immune system deregulation is partially responsible for the abrupt spike in rsv and flu happening.

Re:Bazel 2.0 on Monday December 23, 2019 @07:32PM (#21868854)
Lack of docs plus lack of user base is also a giant failing of bazel. It’s almost always impossible to figure out something I could make happen 6 ways with most other build systems make work in bazel. And there’s little community so now instead of getting work done I am debugging bazel source.

Also building distributable packages with bazel never seemed to work well due to the constant aliasing of so files. Things that would work in the direct bazel build would fail in packages and vice versa so now we had even more pain.

Trying to suck up just header files and multiple so files was always arcane bullshit as well.

We did work with git and other such functionality, but if you had to build a package from another build system to bring into bazel there were always annoying pain points.

Also bazel managed to bring in implicit dependencies in our system so that clearly isn’t something bazel magically handles but was rather a product of your expertise.

After reading build systems ala carte I am just more convinced bazel is not the build system that I would really ever need. I’m not sure that build system exists yet to be honest :). But in the work I do other systems solve my problems better.

Re:Bazel 2.0 on Monday December 23, 2019 @01:59PM (#21866154)
I was subjected to bazel on a small project because the manager insisted we use it. The rest of the company used a number of either custom tools or cmake or premske.

It is utter hell when you have tons of third party libraries (internal or external to the company) that you don’t have the source to and it is especially painful when trying to integrate bazels behavior against other build systems. Also bazels packaging and use of internal symlink renaming was a constant source of suffering. Bazel pretty much destroys a number of totally valid work linux commands for looking for so files.

Bazel might be useful in the case of a monorepo with a massive engineering pool AND a massive cloud infrastructure backing that repo to handle all the artifact sharing, but after having used cmake, premake, waf, random perl and ruby scripts, or just checking vs projects into perforce manually, I’d pick any of those before bazel for most projects. I say that having worked on code bases from a few 10s of thousands to 25+ million LoC with teams small, large, and distributed.

Bazel probably has its place but I have yet to find it.

Re:OMG: Our Machinery Guidebook on Thursday December 12, 2019 @12:45PM (#21774218)
http://www.cs.unc.edu/~smp/COMP205/LECTURES/ERROR/lec23/node...

They meant fixed precision not fixed point math.

Re:OMG: Our Machinery Guidebook on Thursday December 12, 2019 @06:30AM (#21771001)
Pragma once only prevents double inclusion within the translation unit.

On large projects bad header hygiene can cause significant compilation overhead.

Re:OMG: Our Machinery Guidebook on Thursday December 12, 2019 @06:26AM (#21770979)
This is pretty much the standard way to write ABI compatible plugin interfaces in C that can be easily bound to multiple other languages.
Re:OMG: Our Machinery Guidebook on Thursday December 12, 2019 @06:24AM (#21770966)
The patriot missile system tended to miss due to numerical error accumulated due to using floats to count time.

http://www-users.math.umn.edu/~arnold//disasters/patriot.htm...