skysight-inc/HackerNews huggingface dataset:
Not directly related to the topic, but for those who might interested, here is another piece of critique on Gates Foundation in education:

How the Gates Foundation Spins its Research http://jaypgreene.com/2012/01/07/how-the-gates-foundation-sp...

Quote: "With the latest round of reports, the Gates folks are back to their old game of spinning their results to push policy recommendations that are actually unsupported by the data."
It could have given new life to thousands of guidance counselors and administrators the world over threatening: "Don't do _x_, it will go on your permanent record!"
There is a degree to which you can make anything do anything. Using JavaScript as bytecode is actually really easy if you don't care about performance whatsoever. And if you get together a group of smart people who try very hard for a long time, I'm sure you could even get it to have reasonable performance. Especially if the people writing the interpreter are talking to the people writing the compiler.

But why would you actually do that as a long-term solution? JavaScript isn't an ISA. It's not hard-coded into anything. You don't have to throw away all the existing JavaScript code to start supporting something else in addition to it. All you would have to do is write code to support whatever bytecode you actually want to use and contribute it to the major browsers.
HN discourages substanceless comments, but this one is just fine.
I'm using both mechanical and MacBook built-in, and I'm not sure if I like mechanical better.

It's kinda cool to type on it, but the keys are just so huge, it feels like I'm using a typewriter. Using the Apple keyboard is the opposite, it's like I'm just slightly brushing the surface.
Bootstrap, Foundation, and The Future of Web Frameworks
The author is operating under the strange notion that doing a transaction outside the context of full-time work, or operating a business, is illegal.

Maybe businesses like Lyft, Uber and AirBnB facilitate people working in legal grey areas, but they also facilitate direct individual-customer relationships. These open up markets, and are therefore bad for incumbents (e.g. people already in the taxi industry) but good for people who for whatever weren't able to work in that industry before.

And what's with referring to people as "kids"? Is this how you assert your status as alpha male?
>>> If you are a productive individual and you work in a place where lazy, late to arrive, early to leave, incompetent individuals are not only tolerated but promoted, why would you stay? If you do stay, why would you work hard? That's the US Federal gov't GS workforce, particularly the DoD and DHS, in a nutshell.

Annnnnnnnnnnnnnd pretty much every large corporation I've ever worked for.

Most of the smartest people I know usually start their own companies, or work at smaller firms where they get lucrative work to maintain a nice upper six figure salary; doing what they really love to do without all the corporate entanglements.

For example, I had a friend who worked at Thomson Reuters. After three years, he got fed up with the same scenario you pointed out. He started his own translation company (he's from Bulgaria and speaks 6 languages fluently) and now his biggest client? Oh yeah, its Thomson Reuters. He makes triple now running his own show as opposed to when he was working in the meat grinder.
Chef in Action
Writing in a Nonstop World
I agree that he's probably overestimating Atari's impact on an entire generation's psyche, but I like that a) he's indirectly reminding artists to stay conscious of the emotions their artwork provokes in people and b) that's he humble and introspective enough to accept and admit the possible negative by-products of his work.
> JavaScript and HTML are a lot more bloat than machine language code written to the wire.

http://mozakai.blogspot.com/2011/11/code-size-when-compiling... suggests otherwise in a head-to-head comparison: C code compiled to both a platform-native binary blob and JavaScript, then both gzipped (standard practice for any large JS file on the web).

And if you're talking platform-dependent machine code, that's likely _worse_ on the wire in practice, because unlike a platform-independent representation you can't do edge caching or other sorts of intermediate caches. But maybe you meant a virtual machine (i.e. what people ask for when they want a common bytecode)?
Ex-amazonian here, It really depends on the team. There's 2 types of crappy places to be at Amazon: the really important legacy system, or the we need to catch up with the competition product.

In the first case, there's no opportunity for really improving things, it's usually a small team which can really hamper your advancement, and it breaks constantly. You'll work a 40 hour week, but will get paged all the time and have lots of little emergencies.

