Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
adev_
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
181.
▲
by
adev_
2y ago
> So each night a different reactor ramps down and gets poisoned. They do it intra-day. You can currently follow that through their monitoring [^1] > Nuclear has so small margins that if you tell the investors of a new nuclear plant i
182.
▲
by
adev_
2y ago
That is deeply incorrect. EDF as hugely profitable and brought back billions to its main stock holder (the French state) for multiple decades. The recent debt crisis has mainly two causes: - The state has used EDF to shield consumers agains
183.
▲
by
adev_
2y ago
Nuclear can scale up and down. It can do so from 20% to 100%, Reducing under 20% is problematic because it implies a reactor shutdown and restart. 20% is more than enough to modulate side by side with renewables. The French Grid does that a
184.
▲
by
adev_
2y ago
My still-running heat pump from 1981 is not in the list. Unacceptable ! :)
185.
▲
by
adev_
3y ago
Reddit and Forums are full of people with similar experience. Canonical currently uses this "psychometric test" as a decisive critera for candidates https://www.thomas.co/sites/default/files/2019-08&
186.
▲
by
adev_
3y ago
> It's still bad they didn't file a CVE for it, knowing that other languages did so. It reduces trust in their ecosystem. Curiosity question: Do you know if python has also a CVE for this exact same problem ? I am not able to f
187.
▲
by
adev_
3y ago
> My understanding of the vulnerability happens because a different process interleaves access to the same object in the file system between the time of check (TOC) and time of use (TOU) leading to the TOCTOU bug. And this isn't a v
188.
▲
by
adev_
3y ago
The answer to that is there: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n40... It is mainly wording around specifying that the result of a concurrent access can not be guaranteed.
189.
▲
by
adev_
3y ago
> The behavior is undefined if the calls to functions in this library introduce a file system race, that is, when multiple threads, processes, or computers interleave access and modification to the same object in a file system. There is
190.
▲
by
adev_
3y ago
> There seems to be no reason this shouldn't have been a C++ CVE other than the fact that C++ community has different standards for what constitutes safety A security report has been filed for both compiler and actions taken for bo
191.
▲
by
adev_
3y ago
> The GP might have gone a hair too far in saying that C++ “does not consider it a problem at all”, but they’re correct that C++ compiler/stdlib maintainers do not consider it a vulnerability. No this is also just plain wrong. It wa
192.
▲
by
adev_
3y ago
> Take for example CVE-2022-21658 ( https://blog.rust-lang.org/2022/01/20/cve-2022-21658.html ) in Rust, related to a filesystem API. It's true, this was a CVE in Rust and not a CVE in C++, but only bec
193.
▲
by
adev_
3y ago
It is currently pretty clearly describe. Compile it in LGPL mode and you are good for propriétaire use cases. There is nothing fundamentally dangerous with the LGPLv2.1. It is mainly annoying in case of static linking due to the obligation
194.
▲
by
adev_
3y ago
> What, suddenly your are talking about blackouts? Hows that? In your original comment you spoke about prices. Please read my section about peak power again. Their no mention of prices :) The main concern about peak power is related to t
195.
▲
by
adev_
3y ago
> If it's only 10-15 days a year then it should not put consumers and businesses into problems either, no? Are you saying that 10 or 15 days of blackout per year at the level of the European is an acceptable situation to have ? If
196.
▲
by
adev_
3y ago
> If there is a large difference between prices during the day then there is a large incentive to build daily storage. Real peak does not happen during the day. The real peak happens around 10-15 days per year, during winter and when tem
197.
▲
by
adev_
3y ago
The EU electricity market is very interesting if you are a trader. For everyone else, It is a giant shit show responsible of a price increase of around x2 in the last 3 years. And there is not a single valid physical or technical reason to
198.
▲
by
adev_
3y ago
It does not affect only Europe. It is everywhere where Russia has interests. And currently way more influential that it should be. For the ones of you that speaks French, try to search on YouTube or the average social media topics like &quo
199.
▲
by
adev_
3y ago
> where a GC would help (e.g. when there is no clear ownership hierarchy but a lot of mutual dependencies between objects) Not really. This is a straw man argument. Having large graph of object with mutual dependencies represented as ref
200.
▲
by
adev_
3y ago
> You don't need to go that far for GC's bad rep considering that excruciatingly slow Python can be found TODAY! To be fair, the GC is probably the last reason of Python speed problems. Many languages also designed with GC perf
201.
▲
by
adev_
3y ago
If you take the top5 of the top500 (01/2024): - Frontier: Liquid cooled - Aurora: liquid cooled - Eagle: liquid cooled - Fugaku: liquid cooled - Lumi: Liquid cooled with heat recycling. The need for liquid cooled arrived with the usage
202.
▲
by
adev_
3y ago
> It always made me wonder why liquid cooling wasn't more of a thing for datacenters. Liquid cooling is almost a defacto-standard in data centers in the HPC world. The Top of the TOP500 machines are all liquid cooled. Not by choice,
203.
▲
by
adev_
3y ago
> France cant do this. Why... I dont know why. Maybe because the are more desciptive. I would bet that a part of it can probably be blamed more on Parisian being Parisian than on the French themselves :)
204.
▲
by
adev_
3y ago
> For most people it's their 3rd or 4th or 5th language, and they were always so full of joy and happiness than I was trying my best. I think this is currently pretty typical in any language. In my experience, Non-native speakers ar
205.
▲
by
adev_
3y ago
Yes. Several alternatives have been available for a while. The success of Victor has been to make the C++ committee accepts the idea that a new formatter was necessary and to bring <format> in the STL. This was not a small task: The c
206.
▲
by
adev_
3y ago
<iostreams> are currently a good example of pure product of the 199X/2000s when the hype about Object Oriented was around its peak. Almost everything related to c++ iostreams has this code smell of OOP pushed too far: - Usage of
207.
▲
by
adev_
3y ago
Thanks for the experience sharing and the blog, it is very interesting to read and your humility about the feedback is definitively appreciated. I currently also did my own DIY EVSE charger mainly for fun [1]. If you are interested about th
208.
▲
by
adev_
3y ago
> To me more surprising is that Fiat 500e was higher in the ranking, despite costing more and having smaller battery. The buy Price tag is not the only thing that people are looking when buying a car. People do care about maintenance and
209.
▲
by
adev_
3y ago
> EnergyWende" is not a German word. While Java is using Camelcase, German is not using Camelcase. Quick question, outside of the necessity of CamelCase. Are water dam operating companies insured up to the damages of a damn rupture
210.
▲
by
adev_
3y ago
It is wise to not combine sarcasm and ignorance in the same sentence. That allows to avoid looking like a fool. https://world-nuclear.org/information-library/economic-aspec...
More ›