skysight-inc/HackerNews huggingface dataset:
It's the same pattern that repeats itself all over the place. We've seen it with Java, with Ruby, heck, even with PHP. And now with JS: As applications grow, we tend to search for tools to help us cope with the growth.

After doing similar (but still slightly different) things over and over, we start building abstractions and with every thing our abstraction can't deal with, we make them more complicated.

Whether you use the official name of your thing ("factory") or you just run with your own idea and term - the outcome is always the same.

As a library, you feel the need to be abstract enough to cope with every feature request ever asked from your library and there will be tons of feature requests and tons of little parts people want to customize.

And honestly, don't we all prefer using some public API of a self-contained library to patching said library (think of the maintenance as that library gets updated)?

This isn't about ruining a language. This is about making the right choice of library or about the decision of building your own little customized thing that exactly fulfills your requirements (and nothing else), but as your requirements change, you're going to add abstractions yourself and suddenly you're back at the AbstractSingletonProxyFactoryBean, though you might have chosen a different name that nobody but your team understands.

As a library author, try to resist the feature creep; try to be opinionated ("I'm really sorry, but logging isn't pluggable. You want to log to your XML based logging server? That's fine, but you'll have to build your own thing or use a different framework") then you remain accessible and buzzword-free, even though that might cost you some users in the short term.

Language has nothing to do with this.
Serious question, but why would anyone want to do this? The first example on schema.org is for movie information. If you have a website with lots of movie information, why would you make it easier for google to take your information, cut you out and provide answers to queries before they even hit your website? It simply is not going to turn out well for you.
It is only available on invitation IIRC. I don't know when you we can expect this phone in stores, like physical stores.
Those invitations were given out on the forums and to people who where interested/had interest in the Nexus 5.
How many of these people get to work early and then talk over coffee for three hours?
Code source : https://github.com/olgstein/ColorblindHelper
DHH's keynote from the first day of RailsConf, in which he talks a bit about testing and the general perception of writing software as "science", is online here:

Part 1: http://www.justin.tv/confreaks/b/522089408 (starts at 11:00)

Part 2: http://www.justin.tv/confreaks/b/522101045
Actually, from the AngularJS FAQ:

"AngularJS fits the definition of a framework the best, even though it's much more lightweight than a typical framework and that's why many confuse it with a library."

https://docs.angularjs.org/misc/faq

[NB I was curious as I haven't used Angular and I thought it was a framework and I wanted to check to see if I'd got things completely wrong!]
Usually the abbreviation "America" refers to "United States of ...", while if you're referring to the two continents, you refer to "The Americas". And if you want to get more specific, you can refer to North America or South America.
Is there any support for sub-items? Looks great, works fast and simply, and definitely gonna use this!
In the UK, "Asian" usually refers to India / Pakistan / Bangladesh.
That review makes it sound like an amazing phone. Chinese companies that understand product quality like this should have other handset manufacturers scared. It sounds like they're taking their design to almost Apple levels of obsession.
Yeah. You're pretty much right.

The solution is to not use OO. JavaScript is not that good at it anyways.
Perhaps design by contract is the way forwards? Explicit runtime validation of the flow of data through code at each step in the system.

As a frontend developer, I have been moving towards a greater emphasis on functional & integration testing. We're also using scripter here, a test tool that actually compares screen caps with the actual on-screen state of our applications. So a purely visual approach.

There's a wonderful world of testing tools out there. I can imagine it's incredibly daunting to a newcomer trying to decide which to pick up and run with, especially with so many job specs specifically asking for "TDD", and now with DHH saying this.
When you talk about rudeness and politeness, you're talking about manners. Manners are a social system of using shame to force conformity out of members of a given culture.

But I feel no shame for my hobby. Shame is a useless emotion.
Latest I've read is that the bootloader will be locked and phone won't be rooted out of the box. However bootloader will easily be unlockable and rooting the phone is supported and won't affect warranties.
For all the talk of abstraction by so many programmers, I wonder how many of us just really want metaphors. Ways of organizing and relating to code that are at least vaguely familiar.

