skysight-inc/HackerNews huggingface dataset:
I have been both side of the fence, and when I have the freedom to choose which projects I apply for, projects with native UIs always win my heart.

Personally I think it was a good move to go back into native UIs, right about the time people were starting to adopt Angular.
The point is not saying movies are a good source of information. Just that the guy is stating the obvious. We all know that money don't make you happy. We all know that not having enough money will make your life difficult. We all know having enough money will make your life simpler. We all know that human relations get twisted with money. No point in writing an article that is just the clone of most movies/songs/books about people getting rich.
It's good that you don't mention hydroelectric energy, because based on your criteria this is the most dangerous way to produce electric power, killing 170,000 people in a single incident: https://en.wikipedia.org/wiki/Banqiao_Dam
That language with your described properties already exists and is called SBCL (http://www.sbcl.org/). I'm not sure what you're arguing at this point though and don't quite get what point you're making.

Compilers, optimizations, type systems, and proof systems are all very closely related and if you want correct optimizations then you must annotate your code with types that the compiler can verify and use as assumptions in an optimization pipeline. These things are not easy to engineer. Saying just JIT it doesn't make much sense.
This is incredibly myopic.

Burning coal for electricity generation has released in to the environment more radiation, heavy metals, and other pollutants than civil nuclear power could ever hope to.
http://www.computerworld.com/article/3136714/data-storage/ap...

The damning benchmarks seem to be related to AMD vs. Nvidia. I don't know much about that but I'd put it down to optimization issues in a few apps. The 2016 15" definitely plays all games better than any MacBook before it.
> I imagine that if you were to behave
> on Uber the same way as you would on
> public transit, you wouldn't get banned

Public transport can't and won't ban you for having a disability that's inconvenient to the driver, won't ban you for being homeless and having an unpleasent odour, and won't ban you because you're an ethnicity that's currently being discriminated against. And in the unlikely case it does, you'll find strong lawful protections against that.
Things humanity is not ready for yet:

- Eugenics
- Marxism
- Web sites without servers
Although I haven't used any of them yet, the various beeware projects have always been interesting to me. I've especially been watching Batavia [1] because I think it could be a very interesting way to ship form/page validation code written in python to web clients. Lots of projects have tried this in the past but I think the approach it is taking is interesting in that the resulting code is relatively small (compared to other approaches) to serve.

http://pybee.org/project/projects/bridges/batavia/
It's ok, since most people never get "at scale". When you start getting these problems, it means you reached the stars you were shooting for. Having those issues are a good thing.
Yes, definitely! You can use something like https://github.com/mbylstra/django-wham to consume APIs using the same interface.
"Coal,"

Don't mix coal... with wind and solar.

Coal releases proportional amounts of carbon dioxide when used to generate power. On the other hand, wind and solar release fixed amounts of carbon dioxide (during construction and transport) then generate energy C02 free.
I think you don't understand the design process. Not being bitchy, so let me explain.

Instinct should be 1% of design if anything. Design isn't about colors and pretty, it's about a detailed process that includes data structures, mapping processes, analysis of users' behavior and removing all instinct and subjectivity from the process of design. It should include a minimum of guesswork wherever possible. It always amazes me, for example, that shared hosting comes with awstats as standard on 99% of shared hosts, but designers and web-developers alike ignore all the data sitting there available for analysis, to use just one example of how designers aren't using the tools available to them (and you have to know what to do with the awstats data too).

My prediction for the future of UX is that the army of self-taught pseudo-UX 'experts' are going to have to up their game, get some real training and stop being intuitive if the industry is to continue to grow. Would anyone on HN hire a full time software tester/QA who didn't have some training in that field? Probably, but you'd be better off with a QA who is certified.
Yes, as someone who was using MySpace a lot for consuming music, SoundCloud's design was revolutionary.
I could see Use of Weapons or The Player of Games work. Most of the rest of the books are too... weird to get right in a 2-hour movie format.
When you want to write a letter by hand, do you clear your entire desk and get a desk-sized blank sheet of paper to write on ?
It is a highly localized radio player. Reduced data usage seems to be highly demanded by customers and other app owners tell users it's impossible. But I know nothing is impossible :-)

I am currently experimenting with a streaming proxy that will channel data with 60-70% reduced quality (for customers who aren't audiophiles).
> Unless we are talking about multiple threads here (which we aren't), there is no other code that is executing that can change what this const reference is pointing to.

... except if your code calls potentially 'impure' functions.

void f(const int& value)

{

const int a = value;

g();

const int b = value;

assert(a == b);

}

One can't tell if the assertion will succeed.

Indeed, 'value' might have been modified as a consequence of calling 'g'.

You don't have this uncertainity if 'value' is marked as immutable.
This is why went from someone that enjoyed web development in its early days to work on native UIs every time I get the opportunity.

Nowadays I see Web dev as plain work, for fun I code only native.
It only kills in case of a serious incident. Incidents are rare.
Coal pollution and deaths are guaranteed
Problem: AWS Lambda cannot be used for high-traffic low-latency APIs over HTTP right now, because of cold starts and high API Gateway costs.

Project: Keep AWS Lambda functions warm by calling them every so often, making sure enough containers are provisioned concurrently. Currently working on a prototype for an API Gateway replacement.

Prototype available on https://lambdacult.com/
That kind of optimization is well outside the bounds of "sufficiently smart." It happens routinely.
> to have a 99% certainty of our condition

That seems way high. Correct diagnosis by doctors isn't 99%, or even close.
As usual, it's someone that has questions about a theory in fiction that instead of looking for a way it could be right, assume they are correct and easily find a way it could be wrong.

The same reason the future is so hard to predict is the same reason outcomes that don't necessarily make sense at first should be given the benefit of a doubt and reasons should be looked for, not discounted.

Not only does it make things more enjoyable, but you end up learning a lot more. It does take admitting you may not be the genius you thought you were though, so some people have trouble with that...
thanks for catching that :-)
Not quite; the point it's trying to make is that having an enum is not necessarily a guarantee that no new members will be added in the future, or at least it shouldn't be.

I think it's half-right, in a sense that this is true for enums that are used for input values only. If the API adds a new enum value, it can also add handling for that value, so existing clients should just work (they just never use that new value). But if the enum is present in any output data, then adding a new value to it is a contract break, because existing clients can see it, and they don't know what they're supposed to do with it.
No matter how benevolent Amazon may be, it is still problematic that, when you "buy" an ebook with them, they are technically able to remove it from your ebook reader. This is bad even if they only use this power when they mess up or when they are legally compelled to do it (an option they still explicitly allow for). So even if they apologized and promised not to do it again, the point still stands...
"It's not just about the compiler being smart. There is nothing more you can do with x -> 2 + x other than compile it as is.
"

This is just trivially wrong.
You can always add checks that it is a thing that lets you optimize better.
You can always just JIT in addition to static compilation.
Uh?
This happens all the time.
Not all platforms allow for dynamic linking.
You know what really bugs me about the whole affair? And granted. I didn't look into this specific product, but

Why the hell do I need cloud storage at all for a fucking garage door opener?
Exploring the memoize function in Clojure
Can you elaborate on your tech stack? Do you develop for mobile, web, or both?
The only point where the article brings coal into connection with the nuclear power shutdown is wrong:

> Germany buys cheap coal-fired energy from Poland to pick up the slack left by the abandonment of nuclear power after the Fukushima disaster.

Germany is a net electricity exporter.

> Germany is one of the country where coal is the deadliest in Europe

PM pollution is lower than average in the EU for one: http://ec.europa.eu/eurostat/tgm/graph.do?tab=graph&plugin=1...
What @wbl wrote also makes sense. Nuclear power has a closed fuel cycle: what goes in comes out and is stored.

There's no way we could hope to capture all the radioactive particles from a coal plant exhaust, not in the foreseeable future with any reasonable efficiency.
That's not what i said. I fund research grants and review papers for a lot of these conferences and areas :)

What i said was quite specific:
We are talking about aliasing here, and in the area of aliasing, we pretty much know all of the tradeoffs, upper and lower bounds.
We know how good we can make algorithms, we know how to make them scale as well (single cpu, gpu, parallel, you name it). On demand, ahead of time, etc.

You can engineer inside these tradeoffs all you want, and come up with amazingly nice hybrid algorithms that do all the right things.
It's about how much time and energy you want to put into it.
But here, there is no magic left.We know precisely what we can and can't do, and how it will turn out.

Put another way: Given me a budget ( money, compile time, amount of memory and number machines that can be used at once to compile, etc), i will give you your choices, and implement them :)

Additionally, I can also tell you that no matter what your choice, when it comes to aliasing, you are talking maybe 6-8 months of work to build an initial version for someone with experience in the area, assuming what you want is super-complex.

The two current CFL implementations (on demand pointer analysis) in LLVM, for example, were developed by two interns, each in 3 months.

Building a very large scale "as precise as it gets" context-sensitive field-sensitive pointer analysis that worked across 10k machines took me about 6 months (to be fair: starting point was a well functioning distributed graph processing infrastructure. Obviously, that would have taken a lot longer to build :P).

Honestly, the reason you don't see more done here is because it's not the low hanging fruit for most compilers, for most apps people care about. I'm saying that as a guy who really loves aliasing, but also owns google's compiler performance teams.

Like most areas of compilers, alias analysis hits a good enough point, you leave it alone for a while, you run out of other things you can improve that are bigger bang for buck, you come back and improve it, repeat.

In fact, humorously, improving aliasing significantly often makes the compiler generate worse code to start because it now has a lot more freedom to go crazy with optimizations than it used to. So then you have to spend time coming up with better cost models for those optimizations, etc
Why? Cyprus has nothing but to gain from joining Schengen. Where does Greece come in? EU citizens can already travel freely in Cyprus [1], so why would you say GR doesn't want Cyprus in Schengen?

[1] http://www.cyprusembassy.fi/main/index.php?p=Consular_Sectio...
Oddly enough, TimeWarner (Spectrum) is giving me an overall discount on my bill ... in exchange for having TV service. What I mean is, my final bill for Internet+TV is _less_ than just Internet. I don't even watch TV. I threw the installation kit in a box and haven't ever set it up.

Seemed to me they were doing it to inflate subscriber numbers.
Really? It's that simple? I wonder then why all these compiler writers spend so much time on getting the type system right if all they need to do is just add some if statements and then add a JIT.

Guess I can also solve all pointer aliasing problems by just adding "if p != q {...}".
I have found it common to refer to devices as "bricked" without any reference to whether a refund was available, and I have definitely heard people say they returned their bricked device to a store, so I don't think your usage of the term is standard.
Question is when do you stop? At what point does adding runtime checks become too expensive? I doubt you want to end up with gazillion checks for non-overlap.

C and C++ both seem to lack user-specified type aliasing relations. You have to work with standard base types. I want to be able to declare my own type that is unique on its own and aliasing relations with other types.
Don’t pay for what is for free: Fake Adobe Flash Player app found on Google Play
Nokia relicensed it to LGPL 3. Bindings for other languages can have another license though, obviously. For example, the Python PyQt bindings are licensed under GPL or a commercial license.
Brands ranking by 1000 teenagers
We must be using different compilers then. Last time I checked there are some heuristics about what gets inlined and when exactly those heuristics are triggered. Something about compilers being terminating programs and stack depth not being an unbounded resource. I don't know though. Maybe I was reading the wrong literature. What are your sources?
This image is a segment from a study done by Google, page 9 of 16.

https://storage.googleapis.com/think/docs/its-lit.pdf
New sample of Pegasus / Chrysaor malware was found
What else do you base decisions on?
> Really? It's that simple?

Yeah.

> I wonder then why all these compiler writers spend so much time on getting the type system right if all they need to do is just add some if statements then add a JIT.

Because (1) JIT has a latency hit users like to avoid, and (2) you still have to solve the same problem during JIT time, it doesn't magically go away.
buzzzzzzzz No.

Standardization exists. In two ways. Either your brand has a standardization or your platform does. Both work. It's like saying "we only need one coding language" when the reality is quite different.

The disconnect is when brand isn't as complete as platform. Granted, platform has really only fallen into place in the last few years for iOS and Android. But does brand really need standardization initially? No. Because new paradigms need to stand out, either for UX or for impression. Otherwise AOL would be Snapchat, and it ain't.

I respect that coders don't grok product design fully or in parts. But please understand, a great deal of the fun, the joy of tech, is in UI/UX evolution.
Facebook is less cool than Walmart and Wendy's...Pizza Hut.
Paper, 1.1 released
"One can't tell if the assertion will succeed.
"

If value was originally a const object (IE immutable), it is well defined and guaranteed to always succeed.

IE
const char* myString = "Hallo World!";
const_cast<char*>(myString)[1] = 'e';

This is illegal, the same as anything modifying value would be if it was originally const.

If value was originally not a const object, it wasn't immutable, so anything goes.

"You don't have this uncertainity if 'value' is marked as immutable.
"
You can, in C++ mark the original immutable in a way that you can tell if the assertion will succeed.
This is about a Mac Pro not MacBOOK Pro.

You can build a much more powerful computer and put OSX on it.
One biggest takeaway from this is that they can have multiple machines for the same IP address. That is just awesome and also explains how they have probably managed to scale up services 8.8.8.8 without needing to use load balancers.
I do. with very similar configuration to production
UX is about needs and goals of users. Is about research with the users, documentation, and then UI, and usability.
UI is a part of UX. The most visible, not the most important.
This graphic shows it pretty well in my opinion: https://upload.wikimedia.org/wikipedia/commons/c/c9/Energiem...

Purple is nuclear energy. Dark green is biomass, light blue is wind power, yellow is solar power
Project 54/74 to document 54xx/74xx-series logic chips and subfamilies
Ask HN: Alternatives to Coinbase Payment Pages?
Now that Coinbase Payment Pages are officially gone (why,btw?), are there any alternatives? Like a voluntary registry for identifying owners of bitcoin wallets, so I can check up on an address before sending money there?
> Any software or web page you use is backed by an inscrutable pile of legalese

This isn't the case of all software, fortunately. For free software under the GPL, for instance, you don't need to read the GPL or agree with the GPL to use the software. (The GPL is only giving you additional rights, beyond what copyright already permits.) Specifically, I don't think I am "agreeing" to any terms when using Firefox.

If you use a Linux-based operating system like Debian and free software, you don't need to agree to much legalese, actually.

(OK, this is about terms and conditions, not privacy policies. But privacy policies for free software is about giving additional privacy guarantees -- you are not forced to read it or agree with it.)
Not worth the trouble. Its too much trouble with the updates and all that crap. I have people calling me about their hackintoshs and I tell them to call someone else
Assuming you have the resources to cover these events, sometimes you hit scale, but not profitability..
> That statement doesn't jive with his previous posts.

Nope, it does.

His original post (not posts) pointed at foul language first and foremost, which was then compounded by posting an equally charming Amazon review without making any attempt to wait for a reply. So his follow-up matches the post that led to this whole brouhaha.

But let's not allow this ruin all the fun of the vigilante justice and trying to beat the living daylights out this guy.
Rust is actually lovely for peripheral register manipulation.

Check out the zinc project for some great examples.

Likewise, linking to external libraries is trivial.

I'm not saying that rust is better than any other language. But those examples aren't factors in this religious debate
It's dead easy now, the biggest issue might be the sound or gpu depending of your hardware
Fighting the temptation not to go to jail isn't that hard.
Nazis had their moment; we as a civilization already "rebutted" their arguments and decided their worldview is incompatible with ours. If they think they have a better case now, they better present it more eloquently than with provocative symbols.

If someone is wrong a 100 times, why listen to them the 101st time? Also, if their first 50 arguments involved massacring millions, why should we entertain _any_ future argument of theirs? In fact, perhaps entertaining the first 50 ones is what lead to such violence. If we give unlimited room to violent ideas, how can we be surprised when violence takes form?

Why give speech to those whose goal is to deny speech and life itself? I would argue that giving free speech to ideas that goes against the principles of a free society is not only a huge waste of time, but a big danger.
You can build a hackintosh for half the price, only the laptops are relevantish.
What CSS minifiers also leave behind
Yup. I think it can give you a 99% certainty what condition you don't have, but not what you have. Especially not without physical recognition.
Deep Blue did not use brute force search. Like all successful chess engines, it used heuristics to estimate the value of board positions, and focused its search on the positions that looked most promising. A truly "indiscriminate" search would waste so much time on losing positions that even I could beat it.
I can do both, design and development. For what it's worth, I can't design the best nor code the best, but I make damn fine products because I'm not caught up in being the best at either.

I make products that ship, people like, and can be further developed in both design and code by specialists. That's good enough.
It's really easily billions, not hundreds of millions. I work for a much smaller outfit and we (handwave) push the smaller number already.
I watched a cinema rip, to decide whether it's worth to see it in 3D in cinema, for the effects at least (I also didn't expect anything great). In the end I decided not to, because it would just make me angry.

