skysight-inc/HackerNews huggingface dataset:
First PowerVR, now Mali – great news! I wonder if Qualcomm will ever publish some specs on Adreno, though.
A light bulb has more processing power than the PC I used in the early 90s. What an interesting world we live in.
Show HN: Dealora (SMS Marketing for Small Businesses)
But why not just cache the JITed code? There's third party JIT runtimes that do it (Excelsior JET) and it's planned in the official Java 8 runtime.

Caching first-run still gives you the ability to do more/new profiled-based optimization later.
What law protects him in the Embassy?

A few people in this thread are saying that he's not on English soil; that the embassy is under Ecuadorian law.

That's a myth. Ambassadors get immunity and international politeness means we don't go raiding embassies[1] but Assange is in England, on English soil, subject to English law, and being in some other country's embassy doesn't change that.

[1] unless they hold hostages or shoot our police officers
All of the HTTP, socket, encryption, compression etc libraries have a really clean, consistent design based around stackable reader and writer interfaces. This makes it really easy to combine things, swap out transport layers etc.

Go routines and channels are also nice for handling concurrent requests though I find myself using mutexes more than channels for finer grained control.
> That's going to be a large albatross around Go's neck, as it has been around node.js', and Rails before that. Large amounts of developers flocking to a new thing because "this is the thing to use now and if you don't you're dead meat".

TJ's blog post is basically like if DHH ditched Ruby/Rails for Go.

> Personally, I thought Node.js was a terrible platform for serving dynamic web sites. It is, however, a great platform if you need to make a reasonably performant general server with minimal effort (such as a message broker for example).

Totally agree with you,nodejs is not a silver bullet.
Maybe it's because I didn't link to a source. Edited in one now.
Recompiling is an issue on large code bases, that's the problem, power is secondary, slow app startup is primary in my experience.

If you cache jit code it loses it live data benefit for the most part, might as well AOT on your build server instead.
Nabbed a ticket. See you there!
I wonder why Zurb Foundation does not get as much love from HNers?

I use Foundation and I have really no need for a themes market . SaSS and Foundations' media responsive layout enable me to create new themes easily and painlessly even though I am am a back-end programmer.
If you cache you lose most of the benefits of a jit, might as well AOT one time for everyone.
As is AWS but I suspect is easier to migrate from AWS
Well the iptables stuff is fair enough, I just don't see the need for the hex dump stuff as it exists in plenty of other tools.

Also you can generate the bpf bc directly from tcpdump

tcpdump -p -ni eth0 -ddd "ip and udp"|tr "\n" ","

See: http://blog.cloudflare.com/bpf-the-forgotten-bytecode
I totally see your point. I think what's tripping me up is that I'm new to node/JavaScript and coming from a strongly typed world, I'm still writing my apps with that framework in mind. Working with dynamically typed code requires you to think about your application differently and I'm just starting to understand the patterns.
> Not to put down rape or anything but any woman in your life could say you raped her and if she's a good enough actress you could go to prison without any proof.

This is such a myth and I'm really tired of hearing it. The fact is the vast majority of sexual assault and rape prosecutions and charges do not end in any conviction. Also, rates of false accusations are far, far smaller than rates sexual assault and rape, so the reality is that it is rare when something like that happens.

Most women you attempt to press for a sexual assault charge are often unable to get one on the very basis on which you seem to think they can magically send you to jail: people don't believe them, proof is often hard to come by due to the nature of sexual assault, and misogynistic cultural stereotypes are often held up as reasons why sexual assault couldn't have possibly happened.
If you cache everything, you're just doing AoT compilation.

Not at all. That's a false dichotomy. You can restore the past JIT-ed code from the cache and do new profile directed optimizations. Java JITs already do this, just not (AFAIK!) HotSpot.

there are a lot of really smart people working at Google on Android

...and yet their previous runtime was 3 times slower than Sun's one, requiring a full rewrite. Sorry, that's just an appeal to authority, not an argument.
You are probably thinking of Rob Pike's talk, Less is exponentially more:

