zsombor

The language also has a pretty good manual: https://hobbes.readthedocs.io/en/latest/ that also give a bit more background on why this was developed in the first place. Imagine being able to answer real time what is going inside an application engine, even in cases that may involve complicated state. Then doing this without affecting the latency constraints of the critical path. Or being able to change the runtime behavior of an application without sacrificing latency at all while still having type level guarantees that what you are doing is safe. There are quite a few solutions that allow this two requirements but hardly any in a domain where zero overhead really must be zero and not just a vague marketing term. For those that ask KDB does not even qualify on the second requirement while hardly meeting the real time for the monitoring requirement.

I think it is more about urban vs rural voters. Latter group is more likely to vote with CG, even after emigrating. It takes more time for them to pick up western values simply because they are economically disadvantaged at home and to a lesser degree abroad as well.

While some areas of the firm may indeed have what you call old and crumbling tech, this is far from the rule. I expect the electronic trading arm of JPM to be far and beyond what you normally can find at tech firms. The arms race in electronic trading constantly produces innovations out of necessity. The reality is innovate or die, and no inventing yet another sloppy JavaScript framework does not constitute innovation.

I'm putting things into perspective. Hungary has 136 km shared border with Ukraine, it also represents only 0.25% of the global GDP, and it is a small country of less than 10 million inhabitants that took in 700'000 Ukrainian refugees. It is okay to disagree with some of their positions, but to put blame one them for the current mess is ridiculous. As for ratio of dependence I have no idea how you did measure it, but it was certainly not per capita gas consumption.

Orban is the prime minister not the president. As for being chummy no Hungarian prime minister or president current or former has ever served as board member for Gazprom, nor served as head of shareholders for Nordstream AG, or director of the board for Rosneft the Russian oil company. All these positions were/are held by a former german chancellor Gerhard Schröder whom had put Germany onto the path of closing perfectly working nuclear plants and thus leading to the current dependence on Russian oil and gas:

https://bigthink.com/pessimists-archive/germany-nuclear-powe...

You have to build solar panels and wind turbines. Then have connecting service roads able to carry heavy equipment. Wash the panels frequently or watch their performance plummet. Grease moving parts to avoid friction losses. Maintain the rotor blades at the cost of significant downtimes. Replace everything after 20 years as that is their average lifespan. Deal with all poorly recyclable waste you have created. Overbuild all transmission lines by a wide margin, to compensate for the low density and intermittent nature of wind and solar. Accept that what could have been truly space reserved for wild nature is now used for low density energy farming. I really don't see how wind and solar are renewable in the true sense of the word. From an ecological perspective the point should be to use our resources efficiently so as to return large swaths of land to pristine nature. Currently you can do this two ways: one use high density technologies like nuclear, the other is to go extinct voluntarily. My choice was made after becoming a parent.

Both Go and JS are async and callback driven. The difference is that with JS those nasty callbacks are painfully explicit, whereas it is all hidden in Go. Node's callstack is a goroutine, except that the latter can also be preempted. If you have 100000 requests in progress in Node, it will consume at least as much memory as a well written Go program would.

The Linux version was benchmarked with gettimeofday() while the Windows one with QueryPerformanceCounter. The first has a lower resolution of 10 micros and as such the benchmark is not comparable.

For something to double in 10 years it only has to grow by 6.9% per year. This is from a somewhat unusual application of The Rule of 69. Latter is way of determining doubling time of something that grows by x%: just divide 69 by x and that will be the doubling time in periods.

So if the DB grows by 10% weekly, then it will double in 6.9 weeks. If the interest rate is 3% then the debt will double in years, etc.

The Rule of 69 is good for a approximation, that works well with low single digit increases.

The rate of economic growth has little relation to the stock market yield. For one you have forgotten about the dividends, currently around 2%. Now lets assume the company grows by 3%, so your shares will now be worth 3% more. But the total return will actually be 5%.

However here I assumed that there was no drop in optimism, or pessimism over the one year period. For if you were to bought in when expectations were high, your actual return would be lower.

Sometime the relation between growth and return is completely paradoxical. You would expect that in the past 100 years a portofolio invested in UK stocks to be dominated by one of US stocks. After all the first country went from being The Global Superpower to dubious second rate global player, meanwhile the US had done the same in reverse. Yet an investor in UK stocks would have been marginally better of.

Likewise you would expect China with its spectacular growth, to have brought impressive returns compared to the US. Yet that had not happened.

Seems a bit patronizing to assume that farmers will buy a product that does not work, then continue to do so after it had proven that it yields no advantage. If it were the case that the advantage lasts only two years, then nobody will buy the product on the fourth year.

Lastly the "patented life" argument is incorrectly attributed to GMOs. First proponent of patents in this field was no other than Luther Burbank (1849-1926), a pioneer in agricultural science. He had spent the better part of his life arguing for a means to protect his achievements. Finally the Plant Patent Act was passed in 1930, some years before his death. As it stands now "life was patented" for 85 years already, while the first GMO appeared in 1994 only.

On the other hand this is exactly the kind of people you wish for when something like the 1918 flu pandemic will happen again.

