You can rent movies online though. Steaming catalogs are a moving target but online rental catalogs usually have most stuff available. You also don’t need to drive down to the store and risk getting a scratched up disk that skips over a key scene when renting online.
The main sting here seems to be that MemorySegment when allocated from Java code requires bounds checks on all accesses, which the JVM cannot optimise away on random accesses.
However, MemorySegment itself already supports unbounded access when wrapping a native pointer. It’s necessary for even basic interactions with native code (e.g. reading a c-str).
It should be easy to “wash” an off-heap MemorySegment through native code to obtain an unbounded MemorySegment from it. Something like:
void *vanish_bounds(void *ptr) { return ptr; }
I think it would be nice if the FFI provided a way to get an unbounded MemorySegment without resorting to native code hacks though. It can obviously be made restricted like unbounded MemorySegment’s already are.
That should take most of the sting out of this proposal (although it still sounds like a painful transition for a very modest gain).
Rents are high because people will pay that much. House prices are high because people will pay that much. If investors could not profitably buy and rent an house at the prices being asked then they wouldn’t buy them.
Increase housing supply and prices will come down. Decrease demand and prices will come down.
Currently there’s pressures pushing up demand like large scale immigration + an aging population meaning less children living at home, and factors pushing down supply like skills and materials shortages in the building industry due to massive government infrastructure projects sucking up supply and zoning rules preventing housing being built in more desirable locations.
> I suspect you’re mistaking not wanting/being able to speak English for not wanting to interact with non-Japanese people.
Language doesn't have to do anything with it, it's more base than that. On a crowded subway for example, Japanese people won't want to sit near a white person or might get up and move if you sit near them.
People here avoid sitting near everyone. If you have 5 bags of stuff(cause that what tourists do), or even if you are overweight (something not that common here, and space-wise is a wise decision) then even worse.
But I don't think you are trying to have a conversation here, than just trying to push "facts" you read on reddit.
Not overweight and no bags at all. And it's one thing if they were already sitting and then get up if you sit next to them, but were fine sitting next to other Japanese. They are not exactly subtle about it.
I'm not trying to push anything, just recounting my own experiences.
In Australia, we’re moving towards dynamic operating envelopes for solar and other “distributed energy resources”. That potentially includes EVs and ACs.
The idea is the solar inverter is sent a dynamic stream of operating constraints by the distribution business based on network conditions.
It’s already being piloted in places like South Australia, which has very high solar penetration. Regulations are also moving towards requiring smart meters at all households (already the case in Victoria) and all new inverters be network connected.
This impacted home and mobile internet as well as telephone systems. It also had ripple on effects. Optus was the backup communication provider for the Melbourne metro. The metro’s main communication system was down in the morning and they had no backup available causing chaos on the train network.
We were lucky our home internet is not with Optus but some colleagues were out of contact until 3 in the arvo.
I wonder what procedures Optus had in place to even contact their on call engineers in such a wide spread outage.
I wonder if they even plan for that at all or if the first few hours were a scramble just to get in contact with the right people.
> The evidence for the sun inducing skin cancer is not strong.
Say what!? The main cause of skin cancer is UV radiation from sunlight.
Go spend a day outside unprotected from the sun in the Australian summer and tell me otherwise. If you have a light skin pigmentation you’ll be in physical pain and cold shivers from the damage to your skin. Keep damaging your skin cells enough times and you have a recipe for skin cancer.
Australia and NZ have sky high rates of skin cancer (like significantly higher than any other countries in the world) because they have a large population of people with little natural protection living close to the equator where UV radiation is high.
The evidence for sunburn inducing skin cancer is strong. The evidence for sun exposure is far more mixed, especially with regard to melanoma.
That said, there probably is no such thing as “safe unprotected sun exposure” in Oz summer, at least if you’re not very dark-skinned. Very fair-skinned people can develop the beginnings of burn in a literal matter of minutes.
> The main cause of skin cancer is UV radiation from sunlight.
This is not true. The main cause of skin cancer for most people is often unrelated to sun exposure. And sunscreen, ironically enough, is a great contributor towards cancer.
The sun doesn't give us cancer. That it's somehow "harmful" for people to be in direct sunlight is an absurd notion. Getting strong sunlight everyday for an hour or two won't kill you or give you cancer. It'll be great for you.
In my experience using linear search it’s easy to introduce accidental O(n^2) time complexity into a function, which can really come back to bite you.
The benchmark linked looks like the best case for linear search - searching a packed array of ints. Even then from the results after just 256 elements binary search starts to win out (comparing the optimised implementations of both). By 1024 elements the difference between O(log N) and O(N) complexity is clearly starting to dominate the results.
For more complex comparison functions, and pointer indirections (e.g. searching arrays of heap allocated objects), I’d assume the lower time complexity of binary search would dominate results even more.
The issue is the bar keeps moving on where it makes sense to switch from one approach to the other.
I recently implemented the Adaptive Radix Tree from https://db.in.tum.de/~leis/papers/ART.pdf in Rust. It defines explicit node types with different trade offs for search and memory complexity in order to improve overall performance and depending on prefix sparsity, etc; a 4-child node 16, 48, and 256. The 16 and 48 are kept sorted (the 256 has implicit sorting because it's just byte->child) so binary search can be used (with SIMD optimizations)
But in reality, my benching showed linear scan outperforms this fairly consistently and the cost of keeping the keys sorted is not justified (except that it makes ordered iteration easier, so that's the trade-off) -- but evidently did not at the time the paper was written (2016 I think?).
I'm sure there's plenty of examples like this, and I'm sure we're likely using datastructures all over the place that were built under the assumption that linear scan was expensive, and optimizations were added to hash or sort data and those optimizations may actually be hindering rather than helping.
I don’t really follow this. What makes s-expressions a superset of markup languages?
What can’t you express in XML that you can with s-expressions?