There were so many homages to GitS movie, but done so badly! My favorite scene in the original is the museum tank fight scene, where you can feel so clearly how desperate the situation is (from many small details). The same scene in the new movie just doesn't give you any feelings at all about the situation.

Perhaps it's a decent action movie if you don't know or like the original.
If you forget about the static concepts of compilers, input data, and program source code, you see that it's all just inputs to a computation process and it's possible to specialize the program to the input.

(See also: partial evaluation, Futamura projection)
Now you understand a tiny part of the Energy business. 'Nuclear' is not only a technical problem, it is a financial problem. Old plants will be run until they collapse - unless a regulator keeps the companies from doing that. But then the regulator comes onto pressure, because there is huge amount of money/corruption involved to keep the plant online. Every single plant is a multi-billion dollar investment, jobs, surrounding industry, ...

Tepco from Fukushima claimed until the day their plants were hit, that everything was totally safe. Politics supported them. Nobody was questioning them.
AT&T is cooler than Facebook Messenger.

Whatsapp is really uncool, beaten even by TMZ or Yahoo.

Twitter is surprisingly cool, although easily beaten by Instagram and Snapchat (no surprise there).
Yes.
Actually, it kind of is.

Note:
I'm one of these compiler writers.
In fact, i'm one of the compiler writers who wrote the current aliasing implementations for the two major compilers everyone uses, among other things.
If you are going to disagree, please be concrete.
I'm stating that good enough aliasing algorithms exist to do what you want, and where you can't, you can do runtime checks.

People who truly care about performance hand the compiler the whole program, and want it to do a great job.
It can and will.
Your counter argument is what, exactly.

That because people spend time getting type systems right, this must be false?

If so, that's just silly.
People spend time on getting type systems right to make it easier to reason about for people.
Not because it's impossible at the compiler level.
But because they'd rather not have to do it if they can avoid it.
That doesn't mean it can't be done, and isn't done.
FWIW - designers are facing the other way - to meeting and exceeding client expectations. In many cases it's not about what can be built, but what could be. It's not great for devs and most of their best stuff gets tossed when it hits real world production. But for a moment, the client was overwhelmed. And that's what sells design.