skysight-inc/HackerNews huggingface dataset:
For the record: as someone who started in the early '90s in C, I hate hate hate the Go declaration syntax. But the designers make a very compelling case for why it's the right syntax: C function pointers are needlessly convoluted.
One of the great things about Android is that you don't have to be running it on a "high end" phone. Why bother with another new OS for your low-end handset when Android runs pretty well on low-end devices and you still get most of the benefit of Android (Google Apps like Nav, etc, don't require much processor power, they run great even on sub-$100 (off-contact price) phones).
What about Google Play and all of the Android apps? Lose access to those and you have the Amazon marketplace and some fewer app stores. And I hear Google charges for access to Google Play and Google apps like Google Maps etc.

>If Google wants to standardize the ecosystem and is cracking down on these manufacturers who mess too much with Android then I'm 100% on Google's side.
Google needs to be harder on these manufacturers for the good of the consumers, the ecosystem, and ultimately the manufacturers as well. What will the "Android ecosystem" become if they create bigger and bigger incompatibilities and make developers jobs that much harder?

Err, is this related to this article?

>If manufacturers really wanted to customize their own OS, then they would never even try using WP8. And Acer is one of the WP8 licenses, too. So Acer wants their cake and eat it, too? Sorry, but no. Google needs to take actions against further fragmentation, and for removing any opportunities Microsoft might have with their more unified OS.

Again, I totally lost you here. What has using WP8 got to do with Android or Aliyun? How will Acer using WP8 fragment Android?

>and for removing any opportunities Microsoft might have with their more unified OS.

I thought this is considered anticompetitive and generally frowned on by the HN crowd(regardless of it being legal or not)? If Google does something like that while calling Android "open", it'll become a running joke.
If Pogue is this excited about this "Google technology", then it must be really good. But there's something worrying about Google putting it into people's hands possibly a full 2 years before it actually comes to market. While I'm sure the feedback was important, there's still 2 years in which a competitor can come out and take the market before they do, although I'm sure what they're doing with Google Glass is very hard tech and can't be easily replicated, but still. Someone like Apple could probably do it if they really wanted to take on Google in this market.
This one reason I don't read blog articles in an RSS feed. I aggregate them with one, but follow links to the blog owner's site so that I'm reading their content as they designed it.
I don't think that's the only reason he's quoted often. I think the fact that Woz continues to have very sensible opinions on a lot of things has a lot to with.
Thanks for the comments ig1.
Since I made the original submission to Seedrs I have had further thoughts on the pricing model and you're right - SaaS will be the right way to go.

I'm actually going to see if they'll allow me to amend the text. It was over a month ago I made the original submission.

I'm going to go with something like: Basic, Plus and Premium tiers. With added features and support for more employees as you go up in tiers.
SquareSpace Developer Platform
It meshes pretty well as is. If only I could get rid of the strings and redundant arguments.

mymap = pattern {
'_, []' : -> []
'f, [x, xs...]' : (f, x, xs) ->
[f x].concat mymap(f, xs)
}

It shares a lot of the same splat/rest/destructuring syntax.
I have a Galaxy Nexus. The keyboard is precisely why bigger is not better for me. Typing anything one-handed or hitting something on the upper or lower right of the screen is difficult for me; I end up letting the device rest in my hand somewhat precariously, which is extra fun when standing on a shaky bus in stop-and-start traffic.

I'm not the biggest person but my hands aren't tiny. I've been able to use other (e.g.) Nexus phones without any trouble. So from my perspective the bar ought to be higher than "we're making it bigger because we like more pixels" or whatever.
My opinion on the matter is that ultimately this is a maneuver to devalue the dollar. Historically, there are two ways out of massive sovereign debt: 1) default, and 2) print as much currency as you can so that you can easily pay your debts with worthless paper (or coin as it has been historically).

