skysight-inc/HackerNews huggingface dataset:
Southalltravelgroup.co.uk – Travel solution provider in UK
Southall Travel Group is the largest travel group in Southall UK. Southall Travel Group offers best travel solutions to its customers. Call on 0844 855 8150 for any travel related queries.
God damn it, I'm eating.
I do recall reading about Cleopatra and a box of bees. The only link I can find is from Gizmodo, and I won't link to that.
Checkout his homepage it's full of embellishment, so he doesn't believe in what he is saying, it's just currently the trendy thing to say and hasn't had time to redesign his homepage to fit in what he's is preaching.
The pro stuff (802s, etc.) is even longer lasting.

I had a set of Klipsch LaScala from 1960 to 1971 (since they had the "A-type" crossover) in college (in the mid/late 1990s); I don't think loudspeakers really go out of date in general. The crossovers might be worth replacing, but that's about it.
In use: 1955 answering machine called Alibiphone. Tube technology and yes "refurbished".
DAGGRE is a new way to make crowdsourced science and technology predictions
A Nintendo Super Color circa 1984.
The exchange in the comments between Bill Gasarch and the author is excellent:

BG: "When I hear idiocy like this I wonder--- does Coburn KNOW he's wrong and says it as a thing one says as a politician (like when I say 'I know you can all prove this by induction') or does he actually believe it?"

HL: "That is a good question. My guess is he knows it isn't true, but it is political populism, spouting unscientific folk nonsense to be one of the people -- when it serves his political purpose, which is in this case to pooh pooh the need for government regulation. But it is also possible he really believes it -- he sounds convincing in the video, but of course that is how politicians make a living."

In particular, "he KNOWS he's wrong and says it as a thing one says as a politician" is a phrase look forward to using in future conversations.
F.T.C. Is Said to Begin a New Inquiry on Google
I just went back - thanks for the tip. Discussion of transistor radios versus stereo, complaints about touch screens and smart phones (people call them that!?) and someone complaining about the Internet. Its like peeking though a keyhole.
Go 1.1 performance improvements, part 2
Jeremy Clarkson likes to call it a beetle.
_why are you fetishizing this guy?
Sounds like guantanamo bay

"Two days earlier she had tried to rescue Angela (not her real name), an accused witch, when she was first seized by a gang of merciless inquisitors looking for someone to blame for the recent deaths of two young men. They had stripped their quarry naked, blindfolded her, berated her with accusations and slashed her with bush knives (machetes). The “dock” for her trial was a rusty length of corrugated roofing, upon which she was displayed trussed and helpless."
Even if they take great satisfaction in stocking the right batteries and lube? Would it really be OK to have a vintage dildo cabinet over the fireplace?
Leaving Behind the Digital Keys to Financial Lives
Build it, release it, analyse it and only then decide if it needs optimising.

I often share a similar sentiment with teams I work with: Don't throw solutions at undefined problems.

That commonly applies to performance and premature optimization.

I'll agree that there needs to be some thought as to what's being built before, and while, doing so, but spending time resolving as-of-yet-undefined problems means decision making based on high levels of uncertainty.

Get something working and let problems define themselves. Often times, they do so in a way that makes them easier to fix vs. relying on the speculative solution making I mentioned above.
Is anyone building a solution to this? Why should you be trusted?
I got rid of all but two of my x86 machines which didn't have AES-NI. One is essentially unused, and the other is my current home theater box, to be replaced with the Late-2013 Mac Mini. AES-NI essentially makes Full Disk Encryption "free", and FDE is a minimum standard for any machine I'd use today.

If iOS gets biometrics, I'd probably feel the same way about it (and fixing the imaging attack is why I upgraded ASAP off the iPhone 4 and iPad 1). If Mac hardware added real trusted boot hardware, I'd probably replace all of mine at the same time, too.

So, not performance, but features.
> It would crash all clients after injecting just a single message to any node of the network. Message would also be persisted in datastore so it would recrash the client on restart.

