skysight-inc/HackerNews huggingface dataset:
Lets not forget that the usage of javascript correlates with need to target the omnipresence of browser and not for merits of javascripts idioms or design pattern paradigms.

Javascript is a great hacker language. All the improvements as stated above will extend the capacity of js to quickly hack up mvp apps. With that said I think the argument can be made that javascript was never designed from the ground up to support this new omnipresent realtime persistent application platform.

For me the question remains to be seen answered if a server that was designed the ground up to be a server such as netty offers a more stable solution then node.js

I think some might say that ES6 is like putting lip stick on a pig therefore patching up JS to keep evolving as more expressive language.

Every time I run NPM install I wonder what kinds of incidental complexities I am I getting myself into. Then dred if I have learn yet another build system. Every time I run NPM I think of an old Jim Breuer joke [1] -- NPM is the "tequila" in the JS party of complexity.
ASM.js is amazing, but are we getting a little too drunk on our technologies. ASM.js just might be amazing koolaid when it comes to the sobering decision to build something from "the feet up" to serve on purpose and serve it well. JS can be the jack of all trades and master of none and that can be a bad thing. One thing is for sure JS is really fun, but I would not go making a stock market exchange out a javascript codebase.

Speed is not the only performance metric out there. Think stability is often overlooked for having more power over more control. The Influenza in JS world is not spaghetti code but the more harder to grok house of cards library dependencies. This is just my amateur opinion on observations as go further down the rabbit hole of my learning to code journey.

TL;DR JS is a great hacker language but drink responsible when it comes to importing incidental complexity of additional libraries.

[1]
Jim Breuer Just For Laughs
http://www.youtube.com/watch?v=z8dvpsVEJEQ
[2]
"The Mess We're In" by Joe Armstrong
http://www.youtube.com/watch?v=lKXe3HUG2l4
But deploying and managing that equipment does not cost the same. There is another comment in this thread that says only about 3% of operating costs for Sonic.net come from bandwidth. U.S. based ISPs employ U.S. based workers which on average are paid more than employees in say Poland, so it's hard to do a direct comparison. Not saying that we in the U.S. don't pay too much for internet, just that a direct comparison to other countries is tricky.
Block rewriting with Clang
Before you explore Heroku much further, I would recommend doing some cost analysis and see what it would cost you versus hiring some part time or full time DevOps help.

Even if you find that it costs you twice as much to hire a DevOps person, it will be worth it. You should try to avoid the cost (and the impact to productivity) that a Heroku migration would bring if you can.
How Supercomputing Is Cracking the Mysteries of Human Origins
To be honest, I'd be hesitant to recommend most "go-to" freelancer sites like oDesk, Freelancer.com, etc. There definitely are genuine skilled and hardworking people on these sites, it's just there are tens of thousands more that aren't.

I would:

- Look to see if any Visual Studio Extensions you [use/like/that are similar to what you have in mind]'s authors are easily tracked down and see if they'd be open to taking on your project.

- Look within your own network/circles for someone you know or trust.

- Google.

I'd much rather "headhunt" a freelancer and make up my own mind through seeing how they present themselves online, their past work, etc, without being constrained to a thrown-together proposal on a freelance site to decide.

Good luck!
Dude, prove it. The system should be able to exonerate itself by detecting and reporting those problems (and other systems do). At the very least, point to some actual evidence. This is the "engineering" process that the parent poster referred to elsewhere.

Just because a problem is unusual, intermittent, or only affects one person doesn't mean it's not a regular old software bug. And in my experience, it almost always is. And once you do debug it, you often (but not always) understand why it was intermittent, under what conditions it happened, and why you were the only person that saw it.
I agree this "forgotten wo/men" would make a great blog. Important in science, startups, athletics, essentially every competitive endeavor.
What is antiquated about the idea that you don't get to use other peoples' valuable content without paying for it?

Look: the valuable product here is the content. All the technology can do is get in the way. It's great Aereo's technology got in the way less than its competitors, but that still doesn't mean people found the technology itself valuable. The content is what matters. The content is what delights consumers.

