skysight-inc/HackerNews huggingface dataset:
Ha ha, exactly. Just like there are a few baseball umpires who are so bad you learn their names (Angel Hernandez, Phil Cuzzi, Joe West), Intellectual Ventures is one of the "companies" that most developers know of for all the wrong reasons. I remember when they sued every maker of "todo list" software.
The argument is that if you get severely injured the tax payers get stuck with the bill (US may be different) so other people are affected; I'm in favour of compulsory motorcycle helmets and seat belts, if you want to opt out fine, but pay a higher insurance premium.
The United States had the opposite plan during the Clinton administration.
I love this, simply genius. I think it'll make sense to focus on a few select tasks and scale those with great partners, instead of spreading too wide at first.

The pricing doesn't make all that much sense to me. Why not a simple per-request pricing model with a monthly minimum (after a # of free trials)? Or the ability to simply purchase larger blocks for discount pricing?
I commute by cycle frequently in Wellington, have done so for more than ten years. Before that I spent my entire childhood cycling the width and breadth of Auckland City, and while I haven't had a big accident I can think of two off the top of my head which happened to people that I know and would undoubtedly have been a lot worse if they were not wearing a helmet.

NZ's cycle culture has nothing to do with helmets, it has more to do with prejudices and a lack of city planning to accommodate cycling.
Link for the lazy: https://en.wikipedia.org/wiki/Banqiao_Dam

> According to the Hydrology Department of Henan Province, in the province, approximately 26,000 people died[14] from flooding and another 145,000 died during subsequent epidemics and famine.

Video with computer simulation: https://www.youtube.com/watch?v=ctPLXim9WG8
>I still don't quite understand how they do it.

Why maintain and improve your existing services when you can get credit for launching a new shiny thing? Steve Yegge called out this tendency in his (in)famous platforms rant [1]:

They prioritize launching early over everything else, including retention
and engineering discipline and a bunch of other stuff that turns out to
matter in the long run. So even though it's given them some competitive
advantages in the marketplace, it's created enough other problems to make it
something less than a slam-dunk.

Amazon's "speed and agility" comes at the cost of not updating anything, ever. If you want new functionality, you'll have to integrate a new service.

[1]: https://plus.google.com/+RipRowan/posts/eVeouesvaVX
Of course, the correlations between these "realizations" and any actual reality may be zero. That is, "realization" implies that there is some truth that you are realizing is true. But these things may well be not actually true, just impressions from using chemicals to temporarily alter your brains. They may not even be true on the next trip!

Acid trips as a way of actually discovering truth (rather than perception) seems to me to be hopelessly naive.
I use https://babeljs.io/ to compile es6 code for production. It could support this kind of transformation though I'm not sure if it does by default.
In California, electric bicycles that meet certain restrictions are already allowed in all the places a normal bicycle is. If there's a tension between ordinary bicyclists and small powered vehicles in this class it should already exist. Personally, I've found pedestrians to be a much bigger annoyance than faster bikes (whether powered or otherwise) on dedicated bike/pedestrian paths.
Depends what you compare it against, I guess. Seemed like a bargain to me.
Why Dell’s EMC Bid Leaves VMware Looking Like Devalued Currency
> The point I am making here is that Engelbart and Kay were unrealistic in expecting that their technologies would give quick results in the way of Tools for Thought. They had no appreciation for the vast and rich culture that produced the tools for thought enabled by the traditional technologies of writing and printing. They did not realize that a similar culture needs to arise around a new technology with augmentation potential.

I am guilty of deifying Englebart and Kay, and castigating "our society" for failing them. After my honeymoon period with the "tool of thought" people, I've calmed down.

Here's my radical belief: portability is for people who can't write their own programs. (copped from a Torvalds witticism)

Consider writing and literacy: If you really grow up in a literate culture, you can start with a blank page and end with a bespoke document that suits your needs. If you don't grow up in that, you have to modify others' documents. This limits you. Hallmark cards are for people who can't write poetically (no judgment intended).