This is a method under the guise of helping the housing market to inject billions (if not trillions) of extra liquidity. Eventually, that leads to higher inflation, which devalues the currency.
On the other hand, the iPhone 5 looks nothing at all like a jelly bean.
Consumers want chargebacks. They let you get your money back when you get scammed or your payment information is stolen. Does that never happen in Europe? Nobody ever takes your money then fails to deliver the product/service? You never have your information stolen and used to pay for something you didn't authorize?
maybe you should write an article about your Xless environment so the rest of us can see how easy it is
May I enquire, have you used one? Your comments, and those within the article, suggest that you haven't and the writer of the article hasn't.

I run the Sass binary, it watches my files, when I save something it runs them through the preprocessor, sees if there are changes and then outputs CSS to a destination I specified (the public folder of the application, obviously). This takes less than a second, so by the time I've switched to the browser and pressed refresh and it's there, styling a web page.

I write in SCSS, which is a superset of CSS, so I can actually write the Sass file in CSS, have it preprocessed and minified automatically.

In other words, I put in one command to start the SASS binary running, and that's all the extra work right there. So you see, when people talk about extra work, compilation time, waiting around for things etc, they sound like they don't know what they're talking about.

Then if you take into account the time saved from all the functions you now have access to, the stuff that will work the same across several browsers, the grids, the sprite stuff, the typography helpers... (the list goes on and on) it can only save you time.

I hire designers for jobs and after the mess the last one made through only knowing CSS I've decided I won't hire one who doesn't know SASS. It wastes my time and everyone else's on projects now.
I haven't counted how many times I've read "magnitude" in this discussion … Does anyone actually have some numbers to back up the claims?
"One could sort of satisfy naturalethic's wish by choosing a numeral system with pi as basis. Then pi would have digit representation '1' in this system."

I'm pretty sure pi comes out to 10 base pi, not 1 base pi.
The main point is that for CPU bound tasks, other than those that use Numpy, the performance is still a dog with Python.

I threw in the comment about nonblocking I/O niceties as icing on the cake, but since we're on the topic it's worth mentioning that a language with these features built in is superior to one where it is either a tricky library or a monkey patch, referring to Twisted, Tornado, Gevent and Eventlet.
I'd suspect they have several tools like this for code portability. It's relatively trivial to make a simple translator that compiles to Javascript; take CoffeeScript for example. I'd be surprised if there weren't all sorts of tools like these floating around Redmond. The notion of a "runtime" sitting on top of Javascript? That doesn't even make sense. It would also be a waste of Anders's strengths. His strength is in taking something popular and making it modern and usable (e.g. Java -> C#). Coming from him, I'd expect more along the lines of a framework or language extension or ECMA contribution than a runtime or compiler.
Hah, for finance geeks, this was a particularly clever rebuttal :)
From a physics perspective isn't a flying battery a good way to dissipate energy?
At one point, I was sent targetted tweets about attending a conference in the USA - I live in the UK.

So? I live in Sweden, yet I've attended conferences all over Europe and in Canada. A couple of years ago my girlfriend was in South Africa for a conference. We have these things called airplanes which makes that sort of this quite convenient. If there's an interesting conference in the US then why wouldn't I want to hear about it?
There's a Gareth Bacon...

:(
Been looking for this for a long time. Thanks.
They have to be given the means and direction as well. That's the main missing ingredient: a lot of people have time and expectations, but they don't know where to start. A lot of the people I know in this situation simply spin their wheel in unemployment-related anxiety because they can't think of any concrete first steps that will lead to making a better world.
So you want to give clients direct access to your database?
How do you do when compared to other small population nations like Switzerland or Israel, or others?
As the largest market cap public company on the planet, Apple was doing just fine for its shareholders. When have you ever heard the leading company in a market say they're going "thermonuclear" against their main competitor?
I was in the previous batch @ 500startups and I don't think any of the ~28 companies had a solo founder. Doesn't really answer your question but just an FYI.
The iPhone 5 is ok.Tomorrow i order one and have fun the rest of the Year :)
There's got to be a bug because this was on the front page 6 days ago:
http://news.ycombinator.com/item?id=4486108