But then some programmers start talking about abstract math and category theory, and many people recoil because it is too abstract, or because it is so abstract that it is more general than the most immediately obvious metaphor (Functors are kind of like boxes, but not always. You should think of them like computational contexts instead).

Of course metaphors have their place; there is no need in making things less relatable just because. But at some point you may have to abandon the comfort zone of trucks being a specialization of a more general car blueprint.
Very true - the issue is perhaps that you need to be absolutely sure of your problem domain, and absolutely confident in your engineers' ability to maintain eventual consistency (as opposed to simply inconsistency) in the face of changing requirements. More-consistent systems allow much more freedom to change the way your system works without worrying as much about the ways in which it might impact your data storage.

You don't have to go for full serializability - you can very often get away with something simpler like consistent writes and potentially out of date reads. That sort of system scales a long way unless you're very write heavy.
توقعات أمطار غزيرة على المملكة الأسبوع القادم | اخبارية الزلفي
Yeah, Mens Journal is not famous for its rigorous peer review.
OpenWRT Source Code of Linksys WRT1900AC
>http://broxxar.itch.io/flappy48

Really? I have to install a plugin just to play a simple webgame?
The hardware volume controls on tablet/phone work well for me when using the app.
Perhaps it highlights a potential problem and a market that needs to be disrupted.
What Happens to Your Brain on Sugar, Explained by Science
Yes, Google Play store.
Do Canadians self-identify as living in "America"? I would guess not. But Germans certainly self-identify as European.
The author might be confused by AngularJS, but all of the projects I have converted from simple JS to Angular have more than halved the amount of code needed, and made the applications much more easy to maintain.
Tools for Load Testing Your Website and Apps
You have to be very careful if you don't let it manage all your DOM changes, and in general everything is done via it, so it is basically a framework.

AngularJS is much better than what we had before, but it is still not great, and a bit clunky .. hopefully the lessons will be learned and in the next cycle we'll get some nicer slimline things instead (though this cycle could take a few more years to run through).
If a machine doesn't answer to the Internet, it has no need of a public IPv4 address. A machine that only answers to other machines in the same organization should be assigned an address in the 10.0.0.0/8 range. If the organization is not large, even 192.168.0.0/16 would do. In fact, many people would argue that assigning public IP addresses to intranet resources is very bad for security.

Of course, some of these machines actually might have valid justification for squatting on a public IPv4 address. Perhaps their firewalls are configured to drop all packets except those from a handful of "trusted" IP addresses, so a random scanner on the Internet gets no response.

But I doubt that such cases account for the majority of "seemingly unused" IPv4 blocks. What's more likely is that some large organization was assigned a massive block of IPs 20-30 years ago and never found much use for them. IBM owns 9/8. Xerox owns 13/8. HP owns 15/8. Apple owns 17/8. Ford owns 19/8. Several pharmaceutical and chemical companies also own an /8 each, as do some universities. Do they really need 16.7 million public IPv4 addresses? Of course not. But I wouldn't be surprised if they started to sell bits and pieces of their blocks once the price per IP goes up enough.
> internally inconsistent

You mean, "internally consistent"? As in "How much is it?" "One dollar." -> "1$". That's how the (spoken) language works.
Other than Google Play? Because it will have Google Play.
Could you expand on the peering problems?

I was thinking of switching to either A&A or fido.net this summer as they are the only ISPs in the UK that offer reasonable priced IPv6 broadband.
It's even worse. In Java the whole factory/provider approach was down to a limitation of the type system. Yes they (we) went completely overboard with it and the ridicule is deserved.