Given that reality, I think it's absurd to say that regulations protecting the people who create the content, the product without which the whole downstream ecosystem of streaming services and content consumption devices are utterly irrelevant, it's absurd to say those regulations are antiquated.
We use xapo developer services to separate the server code from the bitcoin wallet stuff. They are a legitimate wallet service with a very cool API but you'll be able to transfer emeralds to any other wallet
And do you send the "tv/cable whatever" companies a check for whatever you think the content is worth? Otherwise you are just a thief.
In the future, it's not just eyeballs, but qualified eyeballs. Marketing used to be regional now it's getting really personal. Tracking data allows you to do so much stuff:

facebook look-alike audiences
google data
etc.
About 40k downloads over the last year, 204 topics on the forum and 145 issues in the tracker so far. So, there is some activity.
Buy BBEdit.
"Fuck you guys and your cider, I've been drinking ale for years, but now I'm going to only drink my own pee because you like something different"

That's what you sound like.
SMF is a pita - far, far worse than the process management stuff in systemd.

SMF does not seem to want to own every bit of my Linux machine, however.
> The change forces you to use systemd for cgroups as only systemd is able to write to cgroups. The argument is: If you don't like systemd implement an alternative that does this for you.

And from the looks of it, this has been done: https://cgmanager.linuxcontainers.org/ as reported at http://lwn.net/Articles/618411/
Nigeria First Lady Gets National Identity Card
Thank you very much.

In a nutshell, the manager requests the servers responsible of rendering the demo pages, and those servers contains generic installations that are deployed everytime an user creates a new instance :)

In the global view, this project contains static pages (official website), Play Framework (Java/manager), PHP scripts (cron tasks, some tools) and shells scripts for automating installation. Everything on top of a Apache/PHP5-FPM/MySQL/Debian stack, hosted at Digital Ocean :)
What's Wrong with the Default Alert Rendered by the Browser?
I agree with you in theory, in practice we know this isn't the case. The way content is shared in 2014 and data is duplicated you don't have that right anymore if you are creating any type of digital content. Not out of some "overarching evil" but out of people's desire to share.
Content being broadcast on ostensibly publicly owned airwaves (not that the "public" ever seemingly gets any say in this). While I agree with your point that they didn't own the content, making it illegal to provide a service that improves the reception on those public airwaves to local customers doesn't sit well with me. I'm equally annoyed with the shenanigans employed with Dish and DirectTV to block their broadcast of local channels to local customers. If the content owners are really that concerned here, they can simply move their content to privately owned channels.

Not that I ever expect a court ruling to say anything close to this because lobbyists and money, just saying...
> clearly even the smallest changes upset people

{glances at this HN thread} Yes, clearly :)

I get that these changes are pain points for lots of people, and no one wants to be frustrated using the devices with which they have everyday, critical interactions.

> Who wants reliable, familiar interfaces and predictable functionality? Um.... try everyone!

Sure we want that... and we also want newer, better things. That's a tug of war between comfort and progress. If all we did were laser-focus on reliable, familiar interfaces and predictable functionality we never would have gotten the GUI or the mouse, right?

> A-B testing won't reveal how many people reluctantly embrace the change, rolled their eyes and cursed your service as they completed the task. A-B testing is not all-knowing. It's suitable for colder functional changes, not things such as key separators on a virtual keyboard.

I completely agree. My point was to home in on what you would characterize as change. Your response was very helpful to that end.

> None of this would be a problem if users are simply given choice and meticulous control over the changes and how or whether they're applied. Choice, control, options and user preferences - those should be the key features.

Yeah, it would be comforting if the gmail app let users toggle between "classic" and "material"... and it would also be contrary to that which is (seemingly) the driving force behind Material Design: defragmentation of UX in the Android space.

