xxs

16 ms·

331.
by xxs 1y ago
>5-bit SSL keys. 34 requires 6 bits, though
332.
by xxs 1y ago
if the dispatches do use vtable they won't be inline and won't be faster. The real deal is inlining when necessary, which inheritance doesn't really prevent.
333.
by xxs 1y ago
No, Java does Class hierarchy analysis and has multiple way not to use v-table calls. Single site (no class found overriding a method) are static and can be inlined directly. Dual call sites use a class check (which is a simple equality), c
334.
by xxs 1y ago
Java strings enjoy heavy optimizations, including SSE4.2 and AVX intrinsics. Implementing your own byte[] wrappers (which Strings are) might be useful however it won't replace the built-in Strings. In short: a general purpose String su
335.
by xxs 1y ago
no, mmap is a system call; the memory allocators tend not to use syscalls (often at all) as objection instantiation is very common; also it has to be concurrent and what not.
336.
by xxs 1y ago
Both allow to have software developed for by any 3rd parties - that should include any and the original device seller should not be able to control the distribution. If you really ask: xbox is pretty much the same as an x86-64 PC, running W
337.
by xxs 1y ago
Indeed, I don't see any need to have a tree as a language primitive along with a traversal function (iterator). Tree traversal is not really different than iterating over a vector/list. E.g. even java has stuff like: TreeSet.forEa
338.
by xxs 1y ago
The article mentions one year test at 800C being annealed. I suppose you meant thermal cycles?
339.
by xxs 1y ago
1000MPa is similar to the bolts used in automotive industry, so totally - but not with a bronze age style metallurgy.
340.
by xxs 2y ago
About the ordered removal, if it's not very common, using tombstones (a constant to denote no element) is fine. Too many tombstones would need a compaction phase and still it'd work way better than a linked list. Personally I have
341.
by xxs 2y ago
>Especially if you're trying to be memory efficient Linked list have higher const cost memory wise compared to array backed structures. Even when an array back structure is half empty it's still takes less memory.
342.
by xxs 2y ago
>actions trump asymptotic complexity Which operation of a linked list has any better complexity. The only one I can think of is a frequent removal of random elements in the middle -- and opt not to use tombstones.
343.
by xxs 2y ago
Linked lists have higher constant const memory wise, much slower to iterate, effectively removals of a random in the middle are the same as vector. When used as queues the ring buffers are better for most applications. Their prime use is th
344.
by xxs 2y ago
If anything those Tunisian folks would have to reduce the price to compete. The tariffs go straight to the US coffers at the customs, nothing to do with the farmers.
345.
by xxs 2y ago
>or worse, adding them to hashCode but not equals That's proper bad, however it should be noted in a pull request and explained how hashCode operates - people learn and improve. > there's a hidden dependency between changes
346.
by xxs 2y ago
>Doesn't everyone just use Objects::hash? I hope they do know better, it's actually rather poor. 1st it should not be used for a single parameter - just use hashCode() directly and ensure non-null in the c-tor (or Objects.hashC
347.
by xxs 2y ago
>all methods of class Object finalize() is actually is a very hard mode; I'd not expect any extra senior to be able to explain it properly (incl. the semantics of JMM, the fact half created objects can be finalized; the resurrec
348.
by xxs 2y ago
>It's many thousands of lines in any real project. I dont use lombok and the latter has been actively removed. If you have access to records, lombok is just bad. Even if you dont have - public final fields are sufficient in most cas
349.
by xxs 2y ago
>There are two of us! Realistically, I have trained quite a few folks on my own. >I think it's because devs have an preference for symmetry. Another option is that's the default for all IDEs auto gen, so few clicks/taps
350.
by xxs 2y ago
>"just working" and of course the getters/setters will grow as you add fields... The issue is having plainly useless getters and setter (just use public fields); along with the fact that mutable hashCode/equals
351.
by xxs 2y ago
>add them to hashCode and equals (or worse, hashCode OR equals) That's a fundamental misunderstanding of hashCode, and lombok makes no exception. Not all fields need to be used to calculate hashCode, it makes the overall performance
352.
by xxs 2y ago
>Now, if only I could get devs to stop using lombok.... that's actually not too hard. It has happened to get them all converted to avid opponents of lombok.
353.
by xxs 2y ago
Usually the home country or other touristic destinations. I'd consider that US has been the country with the highest crime... and very obvious police presence compared to any other place visited (I've traveled fair amount)
354.
by xxs 2y ago
Not wanting to spend money there likely comes 1st, being sent to an adventurous free trip South is an extra bonus.
355.
by xxs 2y ago
The way I read it was not if it had effects (of course it does) but mostly how it'd be perceived personally: "I was American, I think I'd be pretty happy about that"
356.
by xxs 2y ago
>friend of mine from Europe Always reminds me how Europe is viewed as a single entity (I guess minus Ireland and England, though)
357.
by xxs 2y ago
The economy being worse is too far of a connection. Most tourists and talented workers won't be visiting blue color farmers areas in general
358.
by xxs 2y ago
This is rather old[0] but still relevant. Surprise #2! A popular open-source framework writes to final fields after object construction via generated bytecodes!... This optimization of the final field is *the* main optimization performed
359.
by xxs 2y ago
>but please come up with something to discourage mutability) Records?
360.
by xxs 2y ago
Back in the '90s I used to consider sun.xxx the cooler version of Java.

More ›