But what on earth is the justification for using that pattern in a dynamically typed language that lets you tack anything onto an existing object without controlling its creation?
I fully agree that TDD has turned into a cargo cult obsession for many developer shops. The benefits of unit tests are usually for the developer, but in over abundance can lead to inflexibility and debt when your system needs to change.
Thank you for the find for #1. I am pleased and surprised to see that my back-of-the-envelope calculation on the speed is correct. I am still gob-smacked to think of that much lead spinning a 2km/sec. I don't have the knowledge of supersonic fluid flows to be able to evaluate that. The paper itself points out various difficulties, including delamination, decavitation, jet formation with speeds up to 6km/sec, and:

> practically generating shocks mechanically at Mach numbers greater than 1.5 without destroying the machine that creates them (as is the focus of this work) seems challenging. For example, a steel piston impacting liquid lead to produce an approximately Mach 1.1 shock would see a compressive stress of approximately 2 GPa, well above the yield stress of most steels.

The paper talks about pressures up to 400 GPa. Another back-of-the-envelope calculation suggests 20 GPa of centrifugal force at the equator, which of course means the pumps need all the more force. This is well beyond a regime where I can make any mechanical estimates.

At this point I suggest that the biggest problem is the engineering to bring the lead up to speed, keeping the sphere in shape with that much force on it, generating a plasma collapse through all of that, and connecting everything to the heat exchanger. That will be a huge challenge in its own right, and must be solved before I would call it an experimental power plant.

BTW, this vortex simulation is from 2008, ... "hardly an authoritative reference" by your own criterion. ;) Indeed, I note that the simulation says 100 kg pistons impacting at 100 m/s, while this 2012 PDF http://fire.pppl.gov/FPA12_Richardson_GF.pdf says the target impact velocity is 50 m/s, which is 1/4th the total amount of energy.

Link #2 directs me to http://generalfusion.com/downloads/ICC2008_MGL.pdf, which shows that in 2008 they indeed planned on a 100 m/s impact, so parameters from 2008 are obviously no longer valid for 2014.
Are these videos working for you? I cant get them to start
An alternative look at the Zendesk IPO
Well Apple still sell the 4S. So, it's understandable.
This post is amazing. I can't stand the TDD zealots who I've worked with in the past. They act as if they aren't even programmers, they are test-framework gurus first and foremost. Product is #1 in my book. Tests are needed but these guys would cowboy around taking weeks to work on a task because they'd use the excuse 'gotta write tests...' This post is a breath of fresh air.
nice downvote. Lots of donks here DIAGF.
TDD has turned into a way for devs to 1-up other devs. When testing becomes a discipline of its own with the knowledge of these testing frameworks, something has gone wrong. Tests shouldn't need much more than assert statements, and maybe a little extra.
It's our DC not broadband connection. We have several peers in the DC but not all are IPv6 and the level of competence is "variable". We had some techs not able to understand IPv6 even from a basic level and one peer screw up our routing.

A&A rock - no complaints at all.
There's also Steve Yegge's epic rant
http://steve-yegge.blogspot.com.au/2006/03/execution-in-king...
not at the moment. but i can add it to the wishlist. thx for support!
I agree with the sentiment but, despite the proviso that we should not go anti-TDD, I still think it's too strongly worded.

If you are rapidly prototyping something then writing tests first is a hinderance. But if you have well defined requirements then writing tests first will save you time.

What's best will differ depending on whether you're designing a web app or building an interface to an SAP system or an external gateway. (My guess is that DHH does very little of the well defined interface building type stuff)
These scavenger hunts aren't merit based reserved tickets. What do they actually do? Who are the targets, and why does Google want these people to attend I/O?

The answer can't be "developers" or "to learn things." Not while the prevailing reason people attend I/O is to get the new shiny toys and the primary means for getting a ticket is a random lottery with no prerequisites for entry and no fee to prevent gaming. What we need for learning is mostly put on YouTube promptly, so presence is not necessary there, either.

I don't understand it at all.
Virgin Media Just Gave All Of Their Customers Plausible Deniability‎
>Test-first units leads to an overly complex web of intermediary objects and indirection in order to avoid doing anything that's "slow". Like hitting the database. Or file IO. Or going through the browser to test the whole system. It's given birth to some truly horrendous monstrosities of architecture.