So too for programming. Today we rely on hundreds of millions of lines of code of others we can't even realistically modify. But I think the future resembles Forth: in less than a hundred lines of code, you write something that suits your needs[0]. You can't do this yet because computers suck.

I'm talking loosely and at a high-level.

[0] I think Forth is a powerful vision for the future: no operating system, no types, no compatibility, no syntax. An executable english language.
They would be fined for not wearing a seatbelt though.
Low speed electric bicycles are federally limited to 750W and 20mph as well, which probably helped guide this regulatory process. I personally think a 20mph speed limit is very reasonable when regulating the use of motorized products on infrastructure shared directly with other uses (paths and bike lanes).
> That's their money that they are taxed on and they pay it.

The only reason Facebook doesn't have to pay taxes on that money is because they gave it to their employees (so it counts against profit). The money comes from FB profits, briefly goes to the employees, then to the government. Hence, the government is getting a cut of the money FB is making. What's the problem?
All this tells us is that large scale power generation, and in particular nuclear generation, is a highly capital-intensive business that probably makes it unsuitable for a startup to tackle.
As long as nuclear is willing to pay for their own insurance (and not backstopped by the federal government: https://en.wikipedia.org/wiki/Price%E2%80%93Anderson_Nuclear...) and pay for their waste disposal, may the best tech win.
Terrestrial Energy is developing a molten salt reactor in Canada.

Meanwhile Terrapower is building their prototype in China, which is developing half a dozen advanced reactor types and currently building a couple dozen conventional reactors.
Experiences with the Amoeba Distributed Operating System (1990) [pdf]
It was more of a rhetorical question, with the remaining literalness directed at the OP :) but yeah, those are fantastic examples! The Berlin Brandenburg [1] was what came to mind immediately, but you're absolutely right that history is like to be littered with other dead developments.

[1]: http://www.bloomberg.com/news/features/2015-07-23/how-berlin...
foo.delegate = self
Some of that is just the preference of the demographics likely to bike, but in urban cycling with cars particularly, speed equals safety. Hence why female riders bear the brunt of harassment such as close overtakes.

Much healthier to be able to be assertive and occasionally accelerate away.
pkfrank - thanks for the comment. we are still working through the pricing model. The current model is on a per-request basis but we are also exploring a monthly fee to keep the quality of the companies that request tasks high. What kind of tasks do you think we should focus on?
I suggest you also get the mentioned Lumix 20mm lens with it: it’s simply a beautiful lens, even compared to more expensive ones. Its only downside is a not exactly state of the art focus speed, but it’s manageable, especially if you plan to do this type of travel photography.
The WHO did a massive study[0] and actually found nuclear killed far fewer people per watt than all others, even solar:

Energy Source Death Rate (deaths per TWh)

Coal – world average 161
Coal – China 278
Coal – USA 15
Oil 36
Natural Gas 4
Biofuel/Biomass 12
Peat 12
Solar (rooftop) 0.44
Wind 0.15
Hydro 0.10
Hydro - world including Banqiao) 1.4
Nuclear 0.04

Note that rooftop construction is one of the most dangerous jobs in the US, with high mortality rates from falls.[1]

Coal mining is extremely hazardous, it would top this chart even just looking at production. Folding in air pollution deaths from burning coal and you add thousands of deaths per day.[2]

Each year coal and oil kill more people than the entire 60 year history of nuclear, including every nuclear disaster.

Even if we focus on worst case scenarios, nuclear is safer. The impact of Chernobyl is wildly overestimated by the public.[3]

For hydro, let's just note that a dam failure in Banqiao killed 171,000. The highest death estimates for Chernobyl (and this is including expected early deaths from radiation exposure that still haven't appeared a few decades after the incident) and you're looking at maybe 4,000.

You could add a Chernobyl every year, even take the most aggressive estimates for early deaths caused by that accident, then ignore all air pollution deaths, and coal and oil would still be more dangerous. They're just that insanely deadly an industry. Nuclear's worst case is safer than coal and oil's average.

