jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
My wife, Arlene, was ill with tuberculosis--very ill indeed. It looked as if something might happen at any minute, so I arranged ahead of time with a friend of mine in the dormitory to borrow his car in an emergency so I could get to Albuquerque quickly. His name was Klaus Fuchs. He was
the spy, and he used his automobile to take the atomic secrets away from Los Alamos down to Santa Fe. But nobody knew that.

The emergency arrived. I borrowed Fuchs's car and picked up a couple of hitchhikers, in case something happened with the car on the way to Albuquerque. Sure enough, just as we were driving into Santa Fe, we got a flat tire. The two guys helped me change the tire, and just as we were leaving Santa Fe, another tire went flat. We pushed the car into a nearby gas station.

The gas station guy was repairing somebody else's car, and it was going to take a while before he could help us. I didn't even think to say anything, but the two hitchhikers went over to the gas station man and told him the situation. Soon we had a new tire (but no spare--tires were hard to
get during the war). About thirty miles outside Albuquerque a third tire went flat, so I left the car on the road and we hitchhiked the rest of the way. I phoned a garage
to go out and get the car while I went to the hospital to see my wife.

Arlene died a few hours after I got there.
Yeah, I've heard of using GA to find good weights for an ANN.

GAs are general optimisation techniques, but 'evolutionary computing' is very closely linked to AI and ML.
Clearly, it's like not having access to HN...

Edit: oh, there they are :-)
Maybe that's what's happening right now :-)

If I would build something like this, I'd go for an interpreter with a stack you manage yourself to handle infinite loops... using a timeout, not by solving the halting problem, random smartass!. But I over-engineer everything so don't trust me on that.

They probably use a timeout on the process too. Actually I would think using "dangerous" (i.e. filesystem) code is the real danger they'd have to defend against.
Stories about Mac App Store rejections are even less interesting than stories about iPhone rejections, because unlike the iOS platform, you can trivially distribute unvetted programs yourself.

That doesn't make this a bad blog post, but, if we can possibly head off a day-long argument over the merits of app store approval processes, that'd be neat.
The job is more stable and there is less pressure to perform. You'll never be outsourced, and you'll never be passed over for promotion in favor of Raju or Yun. If the project doesn't move quickly enough, your dept will just get more money.

The government is a great place for mediocre people to work.
I work at a company where most people are in open areas. The key that makes this work IMHO is that the desks are trivially movable; just unplug two wires and wheel the desk elsewhere. Want to work next to Joe? Move there. Need to get away from a noisy cow-orker? Move his desk, or yours (both have happened).

There is closed office space available, if you want it. Most people choose not to use it.

Once you have mobility, you get to choose who you work with. You can get together in ad-hoc groups for a while, bring more people in as necessary, and leave for some other place when you need to. It sounds too simple and maybe too stupid to be as powerful as it actually is.

I've also worked in open plans where you don't have a choice of where to sit. It sucked hard. I wouldn't do that again.
How many projects are only a couple of hours in length? I started down this road, and ended up with a list of "learning experiences"; nothing that I'd inflict upon anyone else.

I guess I'd add "... but don't release it". If it's just to build up a portfolio, you can usually make the source code available and maybe a demo.

I do like the idea of "programmer portfolios", however.
With regards to the 'connections to the OS', I was attempting to paraphrase this chunk from the official site:

"Node's goal is to provide an easy way to build scalable network programs. In the "hello world" web server example above, many client connections can be handled concurrently. Node tells the operating system (through epoll, kqueue, /dev/poll, or select) that it should be notified when a new connection is made, and then it goes to sleep. If someone new connects, then it executes the callback. Each connection is only a small heap allocation.

This is in contrast to today's more common concurrency model where OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. See: this and this."
It's not just about scalable UI. The Android concept is of fragments. Quoting from the allthingsd interview of Rubin -

