3,127 karma · joined October 6, 2012
Of course there exist politicians who demand that democracy is dismantled, and in that sense are outside the system. But claiming that your opponent is that politician should be done only when he really is that politician, because you're in effect claiming that the conflict with that politician is not resolvable within the system of democracy - effectively you say that democracy will not work to win this battle. So if you're wrong and the politician isn't as anti-democratic - for instance if he's the kind of guy who'll step down when voted out instead of attempting a coup - then you calling him hopelessly anti-democratic is the one demanding that democracy be dismantled.
Supporting rent control doesn't make you stupid/uninformed, but the only other option is evil.
Protectionism is a complex topic in a world with currency manipulation, labor laws variability and geopolitical conflicts; it's only simple (and evil/stupid) in a world without these things.
And immigration is not just about economics, it's about who you want to live next door and vote. Here, people can disagree regardless of economic views.
Where are other biggish examples?
The "styles" page has the biggest bulk of interesting code that I've found in introductory pages: http://felix-lang.org/share/src/web/advocate/styles.fdoc
I guess one always wants to hear an elevator pitch of what a language does that is special relatively to relevant competition. What does Felix have that languages X and Y, its closest competitors, don't have?
So why did she do it? Or rather, what could plausibly be the reason?
From http://people.ee.duke.edu/~sorin/papers/tr2011-1-coherence.p...
"Using amortized analysis, we show that interconnection network traffic per miss need not grow with core count and that coherence uses at most 20% more traffic per miss than a system with caches but not coherence. Using hierarchical design, we show that storage overhead can be made to grow as the root of core count and stay small, e.g., 2% of total cache size for even 512 cores.
Consequently, we predict that on-chip coherence is here to stay. Computer systems tend not abandon compatibility to eliminate small costs, such as the costs we find for scaling coherence"
And now the quote from TFA:
"Do we really need cache coherency across a hundred cores or a thousand cores on a die?"
The paper's 512 cores are in the middle of the range where TFA suggests you start to get enough problems to seriously consider breaking compatibility and foregoing cache coherence. Why is the paper which supports its claims with concrete analysis less credible than an unsupported offhand remark from someone at Intel, a company that made a fortune from all of its CPU designs except that infamous one where they abandoned compatibility?
BTW a basic understanding of coherence might lead one to doubt the claims about lack of scalability. When you hit the cache, you know that you own the data so it's fast. When you miss the cache, it's a very slow operation anyway, the overhead of checking whether to fetch the data from external memory or another cache can't be that bad. And if data travels a lot from one cache to another because of true or false sharing, that's the fault of the code doing that. Coherence is not supposed to make sharing blindingly fast, just to make it correct, and to make false sharing correct as well.
Of course none of this will be relevant if there's no substrate on which to put a thousand of x86 cores, which right now there isn't.
I wish Facebook (and G+ etc.) users cared, I really do. I also wish they didn't share their contacts with Facebook (and WhatsApp, LinkedIn, etc.) Of course nobody cares, so you can't really opt out of these social networks.
Also, reusing names through overloading without providing actual polymorphism, either run time or compile time, is IMO bad, as in I don't get what's there to like. If one open function gets a file name and another gets a username and a password, what's so great in that they have the same name?
(I'm sure someone at MS has an answer to this, it's just that they haven't been tremendously successful in the past with their big acquisitions; I don't think Skype or Nokia paid off. And in general tech companies often buy other companies without much apparent success. Why is it so crazy to doubt their wisdom in any particular instance?)
This thread is not refuting this claim but explicitly or implicitly blames TFA and "the Rust community" for misrepresenting C++ as dead, useless and not worthy of improvement.
Of course C++ is far from dead, enjoyed by some, and used by many more; TFA did not claim otherwise. Of course improving C++ helps those using it; TFA did not claim otherwise. All it claimed was that the current and potential future state of Rust relatively to C++ was misrepresented by people at the C++ side; I think you're more supporting than refuting this claim.
[1] I personally, unlike TFA and some commenters here, must say that I'm not thrilled about anything having to do with unique_ptr (which as TFA demonstrated is not guaranteed to be unique at all, but is as unique as its user made it) and other such; certainly if I have to rewrite an old code base to use new smart pointers, the change will involve every corner of that code base, and I think I'd rather rewrite it in another actually safe language if safety is what worries me. But that's just me; and BTW I haven't personally looked deeply enough into Rust to advocate for it, either.
People will use things which most of the time do not punish mistakes too harshly and don't present problems requiring actual thinking to solve. I think people are right in refusing to use the other kind of thing because the alternative burns too much of one's time and is too risky. Big web companies manage to build such artifacts over the infrastructure that is the Internet and the WWW; I'm not aware of alternatives.
Regarding the edge of technology - Intel doesn't beat others to a new node by making both chips and fabs, it would beat others even if it was only building fabs. And it's not like TSMC is that much behind Intel. Grandparent who mentioned 28nm could mention 16nm except that there the masks will costs much more but it's still millions, not billions.
(Not to mention that for the average person, setting up a website and publishing something there is not an easy technical problem in 2016; most wouldn't know where to start. Personally, I'm not a web programmer but I am a working programmer and I can write a simple web app using a CGI Python script or Django or Rails, and for me setting up a website is fairly annoying in 2016. And anything involving non-static HTML is a PITA, and writing static HTML is no fun, either. The web is not the most pleasant thing, technologically, and this is one reason that a company amortizing the cost of dealing with the web over many users has an easier time than an individual trying to do something over the "bare" web without intermediaries.)
Care to elaborate? Certainly classical computers don't look a whole lot like the information processing of any living being (I guess one could argue that they mimic what humans do with pencil and paper, but it seems a bit of a stretch.) To me other things like say human-made engines also don't look that similar to any life form, but then I think I know very little outside computing, relatively to say the average person here, and hence I'm genuinely curios about your remark and "wouldn't be surprised to hear something surprising."