Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Diggsey
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
26 ms
·
241.
▲
by
Diggsey
5y ago
It's clearly not the "only sensible one" given that no other language works the way Go does here. In C++ this is UB, which is bad, but in keeping with the rest of the language. In Rust, the compiler will not allow you to do a
242.
▲
by
Diggsey
5y ago
> We don’t actually know what string theory is, just that it’s a “framework” that encompasses QFT and much more. We can’t predict anything with it now and don’t see any plausible way of predicting anything in the future, > but the the
243.
▲
by
Diggsey
5y ago
What we call "mass" is actually "rest mass" - ie. the mass when the thing is not moving. Photons don't have rest mass because they don't rest. What photons do have is momentum, and so due to conservation of m
244.
▲
by
Diggsey
5y ago
Interesting, but surely the last thing you want is complex mechanical systems involved that will quickly wear out due to lunar regolith, or having to transport large mirrors to the moon? Sure you get losses from wireless transmission, but y
245.
▲
by
Diggsey
5y ago
The article does consider that option via splitting and storage of water, and then recombination via hydrogen fuel cells. According to the article the mass of the storage vessels needed to store 2 weeks of pressurized hydrogen and oxygen ar
246.
▲
by
Diggsey
5y ago
How about two/three sites around the Shackleton crater which beam power back and forth wirelessly across the crater as each site goes in and out of sunlight?
247.
▲
by
Diggsey
5y ago
How on earth does the US have 3.25 million people who can't afford a calorie sufficient diet? If there's one thing you can get on the cheap in the US, it's calories.
248.
▲
by
Diggsey
5y ago
Firstly, 1ms for a 3TB heap size is very unrealistic even for modern JVMs. Secondly, the figures that are often quoted for how long the program must be stopped are for the "happy path" where enough memory can be freed that the pro
249.
▲
by
Diggsey
5y ago
Yeah, I've also seen several academic papers on performance or "optimization" of existing algorithms which just demonstrate a complete lack of knowledge about how those algorithms are implemented in practice. For example, the
250.
▲
by
Diggsey
5y ago
All of those OSes use the same linux kernel, it's only the user-space part that differs. When you run eg. an ubuntu docker image, the entire user-space of ubuntu is running inside the container. Only the kernel is shared with the host.
251.
▲
by
Diggsey
5y ago
Exactly. Plus, you don't even need to spoof anything - you can show the real login page! There are many ways, but one particularly undetectable one would be to clear cookies and local-storage (causing the user to be logged out). Then u
252.
▲
by
Diggsey
5y ago
That's less a definition, and more a description of what UB looks like. Here's a better definition: https://en.cppreference.com/w/cpp/language/ub
253.
▲
by
Diggsey
5y ago
"Undefined behaviour" has a specific technical meaning. In Go, data races can result in UB. In Java, they can't. Java may be non-deterministic, or exhibit unintended behaviour in response to a race condition. UB is strictly
254.
▲
by
Diggsey
5y ago
The fact that they've succeeded in so many different fields implies that their success is due to a combination of compute power & expertise in harnessing that compute power, rather than expertise in all the different fields they ha
255.
▲
by
Diggsey
5y ago
"Astronaut 001, licence to thrill" This is comically cringeworthy :)
256.
▲
by
Diggsey
5y ago
To be clear: I hate that overcommit exists. I think the whole situation the OOM killer makes zero sense for servers. Having plenty of swap can help with programs that use a lot of virtual memory. AFAICT, there's no solution for the cgr
257.
▲
by
Diggsey
5y ago
It is certainly one way to solve that specific issue, assuming the program was written to take advantage of it. As mentioned, there are several other reasons a program may use a lot of virtual memory though.
258.
▲
by
Diggsey
5y ago
Some programs allocate a lot of virtual memory and then don't use it. Also, linux's forking model can result in a lot of virtual memory being allocated if a heavy-weight program tries to fork+exec a lot of smaller programs, since
259.
▲
by
Diggsey
5y ago
Even with a totally plastic material (which is a stretch, since there are certainly granular elements even in clay soil) the material will deform until it fills the gaps around the arch shape. At that point the material itself is forming an
260.
▲
by
Diggsey
5y ago
That's not how that works... Any granular material, even sand, will spread the forces laterally. It's impossible for the full weight of the soil above to be applied to the steel structure. The only reason you need the steel struct
261.
▲
by
Diggsey
5y ago
Also NAL, but I think there's far more of a case that users of Copilot might violate copyright rather than Copilot itself: - Only a very small proportion of Copilot generated code is reproduced verbatim, so if you specifically built
262.
▲
by
Diggsey
5y ago
Yes, perhaps "key" is the wrong term. I intended to refer to the column that is used in the join condition in not so many words. > It's almost always incorrect not to have at least one JOIN condition involve a key. Eh,
263.
▲
by
Diggsey
5y ago
It's a nice visualization, but it assumes the keys on both sides are unique. Usually the key on at least one side of a join is not unique, and sometimes it's not unique on either side. The behaviour in these cases is an important
264.
▲
by
Diggsey
5y ago
IME, it's the following considerations that make back-end development hard: - Fault tolerance. - Backwards (or forwards) compatibility. - Scalability. - Testability. - Everything around state (backup/restore, migration strategies,
265.
▲
by
Diggsey
5y ago
The definition clearly says that `usize` is pointer-sized, and makes no reference to register size, so it seems there's already a pretty clear distinction? If you are specifically looking for a register sized tyoe then you should defin
266.
▲
by
Diggsey
5y ago
size_t is just a type that's large enough to hold the largest possible object. It doesn't necessarily relate to the register size... This means that `uintptr_t` must be at least as large as `size_t`, and so Rust's usage of `u
267.
▲
by
Diggsey
5y ago
Eh, often there is not a clear distinction between the two. Whether an optimization is correct or not depends heavily on the interpretation of very subtle aspects of the specification. For correctness, it is most important that the programm
268.
▲
by
Diggsey
5y ago
The permissions system I designed at work solves the search problem, although it is not as powerful as what's described in the article. We have three main concepts in the sytem: - Capabilities (eg. "read profile") - Selectors
269.
▲
by
Diggsey
5y ago
> For the exploitability, it doesn’t echo and the rest of the parameters don’t seem like to be controllable. Thus I don’t think this case is exploitable. It's lucky that `CFStringCreateWithFormatAndArguments` doesn't appear to
270.
▲
by
Diggsey
5y ago
Strange. I'm using firefox on windows and didn't notice any problems.
More ›