The second is sexier, and a good opportunity to move up the ladder, but you'll be working 60-80 hour weeks, loads of crunch time, and suffer due to constantly shifting management as the team explodes in growth.

All that being said, there are a lot of good opportunities, especially for younger engineers. Provided you have a decent performance review, mobility is pretty easy, so if you're stuck on a shitty team, that can change after a year+. You'll want to find a team with a manager who's been around amazon for a little while. You're supposed to tell your current manager first that you're looking around at other opportunities, but in practice this is rarely done before all but securing a new position. I recommend the Rowhouse coffee shop for talking with potential future managers. It's usually pretty clear after 2 and has lots of little rooms and well shaded windows.

If you end up stuck on a shit team, without being able to move around, start looking around Seattle. Twitter, Google, Hulu and Facebook are all hiring here, and they all usually pay better, in addition to having better perks. It's quite something to interview at Google's offices and see the difference in culture. If you've just gotten a promotion, or shipped a major product, that's an ideal time to start talking with other potential employers.
>it was too far ahead of its time

I would never get this phrase, does it mean, it is of no use at the moment? If yes, why not say it so.
I'd say Go-QML as well, not just because it already works quite well but because it's actively developed and maintained. I've been following the project on GitHub and Gustavo Niemeyer has done an impressive work so far, and is quick to deal with pull requests and to answer issues.
If you sent a Wuphf (pronounced "woof") to someone, the message went to the recipients' home phone, cell phone, email, fax, pager, Facebook, twitter, and AIM.

The original WUPHF.com beta page is archived at: https://web.archive.org/web/20101122015439/http://www.wuphf....

And WUPH.com's business plan is archived at: https://web.archive.org/web/20101122022512/http://www.wuphf....

On the one hand, WUPH.com was a satire of Silicon Valley in a comedy sketch on an episode of "The Office" called "The Whistleblower" that aired in May 2010. So HootSuite, IFTTT, &c, &c, are all great examples of life imitating art (anti-mimesis).

On the other hand, the WUPH.com beta site mentioned above actually worked, at least for a while, until NBC shut it down. There are a couple of write-ups about this on Forbes:

http://www.forbes.com/sites/oliverchiang/2010/11/19/the-offi...

http://www.forbes.com/sites/oliverchiang/2010/11/19/the-next...
> Furthermore, changing an interface isn't backward compatible so the correct way is to create a new interface every time you make a change.

That's a feature, not a bug. Say we're using implicit interfaces and have library A that provides an interface Foo and an application B that uses A and passes a Foo to some callback system. Now A gets updated and adds a method to Foo, but existing B binaries still call A with an implementation of the old version of Foo, and things fall apart.

Java's model (and COM's and MS-RPC's) model here is better because it enforces good interface hygiene: incompatible types get incompatible names. Then you can choose whether to support the old name as well as the new name, but you're at least consciously making that choice. D's model worries me because it feels like it's easier to accidentally break things.
Piketty for Dummies
Personally, I think it would be better if interfaces were explicit, but the list of interfaces on a type was open, allowing you to add interfaces over any type anywhere, and not just in the place where the type is defined.

type foo = ...

and

impl hashable(foo) = ...
impl hashable(int) = ... // yep, adding to a builtin type

This is the way that Myrddin currently handles it.
clojurescript depends on the JVM.this is a no go for me.Once a cjs compiler is implemented in javascript and can run on nodejs,then maybe i will consider it.
Because it requires some really difficult conversion work under the surface. For example, JS has no concept of integers. To shoe-horn other languages in involves a lot of extra work, which by nature is going to be less efficient.
Worse, the javascript engine's JIT can't take advantage of some of the semantics of the language being converted, e.g. if the JIT knew for sure that the number was an int, it could take advantage of that in various ways, or make a smarter decision based on the known performance characteristics of the hardware it's running on.
I have very little insight into the matter. Just noting some limitations and biases in the data presented. Former employees are probably biased sources of data, too.

