skysight-inc/HackerNews huggingface dataset:
Continuing the sentence from the title, "but they allow you to deal with it better".

The question is what is the business requirement and guarantee regarding the message delivery. In my experience with logging systems is that losing a very small percentage of your data in case there is an outage in the storage layer is tolerable.

That allows us writing code that sends or receives messages using a channel (Go, Clojure) and have sane timeouts to gracefully deal with overload, saving 200 (or so) messages in a local buffer and going back to reading the queue after a read timeout.

With this concurrency model queues are very powerful tool of separating concerns in your code. Having thread safe parts that can be executed as a thread or as a gorutine lets you use 1:1 mapping to OS threads or N:M.

Back to the original point, queues don't fix overload, but I still prefer deal with overload using queues over other solutions (locking or whatever).
Eh, there is too much that can go wrong with that plan...

Besides, the meat puppets will have families back home that might get all sentimental when the inability to question the stupidity of your orders gets them shot.

Maybe better just go ahead and develop the robot army which will render the whole meat puppet order following helmet moot.

Besides being many times more effective, the robot army won't eat as much, won't require a lifetime of pension and medical care, and there will presumably be fewer problems with sexual harassment in the ranks.

So much for the years of developing iron clad discipline... the steam drill is here John Henry.
I'd say a better analogy would be AT&T since it's the former monopoly
Has anyone tried the Focus device? http://www.foc.us/ Curious to hear any feedback.
There seems to be a culture clash on HN.

On one side there is California, where "dick wagging" is an unnecessary instance of gendered language, certain to drive women out of the tech industry.

On the other side there's the rest of the world, where being offended by "dick wagging" seems dazzlingly childish. It's just a penis, most grown men and women know what they are and observe their motions on a daily basis.

In Bhutan they draw penises on things for good luck. http://en.wikipedia.org/wiki/Phallus_paintings_in_Bhutan
I plan to use mine with an apple bluetooth keyboard I'd say you'll need some external device for screens though.
In the case the OP described above, I would think the factory would be pretty good collateral. For a software company that just wants to hire more staff, not so much :)
This link worked for me
Depressingly, the answer appears to be yes.
Yes although our government has forced them to open up the last mile to competition. So unlike with Comcast/AT&T, at least here you can switch to a more palatable ISP fairly easily & quickly. You're still somewhat at the mercy of BT's engineers though if you have a fault on your line.
The push for Twine does come from a specific group of academics who wrote papers about it as a tool for pushing their agenda into gaming. This is documented.

But what's really hilarious is that you will not find a single actual review of Depression Quest on the same sites that gave the product and its creator so much press. For one very simple reason. The 'game' is utter crap. The writing is cringeworthy. Everyone knows the reason it got so much coverage was because of connections, self-inflicted scandal and political ideology. Now they're stuck with having pretended that wasn't the case, so they keep running around in circles about it.
This is precisely why — for some products in some industries — NIH is a reasonable strategy for writing good programs.
The operating system has to support the exFAT file system. I imagine that's the main barrier -- you have to license the exFAT technology from Microsoft.

You can take an SDXC card and format it as FAT32 and it'll work -- of course you'll still face the limitations of FAT32 as far as file size, etc.
Actually they said "more than half" were unacceptable, but still your summary is basically an accurate one of the article.

I don't know if it is the same but in the semi-conductor business the reactor/furnace used to make the silicon boule had an oversized influence on the yield of the wafers produced. That lead to some folks timing their wafer starts to coincide with a specific lot of wafers.
I think this is the announcement I had in mind, I'd just take the published roadmap with a grain of salt, because usually things ship when they are ready and fit into the whole picture.

As seen in dotty, the basic stuff around union types is already working, so I'd be pretty surprised if it didn't ship earlier, especially because there is a demonstrated need for HLists, and shipping HLists without union types ... could be done, but why?