http://commandcenter.blogspot.com/2012/06/less-is-exponentia...
Choose: Grunt, Gulp, or npm?
"shinny" should be "shiny" on this line:

We will do the rest for you. Just look on our shinny loading indicators while we are deploying your code without any downtime!
Maybe it helps with latency? When a user presses a button, you don't want to have to compile some code before you can show them the result.
Actually they are retiring the "Web and Business" pricing plans, which were charging for storage size and introducing a new pricing plan that charges for both storage size and "Database Throughput Units", which kind of obscures what they are charging for - something related to transactions volume and based on my experience with other "cloud hosted" databases, I can guarantee you that it gets pretty freaking expensive.

The smartest thing to do is to never rely on a particular service of a cloud provider. For example we once made the choice of using Amazon's DynamoDB, which is great in the beginning, but at some points along with scale issues the costs went through the roof (DynamoDB also charges for "throughput capacity") and we just switched to Cassandra - but we planned for this migration ever since the beginning.

And this is the problem with cloud providers - the pricing schemes on these services are designed to hook you with affordable prices in the beginning, but later on as your business grows they get much more expensive than hosting your own stuff. So use whatever makes you most productive, but careful about lock-in.
You seem to be implying that, because Assange leaked government documents, it is impossible for him to afterwards commit crimes. It's like some people in this community believe that leaking documents automatically bestows saint status on the leaker.
If you cache jit code it loses it live data benefit for the most part

As pointed out elsewhere: that's just not true.
> Ever asked yourself why deploying your projects to your servers is such a pain?

Personally, no. I haven't heard it from my peers either. I just use rsync and quick scripts; others use PaaS (self-hosted or managed) that generally handles deployment pretty neatly.

The only place I've heard complaints about deployment is inside of large multi-tier organizations, where the problem boiled down to communication issues between dev and ops, not tooling.

I suspect I'm supposed to be the target audience here, but I'm not sure what problem this solves for me. On a first impression this looks mostly like a way to lock myself into a workflow that leaves a lot of unanswered questions (re: server security, platforms/frameworks supported, etc), with very marginal benefits.
Arguments please. The post you are responding to already rebuffs this.
True, but the employer can always fire the employee before the cliff.

If you don't trust the employer, don't work there.
Startup time. JIT doesn't kick into action until after the app has started up and ran through some hot code paths. Up until that time things are interpreted and thus slower.

Secondly there are limits to how much you can optimize at run time. For servers there is more leeway in terms of available memory and CPU power but on mobile you can only optimize so much without slowing things down with optimization and jit code generation overhead.

JIT generated code has to be generated every time the app runs. Besides the pages used to store the JIT code are process private - I.e. no sharing.

Compared to all of this - AOT can afford to optimize more, it only has to do it once, the framework code can be spit out to common shared files on the disk this enabling sharing of those pages and reducing memory consumption. This gives you speed, battery and memory benefits over JIT.
It is really worth having a .do domain? given that they are fairly expensive and seems like google will treat them as specific from Dominican Republic and not generic[1]?

[1]https://support.google.com/webmasters/answer/1347922?hl=en
We wrote a blog post on great places to get free stock photos and shared it on StumbleUpon. We ended up getting 17,000 visits that day and it just went crazy somehow, even though our domain rank was non-existent. We were getting 10,000+ visits for about a week because of that blog post.

After the dust settled a bit on that post we were getting over 1,000 visits a day (still a lot from StumbleUpon) and now we're creeping over over 2,000 a day and slowly climbing.

Obviously, a lot of that traffic was not highly targeted but it still gave us a huge boost and our Google rankings have shot up lately. We're now on Page 3/4 for "Bootstrap themes" and getting more organic traffic which is great.
The author of the rather awesome three.js demonstrated how to make Famo.us' periodic table visualisation with his library: http://mrdoob.github.io/three.js/examples/css3d_periodictabl...
That's not really an advantage of AoT over JIT+interpreter, is it? AoT requires compiling at first run, the JIT can just use the interpreter (and preferably compile in the background).
On our current project (which is quite big) we use Mingle.
you should be able to access content via API - http://getcockpit.com/docs#!api/cockpit-js
FabFriday means Infographics For Sure!
> This is a textbook example of a large, public extrajudicial process.