Oh yes - I agree completely with this.

I'm not sure I agree with testing things with Capybara though. How are you sure your backend controller actions are doing what they're supposed to be doing? Sure your browser might render what you need but what if a model attribute is set to false instead of true? How do you account for that using a frontend test suite?
The Trouble With Rice
"BellKor's Pragmatic Chaos" awarded the NetFlix $1M Grand Prize on Sept 2009
For some foods, yes, perfectly.
Monads -> Computational Expressions.. mostly so that people aren’t scared away.
I've been more than happy with VIm and the vim-golang extension.
Tell me about it! The warm glow of being an early adopter...
I suppose what's really tiring is that this sort of writing is upvoted by enough people to make it hit the front page.

The magic formula is basically : "Bait title" + "personal opinion that is not necessarily backed by any real world experience and expertise".

There won't be that many good developers that actually worked on projects with a huge code base and that support the notion that DI, frameworks and so forth are "bad". The other half up-voted this post and the top comments apparently.
Linux Applications Now Run on IPad – Collaborators and Co-Authors Sought 
There is a new platform to run Linux applications on the Apple IPad. Have you noticed that many stock applications which are free on Linux require payment on the IPhone and IPad? Don’t want to re-implement Linux software on IOS ? QMole is a new desktop system allowing the free operation of software ported from the world of Linux on the IPad. The technology enables retaining a touch screen operation of stock GTK Linux applications without requiring their redesign or reimplementation. Unlike remote desktop solutions that require a network connection, QMole requires none. All “Linux” applications execute locally on iPad, just like native IOS applications.

QMole features a tiling window manager, transparency, virtual desktop support and an initial desktop application bundle combined with support for developing in Lisp, C, C++, Java, Clojure, Lua, Scheme, OCaml, Python, Perl and more.

Are you interested in collaborating on this effort? Please register your interest at the below URL.

http://chriskohlhepp.wordpress.com/qmole-bringing-the-free-world-of-linux-to-an-ipad-near-you/
Later the algorithm was not implemented: http://techblog.netflix.com/2012/04/netflix-recommendations-...
The point you make is valid, but not unique to Google or its products. People yearned for WWDC tickets (a conference about how to use Apple services and platforms) and stand in line for the privilege of getting the latest and greatest Apple product.

You might say that it's a sign of success in the tech world when your brand builds this much of a following.
Let me know how you like the results - ze@fnvlabs.com . I'd be happy to dig out my notebooks and check the times/temperatures for you, too.
You still use duck fat, but you only need a 1/5th as much.

I don't SV eggs all that often; it's easier to poach or sunny-side-up them conventionally for me. In particular, I can't fucking stand peeling eggs.
Cascaded Displays: Spatiotemporal Superresolution using Offset Pixel Layers
dhh has spent so much of his career actively leading Rails that it's tough to tell the difference between his personal evolution as a developer and general trends in the industry. I don't think he even attempts to make a distinction in this essay.

I worry about a push away from unit tests. I can't imagine having to refactor a large application with only system-level integration tests to work with, especially in a dynamically-typed language like Ruby. I haven't written a Rails app in a long time though, maybe these days it's easier to just start over than to refactor.

But any bad day for dogma is a good day for the rest of us. Write software using whatever methodology works for you and always question the value of so-called "best-practices".
Part of the problem is developers are often too hesitant to delete tests. Tests, like any code, should be deleted when their value is lower than their cost. Tests have maintenance cost like any other code. Plus they add to the time it takes to produce a build.

When making significant changes to implementation of something it's often worth just leaving acceptance tests in place for regression and deleting unit tests and TDDing your new implementation
Show HN: Torpe, a pop album cover randomly generated by JavaScript
"when we were all so freaked-out about seeming gay that we'd leave an empty seat between us at the movies."

or, you know, because horizontal leg room...
"Aw man, I need to install Java to run this applet?"

"Aw man, I need to install .NET to run this windows forms app?"