On cost I think you're mistaken too, nuclear remaining an incredibly cheap source of power per watt, but power economics are complicated and that'd take another discussion. All I can say is that this was the standard wisdom of everyone I knew who worked in the energy industry, despite occasional scare stories in magazines about how the "true" cost of nuclear is disguised by subsidies - the math doesn't quite add up.[4]

[0] Energy deathprints: http://nextbigfuture.com/2008/03/deaths-per-twh-for-all-ener...

[1] http://www.bls.gov/iif/oshwc/cfar0020.pdf

[2] Studies on air pollution deaths (spoiler: among the leading contributing factors to mortality worldwide): http://www.thelancet.com/journals/lancet/article/PIIS0140-67... ; http://www.nature.com/nature/journal/v525/n7569/full/nature1...

[3] An overview of the actual mortality impact of Chernobyl found it responsible for a few dozen deaths in emergency workers (fewer than 50, and some of those dying 20 years after the accident). It might be possible to eventually tie a few thousand early deaths to the incident, but we're still waiting, decades after it happened. In general, radiation hazards were widely exaggerated. http://www.who.int/mediacentre/news/releases/2005/pr38/en/

[4] Admittedly biased source, but it runs a few publically available numbers, even nuclear projects with cost overruns look better than some renewable projects: http://nuclearradiophobia.blogspot.com/p/cost-of-nuclear-pow...
I mean, ideally you get a mix of both sources, because they serve different purposes on the grid, but your bursty diurnal power isn't meant to serve as your cheap main source of power.
Looks like they screwed up the DER encoding more than the actual cryptography, incredibly stupid but understandable.
Again, very much appreciate your feedback. This is the main reason why we've posted it here, to get some discussions and learn together what is relevant nowadays to developers and what is not, so we don't have to reinvent the wheel.

To touch base on your example with authentication, we are working on deep-security library that everybody will be able to reuse without any effort. We are approaching security in every layer similar Amazon IAM, and since we are using microservices architecture, developers don't need to write any security specific code, because it is automatically generated at deploy. Everything is collected at deployment time from every layer and applied on AWS for backend and database, while on frontend is exposed in UI as role-based access. Does it make sense?
Amazing Grace...
>Producing a crappy interpreter for a toy C-like language is about the same as producing a crappy interpreter for a toy Lisp language.

Ab-initio perhaps (and even that isn't clear because parsing sexprs is a lot easier than parsing C). But producing a production-compiler for a non-toy Lisp-like language given a compiler for Lisp is a heck of a lot easier than producing a production-quality compiler for a non-toy C-like language given a compiler for C.

> C did turned into a Tower of Babel: in the libraries.

Sure, and for the same reason: it's easy to write library code in C. In fact, that's the only thing that's easy to do in C. So that's what C programmers do: they write library code. They don't, as a general rule, write compilers. So the compilers stay stable and the libraries don't.
AWS IoT Buttons given out at this years AWS re:Invent conference
I have to laugh when I see these posts. So, software development is a special activity that should not be constrained by budgets or deadlines (or estimates)? Where do I sign up? There are so many strawmen here I can't possibly address them all. If you can't provide a credible estimate for a piece of work, you either a) aren't very good, b) don't properly understand the work to be done, or c) perceive some aspect of the job that is unknowable to you (through lack of experience or other novelty). Fixing each of these is up to you. 'a' is obvious (you either work hard to get better or find something else to do). 'b' means you need to ask more questions that allow you to sufficiently complete your understanding of the problem so an estimate is possible. 'c' means you need to isolate the novelty and explain that this part of the problem is new to you and you are not qualified to provide an estimate. Perhaps someone else can provide that insight or you can define an initial activity designed to help you better understand the novel problem until you can estimate the remaining work. NO area of engineering is so cut and dried that estimation is easy.

What IS common is a combination of poorly defined projects and a profound lack of self-awareness. By all means, push back against poorly defined projects ("I can't estimate the work until you tell me what it is."). Lack of self-awareness is squarely in YOUR lap ("I don't understand why it always takes longer than I thought it would..." Well, duh, maybe you should consider that reality for what it is and account for it next time).