Rather, it is instead a textbook example of how public figures that are supported by a group suddenly become incapable of fault.

Instead of letting the legal system of Sweden play out (you know, like Snowden had been trying to fight for with his leaks against the FISA Court), Assange's supporters simply declare that this is some vast world conspiracy against Assange, or that it wasn't really "rape" anyways, and even much more misogynistic things.

In addition all the contradictory evidence against that hypothesis simply gets glossed over. E.g. the extradition thing makes no sense, and never made any sense. Assange was being processed through courts in the U.K. while avoiding Swedish justice, and the U.K. is hardly knowing for making it difficult to extradite suspects to the U.S.!

If Assange was worried about extradition to the U.S. he should have fled from the U.K. ASAP. Given that wasn't what he did, he must have been more worried about something different (perhaps the veracity of the charges of which he was accused?). And either way, as mentioned in a sibling comment, the U.S. would actually have to charge him with something for extradition to apply, and those charges would have to come within the statute of limitations (and perhaps even within a shorter timeframe for whatever country Assange flees to).
Is your front-end/admin panel/... written in Go too? Because when noobs hear "We use Go",they'll think you're using that to generate webpages,CRUD apps,or write CMSes.
Privacy watchdog files complaint over Facebook emotion experiment
It's only "obvious" because it fits into Assange's narrative. If he indeed is guilty to the allegations, would it still be "obvious" that this is a political charade?
To me it is not obvious. Yes, it could be that you are right, but what proves it?
I meant only that if you want to use Scala, you'll inevitably have to also know Java. It's two languages for the benefit of one. The JVM comes with its own issues: which JDK do I use[1]? What happens when one library I want to use recommends a different JDK than another library I want to use? Build tools questions: ant, maven, gradle? Oh, I need to learn Groovy, too? Three languages for the benefit of one. Yay.

There's just an enormous amount of stuff to learn, and most of it is required-but-incidental; none of it (except Scala, in our example) is an inherently necessary part of getting from learning to a production system running Scala on the JVM, but you will end up having to become conversant with many of these things, and probably dozens of similar infrastructure and tooling systems.

[1] Haha. I was thinking this was mainly between Oracle's and openjdk, because that's what seems easily available, but it looks like there are four or five currently updated JVMs: http://en.wikipedia.org/wiki/Comparison_of_Java_virtual_mach...
Since you're directly asking for advice: no. Finish school as planned (earlier? awesome). There will be plenty of opportunities ahead. Don't set yourself on a path of failure because startups are very risky, these guys have no experience funding them and it seems like you're a technical guy having lots of fun (but are you an entrepreneur at heart?). Think about the odds of "startup being a success, in your perspective" vs "startup failing and I still haven't finished my studies". Just my 2 cents.
Assange didn't leak any governments. He only runs a publishing house that publishes the leaks that other people make.
Aeroporto de Düsseldorf Adota Revolucionário Sistema de Estacionamento Autónomo
> But why not just cache the JITed code?

What is the difference between AOT and sufficiently aggressive JIT caching?

> Caching first-run still gives you the ability to do more/new profiled-based optimization later.

Well you could have your runtime running with the overhead of an interpreter, a profiler, and an optimizer, and hope all will turn out well. Or you could just run the machine code without these complexities and know that it is probably close to optimal anyway.
Wut?

Cabs pull over, look at you, and drive off if you aren't the right skin color. It happens all the time.

They assume black people live in poor or dangerous or remote neighborhoods.

The law about cabs being required to stop is totally moot. Cabs simply don't pull over if they don't want to.

Go find a black guy and try to hail a cab with him for a few days. The data will really shock you.
>"it sucks less" is not an argument

