jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
Depends on the discipline though. Hacking will never be communicated accurately to non-hackers in the same way that jazz will never sound right to the non-musician.

I do agree that good communicators manage to somehow frame their thoughts in a way that encourages other people to think a little further, and realise some truth that was staring them in the face.

After all, peotry is about making new things familar and familar things new.

It's unfortunate that great communication is largely unscalable (and hence the reason why YC exists).
Someone should build a "tablet", which is just a large touchscreen (and a battery) that you plug your Android phone into.

No need to duplicate all the 3G and Wireless hardware. No need to have two dataplans or worry about tethering. All your contacts and bookmarks and browser history is shared.

I just remembered Palm did something like this called the Foleo except it turned the portable device into a netbook type thing. I seem to recall it was either a flop or never released, but I still think it's a good idea.
>(biggest tech company..

Good grief. I assume you must be talking about Market Cap and that just happened. If you look at how much money they make they are still dwarfed by MS and probably IBM, etc. as well.

You were complaining about spin?
Using a worse (ahem sorry, "dis-preferable") language isn't like playing an easier part. You're still expected to solve the same problems, just in a different way. It's more like trying to wheeze out the same piece on a beat-up second-hand excuse for a trombone.
"TechCrunch suspects, probably correctly, that apps for Google Voice are being rejected at least in part through AT&T's influence, since Google Voice lets you send free text messages and delivers cut-rate international calls on top of making phone numbers even more meaningless making it scary to AT&T in way like Skype VoIP over 3G." [1]

If you're trying to bypass the phone company that is using the phone as a loss leader of course you can expect that app to be rejected. Skype is approved though, afaik. Is that your only example?

[1] http://gizmodo.com/5324268/apple-rejects-official-google-voi...
Assuming we're not talking about the extra-wide sidewalks common in city centers which sometimes also host designated bike lanes, ordinary sidewalks that I've seen throughout the US and Europe are nowhere near wide enough to fit even a single cyclist passing alongside a pedestrian without a risk of collision. Add multiple pedestrians walking alongside each other, other hazards such as parked cars, less competent cyclists such as children, or pets (on or off leashes) and it quickly becomes a recipe for disaster for one or both of the sidewalk users.

Also, bicyclists in cities tend to travel closer to the speeds of cars than pedestrians, and tend to have more similar dynamics such as turning radius and stopping distance which infrastructure for cars is already designed around. Additionally, car drivers are licensed and there is an expectation of awareness that they must exhibit. This makes it far easier to place slower-moving "hazards" in their path than adding faster-moving vehicles in the path of pedestrians.
In the cities we do invest in that too. Also cycling is superior (faster, cheaper, more convenient) to public transport for short enough trips.

Also public transport and cycling are not opposites of each other. Here in Helsinki a lot of people cycle to the train or metro station and then take that to the city for their commute. You can also take your bike into the train or metro here if that works better for you.

People also drive their cars to the metro/train station and do the same. Parking can be really expensive (and hard to find) in the center if you happen to work there. For example my work place (a bit over 100 person IT company office) we have a total of 2 car parking spots for the whole company that you reserve in a google sheet when you need it.
The most dangerous part of a sidewalk for a cyclist are places where they intersect roads. Drivers just aren't expecting sidewalk users moving at bike speeds.

Some areas have long stretches of sidewalk without intersections those are fine for cycling assuming they have little pedestrian traffic or are wide enough to pass safely.
For a normal NASA flight

"NASA told Business Insider it estimates there’s a 1-in-276 chance the flight could be fatal and a 1-in-60 chance that some problem would cause the mission to fail (but not kill the crew)"

That's fairly low - feels like the age of sail would be far higher -- Columbus's second voyage alone had about 25 deaths just from scurvy. His first voyage was only about 90 crew.

But remember that life wasn't exactly easy on land either.
Nevermind, answered my own question.
Talking about memory, this is the kind of articles that I love to read http://sites.utexas.edu/jdm4372/2010/11/11/optimizing-amd-op...

Trying to get the most out of the machine/arch you have.
Downvoting isn't violence. If you feel so hurt by the loss of imaginary Internet points, you need to sit down and seriously think about what has gone so badly in your life to bring you to this point, and how you're going to fix it.
http://www.usatoday.com/story/news/world/2014/09/07/newser-g...

> Indeed, eating 29 pounds' worth of the radioactive creatures would result in radioactivity exposure equivalent to that of a transatlantic plane ride.

I think you guys'll be OK...
Looks like they may not be. In this article today, some people think the new Mac Pro's issues are thermal related:

http://appleinsider.com/articles/14/12/30/apples-latest-mac-...
For 5.4, recently, yes, since 5.4 is "security only" mode since 3 month ago. For others, not necessarily, since there are a lot of fixes and improvements. Look at CVEs in the changelogs[1], while understanding that CVEs sometimes are assigned for issues like "if you could run arbitrary PHP code, then you could run any code" which IMO is always the case since PHP is not a security sandbox. But if you do not have enough in-depth knowledge to assess CVEs, just CVE presence should be a good upper bound. Note also some security issues are in the modules that may not be even used by the particular server (fileinfo and EXIF modules provided a bunch of CVEs recently but not everybody uses them) or may not be used in a way that is exploitable (so, unserialize() CVEs are only an issue if you unserialize user-controlled data, which is not a best practice). This is not to say those are not security issue, but running PHP version with a CVE would not always make your server exploitable. That said, you should upgrade anyway.

[1] http://php.net/ChangeLog-5.php
That shouldn't happen. Would you be so kind as to tell me your OSX version and Mac/MacBook model? I probably won't be able to spot and fix the bug right away (it's new years tomorrow, after all) but on the long term I of course want to squash this kind of bug.
Calling everything beautiful diminishes the value of the word. And most apps posted to HN are described as beautiful. It's mostly just become filler text now. Worse, this judgment isn't coming from an impartial critic, but usually the author himself/herself. Maybe it's a cultural thing, but not telling others how to judge your product was drilled into me.

Also, being beautiful isn't an inherently valuable attribute. If your product is utterly useless, but good looking, then it's still utterly useless. Some form of user study about the utility of the aesthetic design would be a nice addition in these sorts of declarations.

I don't think the issue is with this project per se, but the trend in the presentation of these sorts of "show HN" posts.
Wait til Keith discovers Go passes arguments on the stack, totally ignoring SPARC's register windows.
I guess it is not detecting my USB turtle beach headset. It says 'off' in the icon.
Reminds me of Parallels Plesk and their horrible ui
Yep, a good search term is "galvanic vestibular stimulation". Here's a good how-to: http://jap.physiology.org/content/96/6/2301
Hot-linking has a very real and ongoing cost associated with it.
You can't discount that most companies fail though, you'd expect the majority of options to go unexercised.

Edited to expand a bit:

Shares are ugly and annoying and cap tables are broken but it so rarely matters. Things should obviously be better and cleaner and more organized but since so few companies return anything to anyone besides the preferred shareholders, I'm not sure the 'cost' of this disorganization is very high. Seems like another case similar to the uncovered call option description of 'technical debt'. By avoiding the time and effort of energy associated with cap table management, companies can focus on things that add value and count on lawyers to sort it out when the work will provide value -- fundraising / M&A. There's a point to be made about the lack of a signal here too, if all companies are bad, then no company looks worse for meeting that expectation.
I don't think this is a correct model. Because gene mutations and second hand effects aren't truly random. For example, prior mutations which confer some benefit and which are therefore selected for can make certain later neutral mutations more likely.
"Give with an open hand, and stop thinking about the tokens with which you will be repaid. Be happy to be worth stealing from. The future owes you nothing."

I see ideas like this regularly on HN, yet when it comes to the GNU/GPL, violators are regularly excoriated. If you don't care about plagiarism, you shouldn't care about a company making money on code you decided to give out for free.

My point is that people that write these articles quickly change their mind when the plagiarism enriches someone they don't like, disagree with politically, or just don't feel deserves to profit off of it.
I've seen open drug trade and violence unprosecuted. A lot of police officers complain that the DA lets most cases go.
I'd need to know what you mean by manipulative and why it seems negative in this context, I apologize because I feel like that might seem sort of pedantic but education as a field has a very large collection of practices that could easily be described as manipulation. At the same time, I'm worried manipulation seems like the right word because I've been focusing mainly on surprise content to establish a fast example for the discussion even though what I've really been trying to drive at is the way that trigger warnings and their implementation/expection impacts the teacher-student dynamic.

I think in general we agree that most lessons don't really need to be surprising, emotionally provacative, etc. But the reason I've been focusing on those examples is because it's not too hard to understand why a professor might choose to employ them situationally (the basic answer being showmanship that drives engagement of some sort). A similar but very different example would be something like a Sex & Gender course, I've only taken a few such courses but the first one really stuck with me because one of the early assignments was simply for students to break into same sex (technically gender presentation but we didn't know that concept yet) groups of two and hold hands in public with our partner for ten minutes. I could certainly see an argument for giving someone with a history of abuse a pass on this assignment but should the instructor have included a trigger warning in their syllabus calendar about it? The point of the assignment, as the professor acknowledged, was in part to make us uncomfortable and aware of how our discomforts might be tied to social prejudice.

You're right of course that this is all just theory. Real life is, well, it's real life it's nuanced and expecting some amount of situational accommodation isn't something I'm against. After all, if a professor offers office hours why shouldn't a student be able to use that time as part of how they work around content that's emotionally challenging for them? At the same time, and I guess what I should have led with in retrospect, my issue with a lot of solutions about trigger warnings or even just content consideration in general is that it's presented as a victimless accommodation when the dynamic from the instructor's side seems to favor watering down content for the entire class so that you don't have to sift through the chafe so to speak. I don't know what a good middleground solution is, and I do think it's worth pursuing one, but as far as trigger warnings specifically I don't think the benefits have been shown to be worth the trade.
> but its too much (and getting embarrassing now) to keep forwarding his stuff to him

What amazes me is when I get misaddressed email, and I reply to say its misaddressed (and I'm not talking about automated services, I'm talking about obviously manually sent stuff), and my reply just gets ignored and the misaddressed email just keeps on coming.
Unauthorized access (in the legal sense) is definitely unintended, regardless of whether it's caused by weak design or code defect.

Posting 0-days on GitHub isn't responsible disclosure. The real test will be to see how fast it gets fixed and what the fixes end up being.
If it is documented in the manual[0][1] is it a "bug?" I think the design is poor (bad default WiFi password, WiFi always on, inverting sensors with no sanity checks) but this is how it was designed to work, it is officially documented as doing so.

I guess it boils down to a definition of the term "bug." But I feel like a lot of the knee-jerk responses (and voting) didn't read the article carefully enough.

It is a core design weakness rather than a "bug" (implying an error) in an actual good design. I think the distinction is subtle but it is there.

[0] https://www.tesla.com/support/energy/powerwall/own/monitorin...

[1] http://azmag.gov/Portals/0/Documents/MagContent/Tesla_Powerw...
Very impressive perf on ARMs side given it competes against decades of x86 specific optimisation in the code.

Intel for example for long intentionally made float performance close to integer of same size, so there was no perf difference in scripting languages that use float internally for all computations.

ARM sucks at web benchmarks because ARM never put any accent on fp perf. Many ARM cores simply don't have fp units at all. The most popular JS vm V8 does a lot of useless float>integer and back conversions under the hood, and that doesn't help either. They are almost free on x86, but degrade js perf on smartphones by double digits.

Second, vector math and vector float math have close to no use in web loads, but a lot of devs still try to put SSE instructions everywhere simply because SSE is many times faster than simple math and many binary manipulations on x86.

ARM on other hand is relatively good with making a lot of ops on byte and double data, because it was historically never aimed at number crunching with extra wide vector instructions.

For the same reason ARMs UCS-2 and UTF-16 parsing performance is that bad. All kinds of parsers exploit fast register renaming on x86 to run tzcnt with very good perf, but they have to revert to relatively slow SIMD bitmasks on ARM. You can feel that a lot when you work with VMs/interpreters that use UCS-2 as their internal unicode implementation.

Hardware peripherals were always x86 optimised too. Yes, almost every device you can hook onto PCIE has been extensively optimised to work well with x86 style DMA, and some higher level APIs like I/O virtualisation, DMA offload engines, and assumptions about typical controller, memory, and cache latency.

Yes, even endianness conversion is there to make x86 jump ahead. Almost all "enterprise hardware" intentionally uses little endian in its protocols, to avoid endianness conversion on x86. Of course at the cost of doing it on big endian machines, that include ARM.

P.S. On other hand, nearly all peripheral ICs aiming at embedded market prefer big endian for an opposite reason.
I did not know that Chromecast audio was discontinued. That was pretty fast.
Single income: Move to a new job. There is 1 short commute per day. It can be in a small city with little traffic, so the commute time is short and low-stress and there is little fuel burned. Childcare is sort of free, and the house is big, so having a big family is easy.

Double income: Stay put, even if the jobs change. There are 2 long commutes per day. In order to find 2 suitable jobs, urban life is required. The commute burns lots of fuel, even if by bus. Childcare is expensive, especially if not of dreadful quality, and the apartment is tiny. Having a family is not really practical.
The retail Hummer was basically a kit car using a Tahoe/Suburban frame.
The future of Silicon Valley: "This internship really sucks. Just when I think there's nothing left they can ask of me..."
You are using the mcarthy blacklist as precedent for banning peoples ability to participate in a social setting. As far as im concerned, since forever that has been used as a reason to question and challenge censorship.
Same with Apple and its policies regarding closed platform (walled garden). But with such analogy people will go mad. Hypocrisy at its best.
Can you associate a PhysicsBody2D with each one of these?
Yes, there are states where that information is not for sale / not freely available.

There's no particular reason that car ownership (or house ownership and pricing) needs to be public information.
I was one of the first who worked on embedded Linux, and I put the kernel and a user-space program in a device with 512kb RAM once. It was too tight to do anything useful with, but just barely. It was no problem doing useful stuff on a 2 MB device (this was in 1999) :)

Though to Linux defence, it is not nearly as bloated over this period of time as, say, Windows, by orders of magnitude. And, you aren't required to compile in everything. It's just very tedious (and frankly a bit pointless) to trim it down..
I assume such breaks are created on purpose by YouTube to reduce downloads and similar undesirable (to YouTube) usage?
No, not necessarily. Check out these numbers:

Sensitivity is what fraction of the affected people are actually found. Here: 90%, so 10% are missed.

Specificity is what fraction of the unaffected people are detected as such. Here: 95%, so 5% wrongly detected ("false positives").

In Europe, there are 60 cases of lung cancer per 100 000 people.

That makes 54 correctly detected per 100 000, missing 6 cases.
That also means 5000 people incorrectly suspected of lung cancer (5% of 100 000).

Update: using the accuracy from the article itself, we would still get a total of 1000 of false negatives (affected but not detected) and false positives (unaffected but suspected). Incidence is still 60/100 000.
I'm very curious how do people feel about the "headless component" UI strategy? First came across the concept at a conference recently -- React Table was one of the key examples the speaker gave, in fact -- and I find the idea intriguing, but I'm not quite sure yet whether I want to subscribe to the newsletter.

Is it a useful way to separate look-and-feel concerns from functional concerns, or is it just another layer of indirection?
Depends if I'm guilty or not.
Are you suggesting that whatever weird food your kids eat is an "upgrade" compared to the normal diet of Bangladeshis?
He did say all the applicants, not just a handful of them.
It's a shame that people can't respect his wish to remain anonymous. I know you didn't do the detective work - it was Reddit user THE_IDENTIFIER - but it would be sad for him to get in trouble.
Yup -- if it wasn't optional, it'd expose their choice to many more users.
I've done both.

2-longish term 5+ months incubation/development, and 1 throw it together in a weekend and see what happens.

The thrown together site got much better traction than the well prepared.

I'm launching another 3 day project (hopefully tomorrow), so I'll know more than.

One thing I have found, and I think your language points to it as well, is that when you are completely dedicated to an idea, you're trying to make it fit.
Whereas if you are in the mode of seeing if their is a market (re: faster projects), your model of 'success' is if it gets early traction.

I thought that a 5 month project was reaching for minimum viable product. Now I'm realizing that minimum viable may be less than viable as a product. Really more like minimum viable market test.
I can think of ways to abuse this already.
I recall there being a Penny Arcade strip about just this sort of thing...

Ah, here it is: http://www.penny-arcade.com/comic/2006/6/19/
Considering what we now know about the iPhone 4G, the spotlight would have been a waste of time; it would just been another moment for Steve Jobs to give the fanboys an aural reason for an orgasm.
This from the municipality that had to put a network engineer in prison in order to get access to their DWDM equipment? Then again, parking is like a $125m per year profit center for San Francisco, so they're more likely to get parking collections right than, well, anything else.
Meanwhile, here in Philadelphia, we recently upgraded from quarter-feeding meters to smartcard meters. Unfortunately, the smartcards spontaneously lose their value with worrying frequency, so everyone just uses quarters anyway.
I think he's saying that the 'focusing on one thing' part is important. Regardless of how well you do a task, if you offer many services, you might not come to be associated as strongly with a particular task in the consumer's mind. Thus, when they come to think of that function, specialists come to mind rather than the you, the generalist.

That's how the theory goes, anyway.
I don't think the studios treat piracy anything like the recording industry does. Many studios turn a blind eye to, or even openly support, fansubbing -- pirating their series with fan-written subtitles. As another commenter said, countries where they're not airing the series on TV are secondary markets, and many studios seem very aware that people in those markets getting access to their material even in illegal ways is a good way to build up enough demand to actually license the series in that country. Piracy builds demand for international anime DVD sales and those that sell well sometimes end up licensed by Cartoon Network, Hulu, etc.
Yeah, but the MS Word format is vague enough, that the only way to ensure that someone else sees the same document you're seeing is to ensure that they're opening the document on the same version of Word, with the same OS and the same fonts that you have.
The Vanity Fair profile was brilliantly written.
I take the opposite (hipster) view. If a language is suitably popular it's because there is something bad about it. Either

A. the barrier to entry for other languages is too high (Javascript for the browser, Objective-C and Swift for iOS, etc), and so there is no evidence that there is anything good about it (you just lump it and accept that's the way things are done).

or

B. Because it is still a generic, C-style, imperative, possibly somewhat OO language that feels very similar to a language you already know, and which is a reasonable choice for nearly any problem (rather than ideally suited to a subset of problems), and you are probably selecting it based on that merit rather than any real technical merit the language offers. (Note that this can be a reasonable business decision, but oftentimes people delude themselves. "We use the best tool for the job"...so long as that tool is Java or Javascript)

As you say, all imperative and OOP languages are fundamentally the same; for me it's when languages veer off that path that they start getting interesting and really differentiate themselves.

As a note, too, 'there is no easier way to create a single GUI for 3 platforms, as JS' is not a testament to how good JS is, but a testament to Netscape being in the right place at the right time. It was a language written in a week, whose syntax was forced by suits to be 'Java like' because that was what was popular at the time, and which had no competition.
That's because I vouched for it. Before that it was labelled [dead], possibly due to downvoting.

Edit: Thanks for the clarification, dang!