Estimating work and committing to those estimates is what a professional does. Deal with it. If estimates are imposed on you that you do not agree with, that has nothing to do with the virtue of estimation. That's a social problem, not a technical one.
California defines classes of vehicles with different safety requirements and horsepower/speed/engine size caps. A 40 mph skateboard shouldn't be allowed on bikeways, or with a bike helmet; and maybe needs lights or something for visibility.
I'm a Russian freely speaking my mind on the Internet.
I’ve only started doing that after I've took my one-way flight from there, with no intention to return ever.

Are you sure those Russians you're talking about aren't emigrants like me?
The other part of 3 part estimates that I like is that it forces everyone to consider the worse case. What can go wrong? What risks are there to this task? And only then do we talk about how long we think it will probably take.

The problem I have always had afterwards is communicating the results. Most people I've worked with cannot intuitively grasp confidence levels (90% vs 95% vs ...). They also invariably want a break down of how long each task or group of tasks will take so that they can negotiate down the estimate, not understanding that the total estimate is not a simple sum of each task. I'd love to hear better ways of explaining/using these sorts of estimates.

The first time was my fault: I left the columns that had intermediate values visible. One of those was the variance in each estimate, which is just the Std Dev squared. The numbers were big. No one could stop talking about how big the numbers were. No one knew what a variance was, nor appreciated that it was just the number in the previous column, multiplied by itself. Learned the very important lesson that you hide all your work, no one gets it.
> Wind is already so cheap, Exelon's CEO (who manages the largest commercial fleet of nuclear generators in the US) is threatening plant closings if they don't get a bailout.

Am I missing something? I don't see anything about a bailout in that article. Unless I overlooked something, it sounds like he's just saying that government subsidies on wind power are excessive, which is the opposite of asking for a bailout.
Electric boards clearly shouldn't be on sidewalks, same as bikes. I'm often stuck slowing down bikes going gently downhill because my boosted board won't go faster than 22. This becomes a safety hazard as bikes try to pass, etc. Bikes don't have separate speed limits in bike lanes and are capable of speeds much higher than 20.

Ability to ride uphill is also a function of output power. This cap is fairly generous but I don't understand why its necessary at all if there's a speed restriction? It'll only limit acceleration and hill performance if there's a speed restriction.
So, small tasks you CAN estimate, large ones not so much. Perhaps the technique to use is right in front of you: decomposition.
or Uber drivers and taxis sitting in bike lanes...
yes on linux(usbnet) at least for a long while, not sure about usb3.x or windows support though.

https://en.wikipedia.org/wiki/Ethernet_over_USB

A quick google showed there are Gigabit NIC over USB3.0 on the market already(for a while):
http://www.amazon.com/Network-Adapter-Anker-Ethernet-Support...
I have a couple of electric bikes and a boosted, and the big advantage to being able to do a steady 25 mph is the ability to take the lane on neighborhood streets and be going the speed limit.
I'm much more annoyed by cars than by any other device on the road when I ride.

Electric skateboards and scooters are awfully zippy and rarely cause any disruption in my ride.
You don't even need VT-d for USB devices, only PCI one.
Think of enterprise applications as puzzles, and think of us as puzzle manufacturers who will help puzzle builders (developers, devops, admins, etc) get the best puzzle for customer needs :)
http://chicago.suntimes.com/politics/7/71/548759/editorial-e...

"Exelon, which operates six nuclear power plants in Illinois, says it needs help because — although it made more than $2 billion last year — it has lost about $1 billion in the past five years on three of its plants: Clinton, Quad Cities and Byron. The nuclear plants are having a hard time competing in the marketplace partly because plentiful supplies have driven down the price of natural gas.

The utility says it is unwilling to run any nuclear plant at a loss, though its nuclear fleet is profitable overall. It says Illinois needs all of its nuclear plants for reliability and low-carbon power generation. It also warns that 8,000 jobs in Illinois would be lost if the plants were shuttered."