Choice is a double-edged sword. Several studies suggest that choice overload reduces happiness, increases stress, and leads to poorer decision-making.[1] On the other hand, one study found that choice overload caused all of those reactions but also positively affected their perceived quality of the brand.[2]

We HNers are a niche of tinkerers who enjoy poring through settings. As I understand it, our love of actively customizing and tweaking is not shared by the larger demographics.

Change bears risk, yes; but personally I would rather groan at questionable changes than ploddingly use an app that sacrifices the hope of exceptional change for the fear of bad change.

To each his own, I suppose.

-----

[1] For anyone interested in "choice overload":

* http://www.newyorker.com/science/maria-konnikova/bad-good-ch... which refers to a dead link that I think was moved to http://ajp.psychiatryonline.org/doi/abs/10.1176/ajp.127.3.27...

* http://www.fastcompany.com/3031364/the-future-of-work/why-ha...

* http://www.newyorker.com/magazine/2004/03/01/select-all

* http://www.nytimes.com/2014/01/21/your-money/the-trap-of-too...

* http://www.gsb.stanford.edu/insights/research-too-many-choic...

* https://hbr.org/2006/06/more-isnt-always-better written by the author of a book that some of the other articles cite

[2] http://www.gsb.stanford.edu/insights/when-customers-equate-c...
That's exactly my point. It's not limited to the Linux core team. We divide into working groups of 2-3 people max to avoid this. Works quite well.
Time Travel Is Real. Here Are the People and Spacecraft Who Have Done It
What dating a model taught me about chasing opportunities
Looks pretty good. Go on and do more of whatever you are doing
TLS encrypts the transfer. It... sort of authenticates the site (modulo multiple holes that exist in that scheme).

But that just pushes the problem on the user: now the user needs to know affirmatively that "rust-lang.org" is the correct source. And they need to know the same thing about every piece of software they install using this insanity.

That's a rather different situation than simply trusting the install-time keys shipped on your system, which you can authenticate manually (via a public key check against a well-published, historically attestable key) with comparative simplicity.
I don't see what's "broken" about these terms. People understand them, and they serve their purpose: explaining the roles of various nodes in the network.

However, I understand your argument that there's really no need to differentiate between "buyers" and "sellers": every node on the network could be either, both or neither at any point in time.

I don't think changing the language used in OpenBazaar really makes much of a difference though. I doubt people are that interested in doing barter trading via an online market. That seems very inefficient (ie. sending a pound of beef jerky in in the mail in exchange for receiving five LED bulbs). The only reason for doing this would be if the two parties don't have proper money available.

It'd be a lot more efficient for either party to sell their good (beef jerky or light bulbs) for money locally (for example bitcoins), and pay for the other item in bitcoins, so only a single good needs to be sent via mail. The party receiving money can then just buy the goods he wants locally.
"That paragraph clearly is recommending Solaris, specifically."

He says, as he quotes a paragraph that specifically calls out SmartOS and OmniOS -- both of which are under the IllumOS branch of OpenSolaris.

"So, CoreOS is the Linux option he recommends? The same CoreOS that uses SystemD?"

The problem he's raising isn't that linux is going to be different, and if you think it is you need to re-read. Try doing it with your --with-reading-comprehension switch. It being different is just a statement of fact, the problem statement was separate.

CoreOS is not a distribution in the classic sense. It is a platform for deploying containers, and in the use-case they've setup the author clearly believes it will allow you to still be successful in spite of systemd.
My own experience. I coded async DHTML back in 2002, with iframes or async XML loading (since 2005 named AJAX). I debugged GMail back then (the first version with the blue rounded corners, the same design as Google Groups and Google Code)

It's incredible hard to find older web resources from 10 to 15 years ago, as most bookmarks don't work anymore. And some current websites sadly try to rewrite the history.

e.g. Aaron mentioned it: http://www.aaronsw.com/weblog/ajaxhistory and you can search through Slashdot.org, (former) digg.com and web.archive.org

