bodyfour

26 ms·

241.
by bodyfour 12y ago
The article doesn't mention why people didn't want recursion to be a requirement. It was probably because the idea of using a call stack was still controversial. For instance, on a PDP-8 (released some years after ALGOL) the ca
242.
by bodyfour 12y ago
The other problem with COBRA is that the insurance company has zero interest in customer service. Insurance companies are famously horrible to deal with, but if your employer's plan gives you trouble you'll probably complain to H
243.
by bodyfour 12y ago
> They are entirely orthogonal That's true in a technical sense, but they're effectively part of the same process for many, many skilled immigrants. Come in on H1B -> Start GC process -> Use ongoing GC application to get
244.
by bodyfour 12y ago
I can't claim your experience since I've never been on your side of the H1B process. I've also been out of people-management for a few years. I can say that when I was in that position it was drilled into me that you need t
245.
by bodyfour 12y ago
Yep -- all you need to get a good war going is an excess of young men and a border. For a domestic conflict you can skip the second part. Or you can look at it from a purely economic standpoint: if your military-aged men are mostly finding
246.
by bodyfour 12y ago
The non-H1B salaries aren't public, but they do get audited. Employers need to be able to demonstrate that they're not paying H1Bs less, or there is hell to pay. These audits aren't rare either -- by the time you're la
247.
by bodyfour 12y ago
As far as I can tell, programming talent is distributed evenly all over the world. So why does the US have such a large software industry? Because a lot of the top talent worldwide wants to come here and work. Places like Silicon Valley
248.
by bodyfour 12y ago
Another thing that is hard in French (at least for me) is listening comprehension. For example, I know many more French words than German ones. Not quite enough to read very much (someday, I hope!) but if I were handed a text in French and
249.
by bodyfour 12y ago
Maybe that was true in 1965, but it's nowhere near the case today. Historically the downtown business core of Montréal was Anglophone while the poorer, rural areas were completely Francophone. However, rural people could still vote: t
250.
by bodyfour 12y ago
At the filesystem layer? No, never. However even in the earliest of days file extensions were common. They followed the usual UNIX preference for brevity: ".c", ".h", ".o", and ".a" were all early
251.
by bodyfour 12y ago
I wonder if it's really safer. You'd probably find that you'd have different magic databases and a carefully constructed (malicious) document might give different answers. Imagine that your email client decided a document w
252.
by bodyfour 12y ago
Yes, UNIX's never had a concept of a limited length file extension. Until the 1980s filenames were limited to 14 characters in total, but you could put a dot anywhere you like in it. I was specifically referring to the part of the art
253.
by bodyfour 12y ago
First, the 3-character file extension predates CP/M. It goes at least as far back as various DEC operating systems like RT-11 and RSTS/E; probably there are antecedents further back in time. I've also seen old filesystems w
254.
by bodyfour 12y ago
Any idea how it compares with the commercial ViEmu plugin? I've never tried their Xcode plugin, but years ago I used ViEmu for Visual Studio and found its emulation pretty solid.
255.
by bodyfour 12y ago
I'd refer you to the top-voted comment from @ daturkel. Because of the psychoacoustic models used for lossy audio compression (and, in particular, the "masking" effect) listening to these delta signals won't give you u
256.
by bodyfour 12y ago
A couple hundred million people are required to pay taxes using it. That implies that there is some inelastic demand for dollars. That factor alone obviously doesn't prevent every currency collapse, but it is a key difference between
257.
by bodyfour 12y ago
My first hint was actually at 6:10 when it reported 61399 bytes of memory free!
258.
by bodyfour 12y ago
The gitjk command needs to operate as a shell alias though
259.
by bodyfour 12y ago
> socklen_t – if your OS doesn’t have socklen_t, it’s either int or size_t. But OpenSSL does horrible contortions to define its own. If the size of socklen_t changes while your program is running, openssl will cope. This doesn't sur
260.
by bodyfour 12y ago
> hostel vs hotel In french there is a common pattern where words lost an "s" while a vowel gained a circumflex. i.e. hospital -> hôpital, forest -> forêt, etc. I'm guessing hostel -> hôtel is another example o
261.
by bodyfour 12y ago
When you think about it, it makes sense for a CPU in a game console to not include things like out-of-order. 100% of the software it's running are program compiles for that exact machine. Therefore you can just tell developers to u
262.
by bodyfour 13y ago
Yeah basically. That could be a disaster for, say, nonce generation. The solution would be to have multiple independent entropy pools and either bind them to cores(/sets of cores) or pick a non-busy one in a contention case.
263.
by bodyfour 13y ago
I'd almost go so far as to say it's almost universal in the US. The main exceptions: Gasoline (petrol) is always priced with all taxes included. If the establishment is small enough that they're not using a register for cash
264.
by bodyfour 13y ago
I think the most common answer is "whatever coins you happen to receive as change"
265.
by bodyfour 13y ago
Since 2.1, jemalloc does support using mremap to do large realloc()'s, although it seems to be off by default. You need "./configure --enable-mremap" to get it. That's good news about sized deallocation, I hadn&#x2
266.
by bodyfour 13y ago
jemalloc's non-standard interface gives you some of what you want, expectially xallocx() http://www.canonware.com/download/jemalloc/jemalloc-latest/d... There have been C++ templates written that use j
267.
by bodyfour 13y ago
Yeah I should have elaborated a little more. I was in a rush. I wasn't trying to endorse 64 bits, but think for a second about what it would take to attack weak entropy here. For every possible entropy state: 1. Put the random
268.
by bodyfour 13y ago
Even 64 bits would be sufficient as long as the entropy is good. It just needs to be large enough that bruteforcing 2^N isn't feasible. 256 seems like a perfectly safe amount to me.
269.
by bodyfour 13y ago
Esperanto has two problems: Spanish and English. Spanish was what Esperanto wanted to be, English did what esperanto wanted to do.
270.
by bodyfour 13y ago
English has some good features: * Limited number of glyphs is a killer feature for the keyboard age * No noun genders to remember * The informal 2nd person ("thou") got chased out of common use centuries ago, along with it

More ›