784 karma · joined April 28, 2010
"It concludes that in a competitive market, the unit price for a particular good will vary until it settles at a point where the quantity demanded by consumers (at current price) will equal the quantity supplied by producers (at current price), resulting in an economic equilibrium of price and quantity."
Note that the "comptetitive market" bit is important as it implies that the market is fully "free", which almost never happens IRL. Price fixing, strategies, stock market, governments, you name it. There are plenty of ways which make this model too basic in many cases. Worth knowing anyway.
That kind of things is best learnt with a grain of salt and some marketing knowledge as well. Read all the posts on "finding the right price" on HN to see how it does not necessarily apply -- but somehow does.
* Everything is a file (/proc, /net) * UTF-8 * WMII
I suppose that's enough for a research OS and its creators to be successful.
I use no script whatsoever and the complication . For a dev environment, I go like this:
$ sudo su - postgres
$ createuser -s nakkiel
And again, no further operation is required until you install a new OS on your machine.I really think we're missing the point anyway. The complicated things, and Mongo's advantage, only really come later when it's time to create a database and tables and columns and indexes..
Anyway, people who call themselves ops or devs ought to be able to do that sort of 3 lines operations.
As I said before, it happens once in your product's dev/op lifetime.
If MongoDB is popular, it's because it has some compelling features/arguments (I'm not sure of which ones exactly). But classical RDBMS seem to be trying to close the gap.
As a journalist, would you approach him openly saying you intend to study racism in the tech industry or would you rather approach him under a general angle and gather what you can in the process?
The second approach has a lot of value because Arriginton talked without the "racism" topic in mind, which could underline latent racism quite well.
Now, it's easy to use the wrong word, etc..
I suggest people who have never experienced racism as a victim to go abroad for a while and get the chance to reflect on their own behaviours. I personally find that the small everyday words that nobody notices are the most difficult to deal with because loud words and fights are easy to discard as the products of some odd minds.
Now, racism in tech? Of course, just like anywhere else. No more no less. Arrington, a racist? He wouldn't be the first nor the last.
There are figures though backing the representation of blacks in the tech world. Those figures are that of education in the US [I'm sure you'll find them]. The correlation is so obvious that the journalist barely deserves her title.
Perhaps the whole US system is a bit racist. Not a delusional Nazi-style racism, just a little latent racism. The kind of racism that makes a part of the population a little less comfortable everyday.
But eh. So is the whole world.
PS: I'm sorry for the rather personal tone and the emotions out there.
At the very least, you won't be fooling around with "What I think I said in the interview".
Seriously? Arch is KISS. There's no magic involved so I don't see how it's more difficult to use it than Debian.
Now, how often do you guys actually perform upgrades on a production box (security aside)?
I go by this rule: If it ain't broke, don't fix it.
It should be noted that a lot of the important stuff is now off-loaded to language-specific package management. Python libraries are a good example with virtualenv and your-sensible-python-package-installer, the actual distro repository doesn't matter that much anymore.
7 fs.readFile(filename, function (err, data) {
8 shasum.update(data);
9 console.log(shasum.digest('hex') + ' ' + filename);
10 });
Here are the results: $ dd if=/dev/urandom of=xxx.data bs=1000 count=200000
$ time sha256sum xxx.data
e774e4c46ab832ec09dbfd1a944044651560c3fdc3c5e2e8b46c2ea7d54f6649 xxx.data
real 0m2.087s
user 0m2.000s
sys 0m0.064s
$ time node xxx-1.js xxx.data
e774e4c46ab832ec09dbfd1a944044651560c3fdc3c5e2e8b46c2ea7d54f 6649 xxx.data
4883
real 0m13.972s
user 0m13.885s
sys 0m0.264s
$ time node xxx-2.js xxx.data
e774e4c46ab832ec09dbfd1a944044651560c3fdc3c5e2e8b46c2ea7d54f6649 xxx.data
real 0m14.043s
user 0m13.433s
sys 0m0.732s
Personally I never make multiple calls to update() but it seems not to be linked here. Oh, and check the docs, readFile() is async.PS: timings of xxx-1.js and xxx-2.js are equivalent on several runs.
Try vimtutor in your terminal. It's supposed to take 30 minutes.
You'll miss a lot of things from the tutorial the first time but you can come back to it as often as needed. You also shouldn't go any further than the tutorial until everything in it makes sense. Once you're at that point, you'll be autonomous for finding new commands and a happy vim user.
I may sound mad but seriously, what's with the a-web-app-for-everything madness?
The author points to something that we're going to loose (or perhaps that we already lost). Now, ads are the only nasty thing that break the guaranty of side-effect-free GET requests. And this is the only thing that matters for geeks and non geeks.
A human-oriented rant would say: "When you visit a page, you don't have to worry about other parties knowing it because it's guaranteed that way. This is about to change. Act now." As far as I'm concerned, it means the same thing. This is HN, not TechCrunch..
The author goes as far as criticizing other side-effects already in place; an example of which is ads. Because you see when you browse an article about Herpes, then you encounter ads about Herpes drugs on every website.
I got hit by this while looking for paid webmails. After a few searches on Google, I started to see ads for atmail on every single page.
There are people who believe it's a violation and I'm one of them.
EDIT: please don't point at Do Not Track or other work-arounds because that's all they are.
Beirut ejecting sidings mournsshuf -n4 /usr/share/dict/words | tr '\n' ' '
As mentioned in the paste:
Please note that this is hacked Python SimpleFold. I don't know how much of the original plugin the code share (as I hacked it loooong ago). Do remember that it doesn't always work (but always do with my company's coding conventiens; hear I have no intent to make it work for others). Also, there is probably some useless crap laying around.
Edit: Judging by my English, I'm really tired. I leave it as-is for posterity and because it's the way it is in the paste.
“There are only two hard problems in Computer Science: cache invalidation and naming things.” – Phil Karlton
The variant mentioning off-by-one errors may be pleasant, and useful for beginners, but is hardly a problem.
When we'll have solved the naming thing we'll be safe.
The rest is just buzz-words and useless noise.
Only after looking at these elements can you get a picture of the project which will tell you a lot about it. How is the support? Do developers even care? Are they serious at issues handling? Etc.
OSS suffers a lot from people who think they can just paste the code, change the implementation when they feel like it, etc.