skysight-inc/HackerNews huggingface dataset:
The mentality of compiler authors writing these kinds of optimizations needs examination. Specifically, inferring value constraints based on value use, and eliminating branches on that basis, is suspect for a very simple reason: if you accept as an assumption that value constraints can be inferred from code, using undefined behaviour to eliminate a branch needs to be balanced by the fact that an alternate branch exists, and presumably the user wrote it for a reason. You can't have your cake and eat it.

Technically correct is not a useful standard. Working code is. If compilers make code like this fail, it should fail very loudly, not quietly; silently eliminating null checks is not a virtue unless it is absolutely known that the null pointer use would definitely blow up otherwise. Which is not always guaranteed in practice, as the memset experiment here shows.

If compiler authors really want to pursue this optimization, elimination of dead code by means of detection of undefined code should result in a compilation error, because the code intent is self-contradictory.
But there will surely be other Feynmans and Einsteins. What difference does it make if that's the same person? Also, why do you assume that we'll acquire more knowledge than we already have? It makes sense to think (as the human brain is a huge energy sink), that our brains are just large enough to process information for one human lifetime. I don't remember most of what I learned at university, and that wasn't even two decades ago.
Well, for me broken internal links and a claim that some framework magically avoids 404 errors are worlds apart.
http://www.nytimes.com/2015/02/15/world/bank-hackers-steal-m...
Site appears down for me.

archive.org: https://web.archive.org/web/20150215195350/http://www.joshba...

Google Cache: https://webcache.googleusercontent.com/search?q=cache:1XzrZ3...
You act as if disregarding the self-report component is minor, but surely it is fundamental.

The original theory is that bullying is a way for someone with low self-esteem to make themselves feel superior. By the definition of the theory, a bully so motivated not to see themselves as having low self-esteem that they will resort to violence. Someone who will resort to violence to avoid acknowledging something, is unlikely to self-report accurately on that same topic.

Self-report is therefore clearly an invalid measure by which to test this theory.
Living in Houston is about as varied as an experience as you can imagine and different parts of town have wildly different density, walkability, sameness and yes soul (Montrose, Museum District just off the top of my head). It's like visiting New Jersey and saying NYC is soulless. Lay Houston + the suburbs you were probably in over the top of both and you'll see it's not a bold statement.

Most of the driving that people complain about are people that don't even have Houston addresses, it's a rare day I drive more than 5 miles, and none of the houses in my neighborhood are the same.
The simple answer would be: by using memory. More bits means that the CPU can operate at larger amounts of data at once.
For example shift would need to perform multiple 8bit operations but it's entirely doable (I hope the cpu he used has shifts with the carry flag)
New HIV Strain in Cuba Has Researchers Rushing to Stop Fast Progression of AIDS
Bitcoin is underpinned by drugs and money laundering, you say? That is funny considering "the most powerful drug trafficking organization in the world" just had 32 people arrested for running a multistate gold-for-cash scheme that laundered more than $100m in US profits.[0]

[0]http://www.theguardian.com/us-news/2015/feb/12/gold-for-cash...
You guys are missing the joke. Rainer is just being smug.
Are banks functioning properly? Just today we heard that online attackers stole hundreds of millions of dollars from them.
Laser cutters are probably where it is at. They are lower maintenance, faster and can make sturdier objects. But not like this: "A camera inside the laser cutting chamber and image processing in the cloud will take the place of a part called a motion planner." Great, now we have a printer that needs a high speed internet connection to proprietary servers just to operate, after uploading everything you print to the cloud. As if the shenanigans that the inkjet people pull are not bad enough, think of how anti-consumer and anti-maker this is going to be.
If we evere figure out quantum entanglement communication then it won't be an issue.
>I was unaware it had became possible to disprove a negative.

Can one not prove the positive?
My rebuttal to the post I replied to was that all currencies are ones and zeros now. The "> " was me quoting their post.
I think it's a pretty open-and-shut case.

Startup companies with no serious experience in information security, or finance, or financial information security are making large web applications that store and trade digital currency. That currency, if taken, cannot be recovered in any way unless law enforcement physically raids the perpetrator, just as if they stole physical cash.

There are millions of unscrupulous fraudsters and black hats out there who realize they can effectively rob banks over the Internet, sometimes as easily as walking in through the side door and walking out with all their assets without anyone ever knowing they were there until they're long gone. Bitcoin banks and exchanges are the absolute most valuable target for cybercrime, due to the incredibly high potential for reward (6, 7, or 8 figures from one heist is not uncommon), the irrevocability of the currency, and the low chance of being found or caught.