Both GMail (2004) and Google Maps (2005) used iframes for the first years. There were still many users with older browsers without real AJAX support - Firebird/Firefox/Mozilla Suite/Netscape, Safari(?) and some Opera. Only IE 4/5+ and current Firefox/Mozilla browser supported real "AJAX" in late 2004. Iframes were supported by most browsers.
I initially thought about charging by modules, it was even the main argument at first.

But this was not adequate because

1. Wordpress theme sellers doesn't care about modules
2. This would require a deep change in the code's plateforms (Wordpress, Prestashop) which is not best suited (this may introduce bugs).

As you said, differentiating the plans with the reset time is a good option. Heck, I even had an hard time thinking what frequency was the best! Not too short (the instance would become impossible to use) and not too long :)
Obligatory:
http://xkcd.com/732/
The Grumpy Editor's guide to surviving the systemd debate
Minesweepers 2014: Outdoor robotic competition on humanitarian demining
We went through this usage based billing (UBB, aka capacity based billing (CBB)) thing here in Canada a couple of years back, where the incumbent carriers (DSL and cable) somewhat successfully lobbied the CRTC to set wholesale tariffs based on a mix of generally lower access fees (paid per subscriber, specifying a certain connection speed but no actual traffic), and interconnect fees (covering a certain interconnect speed between the incumbent's network and the third party ISP's backhaul). The net effect of the model is that a third party ISP's variable costs are essentially the cost of their interconnect with the incumbent, and are dominated by their burst needs during peak usage times. As a consequence, there are a number of business models which this lends itself to (in terms of incentivizing users to shift usage to off-peak times) in addition to straight download cap vs. unlimited offerings.
For example, some ISPs (like Teksavvy, for example) offer unlimited plans with a reduction in speed during peak hours.

There was a LOT of debate on the subject on places like dslreports when this was in front of the CRTC. The general consensus seemed to be that UBB
in principle is a good thing (it allows for more flexibility in third party ISP business models, and roughly aligns costs with income for the incumbent) although the particular tariff prices put forth by the incumbents were inflated and suspect.

As a real-world benchmark, my third party provider (start.ca) offers a 30/5 cable plan with 200GB of usage for $45 CAD (roughly $40 USD) per month. Going to an unlimited plan adds an extra $15 CAD to that, with the risk for overages being borne by the ISP.

Of course, the incumbents' retail offerings are universally terrible (their caps are laughably small, and their prices higher than any third party provider). Because of the lack of separation between their retail and wholesale operations, they're able to offer (presumably loss leader) promotions that third party providers simply can't, and have the benefit of being able to structure their tariff offerings to screw third party providers wherever possible. So that part of the regulatory environment sucks.

Overall though it feels like a decent model (although the actual tariff prices are quite out of line, particularly for interconnect fees). $60 CAD a month for unlimited 30/5 is a fair price in my mind, and if my needs ever change there are enough third party provider with enough diverse business models that I'd likely find something that works for me.
Launching Co-Sign Pages and M-of-15 Multisig API
> "Capitalism" is a system in which people are allowed to exchange and accumulate goods freely.

