but a room-temperature superconductor would certainly lower the operating costs of all of the prototype fusion reactors that currently exist.
1,288 karma · joined June 2, 2011
but a room-temperature superconductor would certainly lower the operating costs of all of the prototype fusion reactors that currently exist.
not that i think it matters that much. the paper doesn’t indicate that synthesis is a particularly sensitive step.
i mean the search space is unfathomably large, so i suppose it’s possible that something like this exists, but the paper quality itself doesn’t.. spark joy? :)
i’ll maintain a healthy level of skepticism until some real materials scientists opine and/or someone else is able to reproduce.
extremely hard is underselling it somewhat :)
for sure. and, as we all know, society only exists so that companies can make money. where would we be without bezos, musk, gates, et al.
and i don’t think you’d expect it to. the increased supply needs to hit the market first. depending on how that money is distributed, that could take a long time. also remember that QE has been central fiscal policy in the UK and US since basically 2007. and it’s safe to say that concentration of this wealth is.. very high.
> has UK M2 declining [..]
it becomes a bit more sobering when you look at the full scale on that graph (when the y-axis starts from 0). it’s a metaphorical deck-chair-thrown-off-of-the-titanic amount of decrease.
i think it would be sensible to add unsigned, and disallow implicit conversion (definitely at least narrowing conversions).
but java is a distant world to me.
nvidia being the only viable solution for 3d on linux is a bit of an exaggeration imo (source: i did it for 5 years), but that was a long time ago: we have amdgpu, which is far superior to nvidia’s closed source driver.
linux’s amdgpu is far better than the nvidia-driver.
which makes sense. but there’s a reason why victims of crime aren’t allowed to be jurors of their own case.
reading from stdin isn’t challenging, nor writing to stdout. if someone can’t imagine why that might be useful, then i’d argue their journey as a software engineer is either at its end, or right at its beginning.
at the cost of potentially sounding inflammatory, “get good”.
regardless, if this described how drug dealers engineer the distribution of their product to optimise addiction, we would not be celebrating it as an engineering marvel.
absolutely. unfortunately, saftey oriented proposals tend to focus on a weaker warning-esque approach ([[nodiscard]], contracts, etc.), which, in my opinion, will ultimately only make things worse. i'll stay away from my type-systems-are-great soapbox :)
the refusal to break ABI, remove non-destructive moves, the strengthening of concepts more akin to their original proposal, are not even on the horizon of discussion, despite us having exemplars of all 3.
it's perplexing, to say the least.
i'm not sure if this is the case. unique_ptr doesn't really do much other than use the type system to ensure that only one instance of the pointed-to value exists at once. as far as i understand, it doesn't strictly do anything at runtime.
i think the original commenters point only talks about how bad TSTZ is as a storage format, and that TAI is not only better than timestamp with time zone, but also UTC in almost every measure - something i agree with - not that time zones are useless. if you need the time zone to be recorded, i think the most sensible thing would be to record it independently.
so should we not store that data, then?
> The "Date" header in emails include the timezone (or UTC offset) of the sender [...]
i don't think that's strictly true - at best it may contain the timezone configured on the local machine when the e-mail was sent (what happens when you fly?), at worst it always contains UTC anyway for privacy concerns. in either case i don't think most people know this is a field that is transmitted, and it's presumably something the sending/recieving party likely already know each other (for personal communication)
> A SQL query that build a report of restaurant orders per hour needs to normalize for time of the day in local time [...]
i'd posit that that data should be stored principally then, surely?
fundamentally, why should the timestamp contain two data points? i wouldn't expect the database to have a single column for, say, my user id and registering user-agent string, so why would i expect it to combine a point in time with a vague location?
that does not surprise me at all, unfortunately.
> One cool thing in MacOS that Windows can't do is aggregate of audio devices/interfaces.
it does come at the cost of latency & jitter: fundamental issues that ultimately stem from having two separate audio clocks. and it's not really a specific limitation of windows, which tend to use ASIO for low-latency audio. there's nothing stopping a an aggregate ASIO driver from being written, i just can't imagine it'd be that useful, indeed, i've only ever used the macOS aggregate device a handful of times, mostly only to try it out.
requiring air is not a limitation, it’s a feature.
holmes deserves punishment on some level, certainly, although honestly i feel 10+ years might be a bit much.
where is this zeal for her male analogues? they’re all playing the same game.