72 karma · joined December 28, 2011
Essentially it's moving doing type propagation in "batch" to a "dynamic trigger" system. How effective that is really depends on the programs (or the programing style) and how often they really change types.
I hope it's not just optimized for the usual benchmarks, but some real code.
~4-6% every 3 years according to http://oir.yale.edu/node/108/attachment
Apparently that gets spent on all kinds of things, just not the actual education the students need. At >30k a year you could really expect that they would hire enough real teachers.
Now it's not good for those who wasted a lot of money on a law school. They made a bad decision and will adjust.
And a lot of papers do not even bother to explain some variable but just assume the reader already knows it. One of the earlier commenters made this mistake very prominently enthusing over Maxwell's equations.
Yes of course the formula looks better shorter when you already know what it means. But that completely misses the point that it was written down to explain it to someone who doesn't already know what it means. If you already do you're the wrong target audience.
Longer variable names would help. Or for online paper just have a tooltip that opens the paragraph that explains what the variable mans when you hover over it would also help a lot.
Or maybe some color coding to easily find it (there was a recent link here recent explaining FFT which used this trick very successfully)
But I guess most Mathematicians don't bother because they only write for a small circle of colleagues anyways.
This only needs a very single table key->value store where every transaction is only a single access. I would just map it to a hash table mapped directly to the raw disk. Doesn't need transactions with a log if done right.
The hash spreads out the allocation, no information leaks for the allocation. If you don't have a log there are no time stamps.
Modern disks are big enough that you dont need to worry about resizing the hash table. And the random salt makes collisions unlikely enough.
That is similar how the STL does it, but not like stdio
I'm not sure I fully agree. - For simple libraries it's likely good advice. - But it encourages big locks and poor scaling. It may be right for desktop apps, but not necessarily for server code that needs to scale. For some things that's fine, but you don't want that for the big tree or hash table that your multi threaded server is built around on. - It avoids the problems of locks being non composable, that is the caller may need to know which order the locks need to be called, to avoid deadlock. Actually it doesn't avoid it, just pushes it to someone else. However if you make sure the library is always the leaf and never calls back the library locks will be generally at the bottom of the lock hierarchy.
Besides github is doing its best to compete on the "largest number of useless buttons/toolbars on the webpage" front with sf. I also found that finding something based on keywords works better on sf than on guthub.
freshmeat/freecode is really great. Lots of great software there (I liked the old name better)
Browsing the freecode frontpage is far more satisfying than the HN page because it's all about real code that does something and very little hype and BS.
Overall universities are just extremely inefficient. Where does all the money go to?
The person in the article who went into an administrative job may have been onto something.
Part of the problem is also the biology/chemistry bubble. In the 90ies these areas expanded extremely and now they are downsizing to more reasonable levels again.
With CS degrees they would be better off.
Macro is a mac developer, his friends are mac developers and he somehow determines Microsoft development is dead because he doesn't do it. And we are supposed to believe him in that.
Next step: profit?
Yes everyone reinventing their own broken flat tire date routines is the way go. If they used the same silly rule on the F22 that explains http://blog.utest.com/international-date-line-bug-caused-fig...
Time related code is really hard to write.
Maybe they should have called it "snake oil" instead.
" Upon at least ten (10) days prior written notice, Splunk may audit your use” …. ” Any such audit will be conducted during regular business hours at your facilities“ … “You will provide Splunk with access to the relevant records and facilities“ "
More or less they screw their customers.
Calling programs like that "pearls" just seemed too wrong to me to go on.
It would have been great to spend the money on Webb on several smaller missions like Kepler, and leave the Mars missions alone.
Whatever science Webb can do is unlikely to make up for the opportunity costs lost in these other missions.
relevant recent HN stories: healthcare: http://news.ycombinator.com/item?id=3661731 lawyers: http://news.ycombinator.com/item?id=3672815
Larry Moran has a lot of good material on this http://sandwalk.blogspot.com/2008/02/theme-genomes-junk-dna....