It's a bank robber's perfect fantasy. It does take a lot of time to liquidate the treasure chest, but it's still pretty trivial to do securely.
Loved reading this. Most original article I've recently read.
I agree... I didn't even realize there was a videos section between the "Try it" and the "Features" section until I read your comment.
Various factions within the scientific community have a lot of very good ideas as to exactly how, in great detail, to go about research and development with a high probability of producing effective treatments for aging at the end of the day. For example, these laundry lists:

SENS: http://sens.org/research/introduction-to-sens-research

Hallmarks of Aging: http://dx.doi.org/10.1016/j.cell.2013.05.039

Seven Pillars: http://buckinstitute.org/CellCommentary
Probably an amplification attack using Google, a clever way to increase the size of an attack without adding too much additional cost.
But your comments are very positive about google.
Glad your doing better. We were there for TCH so I have a similar love of the place and I'm grateful for the care we received in the med center.

That said I'm not sure all of Houston is so tough and gritty, especially around the Med Center. If you drive North 2 minutes from the there the 300 acre Hermann park and the Museum District are both gorgeous.
I'm glad you emphasized potential and mentioned reality.

One other aspect that has become increasingly important is power consumption and heat. Huge data centers now have to worry about enormous electricity consumption and keeping all the equipment cool. JIT code must do more work to compile (and recompile to optimize) on the fly which means more power and more heat.

On the consumer end, Android just switched to Ahead of Time compilation instead of JIT because its JIT performance wasn't that good and it required more power thus sucking battery life.
Different exchanges and principals, so it's unlikely. I don't know what BTER uses on the back-end, but unless it is written in Go, I find the likelihood of a connection to be very small (due to a common vulnerability). On the other hand, if there is a shared vulnerability, it may be in a commonly used library lower in the stack.

There is one possible tangential relationship, however. As I've been researching the transactions, early indications point to a portion of the stolen BTC and NBT from Excoin being placed on BTER prior to BTER's announcement. If this is the case, the parties responsble for the Excoin theft may have inadvertently deposited their coins into an exchange that was subsequently pillaged...