Wouldn't that fail to propagate through the network? Crashing nodes can't forward messages to other nodes.
The quote is the axiom of minimalism (one could say "dogma" by the way it is pushed on others): decoration is WRONG.

Which seems to me awkward at the very least. Just read Feynman's lectures. He does not simply share content. He embellishes it. Or Knuth's books.

Content is not enough for human beings.

I prefer the Renaissance to modern architecture. It just feels more human.
70s: Videomaster Enterprise, Atari 2600

80s: TRS-80 model 100, Sharp pc-1211 (both work and the latter allows weeks long computing on the one charge; eat your heart out Haswell!), MSX 1 and 2 computers (around 20 of them, all working), Amiga 500, Commodore 64 and 128, few ZX Spectrums, arcade joysticks with 1,2,3 buttons, music keyboard with a special connector which fits only a cartridge on the msx, a ton of modems for the above computers (1200/75 baud)

90s: around 8 Apple Newtons, Psion 5, few SGI O2s, 10 Sparcstations, E450 and a big load of laptops/desktops

Everything is working still (if it breaks I fix it to satisfy my electronics and soldering lust). Stuff I use regularly: MSX-2 to code on (making a game, I like the keyboard better than my laptop and it's more of a challenge to write software on paper to such a standard that the machine doesn't crash upon running it, wasting a lot of time) and creating extensions (like ethernet and making it into a 'laptop'), Atari 2600, C64 (last ninja plays nicer with an arcade joystick than the sad controls on the Android emulator) and Amiga 500 (Shadow of the beast plays nicer with an arcade etcetc).
I'm a noob. from what I've read webRTC is encrypted. Is that all I need to have secure communications (video, audio chat). Or do I need something more like this. Is it only text chat?
Simple Pebble Watchface
If you have enough traction that this is a problem, you can get Ryan Dahl / Joyent / et al to help you.

Node's pretty well tested by now for heavy traffic. It's not my personal cup of tea but I imagine that the obvious bugs and performance degradations have all been squished.
In Tamil, its still called cyber.
"Build it, release it, analyse it and only then decide if it needs optimising." I think it depends from company culture.

The thing is if you don't do it right with first go you will have hard time to get it done later. What management cares if it works, it's your responsibility to make it right from the start and they probably won't give you time to make some refactoring/optimizations later, because time is money :(. Sometimes it's hard to explain consequences. I have seen this too many times.

I believe you need to find golden middle, by not trying to hack things to much or overengineering problem, though sometimes is hard to define where is this middle.
Now I'm curious when the first electrical sex toy was invented, and when the first battery (well, smallish battery, not leyden jar or big external battery) powered sex toy was developed.

http://www.vibratormuseum.com/battery/ says 1880, which is kind of terrifying.

I'd still rather have an Enigma, even a 3-rotor, or the Swiss post-WW2 enigma-alike (NEMA or Enigma-K), though.
I think the only problem I have with any of this, is the next Twitter part. If that's what you're thinking, planning around, projecting scaling issues based on, I'd argue you have already ensured failure.
Surely modern electronics exist for like, 50 years now. And progress is getting faster, not slowing down. Research for self-replicating machines is being done on many fronts now.

And those are not "machines which mold plastic shapes", these are "machines that put various materials to precise computer instructions and can be built at home for less than $1k".
I built http://emergencybinder.com/, a set of free downloadable documents that deal with this sort of situation. It doesn't address the "changing passwords" issue, but would, at least, get you a snapshot of all of your account numbers and what banks have them. Your estate's executor should be able to contact the banks, who would have some sort of protocol for liquidating those assets.

It's not a project I actively update, but if you have any suggestions for forms / papers / docs / info that it's missing, I'd be happy to add them to it.
Mozilla uses node.js for several parts of their architecture: https://hacks.mozilla.org/category/a-node-js-holiday-season/ (recommended read).

It should be stable enough for building a large scale application but maybe not easily for an app as big as Twitter (we are talking about a shit-ton of requests per second). You are not there yet though, are you? :)
1886 Columbia Standard highwheel bicycle, the ultimate hipster fixie. Yes, I ride it (though not all that often), including 100 mile rides.

