Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
keldaris
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
keldaris
5y ago
The AVX-512 story is just insane. I can't even begin to imagine the kind of corporate dysfunction that leads to, first, at long last introducing the biggest change in the instruction set since the Haswell era into the consumer CPU line
32.
▲
by
keldaris
5y ago
So, they're effectively killing off AVX-512 in the consumer space before it even really caught on. Makes me wonder whether AMD will bother with it at all. Either way, given the QoL improvements that were in the instruction set, this is
33.
▲
by
keldaris
6y ago
> There's surely no excuse for this The "excuse" is greppability since static has three completely different meanings in C and the desire to clearly denote global variables is fairly common. The same reasoning goes for the
34.
▲
by
keldaris
6y ago
That varies by country and sometimes even by university. In some universities there are far fewer teaching positions than staff scientist jobs, particularly when you count research institutes, while in others a typical teaching load without
35.
▲
by
keldaris
6y ago
I'm a theoretical physicist. UBI would absolutely free me and most of my colleagues from grant writing (and IT freelancing, which frankly has better ROI at this point). I do basically all of my research on a mildly high end home comput
36.
▲
by
keldaris
6y ago
Except people do in fact ship large C projects all the time. The productivity gain associated with moving from assembly to C is undisputed and vastly exceeds any alleged productivity gain associated with moving from C to modern C++. Pretend
37.
▲
by
keldaris
6y ago
There is no way to use the STL and other template code and still have reasonably sized projects do full builds in seconds. That's just an empirical fact. The only way to get C-like compile times is to essentially write C, with minor ad
38.
▲
by
keldaris
6y ago
> Only an extraordinarily ambitious personal project would experience a significant amount of build latency on modern compilers and CPUs, no matter what approach is used. If only that were true. If you write modern C++, use the STL and p
39.
▲
by
keldaris
6y ago
In my experience, you can just do full from-scratch builds in under 10 seconds for any sanely sized codebase (say, under 1M LoC conservatively). This obviously assumes the "orthodox C++" part, so YMMV wildly depending on how far y
40.
▲
by
keldaris
6y ago
The same is also true of the author's previous engine [1], written in C99. Would love to get the author's take on the costs and benefits of switching to Rust on the basis of what's effectively a reasonably sized real world ca
41.
▲
by
keldaris
6y ago
That's a completely fair point, but very subjective. There are lots of people (myself included) who feel exactly the opposite way.
42.
▲
by
keldaris
6y ago
The E14 also has a proper Thinkpad keyboard (or the best you can still get, at least). The difference is profound.
43.
▲
by
keldaris
6y ago
Could you elaborate in more detail? Given your wife's background, I'd guess you were referring to people with pre-existing hyperparathyroidism who are therefore prone to quickly develop hypercalcaemia from even modest Vitamin D su
44.
▲
by
keldaris
6y ago
Russia ceded an immense chunk of its most prized territorial posessions, leading to 11 countries declaring independence and defaulted on almost all of its international obligations. In fact, the harshness of the terms proposed by the German
45.
▲
by
keldaris
6y ago
5 billion franks, the equivalent of hundreds of billions in today's currency (the exact amount is difficult to calculate for obvious reasons). It was significant enough to promptly cause an asset bubble in Germany when the French paid
46.
▲
by
keldaris
6y ago
Although the issue is complex, a very dominant part of the "some reason" was that the German army never really experienced an unequivocal final military defeat (although it was clear to the high command that the war could no longe
47.
▲
by
keldaris
6y ago
There is plenty of proof of long term and potentially permanent side effects, including some that are uncorrelated to disease severity. It's also true the relative prevalence of such side effects is far from well understood, but that i
48.
▲
by
keldaris
6y ago
Technically, I'm in a slightly similar position to yours as I had an uncommonly annoying respiratory infection during the last week of February (I am not in a disease epicenter, however, so my Bayesian prior is much weaker). I don'
49.
▲
by
keldaris
6y ago
What would knowing for sure change for you? As you correctly noted, antibody levels seem to decline fairly quickly, so it's not like you can rely on immunity. It's true that there's a long and growing list of complications as
50.
▲
by
keldaris
6y ago
I deliberately made no comment on the necessity of wearing the respirator in the first place - that's a separate question. I'm simply saying that if you're going to the trouble of actually wearing a respirator, do it properly
51.
▲
by
keldaris
6y ago
> Boom, you're practically guaranteed not to get it. Not without eye protection you're not. You're also practically guaranteed to wear the respirator incorrectly. Wearing them correctly requires training, absence of facial
52.
▲
by
keldaris
6y ago
Yes, that's why I'd love to get an antibody test right at the end of the isolation period. If that's impossible, that might be a reason to do the RT-qPCR test, but in that case it's probably still optimal to do the test
53.
▲
by
keldaris
6y ago
I'm not sure I would volunteer myself because, really, what information is the test going to give you? If you test negative, the instructions are still to self isolate (and rightly so, obviously). If you test positive, there's no
54.
▲
by
keldaris
6y ago
I'm a physicist specifically working with magnetic systems, but I have very little pre-graduate teaching experience, so take this attempt to answer the question with a grain of salt. The reason some people regard Faraday's origina
55.
▲
by
keldaris
6y ago
This is probably a reasonable point in a subset (and mindset, frankly) of C++ that has very little overlap with the subset of C++ I use. Every C++ codebase I work on has RTTI (and exceptions) disabled immediately, so dynamic_cast isn't
56.
▲
by
keldaris
6y ago
Yeah, this is why I emphasized that these are prescriptions tailored to my personal usecases and style, not something that's supposed to work for everyone. I don't do anything remotely Java-related, so I have no opinion on your JN
57.
▲
by
keldaris
6y ago
That's true, but there's a reason I chose not to list it - this has never actually saved me from a bug, ever. Of course, as I said, your mileage may vary.
58.
▲
by
keldaris
6y ago
I'm sure this will be controversial, but my attitude towards C++ type casting is much, much simpler. 1. I only use static_cast, the other three C++-specific casts are, in my opinion, somewhere between useless and harmful. 2. The only m
59.
▲
by
keldaris
7y ago
> which is crazy because there's no cost if you don't raise one This is just false in the general case. The presence (potential or actual) of exceptions often just serves as an optimization barrier in current compilers. That&#x
60.
▲
by
keldaris
7y ago
It's a reference to [1] and a mindset arguably most common in the gamedev world that emphasizes simplicity, pragmatism and performance (including compile time performance) over many aspects of "modern C++". I've found it
More ›