Someone from the top 5% is more likely to hold their a wealth in equities, then the Average Joe from of the 50%. The top percentiles may be paid more, but they are likely to make far more in the long term on their investments anyways.

In this sense inequality is unavoidable fact of life. Much the same as some people are gifted with genes making them more likely winners in a long distance running contest. Unequal but hardly unfair as long as a fulfilling life is possible regardless of such deficiencies. The problem should be phrased in terms of opportunities and social mobility, instead of inequality.

I would be surprised when a study comes out proving the opposite, given that there are strong proofs why beating the market average is difficult: http://www.norstad.org/finance/tsmproofs.pdf. Sure none of these profs exclude the possibility of a small set of consistently winning super managers. But then again even if such superstars exist, ultimately their performance is bound to be self-limiting.

A great tool to create a healthy debate about nothing, while the world changes unnoticed beneath you.

In 2015 clang & gcc have a more or less working devirtualization feature that eliminates the virtual overhead in a simple benchmark such as this. The compiler sees all classes and knows that a particular interface is implemented by only one class, so it simply elides the virtual table lookup. Add that features such as speculative devirtualization that can remove a surprisingly large number of virtual calls in an established code base such as Firefox: http://gcc.gnu.org/ml/gcc-patches/2013-09/msg00007.html

If C++ will exist in 10 years from now, I predict 'virtual' to be just yet another legacy keyword.

Oh yeah having six or more horizontal navigation bars was pure pain. Considering how difficult is to effect changes with an established user base, plus the complexity of the domain itself, their new design is anything but cosmetic.

Have created something similar enabling cross referenced search both from code and diffs as well at https://tixef.com. Indeed the ability to slice into the details of an implementation can be quite useful for actually understanding the code.

Good job making it a browser extension! The low impact install can build on the individual's desires for a better experience.

OTH there was no Heartbleed bug in the SSL implementation of Go's net/http. So much for hardened implementation. Secondly you can use go behind a http proxy, or even in an FCGI etc environment with minimal change to the code.

In a 30 KLOC rails project I find those numbers acceptable. Also you are unlikely to run the full suite after every editor save. Even Jim Weirich runs a single test file and not the full suite.

I am quite sure that the Basecamp cluster contains tens of machines. It also features a rather clever caching design. Please don't try to justify a push towards simplicity as lack of ability to handle complexity.

The sole advantage Paymill has is that you can make use of it from any EU country. That said my experience with them was horrific. If Stripe continues to expand, I doubt that Paymill will be around in a few years.

Instead of the 10 days approval period they advertised I got hit with almost three months. Some of the delay was caused by Wirecard, the bank they work with. I can sort of relate to that. However the significant delays caused by their own contract manager left me baffled. On average her email replies were delayed by 3 to 4 days. Worse the emails were written without much thought. A slow trickle of unhelpful messages that slowly erodes your hopes.

Was she overworked? Or in need of training, I don't know. But for certain the future is bleak for Paymill, unless they drastically improve the on-boarding process.

If it has an effect on overfishing then we should welcome it. Sometimes paranoia can be useful. Or there will be no more tuna left for our grandchildren.

Nature does not care so much about radiation than we do. The wildlife in Chernobyl had fared better after the accident simply of not having humans present. Some like Stewart Brand went so far as arguing for placing nuclear waste in dry cask storage into nature preserves. Just to keep them pristine.

As of Go 1.2 (released a few weeks ago) goroutines are preempted. Sure currently this only happens in the presence of function calls, but it is hard to create a non preemptible infinite loop without function calls by accident.

Whilst thanks to lack of choice JavaScript is so important on the browser side, I would hope the Node infatuation would eventually pass where you do have a choice. Async calls in Node are done via explicit passing of closures. Callbacks, Promises etc all look bad compared to simple sequential instructions like:

   credentials := NewCredentials(token)
   User.findByName(credentials.userName)   

The above is in Go, and it is just as fast if not more. Whilst all requests are on their own goroutines, the runtime will schedule them using the same efficient async io that does not need to be made visible as in JavaScript.

More likely it had merely promoted the quick and easy pop culture, where people no longer take the time of reading a book. After all you can just use google and look up your next short fix.

And?

Considering the impact of fishing perhaps a bit of paranoia will do good for the biosphere. Still I must point out that whatever radiation is released or will be released from Fukushima, is nothing compared to what nuclear weapons testing had done in the last century:

http://www.youtube.com/watch?v=LLCF7vPanrY

so enough scaremongering.

By what standard do you see Fukushima as being worse? Number of casualties? Number of people who had their livelihood directly affected? The effect on the biosphere?

Expect a lot more: the banana for example that had it's reportedly most tasty variant (Gros Michel) gone extinct in the last century. The variant you are buying today (Cavendish) is under great strain and is likely to go down the same route.

Species have been disappearing long before humans existed, there is nothing new here. We have always developed close cultural ties to what we eat, this made changes expensive. Hard to imagine a world without orange juice, bananas, plum fruit or a tasty tomato. Our ancestors lacked the tools to prevent losses. We have it and this only makes the loss more painful.