(Disclosure: I'm a member of the Nu development team, so Excoin's and BTER's exchange problems affect our community)
Likely response to that is "Not a team player."

And you're better off not being there.
It probably hasn't led to any predictions yet. This seems to be a theoretical model for empirical phenomena.

I took a course in material science once, and it's ridiculous how many variables are involved in developing new alloys. Not only does the precise ratio of several ingredients matter, you can get wildly different results by heating the metal to slightly different temperatures. Even the rate at which you cool the metal after heating matters. If we have a better understanding of the underlying processes, maybe we can better decide what experiments are worth trying.
All I have to contribute is that I agree. As someone trying to hire engineers, I genuinely don't understand how companies can get away with such paltry offers.

Probably the most ludicrous to me is Buffer's ridiculously low pay: https://open.bufferapp.com/introducing-open-salaries-at-buff...

I'm offering a minimum of $125k with significant equity in a well-positioned company, but I rarely see good engineers interviewing. Yet somehow these other companies are building engineering teams for way less.

Ultimately, I think it comes to developers way over-valuing hype. Appearing on Hacker News regularly, or showing up in Techcrunch a lot, or getting funded by YC, can apparently provide an automatic $50k bonus on all salaries you offer.
Basically it works like this: If your options become very valuable, the people on the other side of the table are no longer the friendly technical founders that you know and love. Instead, they're replaced by calm, professional capitalists and attorneys, whose sole raison d'etre is to separate you from "your" claim to their assets by many convoluted and entirely legal tricks, all of which feel profoundly unjust to the common man.

They are specialists; they do this all day, every day, and since you are just an unsophisticated code monkey, it's vaguely like playing one-on-one basketball with Lebron. So unless you have something their bosses really want (perhaps domain knowledge of the business) you almost invariably end up with pennies and fake smiles.
Not the best headline there .... at least the way I read it, the headline implies that their advice is currently ridiculous. The article is about an old video.
Philip's UK origins make it especially appropriate!
I think he's parodying the arguments that people generally make for digital piracy.
That is true actually, I guess I meant i don't see for example HSBC(just an example) shutting whole company down because of they are getting hacked while bitcoin systems are are either on or off, isn't it?
It's not that simple, because of inlining and macros.

Those optimizations can be used to quickly throw out unnecessary code like null-pointer checks inside inlined functions, so they are valuable and good to have.

So it's a matter of how much energy you spend on diagnostics, which ends up a rather heuristic field and perhaps we'd just be better off focusing on better static analysis tools that are separate from or can otherwise be decoupled from compilers.
When a physicist speculates, and someone points out that implies a sign reversal in ohms law, "oh well, I'll try again later". There's an immense collection of constraints based on experimental results that they try to respect.

When a philosopher speculates, and someone points out a problem with the theory, welcome to the wonderful world of sophistry and logical fallacy, would you like your ad hominem attack flame merely well done or extra crispy? Usually with a trendy side dish of political correctness and authoritarianism. Not to mention the typical attitude of "experimental results, who needs em?"
Micron is the name behind Crucial.

Kingston has gotten very good (and they used to suck) at least in the eMMC space (not quite a SSD, but close).
Arduino vs. Arduino: Founders Fighting [German]
Telling apart which dead code the programmer thought was meaningful and what is the result of a macro or inlined function is difficult. Using functions and macros very often causes dead branches to be added, and optimizing out dead branches is a huge performance win. The fact that some already-incorrect code incorrectly behaves after these optimizations are applied is not a good reason to stop doing an entire class of standards-compatible optimizations.
Show HN: A Taste of Clojure for the Cjurious
This is more of a jab at Microsoft than anything, since the articles main argument is that Google is the new Microsoft because Microsoft employees work there... Give me a break.
Love this quote: "This is the first time I've actually contemplated NOT replacing production hardware any time soon."

There are two things that benefit from the turnover of machines, one is that Intel stays profitable, the other is that hardware standards have a chance to evolve. The move from ISA->PCI->VESA->AGP->PCIe on video cards would not have been possible had people been holding on to their machines for 3 - 5 years before buying new ones.
The article mentions that it's not just a matter of having 20 grams of X, and 100% of our daily requirement of Y - a lot of these things seem to work together in concert, as catalysts.
Bones also suffer from other processes that damage the structural properties of the extracellular matrix such as cross-linking by hard to break down sugar compounds. There is also a process of growing cellular dysregulation wherein the ongoing bone remodeling favors destruction over construction, and that is distinct from stem cell decline. Every tissue is impacted by multiple forms of damage beyond loss of maintenance via stem cell function, some of which, like the cross-linking, accumulate slowly and cannot be repaired by our biochemistry. Clearance of some sort will be needed.

The body does not replace all of its cells; different tissues have different turnover rates. Many of the cells in your central nervous system will be with you for your entire life. There is research to suggest that even some of the individual proteins in those cells are never replaced either.
It seems that every decade, if not more often, the consensus of what is and isn't healthy changes. Sometimes it's due to fad diets, sometimes it's due to a typo, and sometimes it's just because this is complicated and sometimes we get closer and sometimes we get further from a perfect understanding.

Hopefully, the general trend is to move closer, though.
Changes in my open source life
Microsoft Outlook App for iOS Gets IMAP Support
In what way? Both are suggesting that it is the responsibility of charities to support the changes that disabled people need to be able to participate in society. If you believe that deal charities should pay for subtitling, why shouldn't other charities convert my business to make it accessible?
For sufficiently large values of 'large', large primes are hard to generate. If (that's a big if) we had an efficient method to compute this number to arbitrary precision, we could compute primes of a billion or more bits.
Ugh.. I'm generally in favor of the recent compiler optimizations dealing with assuming undefined behavior isn't triggered (although it has broken a lot of code that had made poor attempts at overflow checking, mine included) I think doing it for the mem* functions is a step too far.

I think it really was a defect in the C standard to not specify behavior of calls like memcpy(NULL, NULL, 0) It has obvious no-op semantics, and every implementation I've ever seen would accept it just fine. I bet there is a lot of code out there that assumes that memcpy() and friends work in this "traditional" way.
"In fact, for products like milk and flour, where fortification and enrichment have occurred for so long that they’ve become invisible, it would be almost irresponsible not to add synthetic vitamins."

How come most countries don't do it, then? At least in Germany I have never seen added stuff in milk or flour.
It should be possible to use a SMT solver to automatically check for code for which the -O0 version has observably different behavior than the -O3 version for some inputs to the program.

Though I'm not sure current SMT solvers are up to the task. (Related: I was using Sugar for something a while back, only to find it was spitting out weird error messages. Turns out it encodes integers as <size of domain> boolean variables, which doesn't work particularly well for large domains - it was hitting a 4 (2?) GB limit on the size of the temporary SAT input file and choking)
The “Funny” internationalization languages could be doing more harm than good
Those who drink alcohol shouldn't become alcoholics. However, it's a risk. It's easy to say that a founder shouldn't go into debt to keep their dream afloat and protect their employees, but the reality of it is very hard. If it weren't a risk, pg wouldn't have written about it. Going back to the original question, a founder reaching into their own pocket might not involve acquiring debt, but rather cutting their own salary. When faced with making a payroll, the founder(s) are likely simply not to pay themselves to get through a cash squeeze.
One could at least throw an error / warning in "obvious" cases, like this.
I'm late to the hate-parade but I did want to chime in to say how much I appreciate all the work the go team has put into the language, and tools. Go is a wonderful tool to get things done with. I recently rewrote a cross platform `enterprise` app from java (25k LOC) to go (8k LOC) and saw improvements in readability, memory footprint, and overall quality. Some notes on my experiences so far:

Go binary size is a non-issue for most software. The java-rewrite I mentioned above went from a 80MB or so binary, to a 8MB executable. That said, there's been a few occasions when I've really wanted to use go for an embedded project, but couldn't due to it's size.

I read somewhere, someone said of go, "you'll come for the concurrency, but you'll stay for the interfaces. This is very true for me.

Generics. Go's red herring. Sure, there's been a handful of occasions where generics would have saved me some boiler-plate, but it's not been a pain point for me.

Tooling, from fmt, vet, to unit testing are all first rate. However, I wish there was a better debugger option for go. I know that gdb works with go (and with a great deal of difficulty if you develop with OSX) but I'm probably not alone when I say I really dislike GDB.

Overall, I've found the community to be friendly both online and in person.

As an aside, I've noticed much of the recent vitriol towards Go seems to come from the Rust crowd which I think is too bad. I enjoy both. Languages are not a zero-sum game. Who knows, the hate means Go has finally arrived.
Creating the public fork and pushing to it is among the last parts of the process of making a contribution in my process. At that point you're making your changes public anyway, so I don't undersand this concern at all.
I'm sorry, but there's a huge difference in preserving a letter and a file. I say this as someone who has worked in the field of preservation (mostly digital) for close to a decade.

Really simplified... For a letter to be preserved: put it in a box and take it with you when you move and hope that the house doesn't burn down. For a file to be preserved: keep backups to avoid data corruption and media deterioration. Also: control physical media obsolescence and format obsolescence. Most people don't have clue about these things. If our cultural heritage institutions don't get their hands on some of these files, most of them will likely be lost.

And no, it's not only about our great grandparents. It's also about the Turings and Einstens. Their day to day mail correspondence has taught us quite a lot. Turing might not have been a good example though... :)
Note especially that the proposal is for "non-recreational operations"
- FAA tends to make a big differentiation between commercial and private
(recreational) activities. I read this proposal as being aimed at movie
production, utility (pipeline, powerline) inspection, and similar operations.