Anyway, I've heard it's a tough place to work, but some people thrive on it... nothing beyond what's in the Businessweek article.
South Korean PM Chung Hong-won offers resignation over ferry
Right now I will look up how long I've spent at a client location to prepare the timesheet for billing. If the app, like Moves, knew where 'work' is, it could do this automagically.

Could be out of scope depending on perspective, but for me it would be killing two birds with one stone.
https://www.dropbox.com/sh/oxn36sidtubcvhi/w5km41TbaY/beta%2...

AndroidFocus, an Android app that syncs with OmniFocus. Currently I have a read only beta out where you can browse your projects, contexts, actions and forecast. Creating and completing actions are next on the list and those features should be ready by next week.

The beta can be joined through this G+ community: https://plus.google.com/communities/103938802070518069711
Having moved to Tokyo last year, I'm really hopeful for more accurate altitude data. Much of Tokyo is under and above ground level, and I wish the altitude data were accurate enough to determine which floor I'm on.

Perhaps Bluetooth LE and beacons will eventually allow more accurate elevation info.
All other languages listed on that page are entirely different languages as well.
>>> Except they won't. The talent pool isn't infinite, passing up talent for silly reasons is a major opportunity cost.

This is a great point. Spoke with a recruiter just last week who talked about the market here in the midwest. He said there's so many openings, he can't find the talent, and companies are advertising further and further out from the city.

He said the last person one of his clients hired lived two hours away and they had to pay him a monthly stipend to cover his daily commute. Sure, they let him telecommute at times, but for the most part they expect him in the office and have to pay for it.
Interesting. I looked at their site and I couldn't find mention of exactly what sort of personal information is stored, but I do see the term "student data" pop up a few times. I wonder; why aren't these guys having the same problem?
There's nothing chauvinistic about it. If you want to hear people honestly and accurately describe "static" type system's flaws -- talk to type system theorists.

Type systems can be provably flawed.

What you can prove about a uni-typed late-bound ("dynamic") languages is quite simply that they're unilaterally flawed.
Five Hard Things That Great VC's Do
That's not how you measure bloat. There's a huge runtime associated with that JS code, and you ignored performance.
The title was linkbaity, so (in accordance with the HN guidelines) we replaced it with a sentence from the article that better represents its claim.
What's with all the hit pieces on the sharing economy as of late?

There's another piece on the front page here too - https://news.ycombinator.com/item?id=7651968

I'm struggling to figure out what the big problem is with more people becoming entrepreneurs?
Are you implying that Martha found a self-evident solution? :)
Wow, I didn't know GPS technology was even capable of that accuracy. It would be interesting to see it used in augmented reality as well as the examples from the article. You could actually have shared virtual objects positioned out in the world.
Typescript is hard.

It's module system is a mistake(it should be module system agnostic,not AMD or CommonJS),and very confusing.

The biggest problem is javascript is so dynamic you cant create type definitions for every library outthere and expect the typesystem to work.

Typescript is good if you are porting something from AS3/C#/Java to javascript,or if You want to model a complex domain,without touching the DOM api(or node api).

It sucks as soon as you try to use jQuery with it.You end up with any everywhere which defeats the purpose of that language.

In my opinion,if you need to pick a js alternative,choose Traceur.
I suppose it might be "bad form", but couldn't you, if you had:

public interface FooBar
{
int foo();
int bar();
}
public Afob implements FooBar {...}

refactor FooBar to simply:

public interface Foo { int foo() }
public interface Bar { int bar() }
public interface FooBar extends Foo, Bar {}

