dom0

67 ms·

661.
by dom0 9y ago
Motherboard price is square to the number of sockets. (This is actually accurate, look it up; and for somewhat good reason).
662.
by dom0 9y ago
Well these are the old Atoms, which are responsible for the bad rep of the brand. "Neither fast nor efficient, but it surely is slow!"
663.
by dom0 9y ago
The ME processor is located in the PCH as far as I know. SoC systems have it all on one die, of course.
664.
by dom0 9y ago
> will address this source of imbalance. Why is it important to do so?
665.
by dom0 9y ago
Duplicate of https://news.ycombinator.com/item?id=14330885
666.
by dom0 9y ago
> if Windows was "perfect" feature-wise and only security updates were provided going forward. Therefore the kernel is secure, assuming spherical cows are used in the bubble memory of the return stack.
667.
by dom0 9y ago
Even if that were so, things are moving away from VLIW. E.g. AMD switched from VLIW to a more standard load-store SIMT approach a couple years ago, and even though it's more complex for the GPU, it increased system efficiency (esp. for
668.
by dom0 9y ago
A PDF file is also mostly plaintext. At times.
669.
by dom0 9y ago
Thanks. This link works for me: https://zadereyko.info/downloads/library/D2T1_Kris_Kaspersky...
670.
by dom0 9y ago
A good example how to not write performance sensitive code, in general, and specifically in Java, would be Minecraft. Though commercially successful Minecraft is (or at least was) an excellent study of how to not do stuff, be it memory mana
671.
by dom0 9y ago
Original title is "Customer Guidance for WannaCrypt attacks"
672.
by dom0 9y ago
> Transfer of the file you were trying to download or upload has been blocked in accordance with company policy. Please contact your system administrator if you believe this is in error. That comes from their end.
673.
by dom0 9y ago
> Slight aside, there are a lot of reasons that Itanium failed, but certainly one of them was lack of backwards compatibility. Itanium did not aim at the x86 market. The x86 translation layer was retrospectively seen as a mistake as well
674.
by dom0 9y ago
(Entirely unrelated to the actual contents) I find it remarkable how visually inconsistent all of the shown screenshots are. (Look at all the small details that differ between each screenshot, like margins around buttons, button sizing, s
675.
by dom0 9y ago
> this executable is ~2MB --- why it needs to be this big, I'm not certain Because writing this in 200 lines against the Win32 API resulting in a 15 kB executable would be far too straightforward. Abstraction is required.
676.
by dom0 9y ago
No, actually the argument is that > the US [government] says [they have intel] has historically been full of shit and completely made up from time to time. Therefore there is no reason to believe it now.
677.
by dom0 9y ago
> America has intel - and good intel from a raid - that shows that ISIS has the capability and intent to hide a bomb inside laptop batteries to blow up passenger planes That's false, it's the best intel.
678.
by dom0 9y ago
These boxes are probably aluminium, which should be ignitable by another metal-fire.
679.
by dom0 9y ago
I don't intend to contradict you, I'm just providing my angle on where the original comment came from.
680.
by dom0 9y ago
Now I know that the PyPA guys do a ton of work to make all this stuff less brittle, and indeed, Python packaging has improved a lot over the years. But overall it's still brittle, complex, difficult to debug and reproduce, and generall
681.
by dom0 9y ago
The issue with using pip and package managers in a similar vein is that they're not distributing complete packages, which usually means that stuff is compiled when installing some application. End users don't have compilers, and i
682.
by dom0 9y ago
Either has headlines made of words, so that's something.
683.
by dom0 9y ago
Uhm, weren't their later graphics systems heavily based on i860 processors?
684.
by dom0 9y ago
pip & similar package managers are a trainwreck everywhere but on developer machines.
685.
by dom0 9y ago
OTOH improvements in the mainstream segments seem to go slower: Mainstream cards are about twice as fast now as they were five years ago.
686.
by dom0 9y ago
https://www.youtube.com/watch?v=ooLO2xeyJZA
687.
by dom0 9y ago
exclusively GC'd
688.
by dom0 9y ago
... is really not relevant to software testing.
689.
by dom0 9y ago
Stack allocation is the default in all practically used languages that actually have a stack (e.g. C, C++), and heap allocation is explicit in all of those as well. Allocation more or less everything on the heap (i.e. using the stack only f
690.
by dom0 9y ago
> surely it also allows malicious actors to prepare to exploit? "There is an RCE in Windows" is not helping anyone.

More ›