For computing tech it would have to be an Apple Newton. It isn't terribly old, but I gave up using my house to curate a computing museum years ago.
If you are not handling every possible error correctly, then you might end up with errors taking down your app with no idea how they were initially caused, so your app can suffer significant downtime without you knowing where to start in terms of fixing it.

If things go wrong in python, you'll probably have an easier time identifying it and fixing it due to actual helpful stack traces.

You should be very very careful when architecting your project and make sure you understand error handing to a T.
Premature optimisation is the root of all evil. If you're building something that will be as big as Twitter, the programming language will be the least of your problems. Figuring out how to scale all of the connected system horizontally, independently, will be more important than whether you chose Node or C# or Java or Python.
Scala 2.10.2-RC1 now available
Whatever you write now would never scale to be Twitter as it is now, there's no point even considering that as you aren't thinking on anything like that scale conceptually. I doubt most developers can. But then writing something that could scale to Twitter scale when you don't have a business or users or revenue would be pointless.

Specifically to answer you question, no. Node could work as a thin publishing veneer on a much larger stack but you just don't get what you need from Node.js end-to-end.
It depends where the issue is exactly triggered in code. If it's possible to get data persisted which crashes system on recall, then it's possible. BM also uses pickle on 'non-secure' data, which could allow much wider exploits with lower level attack code.
Why'd anyone want to build something like Twitter again?
Yahoo! is showing us what a new media company is.
I'm not sure how you're defining 'stable' here, but I'll comment on another aspect of your concern.

Twitter started with Rails, and at some point decided it was more efficient to do an incremental rewrite on the JVM.

I can rewrite the entire backend in a weekend in Python.

I'd bet it took Twitter a bit longer to replace their infrastructure, and they survived just fine.

Build in whatever is rapid, for you. At this very moment. Using your resources.

Keep things service-oriented, decoupled. It'll be easy to replace things one component at a time, if needed.

in summary..

I think it's a perfectly cromulent platform to build on in terms of speed and scalability. But, in case you and I are wrong, follow my advice about staying decoupled and it won't hurt as much.
whether regulation of procreative behavior of people is our business at all

That's the question of whether genetic screening should be made mandatory in some cases... I don't think so, for the reasons you mentioned.