That is neither what the term was coined to describe nor what actual historical systems described with the term have been. If you look at both the specific systems the term was coined to refer to and the historical systems it has referred to (and the specific policies, even that haven't been actually implemented, advanced under the banner), I think there are a couple of defensible short rough definitions that apply well in general (though neither matches perfectly with any popular articulation of capitalism, including that by the socialist critics who coined the term -- the first, based on means, is closest to that typically espoused by proponents [though it strips away the fuzzy term "freedom" for the more concrete description underlying the capitalist understanding of freedom] and the latter, based on cui bono intentionality, is more like that typically espoused by critics:

1. "Capitalism" is a feature of a politico-economic system which is exists in a system to the degree to which that system favors fee simple property rights as the basis for allocating power.

2. "Capitalism" is a feature of a politico-economic system which is exists in a system to the degree to which that system seeks measures and maximizes social benefit weighted by the magnitude of the fee simple property holdings of those participating in the system.
To be fair, pulseaudio did expose bugs in alsa-drivers, so a "known good" configuration could stop working when "upgraded" to use PA.

I have my share of reservations about systemd (and PA), but thought that it might be worth pointing out that "known good" hardware A with software X, doesn't have to mean hardware A is all good, just that A has no bugs/errors not exposed when running X. So Y comes along (new kernel, drivers?) with entirely new code - and suddenly things behave erratically.
> That's pretty surprising given how incredibly conservative/Republican the state of Utah is.

Isn't it conservatives that are for guns and their reason is the anti-government militia amendment in the constitution? I'd expect them not to like NSA either.
Why My Recent Launch Bombed: A Postmortem
Not really. It isn't going to be that important until the hardware is both affordable and ubiquitous. So they can afford to take the software development side slowly.
People don't want to recompile stuff, they want to configure the software to their liking. Basically it's very enjoyable if you're a developer.

And FWIW with Gentoo/Portage you can create and install binary packages.
I think this is bad advice. What you call "BullShit price you pull out of your ass" is called value based pricing. It means pricing your service on the value you bring to the customer, not the amount of work you invested. Because your customer doesn't care! Whether he's a genius coder that threw this together in a weekend, or he's a team of 10 that coded 6 months on this - the customer does not care. If the ROI is higher than the cost, he will buy. If it is not, he won't.

Competition-based pricing only works if the products are completely equal. Like tap water or energy. Most software products are far less equal than programmers think. To us it's all just code. To real customers, even addressing their pain point in clear and concise web copy is worth something, because it saves them time. And that is what you monetize, not the lines of code written.
Circle 3 is saying that's how big the moon would look like if it was actually proportionally sized to the cloud, and actually "in the sky" as opposed to be 238,000 miles away.

Basically, the argument here is that we judge the size of things in the sky under the assumption that they are in the sky. But the moon is not; it does not follow the perspective rules of things that are actually close to us. The figure is saying that when we see situation 1, our brain assumes situation 3 will hold.
Seems like that's the point: There is no legal replacement.

Now, I'd love to hear about some kind of non-legal replacement. Like some kind of crowd-sourced antenna array that makes it difficult to target and shut down.
Wow downvoters, it's ok to have an opinion like this!
Why iPhone 6 Plus Wins While iOS 8 Adoption Still Lags
When unable to provide a cogent response, a parable will be a sufficient substitute.
Looks great! This is only available in the US app store?
I had pretty good experience with building authentication/identity providers with Doorkeeper in Rails. Your clients would then use Omniauth or the Oauth2 directly to login via that provider. I'm boarding a plane right now, so that pulling those projects up for you is a bit tedious but just google them. Cheers!
I've built a way to deploy a Minecraft server using Bitcoin and spent a bit of time last weekend trying to get qrcode.js to run inside scriptcraft.js. My intent is to show a Bitcoin QR code for paying for the instance inside the instance's world. Marketing.

https://www.stackmonkey.com/demo/minecraft/ and https://gist.github.com/kordless/beba0a6fa8edcda3b15a
Android only recently released APIs for sound that are accurate enough for these kinds of applications. As the % of devices running Android 5.0 starts increasing, we'll see sound mixing (and similar) apps there too.
With their profits, I'd argue that -- in terms of the bill you're already paying -- you are already paying for that "10 lane highway". Only, Comcast (et al.) are not investing your payments in infrastructure. Instead, they are extracting them as profit (excessive profit, I would argue).

As to metering, that might work if there were competition. But, as has been repeatedly pointed out, there is little or no effective broadband competition in the U.S.

"No capacity" has a similar spectre in the last mile as to that which was recently demonstrating in the Netflix inter-connection choking scandal. Although last mile requires more outlay than "fixing" Netflix, the money is there (currently in outrageous profits).

The major ISP's have had years -- and very significant government subsidies and other favors -- to fix this. They haven't. We need the infrastructure to keep our economy competitive. Time to (re)regulate, and to open the field up to municipal development and competition.