markhahn

15 ms·

301.
by markhahn 2y ago
Yes, it was traditional "philosphers of mind" who found him dismissive, mainly because those are all basically Mysterians. For instance, he cut Chalmers no slack on the incoherency of Philosophical Zombies.
302.
by markhahn 2y ago
well, the interesting part here is that the tools (verilog and openlane) seem to work pretty well and are highly accessible. designing a cpu hasn't been a complicated exercise for decades, but implementing it has been.
303.
by markhahn 2y ago
100/200/400Gb is widespread in high-performance (HPC or big AI) datacenters.
304.
by markhahn 2y ago
None of those have to do with values, just practice or protocol.
305.
by markhahn 2y ago
Ethics/morals as a strategy to achieve your values, sure. The plan is the uninteresting part - people are interested in the values.
306.
by markhahn 3y ago
new project idea: OpenBackgroundCheck volunteer osint researchers attempt to dox any identity you submit, so you can know whether they're the Right Kind of OSS contributor or not. /s
307.
by markhahn 3y ago
not ecc - this article mentioned all the effort put into hiding suspicious strings. all those string-obfuscating lookups took lots of extra cycles.
308.
by markhahn 3y ago
jeez, why not just compile ssh static?
309.
by markhahn 3y ago
goodie! more, and less-controlled build environments to compromise, what could possibly go wrong?
310.
by markhahn 3y ago
merely keeping build and test environments isolated would have entirely prevented this attack. better hygeine that way would also simplify both environments, since the tools for each are fairly different.
311.
by markhahn 3y ago
do you also lose phones themselves? keys? pens? I probably outed myself as an old with the latter question ;)
312.
by markhahn 3y ago
wake me when the firmware is replaceable too.
313.
by markhahn 3y ago
little hard to understand why it's worth explaining the details if you're going to gloss over the issue of endurance and erase cycle limits. if you do very little writing, you have nothing to worry about with SSD endurance. just
314.
by markhahn 3y ago
The note seems oddly reductionist or strawman-indulging. Nothing about MR says you can't use indices. In a sense, MR is really about sharding! It would be interesting to know how often MR (and its line) has been used on datasets, and
315.
by markhahn 3y ago
sorry, why would low-end torque be important?
316.
by markhahn 3y ago
I admire the idea of hubmotors as well, but once mentioned them to a car engineer, who basically said "think about unsprung weight". Which, now that I think of it again, is a bit silly because most EV mass is battery, not motor.
317.
by markhahn 3y ago
"maximize profits" and "best product for customer" are dual. you specifically want small chip features - or don't you like speed, power efficiency, and low cost?
318.
by markhahn 3y ago
Regularly? That means that some nontrivial fraction are guaranteed to burn. I think you mean that it happens at low probability but is eagerly covered by media. In any case, the fault is almost certainly either physical abuse (which has n
319.
by markhahn 3y ago
More of this please! It's astonishing how anti-modular various industries are. Even batteries, which for all their "oh no gonna blow" are really quite simple components. But why are cars not modular? How about HVAC? Housi
320.
by markhahn 3y ago
+1 this. Intel let MBA-think drive too many decisions (ie EUV). Maybe there was some misperception there, even cultural bias. Pat's biggest real change has been to push the company towards process leadership. They always had good des
321.
by markhahn 3y ago
It's also interesting that Intel made some specific bad technical choices. (ie, not investing in EUV, assuming SAQP would work forever, ignoring the consequences of everything being power-limited...) This kind of decision is hard, beca
322.
by markhahn 3y ago
hasn't been obscure for a long time. this says more about WSJ-reading "enterprise" IT than anything else.
323.
by markhahn 3y ago
You seem to be implying that there is something inherently slow to Python. What? This topic is an example: a detail of one particular implementation, since GIL is definitely not inherent to the language. Just the usual worry about loosene
324.
by markhahn 3y ago
Some of those numbers are very weird.
325.
by markhahn 3y ago
No, swapin kills performance. Swapout is always efficient and always just makes your RAM more efficient. Any normal workload has hot and cold pages.
326.
by markhahn 3y ago
So you came from an S3 or other put-get world, and found actual filesystems odd? I suppose that's not so different from a WMP user's epiphany when they discover processes, shells, etc.
327.
by markhahn 3y ago
Quick read but not worth it.
328.
by markhahn 3y ago
Ok but shame about the apostrophe
329.
by markhahn 3y ago
it's really down to company culture: how many MBAs and PMs it normalizes.
330.
by markhahn 3y ago
It is astonishing that open firmware is not yet normal and expected! How can we begin to expect our systems to be secure, correct, efficient, and sustainable without a fully open stack? Trusting vendors is like the role of the Church in the

More ›