adev_

34 ms·

331.
by adev_ 5y ago
> As for covering things up, that's a specialty of this field, as any former nuclear insider will tell you. We do not know the same "insiders in the field" then. As a former electrical engineer, many of my friends works fo
332.
by adev_ 5y ago
> It's a feature of many cars, and the majority of them buy a standard well working chip for it (usually from Bosch). We do not have the same definition of "working well" and standard then. On the 6 non-Tesla cars I drove
333.
by adev_ 5y ago
> By the way, the F-35 isn't any more expensive than other aircraft. It is more expensive. And the fact that all "modern" militaro-industriel projects goes over budget is just not an excuse to that. The F-16 program (which
334.
by adev_ 5y ago
> Domain name resolution behaviour should be program-controllable, not system-controllable I disagree, strongly. The last thing I want is to get every of my applications Avahi / Zeroconf aware for DNS or SSSD aware in enterprise en
335.
by adev_ 5y ago
> Right, it's hard to see what the advantage of debit would ever be. Not being able to indebt yourself is THE major advantage of debit card. Not everybody in this world is reasonable when it is about spending and finance manageme
336.
by adev_ 5y ago
> Why would you not see that? The risk profile is well understood, and can be mitigated. So well understood that hacks on ATM happens every weeks :)
337.
by adev_ 5y ago
> Had they chosen Linux then that ATM would still be sitting there with just-an-outdated version of some embedded Linux distro. That's wrong, they would have been in a position to update / maintain themselves their own distro o
338.
by adev_ 5y ago
> The specific argument in this subthread is about whether it's okay to build your business on proprietary software or whether there's too much of a risk that the vendor will stop producing updates It has everything to do with
339.
by adev_ 5y ago
> That is a risk that is common to every single industry, and as such is a risk that is easily understood and quantifiable. Honestly: No If it would be "easily quantifiable", you would not see in 2021 still bank ATM running dam
340.
by adev_ 5y ago
> First, you can't predict solar or wind days ahead in the same way you can't predict rain, days ahead. There are "weather forecasts", not cloud reading. You can. And there is companies specialized in that for the Wi
341.
by adev_ 5y ago
> One can be a fan of something without trying to blindly apply it to areas where it doesn't make sense. Starting a discussion with a "I'm a huge fan" before spending the next 10 min to debunk the thing is not "b
342.
by adev_ 5y ago
> I am a fan of nuclear energy for various reasons, and it's obvious that the safety and waste problems can be solved No you don't from your arguments. > The technology is not there yet. There are a lot of promising companie
343.
by adev_ 5y ago
Fact is that even today (13/10/2021) Germany is still running its electricity production at 51% on Coal, when France uses coal for close to nothing due to Nuclear [1]. And it is very unlikely to change on medium term (next 20 year
344.
by adev_ 5y ago
> so they're unlikely to have the classic C/C++ errors Two things here : - This vulnerability is a logic error (no header => root), not a buffer overflow. It could have happen in any language. - C and C++ don't play in
345.
by adev_ 5y ago
> ou could alleviate this by deferring to whatever build system is called in mkDerivation by providing a short-circuiting shell.nix for every subcomponent (eg. a shell.nix to drop you into somewhere where you can `cargo build`). But IMO
346.
by adev_ 5y ago
> If you need to chase a bug into a more fundamental library, say libc, libpng, or your stack's favourite JSON library, iterating on that code with plain nix ("package-based non-incremental builds") will now take 20 hours
347.
by adev_ 5y ago
Nix, Guix or Spack do that correctly.
348.
by adev_ 5y ago
> Any downstream library team can instantly tell if their change has broken any upstream users because a good CI system will just automatically run all tests of all relevant projects. That way a library developer can either iterate until
349.
by adev_ 5y ago
I am really not convinced of the need of any incremental build system (like Bazel) over Nix excepted if you inherited of a giant mono-repo mess. Decomposing your dependency tree into small derivation pose no problem with Nix. Mainly due t
350.
by adev_ 5y ago
> You still need DHCP for more than one reason: 1) You generally do not need prefix delegation in v6: you use IPv6 like it has been designed too: routable address everywhere, /64 per default and prefix over it. 2) SLAAC is stateles
351.
by adev_ 5y ago
Random one : "When you go SLAAC, you never go back" (sorry for that ). IPv6 does not need DHCP on L2. If you even experienced a DHCP clusterfuck, you do start to appreciate the stateless auto-configuration that IPv6 provides.
352.
by adev_ 5y ago
> Then there is the thing that LD_LIBRARY_PATH and similar are MAJOR security holes, and most systems would be best of to use hardening techniques to disable it (not to be confused with `/etc/ld.so.conf`). I do not consider LD_
353.
by adev_ 5y ago
> To me, C++ is an absolute train wreck of a language and choosing it for a new project borders on malpractice. Personnally I tend to think exactly the opposite. And choosing a brand new hype language because "it's shiny and fu
354.
by adev_ 6y ago
My new born son. Remote working allowed me to spend time with him in his early month. And this is priceless.
355.
by adev_ 6y ago
> We have seen no massive adoption rate growth and we have seen no massive cost curve going down. We have also not seen a lot of gains in overall efficiency. It seems that data says the opposite [1]. I know several datacenters in my regi
356.
by adev_ 6y ago
That is a pretty narrow view. The world does not stop only to cars. Even for Toyota. Fuel cells do not break through in the car industry (because battery do the job there) but do everywhere else. - We now have datacenters and hospitals that
357.
by adev_ 6y ago
So on one side, we have a program that costed > 406.5 Billions (2017) [¹] for a failed jet. On the other side, we have the entire Apollo program that cost $156 billion (2018)[²], was stopped because too expensive. And we never have been
358.
by adev_ 6y ago
I'm curious on you describing the 5+ types of services fdb requires. In my world it requires 1.
359.
by adev_ 6y ago
> Most of the time postgres will do fine. For something that scale horizontally, I would probably recommend to use something like FoundationDB for this use case [^1]. A transactional Key-Value store is exactly what you want for this kind
360.
by adev_ 6y ago
Indeed. Fixed.

More ›