"[Fragments] allow apps to split their functionality on varying devices. In other words, the Gmail app on an Android phone will load your inbox on one page, then slide to a new screen to display an email. On an Android tablet, that very same app will display completely differently, loading the inbox in a left-hand pane and using most of the screen real estate for emails. Rubin stressed that Android engineers have thought hard about making sure apps are backwards compatible with phones but still run well on tablets. Rubin started to talk about how fragments will work on Google TV before switching topics--we’re guessing he was simply going to specify that some apps will fragment to take advantage of the TV platform as well."
This is the best hypothetical spam-stopping mechanism I've seen: http://xkcd.com/810/

Unfortunately the implementation may prove a little tricky, although HN actually approaches it in some ways.
At all times, he said, the police must disclose if a camera is present if someone under questioning asks questions about it

If the camera is hidden, the person under questioning might not think to ask about it. One scenario comes to mind where police could secretly record an interrogation and get around the disclosure requirement. They could have a hidden camera and a visible one. You disclose to the person under questioning that this interview is being videotaped and make it obvious that you are pressing record on the camera on the tripod. Then, a few minutes later, tell the suspect that you want to help them out, and say: "Look, I'm going to turn this camera off if it makes you nervous" but keep the hidden camera on. Technically the police would be in the clear because they disclosed that the interview was being videotaped (though not the number of cameras), and the officer only promised to "turn this camera off" and not any others.
I agreed with John Tierney's bet when I read about it at the time but for different reasons. I believed that cheap money was bidding up the prices of oil and other commodities. I believe this is true again now that China and India have huge levels of credit expansion.

Eventually these bubbles will burst and we'll see a correction again. Assuming that the Federal Reserve doesn't do its' part to keep it going.
Yeah you REALLY didn't look very hard then.
Would you click on a link that said "There are many ways in which open offices are not great."?
Can you do the mockups? (see: http://www.gomockingbird.com)

If so, why not try getting one or two screen done at a crowd-sourced place like http://www.99designs.com or http://www.crowdspring.com
- low battery warning -

sound of car crashing
I wonder if it varies by field? The abstract indicates that most entrepreneurs are 35+ in that study ("The 20-34 age bracket has the lowest rate of entrepreneurial activity"), but all the major tech companies I can think of, at least American ones of the past few decades, were by people under 35: Microsoft, Apple, Google, Facebook, eBay, and Dell were all twentysomethings; Nvidia, Oracle, PayPal, and Cisco were early 30s; and I have to go back to AMD (founded 1969) to find a 40-year-old cofounder.

I could be totally missing some, but I did just look down a list of biggest American tech companies to see if I could find anything.
For a different perspective on this, check out "The Grass is Indeed Greener: How I gave up dreaming about the big city and learned to love the suburbs". http://architectureandmorality.blogspot.com/2010/10/grass-is...
I apologize in advance if this post is rambling.
The problem is that the "utility" of suburban sprawl is in no small part due to the historical price of energy.

If and when energy prices go higher (and there are good reasons to believe they will) I think we'll see a necessary shift.

Aside #1: I think of "walkable neighborhoods" as an interesting counterpoint to "sprawl." The health benefits of living in walkable neighborhoods are well established. Aside from health, the folks at walkscore.com recently highlighted research that suggests home values retain better in walkable neighborhoods: http://blog.walkscore.com/2009/08/new-study-shows-one-point-...

Aside #2: Kunstler often makes entertaining points about the aesthetic of sprawl, be he's also a bit of an overwrought doomsayer -- I take his work with several grains of salt.
LCD windshields seem like something that would be regulated to oblivion (what happens if a bug, unlucky particle strike, vulnerability, etc.) causes your entire windshield to become opaque?) That said, in a world tolerant of reasonable amounts of risk I agree.
What feels so strange is that the price of gas matters so much,

Sure a commute 40 miles each way will increase in cost from $5.33 to $13.33. But $8 seems hardly a concern when you are wasting 1.5 hours a day driving.

