withinboredom
Joined 8,485 karma
[ my public key: https://keybase.io/withinboredom; my proof: https://keybase.io/withinboredom/sigs/73lKYnYnXl8zj6I5he8z9w__Y_egIUOa-zxiXwaFMDE ]
email me at landers dot robert at gmail
- withinboredomWe use dedicated machines for our runners. Each machine has like 16+ cpus, 64gb+ of ram. Costs are <2k per month. This pricing change would have cost more than the servers we're running on.
- I also note that you don't mention the cache-line contention issue when accessing atomics in a multi-threaded context. That's a huge performance issue with lock-free constructs.
- I wish I could have waited one year. 0/10, would not recommend that proceedure. FWIW, it's a very common, usually also scheduled long in advance (even in the US). Pretty much every man has to get one over 40; so it makes sense the wait list is long unless you've got something else going on.
- They do? If they misdiagnose something, you can end up in the slow line instead of the fast one, or vice versa. Compared to them, you have no influence.
- In my case, there was no faking urgency. I was pointing out that urgency puts you in a different line that gets priority (basically, cancellations from the longer line).
For some other things, you can travel further away to where there is less demand for what you need, and if you're willing, you don't have to wait as long. These are all different "lines" and they're the ones doing the schedule.
- Don't forget to budget power to run the coolant heaters and prevent them from freezing in the shade.
- Lets not forget that you have to launch that liquid up as well. Liquids are heavy, compared to their volume. Not to mention your entire 'datacenter' goes poof if one of these loops gets frozen, explodes from catching some sunlight, or whatever. This is pretty normal stuff, but not at this scale that would be required.
- This isn't that new. (see: FASTER: A Concurrent Key-Value Store with In-Place Updates. 2018 ACM SIGMOD International Conference on Management of Data and related papers)
However, this is well written and very easy to read.
- There are multiple lists here in the NL. I called for a surgery and got put on the fast list (she said that if it weren’t urgent, it would be over a year wait). Your doc has a lot of influence on how urgent things are and how far you are willing to travel. I got in to see a therapist in a matter of weeks, because I was willing to travel out of the city; otherwise it will be months. The doc can see the lines and give you recommendations; all you have to do is ask to be seen sooner.
- If latency isn't important. Something like this could work. For applications where latency or linearizability is important, it probably won't work.
- I was using an LLM to summarize benchmarks for me, and I realized after awhile it was omitting information that made the algorithm being benchmarked look bad. I'm glad I caught it early, before I went to my peers and was like "look at this amazing algorithm".
- Have you ever followed citations before? In my experience, they don't support what is being citated, saying the opposite or not even related. It's probably only 60%-ish that actually cite something relevant.
- I don’t think they meant literally “any” but more like a device with a speaker could be delivered to you that has a speaker/microphone. Like a Bluetooth speaker you order of the internet. It seems it would probably have to be personally targeted to you, but in that case, there are probably simpler ways.
- The main issue is that there isn't any governance to the plugin store. Once you have a plugin in there, you have free reign to do whatever you want with it. Getting it in there is a PITA though. For example, a library author and I created a plugin, but they wouldn't let me submit it because I wasn't the other author, and they wouldn't let him submit it because he wasn't me. True story.
- They didn't provide any accounting from facts. Did farms usage of nitrates increase? We don't know. Are there more or less farms? All we know is that they assert the datacenter now exists and since then nitrates have increased. It doesn't account for all the variables nor provide a likely explanation for how this could be true; it is only a possibility of many.
- Or rather, a hypothesis disguised as an explanation. It ultimately said these nitrates come from farms, and this new datacenter is exacerbating it. The root cause is still the farms, though.
- Especially when you're sending some quick scratch code in a slack message.
- does it though? It provides a hypothesis, not an explanation.