mtdewcmu

41 ms·

151.
by mtdewcmu 10y ago
Cygwin is slow at things like process creation, I think, which made shell scripts slow. Plus, cygwin was its own environment that required some porting, or, at least, recompiling to get apps to work. The new Linux subsystem runs Linux binar
152.
by mtdewcmu 10y ago
I worked on a web store once that depended on a couple of 3rd party web services and set up subscription billing. The project turned out to be like an iceberg, where 10% of the work went into features, and 90% of the work went into heading
153.
by mtdewcmu 10y ago
I just doubt that it would be news if Caltech or MIT used recycled materials in an experiment.
154.
by mtdewcmu 10y ago
It's difficult to imagine an article like this about the US. "MIT researchers study solar storms using cheap recycled materials." It doesn't sound right.
155.
by mtdewcmu 10y ago
The "green light" part made it sound more like a retinal scan (because the inside of your eyeball is dark and needs to be illuminated).
156.
by mtdewcmu 10y ago
The article is calling for demanding more effort to get a paper published. That would be a change of norms. There's no real way to solve the reproducibility problem without changing norms. Publishing notes seems easiest. It would be li
157.
by mtdewcmu 10y ago
There are already ways to run an OS as a process (at least, as long as that OS is Linux). There is/was a project called User Mode Linux, for instance.
158.
by mtdewcmu 10y ago
Everyone would have to agree to publish their rough notes (on the web). If this was the norm, then no one would be singled out for criticism. Of course, norms would have to change.
159.
by mtdewcmu 10y ago
>> Regarding #2, eliminating context switch overhead and system call latency by running everything in one address space would be huge for some applications. That sounds like basically running node.js in kernel space, which is entirely
160.
by mtdewcmu 10y ago
You could publish notes in rough form and clean them up on demand.
161.
by mtdewcmu 10y ago
What if you basically take your lab notes and blog them?
162.
by mtdewcmu 10y ago
I've dealt with variable-length headers on (binary) things before, and it creates annoyances. It screws up the memory alignment, for instance.
163.
by mtdewcmu 10y ago
A google search for "old unix emulator"[1] turns up a wealth of options. [1] https://www.google.com/search?q=old%20unix%20emulator
164.
by mtdewcmu 10y ago
I'm thinking that it might be useful to include a magic number, so that you can distinguish a Multihash from a plain hash.
165.
by mtdewcmu 10y ago
You could be a little bit opinionated and limit the choice of formats to a small set of ones that are a good idea. That would encourage good design and it would allow you to shrink the metadata. Perhaps one byte would suffice. It's not
166.
by mtdewcmu 10y ago
Good question. There are instances where it allows you to write cleaner (and faster) code if you can identify the parts without necessarily having to parse the metadata.
167.
by mtdewcmu 10y ago
I guess it depends on how precious space is. A naked hash is very information-dense. In certain applications, inserting a prefix of several bytes to each hash makes a difference. OTOH, if the hashes end up being inserted into a table in MyS
168.
by mtdewcmu 10y ago
It's just a concept.
169.
by mtdewcmu 10y ago
You could run Solaris[1]. They don't seem to provide versions older than 10. [1] http://www.oracle.com/technetwork/server-storage/solaris10/d...
170.
by mtdewcmu 10y ago
Uuids are too short, but I think that Uuids are the relevant prior art for this type of thing.
171.
by mtdewcmu 10y ago
This seems kind of like a cross between a uuid and a plain hash. Perhaps it would be better to incorporate the hash into a uuid. Uuids already have metadata.
172.
by mtdewcmu 10y ago
Hashes don't currently know their own lengths, so I don't see why they'd need to.
173.
by mtdewcmu 10y ago
You could probably omit the length, because the length is probably already known implicitly. E.g. git knows the length of its hashes without having to read the hash. If the length < the full hash, it can be assumed to be truncated.
174.
by mtdewcmu 10y ago
It seems like it might be better to put the metadata at the end. That would make it easier to truncate to a certain amount of entropy. Also, it would make it possible to trim off the metadata without having to understand the format to figur
175.
by mtdewcmu 10y ago
It seems to serve approximately the same purpose as Berkeley DB.
176.
by mtdewcmu 10y ago
"Alligator" comes from "el lagarto" ("the lizard")[1]. [1] https://en.wikipedia.org/wiki/Rebracketing
177.
by mtdewcmu 10y ago
Some suggestions: Add some way of marking which papers are good. Just because you read it doesn't mean it was worth reading. Also, show the year of publication, if you can find it.
178.
by mtdewcmu 10y ago
This seems to serve the same purpose as, e.g., Access. What is different about this?
179.
by mtdewcmu 10y ago
>> you want a surgeon who doesn't think twice about huge terrible bloody trauma, people freaking out and intense pressure. You want a surgeon who will be bold, roll the dice and do what needs to be done. Essentially, a sociopath.
180.
by mtdewcmu 10y ago
What if you took the information that doesn't fit in the paper and publish it on the web?

More ›