Well the link in the previous post had a trailing slash.
(I'm a full time Ruby/Rails programmer, and I have been for five years.)

There's a major flaw in the R/R culture: they have no interest in maintaining stable APIs. If you want to upgrade your Rails app to the latest version of some library, you might as well do a rewrite of your entire app. So many of the APIs change from release to release that most of your gems will stop working unless you upgrade. When you upgrade the gems, your code will stop working, because most of the gems will have changed their public API. If you've got a non-trivial application, you will essentially be unable to upgrade. You will stop getting security updates. What minor upgrades you can manage to do will leave things partially broken, and you'll just get used to it being broken. (for example, one project I've worked on is stuck with a brain-damaged RSpec library that reports error messages without interpolating the strings, you always get "Expected CONDITION, got FAILURE, see CODE" in the logs)

My recommendation: only use Rails for short term projects that will be completely shut down after a few months.

I know that it's common wisdom that "no ruby engineer will ever want to switch to java", but that's because you've never been saddled with a 2-year-old rails project (or a 5-year-old plain-ruby project, which will have the same symptoms, just more slowly). Then your team will be begging for something that runs its test suite quickly, that has enough static analysis to know if you're using an outdated API, that has a decent metrics library, where you can query the state of the VM, that doesn't constantly leak memory, that plays nicely with databases that have real constraints, that has fewer race conditions in common libraries, etc etc etc.
The difference is small because map is trivial, but the implications of using higher order functions isn't. Even something like trees sees a divergence between the styles (not necessarily in the order of assembly language vs. high-level, but certainly more than you're making out).

Higher order functions are really useful for splitting apart navigation of a data structure and the processing of the data contained within it.

Given that you can use purely higher order functions for control flow, I wouldn't say one is more essential than the other.
and by the way, I can't recommend Node either. As far as I can tell, they're eagerly making these same mistakes.
these are the ideas behind scroll kit and i'm glad you agree with them. but we'd be some pretty shitty hackers if we just talked about them and weren't trying to actually DO something to change things.
And you keep wanting people to mean only "I" when they mean "some".
I think in 5 years we'll look back and see this as web design's "VonDutch hat" moment.
In case it wasn't clear, that aphorism is supposed to be telling you to get into the habit of reading the source code of the libraries you use. It is often the fastest way to solve your problems, and you'll learn a lot about the lib and about the language in the process.

Without the ability to do this one can only be a plumber fitting other peoples' appliances.
tldr:

> Disclaimer: we love Python, and it’s Dropbox’s primary language, so we’re probably biased.
Though Amazon never extracts any marketing mileage out of the openness of android. Google just sounds disingenuous here
If it did whole-program optimization, it theoretically could. But it is probably too costly. You don't have that much time and resources to optimize JIT, as you have doing static compilation. That's why, contrary to common beliefs on static vs dynamic compilation, still static compilers win in most cases, compared to even very mature things like JVM or .NET CLR, even though they have much easier task than JS.
I don't think C will always be faster. A JIT-compiled language can theoretically be optimized better than a precompiled binary, because the JIT engine can recompile hot code based on observed behavior on the actual system with the actual data.
Kind of reminds me of http://www.youtube.com/disco
It's a very nice idea, I would love to see more creativity in the web, but I don't think I agree with the implementation or what I see as the user base. Every blog page is not just a template, it's someone's vision of the world. It's an identity and a brand that the blogger tries to create and extend to its users. Using this new style the blogger would completely lose any form of identity and become more of a sparkling instagram knockoff than a medium to share rich content to its user base.
I'm guessing you're looking for something punchier than the Wikipedia page.

But may I recommend the EconTalk podcast.
http://www.econtalk.org/archives.html#category