Cheap energy is certainly necessary to create sprawl, but it isn't the only thing. Rather urban areas are often downtrodden in the US. Take a look at San Francisco, a pretty nice place by big city standards; compared to its suburbs, it has worse transportation infrastructure, worse schools, more congestion, more noise, more expensive, more danger, more pollution. The benefits win out in my 20s, but I sure wouldn't want to raise a family there.
Yeah, I get that. Reading it back it's a little fought to discern, but my intent was in fact to convey that all design considerations of the button and the logo was in PayPal's hands.

Congrats on the bundle by the way. It's great product!
Taxpayers should take the brunt of the damage in the end. They hire the police after all.
It really was such a brilliant move on Netflix's part.
You're pulling "statistics" out of your ass and being kinda racist. Don't do that.
Would be cool to add in other startup stats at some point! Could potentially use http://mattermark.com/.
I'd like to think that the Chinese government would be more targeted about what they infiltrated in this way, unlike the NSA. Would I be the least bit surprised if it was revealed that both Chinese and Russian state sponsored teams have hacked large swaths of the routing and SCADA control tiers in the US? Honestly, it wouldn't surprise me at all as it is in their best interests. This is the world we live in sadly.

The one upside of this is that as technologists, this gives us the ammo we need to really work on crypto and proactive security from the beginning. Things that were previously thought of as tin-foil paranoia, such as ssl communications from data center to data center on leased fiber lines, are now par for the course after it was shown that Google traffic was being intercepted at crossing points. As a US citizen, I almost see it as a duty to work on proactively securing things where possible, not just to prevent my own government, but potentially less friendly governments or organizations from snooping.
Google/Facebook both minted several thousand millionaires at IPO. The vast majority weren't CXAnything.

I don't know whether the article is about income or wealth, but if one puts "big money" at, say, $250k of gross income, then it's clearly achievable in software. Options include a) get a job at AppAmaGooBookSoft and stay in it for 5~10 years or b) hang out your shingle as an independent consultant and charge $8k+ per week at 75% utilization.
...so did you read the privacy policy?
Or at least keep them in tact...
I believe what you're saying is "this time is different."

No, it isn't.[1]

In the ascent phase of the bubble, everyone but uber-bulls is proven wrong. But what matters is whether what is happening today in terms of valuations and capital raising/spending is sustainable. I believe it isn't. AirBnB or Uber or what have you may be a great business, but a great business can be a lousy investment at the wrong price.

So you may continue be right, in the sense that share prices may keep going up, but that doesn't mean investors participating at these levels--or at the quadruple levels you forecast that may indeed come to pass--are being rational.

What's happening now doesn't have to be exactly like it was in 1999, just like what happened in 1999 wasn't exactly like the Nifty Fifty stock bubble of the late 1960s.

PS I had a front-row seat in 1999, as I worked for a well-known VC firm on Sand Hill (still there, still well-known).

[1] http://papers.ssrn.com/sol3/papers.cfm?abstract_id=240371
> If you want to tweak your car, you need to do a lot of stupid busywork with your wrench before you get to anything interesting.

Sounds plenty analogous to the many parts of the compiler or interpreter toolchains in place in modern OSes.
I'd say the mapping is good enough. PUT updates a current object, which can be done again. POST creates a new object which can't be repeated without producing another article. CouchDB has automatic versioning which is mostly transparent to most operations. (on a single instance)
The combinations are found by finding linearly dependent rows of a sodding enormous matrix modulo 2. This can be done using elementary linear algebra, but you need humungous amounts of memory.

Err... no, not really. In addition to taking O(n^2) storage, a dense solve will take O(n^3) time, which is quite infeasible for typical matrix sizes.

Instead, we use a sparse solve, such as the block Lanczos algorithm, which takes O(nw) storage and O(n^2w) time, where w is the average row weight.
I'm impressed that MetroNaps has discovered the optimal napping position.