But I'm more interested in the other question, regarding voluntary screening of sperm/ovum/embryos... I wonder how big this will become in our lifetime, and how people will react to it.
I think that most people that have lots of experience using Node would say that it is stable enough for the most part (that's what I tend to read anyway, big grain of salt with that). Cross-platform compatibility is much, much better than it was in the distant past. It will be the idea and not the technology you choose that will determine whether or not it becomes the 'next Twitter', as long as it is developed soundly. It shouldn't really matter. If you did end up scaling up before the final kinks are worked out of Node.JS and commonly used libraries, then like you say: Just write it in Python over the weekend and see if you can do better.
I believe I read it here when the google plus real name policy was debated.

Here's an old article mentionning this fake name trend: http://www.guardian.co.uk/society/2011/oct/02/facebook-child...

I am not a teen anymore but I find this surprising because IRC, MSN was all the rage when I was younger and nickname was really the norm. Just like those _xx_daemon_xx_@hotmail.com addresses.

I am a supporter of half-anonymous practices and I am surprised it's not more widespread than I believed.

Update:
And from http://www.pewinternet.org/Reports/2013/Teens-Social-Media-A... I can see fake names seem to be marginal, with people managing at least one real/official account.
That's true. but I believe the website could be useful if you know what it is....

a lesson we can learn from its failure...
I can't really speak for twitter but we use node.js happily at Soundkeep. It works greate for our use case of streaming audio processing. It has come a long way since it started. Obviously it isn't as mature at Ruby/RoR or Python/Django but not nearly as bloated either. The comparison is weak though since it isn't a framework but more of an environment. A lot of people like to think of it in comparison to the big frameworks though. Node.js is more about smaller libs and modules than any single framework.
I don't really see what BitMessage provides over TorChat for example, other than being able to deliver messgages when the sender is offline. It's a much easier protocol, and much less that can go wrong.
Twitter was built on Rails when Rails was much younger and less stable. I think you'll be fine with Node.
I start to wonder why everyone's heard of Tumblr but not Jux. Marketing problem?
I'm using Python, which has had sqlite as a standard module since Python 2.5. Therefore, I don't need to install any third-party module.

NoSQL provides command-line programs. sqlite is embedded in the same process. Error reporting across exec boundaries is much more complicated.

NoSQL requires standard unix command-line programs, and for at least one case "This program has only been tested with GNU sort" This makes portability to other OSes, specifically MS Windows but perhaps also OpenBSD, harder.

Hence there's no "simple" about using NoSQL for my use case.
Let me try again.

You make FOO.
You also make XXX, which runs on FOO. XXX is very popular.

I make BAR. BAR is very popular, but can't run XXX.

BAR and FOO are competing products.

You say, "FOO is better than BAR because BAR doesn't have XXX."

You don't make a version of XXX that works on BAR.

You can't use the fact that you don't make Office for iOS as a short coming of iOS in advertising. That doesn't make your product better, it just means that you aren't making Office available.

Any clearer now?
As long as policeman and soldiers are humans, especially from the same country as you, there's the hope of appealing to their humanity to stop them from committing atrocities. Unmanned drones or robot soldiers are much scarier.
AirBNB does a lot of node.

Much of their stack is node.

Like others have said, 'too many users' is a first world problem that many would like to have.
Node could work as a thin publishing veneer on a much larger stack but you just don't get what you need from Node.js end-to-end.

I'd be interested in you expanding on that claim. I'm indifferent towards node, but this is my area of concern. I don't see anything inherent to node/v8/js that would be limiting.
So many investigations on companies like Apple and Google. I guess they are not "too big to trial", like the banks.
btilly gives a starting point for a derivation, which is great. Here are two other ideas, working from the other direction. Notice that the Gaussian is closed under rescaling, that is, if the variables X1...Xn are all iid Gaussian, then the properly normalized sum is N(0,1). In this sense, the Gaussian is an attractor of the normalized transform. Another worthwhile experiment is to generate 6 or 10 iid uniform variates, and notice how close the normalized sum is to Gaussian. It converges rather fast. You can do this by Monte Carlo, or symbolically using Mathematica.
Yes. Voxer uses it at scale, they are doing realtime voice over HTTP

Also lots of other important companies use it behind the scenes.
We've built the control plane to Rackspace Cloud Monitoring in Node.js, and overall the experience has been positive.

A few things to look out for:

1. Error handling. In node you can't just wrap your code in a try/catch. And even if you register a listener for uncaught exceptions, you almost certainly have state shared between requests (for example, a database connection pool), which makes trying to handle such exceptions risky. To use node effectively, you need to be very careful to prevent exceptions from being thrown in unexpected locations.

2. Code rot. It is a lot less obvious what is idiomatic in Javascript as compared to Python, etc. Its easy to end up with a wide range of styles and patterns, which make maintenance difficult.

3. Missed or double callbacks. These are interesting mostly because they are not something you would see in synchronous code, and they can be quite difficult to troubleshoot (especially double callbacks).

Mitigating these issues is as much a cultural challenge as it is technical. Lint everything, review code aggressively, and don't merge code that doesn't have tests. Choose libraries carefully (the ecosystem has come a _long_ way in the last few years).

All of that being said, these are things you should be doing anyway. Develop a good tech culture, but get your product out and grow your user base. If you become the next Twitter you'll have the resources to undo any mistakes you make now.
I run http://jsonip.com. It's a single node process running on a VPS. It supports more than 10 million requests a day and barely stresses the system. Granted that its a relatively simple app, but it's raw node.js. I can easily scale it in a few simple ways like adding a caching layer and/or load balance a few extra servers. Haven't needed to yet.
DropBox client defected and lost my files
i think email. I don't know why people provide their personal details on login panel of different site(giving ur FB is like that for me) but i will never do that.
Perhaps. Don't you get music playing in your head?
Or AAAA records.
What's with that headline. The real story seems to be that they are out of control of their environment. It's been heavily invaded by modern society, which is extracting natural resources. As people are harmed by modernity, they can't figure out the reasons.

There are people in the US like this, too. Look at the lunatics in the Westboro Baptist Church.

Or the Tea Party for that matter.
They seem to be targeting growing businesses that are consistent with their "global media company" ambitions. Why do you think it is insane?
This sounds like a Maserati problem http://www.urbandictionary.com/define.php?term=Maserati%20Pr.... To answer your question though, many big companies now use Node.js and it is stable enough.
The Framework Cycle (On JS frameworks versus modular approaches)
Recordium is on US App-store now (free for 1 week)
Have you tried a Promises implementation like deferred https://github.com/medikoo/deferred to manage callback spaghetti?
Show HN: A CRM built on Google Drive
The client UI is very nice and straightforward. But it's borderline unusable on old laptop (on my trusty 1000he atom n270) because of the raw power needed to compute and send messages.
Thanks! In fact, I knew that Rackspace uses Node and thus am incredibly happy that I got an answer from you folks.
Any particular architecture you guys followed in building your app?

I'm doing as many things right as possible, but I would rather take as much advice as I can get than being sorry later. Node, like Python, isn't really forgiving.
The $6,600 Master's Degree.
Creationism also has little place in church. Most denominations of Christianity reject the literal story of Genesis, and do accept evolution. They're just a little quiet about it because there are masses of people out there who do believe in creationism. The main reason why they do is because they think a literal interpretation of the Bible is a sign of strong faith.

That's just how many people are: doctrinaire. At least on a handful of controversial issues. (They aren't so uptight about impractical things.)