Yes it's not an argument.
It's conventional wisdom that it's easier and faster to create app in native toolkit than in HTML/CSS.

I refereed to my components argument not to "suck less".

>>tags are tags like any other HTML tag.
>And what do you think lives inside the tags, pray tell?

You don't have to think about it (you just import the component) as you don't have to think what's current CPU pin state. You just use attributes to communicate with the component.

>"That's the point, the complexity is still there, just hidden."

And there is a value in this. Higher level langs hide complexity as well (eg. C# vs C) and that makes them usable.

>It's also wrong, web components make it somewhat easier to reason about the existing mess, they don't actually fix issues

I don't agree. In my entire web dev career single biggest pain in the ass was more or less like "what CSS rule is breaking my div style".

Since ShadowDOM brings CSS fence between components as you probably know (do you?), ShadowDOM makes it way easier to create HTML/CSS ui simply because it's hard to make CSS rules breaking whole app view.

I do agree layouting is an issue - it's just not that important at least for me - joe average web dev

[edit added what gives us Shadow DOM CSS boundry]

[edit2 - hell yea! no arguments? just downvote!]
I'm not sure I understand how.

You've gone through the JIT process of live profiling, hot spot detection, compiled down to native code etc. etc., then saved it along the way so that next launch you can start fast with everything already optimised (but also in a position to continue to learn and improve should the opportunity arrive.)

Your first run or two will be slower, beyond that you should be as fast as your code will go.
Isn't most of that then HIS fault? Yes, I think it is.
"You can restore the past JIT-ed code from the cache and do new profile directed optimizations."

Sure, but now you're paying for the compilation/runtime analysis stage more than once. If the JIT compiler is actively doing any profiling of your code, that's time and watts being spent not running the program the user wanted you to run. In order for it to be a net gain, you have to improve the efficiency of the user's program enough through JIT to pay for this repeated cost of doing the analysis however often you do it.

You can profile more intensively and more often, thus improving the generated code, but now you need to improve it a lot. Or you can profile lightly or infrequently, but now you have way less information with which to improve it.

In practice, it seems to be very hard to do significantly better than just running it through a good compiler once.
Up until that time things are interpreted and thus slower.

That's true - but not specific to mobile.

For servers there is more leeway in terms of available memory and CPU power but on mobile you can only optimize so much without slowing things down with optimization and jit code generation overhead.

Which makes me wonder why it's going into new versions of Android (running on 4 to 8 core devices, i.e. having plenty of free horsepower). If anything this is becoming less of an issue.

JIT generated code has to be generated every time the app runs.

False.

The memory savings argument might be something - particularly with heavy use of system libraries. Android phones usually have relatively memory compared to their other resources.
https://segment.io/team

Also listed on his GitHub - https://github.com/visionmedia
Read the comments below the article.
The answer is "yes".
Google.com/killer-robots.txt
What is the difference between AOT and sufficiently aggressive JIT caching?

AoT doesn't adapt to changing program profiles.
This is a textbook example of a large, public extrajudicial process.

Utterly inept, you mean?

If they wanted to lock up Assange so badly, why not just stick some child porn on his laptop?

Or send a bomb threat coming from his email address?

Or punch someone in the face and claim Assange did it?

Or get him rip-roaring drunk, deny him use of a lavatory, and arrest him when the inevitable happens on the walk back to his hotel?

Or 5,001 variations on this theme.

In other words: I believe it's neither competent enough, nor incompetent enough to be staged.
FCC: A Report on Consumer Wireline Broadband  Performance in the U.S.
Wouldn't the background JIT thread possibly cause some of Android's notorious stuttering in the UI?

Let's be honest, today's smartphones are more powerful than desktops of only a 3-5 years ago for most things, have as much RAM, decent GPUs and as many cores and near enough as much storage. It's actually pretty miraculous what's been crammed into these tiny mobile computers. When you remove the battery out of one it's pretty astonishing how much computing you can fit in a few ounces.
Concise CSS
In practice, it seems to be very hard to do significantly better than just running it through a good compiler once.

Why aren't the other Java runtimes doing it, then?
> the "tomcat stop; ant remove; ant clean; ant install; tomcat start... okay, NOW you can test" was quite difficult to develop against iteratively

Ok this makes even less sense to me. In 10 years when Go has the completeness of these big Java systems it'll be even worse since there won't even be a dynamic loading option and the only choice will be to restart the entire system like that.

If you want to like Go because it has fast basic features and that's all you need that's one thing, but it doesn't have anything to do with compiling speed does it?
It is not pay to win. In fact, you can get everything without paying a penny, it just takes longer. For example top players have not paid anything.
Opera. :)
Show HN: Sotro, The Social Introducer App
As far as I can see, it's not "being alone thinking" it's "being without any mental stimulation".