"Aw man, I need to install QT framework to run gimp?
"
Recommendations generate 38% greater click through in Google News (2012)
The research paper on it: https://research.nvidia.com/publication/cascaded-displays-sp...
Bitcoin is Here to Stay: 5 Aspects Sufficient to Fight the Crisis
I'm excited to ship units and what more creative cooks come up with, I'm boring, I only think about products these days.
The service sector generally starts between 7 and 8, and is pretty large.

I generally start working (on blogging side projects) around 7:00 but don't show up at my day job till 9:30. I'd have to be a partner/founder/MD/CxO level before I'd be OK with 7:00 meetings. Why would I give the morning hours away?

If I could get up at 5:00 without being too out-of-sync with the rest of the world, I would. It's insanely productive. I seem to be naturally creeping in the early direction by about 15 minutes per year I age.
Growing crops with desalinated water costs more for the energy to produce the water than the price of the crops grown. That's why desalinated water tends to only be used for domestic supply. The real problem is energy price.
I had to scroll down too far to find this.
Like I said, needs better OCR.
A new interactive map of Barcelona’s landmarks.
All guilt I've been feeling about not always writing tests first... Gone! Phew.

I think point of this is... TDD is still good. But it's not ALWAYS good. A great way to frame thoughts, but writing tests last isn't "wrong" either.
This is the first time I hear about Uber in Moscow, and I live there. Never seen it advertised or anything.
I think this really hits the nail on the head. When you start out with an app, you just want to say

func:
print "Hello World"

and be done with it. But when you grow, you realize that you need it to be able to print hello world in many languages so you add I18N

func:
unicodePrint(geti18N(HELLO_WORLD))

getI18n(I18N_KEY): curlang.get(I18N_KEY)

1091_en: "Hello World

and then someone accidentally broke something so you want to be able to unit test it.

func(printer=stdoutprinter):
printer.unicodePrint(geti18N(HELLO_WORLD))

getI18n(I18N_KEY): curlangmap.get(I18N_KEY)

1091_en: "Hello World

interface printer ...

singleton stdoutprinter ...

Ideally you'd want a framework that caters to all of these stages
Unnamed Russian Banks Are Using AlterGeo’s Location Data For Credit Ratings
We're expecting cleanup to be very easy; mostly a wipe-down every once in a while. But you're right of course, kitchens are messy places and we certainly took that into consideration. The grille is entirely necessary for Mellow to function.
Anistock videos
Looking after your bike properly – Part 2
It took a long long time, but they eventually started.
Pretty sure the intention here was to say that the author uses "$1" in some places and "1$" in others. I'd verify this, but I can't get to the site.
I switched to angular explicitly for the dependency injection. Registering a singleton so it can be passed in to other functions and mocked out easily in tests is something I find extremely useful.

Whether the framework should provide three different ways to register the object is another matter (a design decision along the harder-to-grok vs accommodate-variety axis) but, frankly, if you don't like factories, don't use them.
TDD is but one example of the apparently inevitable fate of good ideas in software development: it becomes the One True Way, universally applicable, and the new litmus test for distinguishing Real Developers from troglodytes. Whenever a developer gets a new tool, she is supposed to throw out the old one (there will never, of course, be more than one in the toolbox at any given time.)
Them bait titles. Make it stop.
I dislike mocks. I've never seen the point in testing code against an entirely fictional representation of the most complicated and slow part of the system, just because it happens to be more convenient. Of course it's more convenient. The only compelling reason I can see for mocks is when you've got code that hits external live-APIs that don't give you any real option for automated testing (E.G., reading from and posting to the Twitter API).

If an app is worth writing, and worth writing tests for, do it justice and test the whole shooting match. Yeah it's hard, but that just makes it all the more worth doing. Automate your tests so that they cover everything that is important, from DOM elements on a dynamically built webpage to your model (and therefore the data that gets written to your SQL database), but don't pretend that stubs are substitutes for this. If your model relies on a database, let it rely on the database during the tests too, otherwise what exactly are you testing?