I think I would be more comfortable sleeping in a wierdo pod if there weren't people walking buy taking pictures of my limp limbs.
Thanks for this. I just pulled down the molokai theme and it is very pleasant.
Hotels might love this. I remember seeing something similar, with an N64 hotel console a while back.
Good advice thanks for the reply
> I think something like Alfred Hitchcock Presents is very watchable today and I often do. You get a little mystery and murder and all within an hour. There were other watchable programs, like Perry Mason or something.

Those tend to be pretty good, I agree. I watch them on Me TV sometimes. (Digital subchannels are what UHF and cable were Back In The Day: Cheap timeslots filled with whatever someone has to hand.) However, they're good writing one episode at a time. These days, you get good writing a season at a time; it allows more characterization, more complex plots, and more flavor. Breaking Bad is a novel-length plot, something TV only did in soap opera form back then. And soap operas have never been accused of having good writing.
Great for you. I happen to have spent my life talking to people using messaging apps instead of email, including business contacts and family. If you think your email is somehow valuable and my instant messaging logs aren't, that feels quite a bit insulting.
> USD [...] is a perfect currency for exchange, it's just not a great store of value.

USD is a fantastic store of value. Since 1982 (arguably the beginning of the modern inflation-targeting era), the USD has lost no more than 6.3% of its value year-over-year, nor gained more than 2% (CPI measured, source https://fred.stlouisfed.org/series/CPIAUCSL#0).

In contrast since 2016, Bitcoin has 60% of its value year-over-year (2018) and gained 1700% (also 2018).

A store of value is not a story of appreciation and hoping for a gain, it's a story about holding a stable and most importantly predictable value into the future. The USD more than satisfies this condition. Bitcoin does not, no matter its speculative merits.

Most importantly, society does not owe people a fictional store of value guaranteed to never lose purchasing power. People don't eat quarters, nor do they live under dollar bills. It strains credulity that a nominal token (however minted) should hold a guaranteed value, without taking capital-like risks required of any productive investment.
> That Splitwise entry isn't a bank transaction until maybe weeks later when I get a Venmo payment from a roommate covering several Splitwise requests, and for my budget I want to match up the $100 charge at the grocery store with the $50 Splitwise request with the $250 Venmo payment that was only partially for the $50 owed on groceries... not an easy problem to solve in a general way that makes lots of users happy.

When you spend $100 at the grocery store you make an entry with $100 subtracted from assets:bank, $50 added to expenses:groceries, and $50 added to assets:receivables.

Once your friend pays you $250 for your outlay, you add them to assets:bank and subtract them from assets:receivables.

It’s a little tedious in a spreadsheet, because each transaction results in at least two new rows, so it can feel redundant, but this is basically double entry accounting that can handle this and many other situations.
Under 49Hz they start disconnecting consumers. If that does not stabilize the dropping, under 47.5 Hz they disconnect the power plants and the network fails. [1]

[1] https://www.netzfrequenzmessung.de/abschaltung.htm
All of Europe's national grids are interconnected, and most of them import or export more than 10% of their power budget (some both, depending on the time of day). A large power fluctuation/blackout in one country can easily spread to neighbouring countries, the junctions can't absorb the sudden shift in network load.
It's a backup which demands that you WRITE down a very long numeric code, then manually copy files off and then hope your family doesn't lose all of it.

It's a horrible user hostile process which isn't even implemented for iOS.
In terms of statistical preference, I'm not sure there's a actually huge difference. Some people like blue steaks, others like well done, most people are in between.

I think people who like rare steaks just talk about it more because it's the "right" way to prepare the "best" cuts. A $200 steak is just going to be most flavorful when it's on the rarer side. But its just a signaling thing if you're talking about skirt or flank.

Same question could be asked "why does everyone all the sudden love whiskey neat so much?" - they don't, its just that the whiskey folk talk about it conspicuously.
I haven't tried React without JSX, but I do find that switching over to the functional style interface I'm writing a lot less JSX. It's still there, and it's still the natural way to write the base-level components (divs and spans).

But at the next level up, it becomes really clear that <Foo x={1}/> is just syntactic sugar for Foo({x:1}), since Foo is just a function.

A lot of my code starts life as some chunk of a complicated render that gets refactored into a function. Then that function quickly becomes a React function component.

Next clean-sheet project I may try react without JSX. But I still rely heavily on newer ES features, so there may still be a cross-compile stage of the setup. While create-react-app is depressingly heavyweight, it is really fast and new JSX projects go up in a minute.
The worst part of it is people who imagine robots hunting you would be for some reason 'worse' than horrific humans militia such as SS have done in the past.

Any atrocity has been done by humankind already.. we didn't wait for robots.
I’ve said this many times. Also the UI is buggy and many things you expect to work don’t (like dragging a link or a word to the tab bar to open a new tab). It’s such a shame because other browsers such as edgium and brave are faring much better
Yeah, readability is far more important than elegance in the long run.
Not sure on this but a few parts of this case are out of the ordinary like the jury asking questions during the case.
This text remembers me of some techniques used on qmail, which has a great security record.
Look up the press conference by Cuomo.
That's an excellent solution. A couple of points:

1. It is usually not a good idea to use your key as a function of the message. Here, you would require your hash function to have a good min-entropy given inputs from whatever distribution M comes from. I believe SHA-256, as of today, will satisfy these needs.

2. Even if H is modeled as a perfect hash function (i.e., a random oracle, in crypto literature) you would require that AES itself does not use H in any particular special way. Think of AES' which is just like AES except when k=h(m) for any message, it just outputs k (i.e., cheats). It would be nearly impossible to detect this behaviour of AES' under normal circumstances because H is pre-image resistant, but clearly, this would trivially void the security of the scheme.

The suggestion is exactly what came to my mind, but the proof, although should most definitely hold when instantiated with AES and SHA-256 will require some work to be proven in general.
I love your product but your encryption is pretty useless and y'all must know it.

It only protects my data if your S3 account is compromised. There is a much greater chance that your web frontend, servers or client are compromised (either by an external or internal attacker) and then my files are easily accessed and decrypted.

It is like naive programmers who store user passwords with 'government level encryption' instead of correctly salting and hashing them, thus having to put encryption key in the source code

select AES_ENCRYPT("user password", "our secret key");

Saying your CEO can't access it, is just more security theater.
function decrypt(cipertext, key) {
var req = new XMLHttpRequest();
req.open("POST", "/retrieve_user_key?key="+key);
req.send();

// decryption routines
return result;
}

Do you trust Dropbox to not send compromised JavaScript every time? If so, why not trust them with your keys in the first place?

Of course you also need to trust the desktop Dropbox client. The only (approximately) truly secure way to do this is with an open source client you can inspect and compile yourself (i.e. tarsnap).
Of course. I do it every chance I get.
Isn't one of the major cool things about dropbox that if your computer hard drive gets smashed (and thus the key is destroyed), you can still access your files somewhere else?
Which of these things is a benefit of make?
Yep. Author is romanticizing the "democratic" web of the time before facilitating companies simplified the process of getting and being online. The reality I remember is that it wasn't a democracy; it was a technocracy and the barrier to entry was high. It still is; hosting one's own full-fledged web server that is secure and reliable has only grown in complexity in the past decade, improvements like Docker notwithstanding, and it's no wonder average users have flocked to Facebook, Google, and Amazon for simplicity of access.

To take Facebook as example, people seem to often forget that the primary feature Facebook offers the average user is simple low-cost blogging of small thoughts and reliable auto-aggregation of those blogs. No fussing about with running one's own RSS feed or managing RSS subscriptions.

If the "web is dying," it's dying like a wooly mammoth---ill-suited to a changing climate. The mentioned companies created an ecosystem where the fundamentals of communication, location, and commerce can be accomplished without the technology getting in the way. It's no surprise users flock to them.
Maybe you want to functionally validate your task in the SW environment that you can take with you.