Missing a couple of features you want to add?

The "able to find this" (the 1981 Exxon magazine) needs context to appreciate re: the dispersion of certain personal belongings over time. I would have picked the magazine up in 1981 or 1982 (possibly 1983) at the school energy fair, and it remained in my physical possession for the next 40-something years.

In elementary school I did not have a significant amount of possessions outside of toys. Then in middle school I got a small desk, and in high school I got a larger desk, and it ended up in a folder of "neat stuff" that I saved.

Then after college my stuff from the desk ended up in a banker's box, which I still have, along with a couple of other boxes of stuff from that era. This year I looked for maybe 20-30 minutes and found it.

I still have all of my copies of Compute's Gazette from the mid-late 1980s.

I will say that it is amazing to be able to go online and find all sorts of old computer/electronics/whatever magazines from the 1950s-1980s on archive.org or bitsavers or worldradiohistory.org and there they are... unless they're not.

I'm not in the petroleum industry, but about 45 years ago I was mesmerized at an energy fair at my elementary school by this Exxon magazine that showed the refinery flow with a bunch of little dots: https://archive.org/details/p-2330663/P2330670.JPG

Taylor series in general are a poor choice, and Pade approximants of Taylor series are equally poor. If you're going to use Pade approximants, they should be of the original function.

I prefer Chebyshev approximation: https://www.embeddedrelated.com/showarticle/152.php which is often close enough to the more complicated Remez algorithm.

Now I'm ready to get out my checkbook.

What factors influence the cost of such a computation in today's cloud computing market?

How does the price scale with N and the rate at which I want to complete the problem? (for example, if it takes 1000 AWS instances 10 months or 10,000 AWS instances 1 month, am I going to pay the same? I'm assuming the length of time to run this is less than a year, so not long enough that the cost would decrease significantly during the computation.)

Are there aspects of flexibility that would decrease the price? (example: the cloud servers can put my computation on hold or throttle the CPU anytime they want in the short term, as long as the average rate my computation is running in any given day is, say, more than 80% of full-speed)

Lenstra used the term "dollardays" to describe the cost of breaking cryptographic keys as something that scales with the capital cost of the computing equipment (40 million dollardays = 40 days on $1 million worth of computers, or 1 day on $40 million worth of computers) but with cloud computing it seems more like it would be a piecework pricing structure.

Comments URL: https://news.ycombinator.com/item?id=47044151

Points: 1

# Comments: 0

(side note: does anyone else get thrown off by the Epilogue font? It looks very wide in some cases and very narrow in others... makes me want to override it with Stylus if my employer hadn't blocked browser extensions for security reasons, which raises the question of why I am even reading the article on this computer....)

Am I the only one who worries about agents creating malicious/unsafe code to execute?

What code review tools do you prefer?