Additionally, a lot of things mentioned in "Don Giovanni" are already ready-to-ship today (sans a few minor requirements). For instance Giovanni's 1.3, 2.1, (some parts of 2.4 already shipped with 2.11), (approaches for 5.1 were already discussed and benchmarked), 5.1/5.2 (will happen when targeting Java 10).

My recommendation is to take that roadmap as a bottom line, but be prepared for drastic changes. My current guess is that if work gets done at the current speed, it might be possible to move things to earlier releases and subsequently eliminate a whole release in between, e. g. shipping the features of three releases in two.

But that's all just my educated guess.
> Every intermediate layer that Google does not control is a risk to their business.

Every intermediate layer that Google does not control is less access to information that they can use to build an advertising profile on you. Hence their strategy of attempting to control the network edges to gain as much visibility as possible (see Chrome, Android, Google Fiber etc).
Please continue. Very interested.
Dear Megan Trainor: so you think I was strong?
Unregulated Crowdfunding
Thanks again for another great answer. I can see where the legal/regulatory overhead for issuing debt could be a big roadblock. It is my understanding that a lot of early stage financing is 'convertible debt', with the idea to convert it into equity at a later time. I wonder how often start-ups decide to pay off this debt from revenue rather than allowing it to convert? Would that be a big no-no?
Ha not sure if this counts, but around a year or two ago I found out a cheap source of page rank which I pointed to one of my loans lead gen website which resulted in me ranking for some fairly decent money keywords. I was making few hundred a day for a couple of months before the website was penalized by Google.

I mostly dabble in whiter-hat stuff now but the progress is slow (but hopefully it lasts longer) and make a few hundred per month.
It has taken me months to build up will power to the point where I can work on coding projects in my spare time consistently. Fail. And not care and keep carrying on.

Some ideas that may help:

1. Enter a hackathon. Group up with people and you will be compelled to code.

2. Train for a half marathon. Increase your endurance and your ability of will to keep to the training schedule.

3. Have children. Ironically the ridiculous overhaul this has has on my life has increased my resilience. Last night I got woken up 3 or 4 times. That's normal. I feel OK. Also the children will motivate you to the long term goal of having more time with them and not being stuck at work for so many hours.

4. Do the equivalent of having children - maybe take a second job for a while to get used to the extra hours.

5. Give up TV.

6. Give up Caffeine.

7. Give up Alcohol

8. Give up Socializing

9. Learn to get an itchy feeling on any day you haven't taken action. It's a horrible feeling that keeps me glued to the laptop.

10. Therapy. This should be for everyone not for just the very depressed etc.
Owncloud has something similar but it's very new. Also, it means you run it on your own hardware, and it's open source. https://owncloud.org/blog/owncloud-7-sneak-peek-online-colla...
So, UNIX boils down to "the accumulated cruft of 40 years of bad ideas"?

I'm not disagreeing on the principle of immutable servers, but that's a pretty bold claim.

I don't see getting rid of the "accumulated cruft" as being a particularly interesting reason for exploring the unikernel or immutable server concept. The benefit is in building for scale and redundancy. The lighter your image, the easier it becomes to replicate it and maintain it, generally speaking.

Further, there is an argument to be made that building your own cruft into your system is counter-productive compared to letting the operating system cruft handle it. The Linux developers are probably better at it than you or me; unless we understand our usage patterns dramatically better and the options for optimizing them, it may be best to trust the OS "cruft" to do the right thing.

In short, I'm not really taking a side on this one. I believe there is interesting research to be done, and probably useful outcomes to be found, in this direction. But, why dismiss 40 years of operating system refinement by some of the brightest minds in the world as "accumulated cruft...of bad ideas"?
Except that all the docs are in C#, which means if I want to consult them, I have to either know C# or know how F# interops with C# (and therefore understand C#). Trust me, I would love to, but I don't have the time to learn two languages for one project.
http://www.asu.edu/clas/sirgtools/ecology-1991.pdf says that Pogonomyrmex rugosus travels at 0.1914 * T - 1.983 meters per minute, for ground temperatures T (in C) between 20 and 40. This is roughly 3.8 m/minute or 60 mm/sec.