At the same time, the religions must adapt to reality. They need to be practical.

Indeed, the only way that the Catholics in PNG managed to do that peace rosary thing was basically by rejecting the old doctrines that, among other things, led to Catholic enslaving or killing "savages" and others who didn't believe in their God.
Exactly. Your biggest challenge today is getting some users. Build a product that allows you to do that, and then worry about whether it scales.
I didn't. That's fantastic - exactly what I needed; added it and gone back down to 2 dynos.
Why not use gevent or Tornado? Wouldn't that eliminate all your real time concerns when it comes to Python?
Yes, it is stable enough. BUT, that assumes you know how to write code that will work under various conditions that can and do arise.

The main thing that can cause shit to hit the fan is not properly handling errors. I highly suggest using domains, and that when an error occurs, if you can, that you gracefully exit. If not, then all other requests will just abort and that isn't very user friendly.

You will also want a way to be notified of errors, so you can stay on top of them and fix them right away. I use winston and have the error level set to email me.

If you want to talk in more detail, contact me... address is on my profile.
The same practices apply everywhere, not just for any one particular stack.

On a side note, if you've already written your entire backend, I'd recommend user testing, then releasing your product (so that you actually have a chance of becoming the `twitter' you so desire) instead of focusing on your particular (seemingly already-decided-upon) tech stack.
How does an incoherent paranoid extremist rant make it to the top of this thread?
Sure. So is PHP. Yes I'm making a somewhat sarcastic point. Yes, I'm also quite serious.
Indeed. It's about knowing what tools are best to use when. My comment was more about how some (albeit not all) of the concepts of functional programming can help tackle the first few stages of larger projects and can often help to lower the chances of spaghetti code.
I'm not sure this would work; the phone will introduce a delay in the feedback, and this can be bad, and also, the sensors need to be placed in fixed positions for the best response (the gyro is usually placed right in the center).

Also, petrol/nitro engines are not the best for this kind of job, as it needs a very fast response in rotation speed and fuel engines have a high latency. What you can do is use a fuel engine as an electrical power generator or use variable-pitch propellers to get a faster response.
Products I Wish Existed: The open web (part 3/3)