http://wqad.com/2015/08/04/quad-city-wind-energy-farms-on-th...

"This really is a critical time in the 41-years at the Quad Cities station where we have never been in a position where me may have premature shutdown," said Bill Stoermer, Senior Communications Manager at Exelon in Cordova. "We really need the state legislature to act. They of course are focused on the budget and to try to get some budget resolved. We certainly understand that, however we're going to be forced to make some decisions by the end of the year regarding our plans here in Illinois."

http://midwestenergynews.com/2015/05/01/exelon-we-have-to-ha...

"Exelon was happy to embrace risk when wholesale power prices were on the rise and profits from its generation business were flowing, Hendrickson said. Only now, in a market where nuclear power is under pressure from relatively inexpensive natural gas and wind, is the company asking for help in the form of a $300-million-a-year subsidy."
A flat address space is the future. You don't need virtual memory when a flat address space can hold all memory addresses for all processes as it does now with 64-bit processors.
A tremendous vote of confidence for AL and while it may take time for this to impact the market, $400 Mil. is a lot of money and it will have a long-term impact on how seed funding happens.
thanks for the link, I agree it's bad practice if there's any kind of lookup/security based on the slug. We have a few other mitigations against looking up anything security wise from the slug itself. but will take it into consideration as I agree it increases guess-ability of the slugs and could leave us open in future.
Dell buys EMC
I'm building a microwork platform but so far the main focus has been on the worker side and not on the submission of jobs side. Are you set on just using MTurk as your backend for workers or would you be willing to work with other providers?

If you're willing to work with other providers, what kinds of requirements would you have to ensure that the workers were high-enough quality for your needs?
That makes sense - I suppose in that sense, matching the regulation for bikes and for boards doesn't really make sense. I have an e-bike I built that won't do over 20 on electric power, but I still do tend to take the lane and go 25-30 on the street thanks to pedal assist (which boards don't have).
Oh? What about Libya?
I don't want a USB NIC, though, I want just USB to USB with as little shit in between them as possible to be as cheap as possible. Maybe even allow straight DMA to DMA across the machines due to it being USB 3.x.
I should also add that we don't use the URL for any kind of security/lookup. we rely on other information for that. as such the aim is to give readable canonical urls to your application, much like most apps use a /{username} slug
They could be Volkswagened:

When on a level surface, cap the speed to 20mph. When on an incline, turbo mode!
> There are 30 three-star restaurants in Japan, as of this writing, compared with 26 in France and 12 in the U.S. Michelin began rating restaurants in Japan around the same time the guide came to America.

As a French guy who lived in Japan for some time, I've got a very simple explanation for why Japan has more Michelin stars than France.

If you go to a normal average restaurant in France, the food will usually not be very good, they will serve dishes prepared with pre-made sauces from Metro, they won't serve anything amazing. There's a very big discrepancy in France between normal restaurants priced less than 20 euros per person for lunch without wine and the gourmet more expensive restaurants.

People also go out to restaurants a lot less than in Japan so there are less restaurants in France. In Japan, Osaka has 16,000 restaurants. Tokyo has 55,000 restaurants. Paris only has 14,000.

Even restaurants that are not very expensive (1000 yens lunches) in Japan tend to only use homemade ingredients. They don't use pre-made sauces. The average quality of normal restaurants is much higher and a lot of the Chefs at those restaurants are actually passionate about the food and try hard to improve their skills.

So, it's simple, Japan is a country with at least twice the number of restaurants per population as France and with a much higher percentage of passionate chefs that want to improve their skills and are there for the love of food rather than for earning money. It's actually surprising that Japan still has so little Michelin stars.

As for michelin stars, I actually trust the Gault et Millau guide a lot more in France, they don't care as much about the atmosphere and the service, they care about the food and ultimately that's the only that matters for me.
Integrating Jenkins CI with AWS Device Farm for Android Testing
Learning FP the hard way: Experiences with the Elm language
I feel like that quote is a relevant content considering the post is about how YC was good for their startup... and they're listing ways in which YC was good for their startup.