The equation for Messor pergandei is 0.0878 * T - 0.1724 or roughly 40 mm/sec.

So 50 mm/sec seems quite possible.
All I can say to that is that if you value value than assessing productivity is not for you.
Where have you heard this ? Everything I've seen to date has Google/Volvo at the same level. And it's somewhat irrelevant how many years Google is ahead when they have zero experience in bringing automative to market.
Also, complaints about paywalls should not be allowed on HN.
Yes I remember the days when you edited a line by using the arrow key to go up then copying character by character, then edit the bits you want as you go along. Or something like that. Magic!
Book Review: ‘Information Doesn’t Want to Be Free’ by Cory Doctorow
Food review blog and craft beer – South Florida
As much as I like OpenSCAD for its scriptability, the OP is really pushing the limits of what you can do with it. I'm hoping FreeCAD takes off eventually in this space (hobbyist parts design).

Of possible interest to those reading this, I worked on a project in college that did a similar thing with AutoCAD for full-size water treatment plants. A web interface[1] accepts input which is sent to design scripts, where equations of fluid dynamics and other physical constraints are used to scale components appropriately for the size requested. From there, the AutoCAD command prompt is accessed to generate a 3D model and various construction-oriented section views.

[1] http://aguaclara.cornell.edu/implementation/design/
Isn't that a security hazard? The mechanism of these captive portals is literally a MITM attack, and I don't see how to distinguish a benevolent from a malevolent use of it.
There's also ImplicitCAD, which is Haskell and actually more powerful in some ways. Unmaintained as of this summer, though.

http://www.implicitcad.org/
No problem, it's a pretty common mistake.

Every single star you can see with your naked eye is inside our galaxy. Even with telescopes - you'll need a very big telescope, by amateur standards, to resolve stars in other galaxies.

As for non-stellar objects:

Naked-eye galaxies are very few - they're all on that short list linked above. And only the first half are easily visible, and then half of those are in the southern hemisphere.

Omega Centauri actually almost looks like a fuzzy star - almost. It's pretty small.

You can see some nebulae (like the Great Orion Nebula) and star clusters (like M13) naked-eye, but they are only a few, and you'd have to drive far into the middle of the desert for most if not all.
So variables are explicitly declared, don't have issues of mis typing a variable name and accidentally declaring a new one.

Note: This is just my thinking, I don't know if it's the actual reason
Aren't all of those about telecommunications? The name seems apt.
Temple Grandin: AMA
I'm near sighted. My eyeglass prescription is about -6.5. Using either windows or linux, anything over about 105 dpi is too small and I need to get closer to the monitor than what is acceptable from an ergonomics stand point.

If I need to use something with a higher dpi for any length of time, I have crank up the font size which causes some problems in some applications.

Right now I use a 19" 1280x1024 and a 20" 1600x1200. A monitor like this would be great.
I'm definitely in the same camp.

I don't use Redis, but one thing I like about it is that it's a fairly generic storage layer that you can adapt into various data models; you can implement higher-level tools using its lower-level ones. I would love to be able to build a whole database machinery out of specific primitives.

For example, a "column" is basically a primitive you should be able to instantiate using some kind of storage strategy: keep it in RAM, keep it partitioned into chunks, append-only, compressed, sorted, remote etc.

The main thing that I want is to separate data from queries. It's always baffled me that traditional RDBMSes choose to commingle tables and indexes. Why does my commit have to wait for the indexes to catch up? Why do indexes have to be involved in the slow, complicated system of updating tuples that involve transactions, locking, paging and so on?

A better approach is to separate the two entirely:

1. The careful, slower ACID core that journals, fsyncs, keeps my data safe and provides a rigorous data model.

2. The super fast read-only, distributed indexes that organize the data in the most efficient way for querying (mostly through RAM and vectorization).

