401 karma · joined February 26, 2010
Andrew: Vendors of multicore processors have expressed frustration at the difficulty of moving developers to this model. As a former professor, what thoughts do you have on this transition and how to make it happen? Is it a question of proper tools, such as better native support for concurrency in languages, or of execution frameworks? Or are there other solutions?
Donald: I don’t want to duck your question entirely. I might as well flame a bit about my personal unhappiness with the current trend toward multicore architecture. To me, it looks more or less like the hardware designers have run out of ideas, and that they’re trying to pass the blame for the future demise of Moore’s Law to the software writers by giving us machines that work faster only on a few key benchmarks! I won’t be surprised at all if the whole multithreading idea turns out to be a flop, worse than the "Itanium" approach that was supposed to be so terrific—until it turned out that the wished-for compilers were basically impossible to write.
Let me put it this way: During the past 50 years, I’ve written well over a thousand programs, many of which have substantial size. I can’t think of even five of those programs that would have been enhanced noticeably by parallelism or multithreading. Surely, for example, multiple processors are no help to TeX.[1]
How many programmers do you know who are enthusiastic about these promised machines of the future? I hear almost nothing but grief from software people, although the hardware folks in our department assure me that I’m wrong.
I know that important applications for parallelism exist—rendering graphics, breaking codes, scanning images, simulating physical and biological processes, etc. But all these applications require dedicated code and special-purpose techniques, which will need to be changed substantially every few years.
Even if I knew enough about such methods to write about them in TAOCP, my time would be largely wasted, because soon there would be little reason for anybody to read those parts. (Similarly, when I prepare the third edition of Volume 3 I plan to rip out much of the material about how to sort on magnetic tapes. That stuff was once one of the hottest topics in the whole software field, but now it largely wastes paper when the book is printed.)
The machine I use today has dual processors. I get to use them both only when I’m running two independent jobs at the same time; that’s nice, but it happens only a few minutes every week. If I had four processors, or eight, or more, I still wouldn’t be any better off, considering the kind of work I do—even though I’m using my computer almost every day during most of the day. So why should I be so happy about the future that hardware vendors promise? They think a magic bullet will come along to make multicores speed up my kind of work; I think it’s a pipe dream. (No—that’s the wrong metaphor! "Pipelines" actually work for me, but threads don’t. Maybe the word I want is "bubble.")
From the opposite point of view, I do grant that web browsing probably will get better with multicores. I’ve been talking about my technical work, however, not recreation. I also admit that I haven’t got many bright ideas about what I wish hardware designers would provide instead of multicores, now that they’ve begun to hit a wall with respect to sequential computation. (But my MMIX design contains several ideas that would substantially improve the current performance of the kinds of programs that concern me most—at the cost of incompatibility with legacy x86 programs.)
Source: http://www.informit.com/articles/article.aspx?p=1193856
I wish more sites just gave you a dump of all their data.
I didn't realize you ultimately throw away your first oauth key, and keep the second oauth key.
i'm also seeing lots of errors in the server due to authentication reasons, clearly i have some learning to do in terms of how oauth actually works.
I mean I basically made this because I wanted to start making a old school type of personal web site (80cols.com) and didn't want to have to scup files all over the place. I also didn't want to use an existing blogging platform. The major disadvantage is you can't run script or anything, but it's great for serving static content. I mean I could basically load gigs of videos and photos and just share them with the world if I wanted.
I need to do more, but at least now I know there's interest. I didn't even know that before launching.
The Dropbox authentication screen says: "This app will create a folder named webcache in your Dropbox. The app will only have access to this folder." But yeah you have no idea what's going to happen when you click that grey Submit button.
I agree the lack of polish makes it look spammy. Maybe some rounded corners and bubbly clouds would make it more trust-worthy. Along with an invitation to come over my house and have a beer.
If you enter "foo" it will create foo.80cols.com for you and create a folder in your Dropbox called Apps/webcache/foo.80cols.com and host it. If you enter "www.yourdomain.com" it will work too, though you need to setup a DNS CNAME record and point it at 80cols.com. Clicking sunlit links whatever domain you enter to a folder in your Dropbox account called Apps/webcache/www.yourdomain.com/ Then whatever you put in that folder will be automatically synced to webcache and hosted within a minute. As you update the folder it will sync within a minute. Unfortunately Dropbox does not have a push API so I have to poll Dropbox to check if your files changed. Otherwise it would be faster. Dropbox has an rss even feed but it's not really designed for programmatic access and I would need to ask the user to provide it. Supposedly an events API is coming; that would be very cool.
You can email me, not a great solution I know. You can revoke access in your Dropbox account.
If you enter "www.yourdomain.com" it will work too, though you need to setup a DNS CNAME record and point it at 80cols.com.
Clicking sunlit links whatever domain you enter to a folder in your Dropbox account called Apps/webcache/www.yourdomain.com/
Then whatever you put in that folder will be automatically synced to webcache and hosted within a minute. As you update the folder it will sync within a minute. Unfortunately Dropbox does not have a push API so I have to poll Dropbox to check if your files changed. Otherwise it would be faster. Dropbox has an rss even feed but it's not really designed for programmatic access and I would need to ask the user to provide it. Supposedly an events API is coming; that would be very cool.
It's faster, supports index.html, and directories. I've found public links to be slow. Additionally it's extensible because it's running on an http core I can modify.
though clearly i need to learn how to make an effective landing page, because no one who is visiting actually trying this service.
They are the individuals who interviewed at multiple places, got multiple job offers, and negotiated with the employer of their choice.
The problem with working for Abu-Dabi or some non-tech company is they won't know how to assess engineering value, and so I doubt they'd pay a premium for it. Perhaps some desperate company would do payscale * 20%.
The desperate rich non-tech company approach might work well for someone with a very nice looking resume with lots of corporate experience, who actually isn't very good.
However, none of that that will compare to a great engineer starting a bidding war between major tech companies (google, facebook, amazon, etc.). Companies that have a much better idea of what you're worth, and are willing to pay.
It's just right now for mobile, apps can be so much nicer and more capable than their web-based counterparts.
In my experience, it never goes well.
As these battles get larger, companies will dump more and more resources into their legal arsenal.
The ever larger legal departments at these corporations will then need something to do. Budgets to spend. Targets to meet. Goals to hit.
Release notes for 2.6:
"This release fixes an unexpectedly large number of flaws, from outright bugs (surprisingly many, considering this is "grep") to some occasionally debilitating performance problems."
"This release fixes an unexpectedly large number of flaws, from outright bugs (surprisingly many, considering this is "grep") to some occasionally debilitating performance problems."
Current version of grep is 2.10.