If someone says to me: "here's a really hard problem, no go in that quiet room and come back when you have the answer", that would be "being alone thinking" and that would be fine.

OTOH, if someone just puts me in an empty room with nothing to do and nothing in particular to think about, I'm going to get bored very fast, which is going to make the time seem to go even slower.

The actual report is behind a paywall so I can't see the details but I suspect there could be hugely varied outcomes for the choice to administer a shock based on how the intensity of the shock is described (and how bad it turns out to be in reality). The finding that women are 25% less likely to shock themselves might just mean that the men are more adventurous or less risk-averse, not that "men don't like thinking".

I highly doubt many of them would have chosen to administer the shock if it was presented as "definitely lethal" or "excruciatingly painful", whereas I can imagine that while bored someone might simply be curious to find out what a mild electric shock feels like. FWIW I've had lots of 240V shocks and they aren't as painful as you might expect; not at all painful in fact, most of the time.

As far as I can tell, it's not that anyone chose the shock instead of continuing to stay in the room, which might have been more interesting. That fact that someone apparently shocked himself 190 times implies that the time in the room was fixed regardless; it also implies that the shock wasn't particularly painful.
I was surprised as well, until I saw that. The npm/gulp/bower/less/node stack is pretty awesome for full-stack web development. All in one language, all open source, easy-breezy package management. If Go had that sort of complete stack (and for God's sake a package manager to rival npm), I'd probably be pushing Go as hard as possible at work.

As it stands, there's way too much friction and it would cost a LOT of money to invest in Go. There's a good chance that the ecosystem may not evolve to Node's level for years - and worst of all, if you want to build competitive web apps, you still can't avoid Javascript.
I quite like it!

My criticism is that after a while movies that I already marked as "liked" still appear in the Discover tab. By the same token, simplify the 5 different ratings modes into at most 3:

- liked it
- dislike(d) it
- put it on the "to watch" list

The rationale for this being that I'm not going to rate all the things I watched with 0-10 stars, and if I heart an entry that should train the filter and it should imply that I already watched it.

I get that you want as much data as possible about who watched and liked what, but if it's tedious to provide all that detail people won't do it.
Wouldn't the background JIT thread possibly cause some of Android's notorious stuttering in the UI?

No? Why would it? Unless it's a single-core device with bad scheduling and prioritization, that makes no sense.
Thanks for the reply. Game is called RPG MO. I might have to start showing the logo on loading and log-in screen then :)
could be great... someone already booked vacations. Next time would be great to know it a bit more in advance (especially for the ones wishing to combine it with corporate jobs).
And? The Declaration of Independence is not a binding legal document. It's legal significance is exclusively as an input to the Constitution. (Well, that and severing us from England).

You probably ought to make the provenance of that quote known, too:

http://candst.tripod.com/doinotlaw.htm

Or, just read more of his site; the most recent SCOTUS decision he cites on it includes the text:

"The Declaration of Independence, however, is not a legal prescription conferring powers upon the courts"

I have to ask... if you believe that the Declaration is a binding legal document, do you also believe, as the Declaration asserts, that all our rights come from God?