maxwell86

8 ms·

31.
by maxwell86 5y ago
I drove a similar route as the GP, 1100km round trip for a ski trip to Austria, aiming at 190kph. I didn’t have to tank for the round trip, but I decided to tank on the way back cause in Austria tanking is much cheaper. My car isn’t particu
32.
by maxwell86 5y ago
In Germany, the autobahn is the motorway. I typically drive at 180-190kph, that’s my “relaxed driving” speed. 160kph is “falling asleep” kind of speed unless you have a super loud car.
33.
by maxwell86 5y ago
A 50 minute per session.
34.
by maxwell86 5y ago
I did a similar trip earlier in January. 1100 km from Germany to the alps (550km per way). I had to stop once for the full 1100km trip to refuel (before leaving Austria on the way back cause it’s cheap to tank there, not because we actually
35.
by maxwell86 5y ago
This is not rare. Just open Google street view in Germany. Most buildings are blurrier like this.
36.
by maxwell86 5y ago
Auto complete has worked for everyone that wanted it enough to invest 10 seconds to Google it and copy one line into their confit file for at least the past 20+ years. This just seems to show auto complete with an annoying popup instead of
37.
by maxwell86 5y ago
> To me, the parse() call seems the most volatile -- what guarantees are there that the bytes you just read are parsable? None, which is why, in Rust, parse never throws an exception on a parsing error, and instead, returns a Result<O
38.
by maxwell86 5y ago
> cancellation looks like *the await call* panicking Emphasis mine. In Rust, "cancellation" happens at well defined "await points".
39.
by maxwell86 5y ago
99% of commutes are less than 200 miles. Current car batteries support large numbers of charge cycles and have a capacity that's high enough for these trips. However, many drivers do a bunch of 500+ miles drives per year; 1, 10, or 100
40.
by maxwell86 5y ago
The article clearly states that Foxconn _violently forced_ children out of school to cover their worker shortage. The parent is clearly illiterate and from their tone, they must be dealing with some serious issues. So there is no point in r
41.
by maxwell86 5y ago
> he saw a foreigner whom he believed to be one of the Amazon staff going through his desk drawer and checking the pockets of his uniform on his chair. So an US Amazon employee helped to get this guy and their Familie tortured for two y
42.
by maxwell86 5y ago
As a German citizen, this isn’t nuts. Leaking extremely sensitive user data, like their IP addresses, to third parties, enable them to finger print users. Leaking those to third parties outside the EU, and in particular to companies whose r
43.
by maxwell86 5y ago
> Maybe Im being a bit cynical. If Apple, Intel, AMD, NVIDIA, Arm, Qualcomm, etc. would all contribute to open source to make everything work on all their devices with good perf, then that would be very good for all users. Expecting AMD
44.
by maxwell86 5y ago
> “Americans [that answer surveys] say, 76% to 11%, that..." There, fixed that for you. I don't recall the last time I answered a survey. I have better things to do, like hanging around here.
45.
by maxwell86 5y ago
same, i'd like to see such an approach
46.
by maxwell86 5y ago
Have you taken Rust appart yet?
47.
by maxwell86 5y ago
They've been saying that from the beginning. There are billions of ARM devices, the ability to sell a GPU to each is worth money.
48.
by maxwell86 5y ago
> Wonder if this means Nvidia will jump on the RISC-V bandwagon instead? Nvidia is a big contributor to the RISC-V standard, all Nvidia GPUs have had RISC-V chips in them for many years, etc. So no need to wonder, this already happened,
49.
by maxwell86 5y ago
I always assumed NVIDIA wanted to license IP through Arm just like Arm does.
50.
by maxwell86 5y ago
> No Arm and Softbank said so much last week. Arm does not take profits from Apple CPUs.
51.
by maxwell86 5y ago
IIUC, part of the deal was that NVIDIA would license its designs via ARM.
52.
by maxwell86 5y ago
If you heat the helium enough, yes. But even with 1 order of magnitude less volume, the fluid dynamics are still really bad. These things "fly" like a brick, we are just making this brick lighter and lighter, but a brick is a bric
53.
by maxwell86 5y ago
The math is simple, its just the Archimedes principle, fluid drag force basics, and power law of propelers and jet engines. Archimedes says: m = V * (density air - density helium) that is, the total mass that you can carry (including helium
54.
by maxwell86 5y ago
No, because people buying a luxury air yacht care about going from A to B. If your claim is that there is a market for luxury air yachts that are extremely expensive to maintain, require a huge crew 10x larger than a yacht, are 10x "s
55.
by maxwell86 5y ago
There is a single contiguous memory allocation, which mirrors itself. One thread produces elements and pushes them at the tail (e.g. I/O bytes, in batch), and one thread consumes as many elements as possible in batch from the other end
56.
by maxwell86 5y ago
> Hopefully you’re not looping over all the elements in your deques super often, or there wouldn’t be much point in using a deque! I do this all the time: one thread fills the deque, while another thread consumes as much of it as passibl
57.
by maxwell86 5y ago
> n the context of a generic data stucture, unboxing is not likely to unlock a huge number of optimizations. This is not true, the difference between a Vec<Box<T>> and a Vec<T> is huge. You can't easily vectorize a
58.
by maxwell86 5y ago
Its not only CPU cache, its the whole CPU. Having one function per type results in more instructions in total, cause you end up with more copies of the function, but less instructions when dealing with one type, like in a collection of valu
59.
by maxwell86 5y ago
You can just verify using any language with powerful optimizations and whose generic system supports both boxed and unboxed generics, e.g., Rust. The difference between passing an unboxed generic and triggering monomorphization vs passing a
60.
by maxwell86 5y ago
> At most you’re getting the benefits of unboxing Which is.. 3x? or 10x? > These tests are probably just picking up the cost of an extra allocation required to box a primitive type as an interface. I've seen unboxing deliver 100x

More ›