Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
etal
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
121.
▲
The Internet is incomplete, says its co-designer, Vinton Cerf
(computerworld.com)
6 points
by
etal
17y ago
|
2 comments
122.
▲
by
etal
17y ago
I think it's interesting how the success of projects like this sometimes seems to depend completely on a single person having the right combination of interest and skill. The Jython project was just the coolest darn thing until, from what I
123.
▲
by
etal
17y ago
It's usually one or more of: 1. Using a simple prototype VM seemed easier during initial development 2. When the language was developed, no suitable common VM existed 3. The language developers thought they could do it better for their spec
124.
▲
by
etal
17y ago
Probably going for another meaning of the word, like dull or boring. Not that it's strictly correct, but in headlines, sometimes it's the thought that counts.
125.
▲
by
etal
17y ago
I found his example rant informative: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/...
126.
▲
by
etal
17y ago
The shape of this kind of graph usually isn't very meaningful by itself for showing subtle patterns -- you're right that the extremes of the graph always look like that. In the original article, if you line up the Bing-vs-Google and Bing-vs
127.
▲
by
etal
17y ago
The article doesn't mention any free/open-source versions of Whitney's work, but I do know of one, A+. It was extended from A, which does get a mention. http://www.aplusdev.org/ On another note, has anyone here played with the latest and
128.
▲
A Conversation with Arthur Whitney
(queue.acm.org)
13 points
by
etal
17y ago
|
6 comments
129.
▲
by
etal
17y ago
The focus on Comet and an event-driven model remind me of HAppS. Is there something about this approach that's especially appealing in pure functional languages?
130.
▲
by
etal
17y ago
The interesting lines in the large graph are the faint ones showing the adoption level of specific versions of each browser. With Firefox, each new version quickly replaces the previous one in terms of adoption, so when you see that Firefox
131.
▲
by
etal
17y ago
It is a good approach. The PLT Scheme textbook How to Design Programs walks you through a process for writing new code that more or less goes like that: 1. Write a comment describing the problem. 2. Write comments describing the form of a
132.
▲
by
etal
17y ago
Some of it's the regression effect, where the extreme results really are flukes -- and the achievers are aware of it -- while average results are more likely to be statistically representative. Of course, "aware of it" is key, which is why
133.
▲
by
etal
17y ago
Or else it's biased. It's easy to fool yourself with a large number of anecdotes (listening only to like-minded people, for example), but "data" implies some directed collection was done and some thought was given as to what you're actually
134.
▲
by
etal
17y ago
The papers I've seen that have more than a dozen or so authors often work like this: The first and second authors were the project drivers, and did the writeup; the names in the middle were involved in data collection, number-cruching or su
135.
▲
by
etal
17y ago
Foreground versus background processes probably makes a better metaphor. It is possible to truly multitask, beyond just franticly switching focus -- we do it when we drive or play sports -- but only one task actually has focus. The rest run
136.
▲
by
etal
17y ago
So many apps are built to be extensible now that I'd say it's still completely normal to fall into programming without any special effort. Remember that in the good ol' days, most kids didn't even have access to a computer. Now, any suffici
137.
▲
by
etal
18y ago
That's problem #1 in the current format of humanities graduate education. The assistantships train students to teach classes and grade papers, and the research and dissertation process teach students how to get an academic paper published.
138.
▲
by
etal
18y ago
The way I read it, and the document discussing the VCS switch (PEP 374), was that the Big Three DVCSes (git, hg, bzr) were essentially all just fine. Git is the fastest and hairiest, Bazaar is the slowest and cutest, and Mercurial covers bo
139.
▲
by
etal
18y ago
From the Python style guide (PEP 8), on comments: Python coders from non-English speaking countries: please write your comments in English, unless you are 120% sure that the code will never be read by people who don't speak your language.
140.
▲
by
etal
18y ago
As a PhD student, I get criticism for taking on tasks that are short, useful and possibly clever, but not novel. If it can't go into a published paper, it's a waste of time, apparently. And really, there are so many minor improvements that
141.
▲
by
etal
18y ago
For an easy +12, I recommend the "simplecv" LaTeX document class -- it's included somewhere in the full TexLive distribution. That Computer Modern font on a resume or CV, combined with judicious use of small caps, looks deadly serious. h
142.
▲
by
etal
18y ago
I like the O'Reilly book, Learning the Bash Shell: http://oreilly.com/catalog/9780596009656/ I keep it on hand as a reference for shell scripting, since it's both thorough and fairly portable.
143.
▲
by
etal
18y ago
Well, it could be treated similarly to version numbers in code. Once a given JS file is loaded, whatever __LICENSE__ evaluates to (e.g.), that's the program's stated license. If that global variable isn't set, then you know you can't assume
144.
▲
Google's 5th Summer of Code: Meet Your Mentors
(google-opensource.blogspot.com)
1 points
by
etal
18y ago
|
0 comments
145.
▲
List of GSoC 2009 mentoring projects
(socghop.appspot.com)
5 points
by
etal
18y ago
|
0 comments
146.
▲
by
etal
18y ago
Here's the note in PEP 3108: sgmllib [done] * Does not fully parse SGML. * In the stdlib for support to htmllib which is slated for removal. Based on that and the standard docs, it looks like it was lost in the standard libra
147.
▲
by
etal
18y ago
This is actually a pretty good introduction to dynamic programming. It covers some neat Python tricks along the way, too.
148.
▲
by
etal
18y ago
The whole bug thread is good information, but: if application developers actually follow approach #3 en masse, won't that massively slow down the system? I see some cargo-cult potential in fsync-after-every-write here. The emacs example may
149.
▲
by
etal
18y ago
Gnome ran a survey to see what contributors are using and what they like. The most thorough crunching of that data is here (scroll down a bit): http://blogs.gnome.org/newren/2009/01/03/gnome-dvcs-survey-r... Another analysis of the same d
150.
▲
by
etal
18y ago
It looks like the pure-Python fallback implementations were a big deal for the (nearly resurrected) Jython project, in particular: http://fwierzbicki.blogspot.com/2009/02/progress-with-mercur...
More ›