Now, I don't really need my write node to be a super-complicated distributed, replicated, gossip-based hash-ring-sharded, quorum-coordinated eventual consistency monstrosity. Single master is fine as long as you can keep standby replicas that are easy to fail over to.

What I want is for there to be a whole gaggle of read-only slave indexes that get my data reasonably quickly and are super fast to query. Indexes can be eventually consistent; but they don't need to be safe. Indexes can be reconstructed from the master data, after all. All we need to do is for indexes to ingest a continuous stream of data changes from the master.

Again, the master can be a bit slow: As slow as Postgres, at least. But the indexes, since they don't need to deal with transactions or locking or anything of the sort, can be really fast. Splitting the two up means they can each worry about different things, and apply different tolerances and constraints to what they do.

Today, we accomplish something similar by using ElasticSearch with Postgres. It's not good enough in the long run; they have completely different query mechanisms and data models, for one. It's also difficult to keep ES in perfect sync, and ES is generally heavy-weight; ES indexes are beasts, not very mobile. For example, the schema is mostly static, and changes require cloning the index (which I find weird). Still too fulltext-oriented; it's just not quite as good at non-text stuff. GIS support is lacking. And so on. A uniform query/database system is definitely needed.
DDG uses Bing and some other search engines, but not Google (except when you explicitly redirect your query with !g).
They're trying to copy the OK Cupid analysis blog, I guess.

Unfortunately for Uber, they're well on their way into creepy already.
So why don't posts like OP's seem as absurd as mine?

I think the Fine Article does seem absurd. And while he doesn't come right out and say it, I think he would agree that in hindsight his approach was absurd. The whole second half of the post is about how actual programmers get actual work done, and it's nothing like the first half.

The interesting question is why did he think his original approach was reasonable? Did he not talk to an actual software engineer before embarking on his journey? Sure something like his original path can be successful for some people, but it that a reasonable expectation?
404 - Article Not Found
Hi-
Already tried both. Anyone able to ACTUALLY get Java 8 running on Chrome 64bit?
Database vendor frames history of computing in database evolution, makes snide remarks about competing technologies, admits it has no idea where the world is going while invoking the 'history repeats itself' notion. Well, duh.

OTOH, databases are only one component of modern architectures, which the article correctly asserts are largely limited in terms of scalability by throughput and latency. However, scalability is often secondary to functionality. And in terms of functionality, the long list of database types trawled out through the article only serve to highlight the real chokepoint: cognitive overhead.

Perhaps what we really need are tools that enable us to more easily stop and think about the problem. Ideally, tools to test, profile, compare and switch between storage or other subsystem architectures without having to delve in to infinitesimal intracacies of each.

Success really depends on the conception of the problem, the design of the system, not in the details of how it's coded. - Leslie Lamport
So "traditional" sex is a PRNG that first generates a large number of random combinations of bits, picks two of them at random, returns those two, and discards the rest. Sounds rather inefficient, right?

These bdelloids, on the other hand, just decided to shuffle the bits in place. A bit insecure (prone to errors and contamination), but very efficient in highly constrained (frequently dehydrated) environments.
404 - Article Not Found
The article you were looking for was not found, but maybe try looking again!

You can get the text from the RSS feed [1].

---

Yesterday evening Pacific Standard Time, Azure storage services experienced a service interruption across the United States, Europe and parts of Asia, which impacted multiple cloud services in these regions. I want to first sincerely apologize for the disruption this has caused. We know our customers put their trust in us and we take that very seriously. I want to provide some background on the issue that has occurred.

As part of a performance update to Azure Storage, an issue was discovered that resulted in reduced capacity across services utilizing Azure Storage, including Virtual Machines, Visual Studio Online, Websites, Search and other Microsoft services. Prior to applying the performance update, it had been tested over several weeks in a subset of our customer-facing storage service for Azure Tables. We typically call this “flighting,” as we work to identify issues before we broadly deploy any updates. The flighting test demonstrated a notable performance improvement and we proceeded to deploy the update across the storage service. During the rollout we discovered an issue that resulted in storage blob front ends going into an infinite loop, which had gone undetected during flighting. The net result was an inability for the front ends to take on further traffic, which in turn caused other services built on top to experience issues.

