HN user

Skriticos

93 karma
Posts0
Comments23
View on HN
No posts found.
[dead] 16 years ago

In 1945, 1 troy ounce of gold was worth something in the vicinity of 35 USD.. As of today it's over 1100 USD, and going up really fast. It would have been unfortunate to have it paid back in gold.

http://www.nma.org/pdf/gold/his_gold_prices.pdf

Also some figures for what was mentioned in the article: http://mises.org/markets.asp (the last set of diagrams show the national debt figures over 60 years, useful to get an idea)

I'm by no means fan of windows, but the article was an obvious troll from the beginning, as it was quite evident that they were mixing up cache with real memory usage.

What really surprised me was that such a pointless 'story' generated so much fuss. Waste of time.

Please Rob Me 16 years ago

Then again, he might also tweet that he is on vacation while sitting on the closet, with gun..

Are you friggin' kidding me. Wikipedia hosts so many sites and serves so many requests that they are their partially their own cloud. They would not gain much from switching to some other cloud, not to mention the probability that there is no other 'cloud' that could handle them ad hock. I'm sure Amazon would swallow big if Wikimedia came to them with such a request, then probably laugh out loud. Get real..

A bit wrong of a comparison. A car is a tool, and can get dangerous, which is why it has this strict interface and education rules.

Computer usage is more like math. It's something you just need, part of every day life, though many people still hate it, as it is more flexible. GUI's really share similar concepts, you just have to adapt them, and if people hate one word, than it's adapt - seriously hate.

You really have time to figure out how things work and GUI's are really no rocket science to figure out.

Nobody expects users to become system administrators or application developers, but answering questions about self explaining clickable graphical elements is very painful. (With a little endurance you could probably get a chimpanzee to understand most of our 'modern' UI's).

I doubt that a 16k file with an OS in it manages to accommodate a virus too.

It's probably heuristics, AV software is very picky about stuff that does booting a system or have very optimized code. You see this kind of alert in the demo scene quite often too, because AV also don't like their packing algorithms.

I'm on 64bit Linux here, and as long as I used the Adobe Flash plugin, it regularly crashed (in various ways, most of the time just the flash subsystem).

I know there is a 64bit version now, but I got genuinely fed up with them, so I deleted the plugin and use swfdec for youtube and just don't care about the rest. Can't say that I'm bugged much, my browsing experience actually improved.

The main reason I boycott flash is still, that it is by no means sustainable and it inhibits the progress of the web a lot (get the feeling of a hamster in a hamster wheel, solving the same damn problems over and over again). It must simply die.

Sounds like a chicken and egg problem to me. If we collectively ignore ogv because there are no current hardware en/decoders, then why should anyone build it? These things are built when enough demand is present. For that, the push from the Mozilla foundation seems to be reasonable. Once there is more demand, the tech comes automatically. If we clinge to H264, nobody will ever build the right hardware. It's basically a demand based resource allocation problem, and Firefox is doing the demand part. Seems reasonable to me.

That was just the first comparison that I came around at it sounded reasonable. I would actually prefer if someone else would show more of these. But not a lot of folks do that. Everyone is just bitching around.

Also, maybe there are problems with theora, but then again, it's better to push it to more attention and fix the problems now than settle with a halfassed, non-sustainable solution and having the same discussion same time next year again. Seems to be very ineffective.

Any chance for a QT entry in the Libraries & Frameworks section? That's defiantly a framework worth noting, but I'm not sure how much cheatsheets are out there for it. They are kind of hard to find.

Remember, that's not inflation adjusted. It's a common banking advice though. (Not a stupid one).

As for your problem, do what most people say here: invest in the best asset you know: your business model. If you are very lazy, then just simply figure out how to let someone else do the work.

And I wonder if you meant that question seriously? The wording sounds awfully naive.

I agree. The most effective method would probably be to select various topics of practical usage for maths. That way the likelihood of finding interesting topics for all at one point or the other would increase very much. This would also help the kids to get a little more perspective of how the world actually works, which might benefit them.

Rhytmbox / Totem are the default media players on Ubuntu, and yes, an installation dialogue pops up when a codec has to be installed.

Tex Source Code 17 years ago

I wouldn't exactly call it source code.

It's more like a book with extensive description containing all the source code.. without much structuring.

Somehow it hurts.

.. then again, maybe the dvi/pdf version I saw just missed that. Not very experienced with TeX, but I guess the output can be rendered nicely. Why did you post the TeX source edition of a book?

No amount of technocracy will change how people solve problems.

The are basically two ways:

1. Apply predefined solutions to solve a problem (i.e. Use gadgets and applications someone else programmed).

2. Develop a custom solution to a problem (i.e. Put together your own program that solves your problem).

Arguably the next generation will learn to apply more complex predefined solutions to problems, but they won't magically start to migrate to the second mindset.

I have a copy of "Advanced Programming in the UNIX Environment, Second Edition" (featuring very good description of C/POSIX/SuS/XSI protocols/api's and programming techniques for Linux/BSD/OSX/Solaris/other UNIX systems). Anyone who seriously wants to do thread safe multiprocessing or other complex low level stuff on UNIX platforms should have a copy of it. It's basically "the book" on the topic.