Another thing about the FAA - once they write rules, they are
generally reluctant to change them, so for anyone wanting to comment
on the NPRM, sooner is better than later.
I'm sorry, engendered... but are you an idiot? Do you even understand the context of the conversation?

-Matt
https://www.youtube.com/watch?v=x8wcP-W2pTQ&list=UUysVbKMJEm...
From the paper: 'Even for very long 100-year projection horizon, with the most radical life extension scenario (assuming no aging at all after age 60), the total population increases by 22% only (from 9.1 to 11.0 million).'

That stat is for Sweden—in case anyone wonders where the numbers are from.

Anyway, that's for the next 100 years. In 5000 years one would hope the human race will be multi-planetary. Looking at the time-scale, concern is still misplaced.
What about by default throwing an error or warning only in cases where it is "obvious"? (i.e. only in cases where the check was explicitly stated, so no macros / function boundaries / etc)

Ditto, if you have an explicit block (i.e. no macros / etc) that always causes undefined behavior, warn or throw an error by default.
There are way too many projects / websites where the 'about' page fails to state the blindingly obvious eg 'CrunchBang is a linux distribution'... which would save a lot of people a lot of time.
No Need for Bike Locks: Tokyo’s Amazing Underground Bicycle Storage System
I spent some time on Quirky ~3 years ago, trying to push designs for my desk 'leg hammock.'

At the time it suffered from the problem of everyone ganging together to only vote for people who were regular users in the community who had gotten to know each other. It disadvantaged a lot of people who had great ideas and designs, who weren't interested in all the effort to build 'alliances.' The Quirky team acknowledged it was a problem in some private emails, but I really don't know if they ever changed the system to minimize that, maybe they did? It's a shame because I would have used it more if they had solved that problem.
IMHO the website tries to hard to portrait wake as a better language than others. Its ok to compare yourself to other languages, but the bytecount (which doesnt really say much about a language) and the coloring of the boxes leave a bad taste with me.

Same in the "What Wake did without" section. Yes, you do not have those features, or bugs, but have you really "FIXED" a bug? There is no bugs you have fixed, just different design decisions.

edit:
The language may or may not be actually worth something, but those things make it look like they try to hard to me.
4KB random writes should have a WAF of 2-7 depending on over provisioning and assuming random writes. But real workload are not purely random so it will be better than that.