In particular, Barofsky on Bailouts (http://www.econtalk.org/archives/2012/09/barofsky_on_bai.htm...), Johnson on the Financial Crisis (http://www.econtalk.org/archives/2011/11/simon_johnson_o.htm...), and Wapshot on Keynes and Hayek (http://www.econtalk.org/archives/2011/10/wapshott_on_key.htm...).

Hell, the entire EconTalk podcast series is full of so much braininess.

This is a pretty complex subject and there is more to it than just printing money and buying up T-Bills.
Ferrofluid oil spill cleanup
I don't happen to believe that what is legal is also moral.
Well, the iPod hasn't exactly been completely reinvented over the past decade. The first version is usually the breakthrough, and then it gets refined.

Same with the iPad.

I'm not sure what people were expecting with the iPhone after all this time..
this is great news! for people who prefer python-like syntax, coffeescript is a no-brainer. sites like js2coffee.com make it really easy to make the transition.
Lessons learned from michael clarke duncan
If he wanted to do that he would have done it in June or July, not now.
Dude, charge for this. Seriously. Add some value by providing personalized practice tips.

If this had a mobile app I could carry around a golf course and map my every shot, I would pay plenty of cash for that. Automated stats that would help me focus on the shortcomings of my games and let me understand the trends of my shots.

In fact, I may have given myself an idea...
"I imagine it's a lot more difficult to recruit ultra-talented hackers, especially since they are totally unqualified to recognize them."

Very real. Best hackers spend their time hacking, not trying to get grades or climbing the hierarchical ladder.

Just think of Steve Wozniak, he was so afraid of not being able to engineer anymore if Apple gave him executive power. He refused to climb the ladder so he could continue tinkering in the lab.

In those big orgs the people that want to get power use to be sociopaths and "power addicts"(people that choose power over everything else in life).
Multi-language IDE (Compiler)

//Doubt this is a million dollar idea, but i love to have one ^_^

The idea is simple, as you are coding, you can switch between languages as you please. All languages able to access variables and methods in any other language you have already used. All you have to do is identify what language the sections of code are.

EG:
<C#>

public list<int> DataSet = new list<int>();

public string GetSortedData(list<int> unsorted_data)

{

//sorts the data

//Converts data to string (as delphi dosent have list<int> class... i think.)

}

</C#>

<Delphi> //sory its the only other language i know atm

ShowMessage('Sorted DataSet: ' + <C#>GetSortedData(DataSet)</C#>);

</Delphi>

It might be tricky to do, but damn would i want an IDE that can do that!
Pragmatic.js code style guidelines by Thomas Fuchs
I've evaluated Lua for a number of use cases and even use it on my Ti NSpire calculator occasionally, but it has some horrible problems, particularly related to metatables and the concept of 1-based indexes. It also doesn't give us any advantages over other languages. LuaJIT is impressive I will say though.

However, Go's apparent concurrency focus is a bad assumption.

The problems that Go solves are simply: simplicity, synchronisation, thread scalability, time to market, modularity, testability, consistency, security and memory management.

All of those, you really can't do in C quickly and safely.

Go is a fixed C, with a fixed standard library that suits NOW, not 20-30 years ago. That's all it is and that should be applauded and praised. It also fixes the inevitable mountain of stuff you have to do to get something significant done in C and ignores the utter retarded complexity of C++ and Java.

Ultimately:

A single person can build something significant in Go in a week.

A single person cannot build something signficant in C in a week.

cgo is very easy. I've plugged SDL into it in a few minutes.
The Fed is trying to stimulate the economy. The ideas is people and companies should spend money, invest, give loans, etc. The Fed can't force you to spend, but they can raise the inflation rate. Ideally this means you decide to shift from saving to spending and investing and the economy recovers.

The downside is that this hurts savers, particularly small time savers who aren't investor class people. And is still not guaranteed to work. So you get the worst of both worlds, a higher inflation rate and still not enough jobs.
I think Glass is an intermediate step. The biggest issue that exists right now is the fact that we would love to have huge screen but don't want to lug them around; want full keyboards but they don't generally fit in our pockets...

My thought on this is that we'll eventually turn to the next best (but scary) way to interact with computers: implants. I wrote about it in a blog I have just for "brain dumping" of stories I want to eventually write, but perhaps it's relevant here: http://writersdrano.wordpress.com/2012/01/15/the-first-step-...
Injustice Continues as Megaupload User Data Negotiations Go Bust
Writing functional JavaScript (video from javazone 2012)
No I use the term "current location" as Facebook labels it. You are correct in saying that other platforms call this differently but they are all asking the same general question. "Where do you normally live now". I think you are incorrect in the sense that this shouldn't be a supported part of the API. If your platform is based on Geo (Like Foursquare) then you can of course utilize additional checkins to help solidify the concept of a users "current location" but I still think its really important to index properly. These design decisions that you talk about were implemented before they were supporting geo tags in the API. I think its an easy design change to support this methodology. The platform, the users, and the developers would all gain.
I just check if there's a @
Sorry about some grammar mistakes :/
>why should he just sit there quietly while other people violate his license and profit off his work?

Gee, I don't know. Maybe for the good of the hundreds of thousands of users of iOS/VLC? Maybe because the other contributors had agreed to this and didn't care for the technical violation, especially since both the code was available and the app was free? Maybe because also working for Nokia seems like a huge conflict of interest?
Big, big fan of CoffeeScript and glad to see Dropbox hopping aboard.

That being said, some of their examples are lackluster.

@originalStyle = {}
for k in ['top', 'left', 'width', 'height']
@originalStyle[k] = @element.style[k]

Should really be something like:

@originalStyle = ['top', 'left', 'width', 'height'].reduce (hash, position) ->
hash[position] = @element.style[position]
hash
, {}

... though that shows off some CoffeeScript warts.

Also,

Sharing =
init: (sf_info) ->
for list in [sf_info.current, sf_info.past]
for info in list
@_decode_sort_key info

Why aren't they using CoffeeScript classes?

class Sharing
constructor: (sfInfo) ->
...
This might just bring me back to Video games...
For the curious, confused, or uninitiated, this whole phenomenon is almost certainly based on the coincidence that "separation" and "Kevin Bacon" sound similar, combined with the well-known phrase "six degrees of separation" (https://en.wikipedia.org/wiki/Six_degrees_of_separation). Thus, "six degrees of Kevin Bacon".
Funny part is that this submission made it to the front page again... I guess this is a really popular topic?
Is going solo a good idea?
Following this advice creates a lot of "I never got my activation email" and "Why won't it let me log in" support emails that are a big pain to deal with. It's pretty important to nip that in the bud, hence immediate email address validation.
You can accomplish this, after a sort, using databases like CouchDB and Mongodb.

While its entirely possible to write a pure client/database web application, you are going to run into security issues. You are inherently opening up your database to the outside world, and javascript clients are inherently un-trustworthy from a security angle.

If I were designing such a platform, I would segment actions into "safe" and "non-safe" areas. Safe areas would be client/database actions that are ok for the javascript client to access externally. Non-safe areas, such as account creation and editing, financial interactions, etc, would need a middle-tier server-side application layer. The middle-tier would need to act as a proxy that handles validation of database requests, etc.
Things I Hate About Interviewing With You
If you've been developing login systems for any length of time, this should be fairly obvious.

Be careful about taking that "it’ll get bounced" attitude too far though. The last time I did so I forgot to trim the email addresses and didn't lowercase them. Failing to trim will probably result in the email going through, but then might cause problems later on when you try to match their login ID to what they enter the next time.

A similar issue arises for case. Email addresses are supposed to be case sensitive but providers don't seem to take advantage of it in practice. Again, the case a user types varies from time to time (I assumed nobody used upper case... it seems silly). And if you switch to case insensitive login IDs down the line, you may have to deal with duplicate accounts (same email but different case).