And keep FooBar the way it was, but now cast it to a Foo (or Bar) when you don't want a FooBar?
If you are a large company, you can move faster if devs aren't all working on the same repository. If all your code is in one repo and one team makes a breaking change to their part of it, everyone's code fails to build. If the source code is broken up into separate packages, each team can just use versioned releases of the packages they depend on and not have to worry about fixing compatibility issues.
The general answer is that it puts swapability of implementation in the hands of the caller, not the callee.

Let's say I have a function A that depends on concrete type B, and that I only use a subset of B's functionality. Now say I decide, hey, I'd actually really like to be able to swap a different implementation of B at runtime.

With traditional interfaces, I would have to either:

a) define a subset of B's functionality as interface I and change B to implement I, or

b) define a subset of B's functionality as interface I and define a wrapper that implements I in terms of B.

If I choose (a) and many other callers end up doing the same thing to B, then B implements a mess of little micro-interfaces that it really should have no reason to care about. If I choose (b) then the implementation of A is way more complex than it seems like it ought to be.

===

One place this comes up all the time is testing: Object A relies on a subset of the interface exposed by service S, and service S is hard to create in test environment. With Go interfaces, A just defines an interface for the subset of S that it needs, and the test code for A implements that interface. S doesn't need to know anything about it.
Go Home – Engineering Work/Life Balance
Aside from the "sharing economy"'s brightest lights being designed to enrich everybody but the people doing the work, while offloading all of the risk onto the people doing the work?

Nothing, I guess.
Google is Planning to Dismantle its Social Network Google+
That's sort of a problem. It is unfortunately often implied that leadership beats all other traits. Here we have a - specific - example when it doesn't. This example won't change the culture which values leadership above everything else (if, e.g., we have such a culture). And that's, I think, an important idea out of the story.

Leadership could be valued so high that someone would automatically equate success with leadership. I.e., that who solves the problem is the leader by definition. Which is not - but might be overlooked too often.
I think it might be a city thing as well. I grew up/currently live in Toronto and talking to strangers outside of specific areas/events is often met with distrust or a feeling that you/they are invading personal space.
IMO the biggest problem, even worse than type coercions, is the error silencing regarding wrong argument counts.

This can easily hide so many bugs, it's amazing it is acceptable to anyone.
It's not sharing: it's renting.
Is the IPCC Government Approval Process Broken?
That's almost worse. So instead of nameless Joe E. Dev getting a chewout from Bezos, his boss's boss does, who in turn chews out his boss, who in turn is furious at Joe E. Dev for causing the ruckus. Ouch.

Edit: Wait, I just re-read that. You mean each time Bezos receives a credible complaint from the public, he personally forwards it to all his VPs? Isn't that a massive time hole for his VPs? I'm sure it focuses people on random complaints, but then they spend much less time focusing on making their service(s) better for everyone.
> The people who hate javascript the most are the ones who wish it was something else.

Ask yourself,how can a single language can fit every use cases,for every developpers? We cant agree on what we should use on the server,but we are basically forced to use 1 language in the browser,of course some people are going to hate it.

I shouldnt have to adapt javascript,javascript should adapt my coding style.But aint gona happen.

Weak typing and Type coercion are imho the biggest flaw of javascript,I can live with the rest,but not that.

Proxies will help a bit though.Devs will definetly abuse them.
The problem is people in precarious jobs becoming "entrepreneurs". Risk - the very thing that was used to justify the profits of the Man - is shifted to the employees.
Start with the eBook and see how that goes: they're really cheap to produce. If it's going decently, reinvest some of the profits into making a print on demand book. Print and eBooks are very different, so what you invest in one won't translate to the other.
Duck typing and structural typing are not the same thing. In structural typing you are still making assertions about the type, in duck typing you are deliberately avoiding them. The opposite of structural typing is nominal typing, where in types are named and explicitly associated with the objects they represent.

Particularly, this is extremely wrong when talking about structural typing:

> - More importantly, it severely limits the tooling available since the compiler has a lot less knowledge about the types you are dealing with. Automatic refactorings are all but impossible with structural typing.