Once we detected this issue, the change was rolled back promptly, but a restart of the storage front ends was required in order to fully undo the update. Once the mitigation steps were deployed, most of our customers started seeing the availability improvement across the affected regions. While services are generally back online, a limited subset of customers are still experiencing intermittent issues, and our engineering and support teams are actively engaged to help customers through this time.

When we have an incident like this, our main focus is rapid time to recovery for our customers, but we also work to closely examine what went wrong and ensure it never happens again. We will continually work to improve our customers’ experiences on our platform. We will update this blog with a RCA (root cause analysis) to ensure customers understand how we have addressed the issue and the improvements we will make going forward.

---

[1] http://sxp.microsoft.com/feeds/3.0/devblogs
I hope to read more in the post-mortem RCA but I am curious what their flighting missed, is flighting so limited that is does not see the cross region scale or something? I also had the feeling from watching Mark Russinovich discuss previous failures that their patch rollouts were much more controlled.
Censoring wouldn't break the law, they're already doing that. And the blog post specifically mentions that it wasn't blocked using DNS but by a redirect from a Google server.
Actually they do, which is why if you run the drive sans NCQ you get lower sustained throughput, and get overloaded faster.

Having a queue of messages allows optimization in ordering the messages.
Pioneers Die Broke (2002)
Out of interest what language are you coming from?
Awesome! Looks very similar to Origami -> https://facebook.github.io/origami/

I have never used either, but both look so much better than working off static PSD comps. I would be curious if a person who has used both can chime in on their impressions.
> They paid Firefox $300mil a year for three years

Mozilla's 990 forms are public. For 2012 I see a bit more than $9 million in revenue, of which $5.4 million came from contributions [1]. "$300mil a year" makes no sense -- unless there is something I don't know about how non-profits are supposed to report their revenue.

[1] https://static.mozilla.com/moco/en-US/pdf/2012_Mozilla_Form_...
I look at it the opposite way. There needs to be a way to allow software developers to say, "My profession's ethics will not allow me to develop this (credit card, medical record, banking, etc) software in the way you've specified. You can either change X, Y, and Z, or give up on having the accredited software engineer label on it." It certainly wouldn't be required for many or even most applications, but it seems desperately needed right now (c.f. healthcare.gov).

Done right, this allows for both non-accredited software developers, and professional engineers to live and work side-by-side.
What kind of business are you in?
Pursuit of Beauty by DHH. 2005 Ruby on Rails Presentation
Why did BT recommend using a VPN?
Beauty leads to happiness

Happiness leads to productivity

Thus

Beauty leads to productivity

- DHH
If anyone from 42Floors is reading this: your link to your own site with the anchor text "office space" is a relative link and therefore broken:

<a href="42floors.com">office space</a>

You need to make that http://42floors.com or it's not going to work for users (and search engines ;) )
I always position all of my monitors at the same distance from my eyes. That's because I'm an old guy and my eyes can't focus to different distances easily like they used to. So I have a pair of single vision computer glasses - like a reading prescription, but adjusted for the approximately 20" between my eyes and the laptop screen (almost exactly the half-meter you mentioned).

Typically I have three displays in a row: a monitor on the left and two computers on the right, a MacBook Pro Retina and a ThinkPad W520 (145 ppi). Whichever computer I'm primarily working on that day goes in the middle and is connected to the external display.

I wouldn't be able to use a display 34" from my eyes unless I used a different pair of glasses, and then I'd have to switch glasses back and forth to look at the different screens! Unless I gave up using the laptop screens at all, but I'm not about to do that.

So with all my monitors at the same distance, what feels like a "retina" density is the same on all of them.
People rightly or wrongly don't feel comfortable modifying GPL code. And don't see any benefits to GPL. That seems pretty straightforward to me.
Tech Reacts to the Demise of Partial NSA Reform in the Senate