The compiler has as much information in structural typing as it does in nominal typing. The type of an object is determined at compile time either way, it's just that in structural typing Account implements Serializable and Entity because a subset of its methods match the definitions of Serializable and Entity, not because you said it does.
Ok come on. You can at least comprehend the thesis of the piece. "Entrepreneur" drivers have poor job security. Is this a fundamentally better model for the middle class than being an Avon salesperson? That is a totally legit issues to discuss.

This may be a perfectly good short-term way to earn some cash, but the article is about the bigger picture for our economy. Don't pretend to not understand when you're really just tuning it out.
FPV with Oculus Rift and a Quadcopter
I'm actually planning to add "favorite playlists" so you can mix/match certain genres.

There's no back-end algorithm to determine what tracks you'll like... but developing a "likes"/"favourtites" system is easily doable. Will DEFINITELY consider it.
Could you shoot me a mail? josh@josh.mn :)
The speaker actually begins talking about racket and how they use it at about 6 minutes into the video. Here's a link:
https://www.youtube.com/watch?v=oSmqbnhHp1c&t=6m0s

Interesting to hear how they replaced GOAL in their toolchain. The people I've met who used GOAL in the past talked at length about how much they miss it.
HA. So funny because I totally commented on the Facebook post you guys posted. ANDDDDDD I commented on the HN post :) something about volume control.
I hate to be that guy, but nothing you have under IDM is actually IDM. It's decent glitchhop/dubstep, but I don't know how/why you created that sub-category to shoehorn IDM in there somewhere.
For trusting blogspam, maybe. For putting stock in the comments elsewhere under this post, not so much.
Would you articulate why it's a "no go" for you?

Leiningen[1] takes away 99.9% of the pain of having to work directly with javac, maven, classpaths, etc. And lein-cljsbuild[2] offers a configuration-driven approach to compiling and testing.

It's perfectly possible to create setups where node (plus grunt, gulp, shell scripts, make, etc.) "drives" leiningen, and vice versa. About a year ago I contributed such a setup[3] to David Nolen's mori library.

[1] http://leiningen.org/

[2] https://github.com/emezeske/lein-cljsbuild

[3] https://github.com/swannodette/mori/blob/master/package.json...
As someone who has seen more than a few self-published books, I hope you won't take offense if I give you a bit of advice: get a better cover done. I can't quite point out what's wrong with the one you have (I'm not much of a designer myself), but the elements don't go together very well, and the title looks flat. The chicken is ok, it just needs to be worked in there differently, I think.
Keep in mind that this measures the median tenure of current employees, which significantly biases against companies like Google and Amazon that have done a lot of hiring in the last few years.

A better measure would be the median tenure of employees that left.
Diving deep into Python – the not-so-obvious language parts
I won't say it's good or it's bad, but I will say that it bites me on a pretty regular basis. You start with some code that says this.something() and you decide to move it into a callback and miss converting the 'this' references to 'self' because in the previous incarnation, it didn't matter, but now you're calling out to code that helpfully fixes up the 'this' reference when calling your callback. I literally fixed one of these today.
I'm not saying they should pay no tax but my guidelines still apply. Keep taxes reasonable. Don't be dicks about it. France is being a dick. They made their own tax laws. If what companies do is legal under their tax law you can't whine about it and try to extort/sue them for more. Instead, change the law and deal with the fallout (more tax revenue or more unemployed French people). If there's no incentive for a company to have employees in a country there will be NO taxes paid and they can all eat cake.
What's the advantage over /r/woodworking?
As someone who grep up during the Cartoon Cartoon era, and am a big fan of many of those shows (Power Puff Girls and Dexter's Lab were quite good), I'd say yes.

At the very top level, Adventure Time actually has serial elements, as opposed to Cartoon Cartoons' strictly episodic nature. Character's actions in previous episodes have real and lasting consequences.