skysight-inc/HackerNews huggingface dataset:
What is micro python?
One of the cool features of my home state is the Citizens' Commission on Salaries for Elected Officials, a 17-member commission with ten of the members being selected randomly from the voter rolls, like jury duty.

http://www.salaries.wa.gov/default.htm
Good point: "I may be more acceptant of sentences with weird grammar."
See your code in action with a visualization engine
Guess What Year 'Computerized' Peaked
It's not really possible to send encrypted messages to people who aren't already using OpenPGP, since you need to get their public key, before you can encrypt the message. You could presumably encrypt it with some symmetric cipher ahead of time, then send them the encrypted junk and say, "Send me a PGP key and I'll send you the passphrase for the message!", but I dunno that anyone's going to do that.

That said, pretty much every message I send to someone who doesn't have a key on the keyservers includes, "Hey, send me your PGP key, I don't do plaintext."
I think you're wrong about both of these. Yes, it's true that you need to inherit from NSObject in some cases, but Cocoa is complex anyway, and this is not added complexity, so it's not different from objective-c in this regard.

For #2 you are flat out incorrect. Swift arrays can be containers of AnyType, in which case they interoperate perfectly with NSArray, and this is the default behavior when working with Cocoa.

Your fear about type related complexity being a real issue seems not to be justified by your examples.

Compared to dealing with the C based fragility of Objective-C, Swift is simply better for anything that it can do.
>1% of a given group A may be doing the creating, however many of the other 99% of group A may well be active in group B and be a creator there.

The Free Market is structured along this assumption. 1% of people will make software, 1% will make music, 1% will farm, 1% will teach, 1% will build chemical plants, etc. etc. but they will each enjoy the other 99%'s productions. The assumption, of course, is that this will naturally fall into place. (Automation and even globalization/outsourcing threw a wrench into the system).

However, this "Law of Conformity" (mentioned in the great-grandparent comment) still applies in this 'new age' of 'basic income'. People will still converge on commonly esteemed things i.e. there will be A LOT of musicians, painters, filmmakers, etc. (many of whom will make crap stuff -- as is already noticeable on certain 'sections' of the internet).

Also,one of the real (current) reasons you never get payed a lot of money for helping people is because: the people that need the most help usually cannot pay you (or at least not pay you well).

The people buying your software, art, etc. are buying it after their own needs are well met (usually). That is the basic premise of consumerism. The morality of consumerism is an issue all on its own.

But it is also arguable that the Free market itself converges (or causes people to converge) due to this "Law of Conformity". The past few generations have pushed their kids like crazy to opt for 'better paying' careers, simply for the fact that they are 'better paying'.

Why? The Law of Conformity, I guess. :P An on topic video came out today by a fairly popular YouTuber, on the last point I mentioned (about the high-pay career pushing): http://youtu.be/16pVXq7Lscg
The argument of authority of Go designers is actually my point. By designing the language in public (even before having source available) they now don't want to admit their errors, and neither do their supporters, because they are authorities, supposedly. I'm thinking of Pike in particular.

By keeping these discussions private, the Apple team did not need to protect their egos or their authority. We do not know who is responsible for which decisions at which points in the design, and they don't feel the need to defend their choices in public.
Here is what Shulgin himself said about MDMA in relation to "brain damage":

"The "permanent brain damage" is based totally on studies done with
experimental animals, with the findings extrapolated to encompass the
human subject. In a simple statement, there have been no studies in man
that have indicated brain damage.

The "holes in the brain" is an even more outrageous deception. These
popular holes are areas in brain scans that appear less active in
attracting radiolabelled agents that are agonists for certain receptor
site areas. The pictures that are shown for comparison are not of the
same person with or without MDMA in them, but of different people, one
of whom has used a lot of ecstasy and the other one without any such
history. The quintessence of this line of mythology is an article that
appeared recently in the Willamette Week. It not only assured the
reader that there were holes generated by serotonin loss, but that they
became flooded with dopamine (the default neurotransmitter) and, being
attacked by hydrogen peroxide, produced rust.

Sorry, drug warriors. No damage, no holes, no rust."[1]

Granted, that was from an interview in 2001. For more recent research see erowid[2], and simonster's post later in this thread.[3]

I would personally be far less concerned about the neurological/mental effect of ecstasy itself than the purity and identify of whatever passes for ecstasy.

This is a very unfortunate effect of the drug war: it makes everyone less safe.

If drugs were legalized, they could be regulated and their purity and dosage could be reliably labeled, just as currently legal drugs are in your neighborhood pharmacy, and people dying because of counterfeit drugs would mostly be a thing of the past.

[1] - http://www.cognitiveliberty.org/shulgin/adsarchive/brainhole...

[2] - https://www.erowid.org/chemicals/mdma/mdma_neurotoxicity.sht...

[3] - https://news.ycombinator.com/item?id=7842632
What is the difference between GnuPG and OpenPGP?
Bug On GnuTLS Allows Hackers to Run Malicious Code
Agree that 3D printers are hard to compare - while reading, I thought of yet another thing that doesn't seem to be mentioned in the article or on the site: speed.

Besides the obvious size and build area, the main functional difference between my very modified Solidoodle 2 and my friend's Rostock Max seems to be how quickly each can produce a print. The Rostock's delta positioning and lightweight nozzle carriage give it a substantial speed edge, but those qualities aren't reflected in most reviews.

Speed vs. quality is always a tradeoff, though, so to collect this spec in a way that would compare printers you'd need a test print and some sort of specific quality standard. You'd also need to tweak each printer's slice/gcode generation settings, since some printers come with profiles tuned for speed and others for quality.
>> No implementation problem. Right now, only ~80x24 grids are life grids, and they aren't yet connected.

> That is disappointing.

Okay, I feel like this is some weird negative spin here. You will be able to have as large a finite area as you want. A single "life field generator" will support ~240x75. You will be able to have as many "life field generators" as you want. You will have to invest in in-game resources, though. It won't be pay to win. But it will serve to throttle the number of occupied grids.

"As large as you care to have" is fine and generous, I think. If you want "effectively and effortlessly infinite," I'll just leave that for someone else to pay for the server time.

> I think you could find other, more creative, ways to prevent infinitely growing formations from crashing the server.

Hey if you want to volunteer an implementation in Go, this is well travelled territory. You can look those algorithms up and implement them yourself. That's not my main focus, so I'll not spend the time right now. As for a game world, it's fine to let people mine resources and stake out as large a region as they care to. I'm going to do a Life-world sort of as an art project/portfolio piece. The Ultimate Shared Life World is just not my present goal. But who knows? We'll see where this leads.
Why Messages in iOS 8 will make driving safer
The current state of affordable 3D printers is such that you will get much more variation of print quality due to [mis]calibration of an individual printer than you will from printer model to printer model.

For anyone remotely "Maker"ish, I recommend buying a RepRap rep-strap kit like the MakerFarm Prusa i3 kit and building the kit themselves:

http://www.makerfarm.com/index.php/prusa-8-i3v-kit-v-slot-ex...

The results are as good as any of the affordable FDM retail machines costing up to $3000 and having pieced it together you're better equipped to deal with the situation when your first stepper motor dies or your heated bed needs levelling or your extruder has a massive jam. The Printrbot (kit or assembled) is good too, but being PLA-limited kinda sucks in the long run.

If you really don't want to build a kit, I'd recommend LulzBot, great company.
Didn't peg Hawaiian Pidgin even though I purposefully answered a couple questions that way (like "stay x") while choosing standard grammar otherwise. Top was just standard American English, the other top three were just like black Vernacular.
Shulgin on Sassafrass and Safrole:

http://www.cognitiveliberty.org/shulgin/adsarchive/safrole.h...
OTOH, GCC and Clang provide warn_unused_result, and it's easy to define types for returning errors from functions that throw a compile-time error if ignored by the caller.

I find explicit error handling safer and more elegant than exceptions, especially if you consider that writing exception-safe generic code is hard and error prone.
I felt that 30 FPS was too choppy when moving left-right between home screens. 60 FPS works well. "Glass" is deliciously retro.

I actually liked a faster "wave propagation" speed.

All personal taste though, which Android excels at. =)
> how to store various types of data so that both it and its associated indexes remain fully accessible and searchable, with a minimum of maintenance, across decades or centuries, even as formats, maintainers, and institutions rise and fall

Very nicely written description of something useful. IMO much better than the words on that website.

What I don't like about the website is the "jargon". These words are from just the first paragraph:

formats
protocols
modeling
synchronizing
post-PC
objects
FUSE

Huh?

The website text was probably written by an engineer. Reminds me of a great quote:

"engineers are all basically high-functioning
autistics who have no idea how normal people
do stuff" - Cory Doctorow
Yes! This is the goal. It's very difficult to explain these specifications, and I don't think our website has reached that goal yet, although it's an exciting problem to try to solve.

The problem comes down to what you're using your printer for. Like you said, its often better to use a "lower resolution" printer because it's faster and more reliable.

For the question "How good will my print come out?" we've tried to answer that with a '3D Prints' picture feature that are provided by the community, so you can see what quality other people get out of a particular machine.
Show HN: HTTP radio-type track stream fetcher
To phrase it better - I don't have any idea whether the UX skills of the team match up with the technical skills. I wasn't criticising anything in particular, just noting a lack of knowledge on my part.
Yeah? Interesting. Because all popular languages that I've used, up until Go, fail at concurrency at such a basic level, that it's almost as if their authors don't understand what concurrency is. Except Erlang. But then again, I said popular.

C/C++/Ruby/Javasscript/Python/Java/C# - all fail miserably, utterly and completely at concurrency. What Go accomplishes with channels, goroutines and the "select" statement has been an eye-opener for me.

Watching people struggle with threads/mutexes/shared memory in the 21st century, or with some half-baked library, is truly sad.

I'm really surprised that all Go features have been present since the 80's - It's strange I have utterly missed a feature as basic as concurrency in those! Very interesting.
Winners and Losers In The Last Second Economy
Could you have "Classic" (current) and "Remixed" (tweaked) versions of the current presets?
Show HN: C++11 immutable string
I'm looking for feedback on this approach to an immutable string (istring). The idea is to provide a super fast immutable string that can be efficiently passed to lambdas as well as be 100% thread safe.

Another bonus is faster hashing. If a string literal is given to istring, then the hash is computed at compile time! Other strings will have their hashes cached for later use. The istring is designed more or less after the python string in this regard.

It should also consume less memory than std::string and perform faster in all other areas.
I grew up in the UK, the media loved sensationalizing a drug death. 1 pretty white girl dies from water toxicity while on ecstacy (AKA not a drug overdose, a death due to lack of information on safe usage), whilst organizations like MADD are fighting like crazy to reduce the daily manslaughter caused by people knowingly and irresponsibly using alcohol.

When one of the big scandals was going on I remember there was an advert on TV warning against binge drinking. The advert was this girl saying how her and her friend were out at a club, her friend was staggering about so they went back to her apartment because she was closest. They laid on the bed and went to sleep, she woke up the next morning and her friend was ice cold. Dead, choked on her vomit in her sleep. The UK has almost 9000 deaths a year related to alcohol.

The UK in 2011 had 6 deaths where ecstacy was a possible contributing factor. Drugscope is an interesting if skewed view.

http://www.drugscope.org.uk/resources/faqs/faqpages/how-many...
TL;DR

If your job helps others, you may want to do it [1] for reasons other than money and therefore get paid less.

[1] http://en.wikipedia.org/wiki/Maslow's_hierarchy_of_needs
He's clearly above this board and could get rid of all of them if he wanted to. I think all involved know and understand that, and hope it never has to happen.
Speed is difficult, because for many applications you don't want it. Speed means more heat, and more heat means higher chance to fail with step loss or other problems

I do think that max print speed could be a good metric to put on the top pages of each 3D printer. I think you're right in that its an important metric that people like to know, even if they don't often crank it up to those speeds.
You know what else sucks about buying a 3D printer? The cost of shipping one outside the United States.
> it may be the programmer, making the software that powers our world

Most paid programming jobs in IT are bullshit jobs that have no benefit to anyone. They just prop up other bullshit jobs in the accounting or legal departments, duplicate work done in some other company's marketing division, make the systems compliant with some new government regulation, work around bugs put in the systems for the express purpose of generating paid after hours call outs, exist just so the workers involved can list more new technologies on their CV's, are contractor jobs doing the work of the employees who are spending their whole day trading shares or doing nothing, laundering some open source software so it can be made proprietary, ... ... ...

Any programming job of any real benefit to anyone isn't even unpaid work. Someone doing a personal pet project is really paying because of forfeited income, as also is a student paying fees to work on a research program somewhere.
Thank you. And don't get me started on vs2013 update 2. I wasted a day putting up with it but eventually had to uninstall out of frustration. After that experience I can't see myself ever installing update 2 unless there is a showstopper bug in update 1.
That is quite a dissapointing attitude. Everyone would use it if a) it was easy. And b) if they weren't being mislead by providers that their email is so secure.
Yes, that is my point but I didn't make it very well. If Objective C were routinely subjected to these sorts of projects, I think its over-all reputation would be a lot worse.
Lulzbot is a great company, and they've been around for years already.

I think there's universal agreement in the community that the best way to understand your 3D printer, and therefore calibrate it the best and get the best prints, is by building your own. That's definitely the way to go, especially if you have kids.
How about BEAST or CRIME?
Cool feature: There is an overview of all the 3dprinters on their site https://thre3d.com/category/printers and you can order by buildsize/price
You are blurring the distinction to drive home your point. The fact is, superstition carries a negative connotation. Discipline does not.
Sitting Inside Elon’s Spaceship, the Dragon-2 Capsule from SpaceX
Brazilian here and I got

1. US Black Vernacular / Ebonics

2. Singaporean

3. American English

Native:

1. Dutch.

2. American

3. Greek
Sequoia Capital invests $15 million in mobile gaming company Octro
A current real alternative that uses native binaries to avoid the JS issues is WebPG[1]. I've been using it for about a year and while it has its rough edges, it's a pretty solid tool (and approach).

1. https://webpg.org/
This version of Visual Studio still seems to have XP support.
That's a huge problem. Here's why:

1) They're really really really heavy
2) Most companies are small and don't have distribution set up
3) Many companies can't make enough printers (they're kinda like garage operations), have huge lead-times, so they don't even want more orders from beyond their serviceable territories.
How is it different to git? Or I guess bup, more appropriately.

What is this doing that solves so many problems that apparently they can't outline what it is actually doing on the frontpage of the website in clear language?
32 years in California, then 22 in Washington. I too got Norwegian and Swedish as the guess 2nd and 3rd guess for native language.

For my English variant, Standard American was first, then Canadian, then Singaporean.
Not really a guru, but RPC is traditionally not thought of a message queue architecture -- it's almost always built around a request-reply cycle with no queueing.

Reactive Streams seems to really boil down to a push-based (Functional?) Reactive Programming (with some queueing added in in the distributed case). As Erik Meijer explains[1], it's mostly about a small extension to the "Observer" pattern which comes about if you dualize the "Iterator" pattern properly.

EDIT: In short, there's very little really new under the sun here in CS terms, but this approach seems to be going through a hype cycle at the moment.

[1] https://www.youtube.com/watch?v=looJcaeboBY (I'm sure you can find other explanations, but I like Erik's.)
Yeah, that's entirely possible.
I agree that readability trumps shortness of code. I want not for APL nor code run through a javascript minifier.

But the branch and explicit boolean comparison are additional structural complexity (not just "verbosity") and invariably harms readability to me. Care give a poster child example for where it helps readability? Unless it's unclear <expression> results in a boolean - a problem better solved through better naming - code like this forces me to perform the equivalent simplification in my head to understand and reason about the code, a process fraught with error and distraction from my actual task.
I don't understand. Why would you make everything in-house especially for site like Ok-Cupid which is not exactly used to power rocket engines.
I was here in the US during Tiananmen. The western media at the time reported the full story about the "tank man", and that he was pulled away. No western outlet (that I can recall) ever asserted that he was crushed by the tank. They were showing the utterly remarkable video on a loop, constantly - the tank trying to drive around him, but not being willing to run over him. So it's not so much explicitly censorship, as much as the fact that through the lens of time, that fuller story is not really told.
But when displaying the cleartext of a previously sent email or received email... they must be able to decipher the encrypted text in order to display it to the viewer, no?
> (I mean, I will anyway. I just want to know if you mind.)

That's an excellent way to ask for permission while being clear that you don't need permission.

I'm always wary of asking for permission in situations where it's not absolutely needed. What if the person says no? Then if I go ahead and do it anyway, I look like a jerk.

I'll have to remember the way you did it.
> It is though; its all non-ionising radiation. Both the wifi and your phones broadcast information indiscriminately in the interest of connecting to infrastructure.

I was not referring to their nature, but to the power of the emission.

> Whereas a mobile phone can range from 21 dBm (125 mW) for Power Class 4 to 33 dBm (2W) for Power class 1, a wireless router can range from a typical 15 dBm (30 mW) strength to 27 dBm (500 mW) on the high end

The radiations from your phone are more powerful than from your traditional router, plus your emitter is usually close to your body, while you usually far away from a wifi router.
This escape the room as a live event started in Hong kong a few years ago. Glad to see it finally come here.
EMH says this will get priced in, and companies who pay dividends will just switch to stock buybacks or other more efficient methods of capital distribution.
straight lines are straight in a photograph because of precision manufactured optics shaped specifically to achieve that effect, to reduce "chromatic aberrations" and "barrel distortion".
From Wikipedia:

In law, sedition is overt conduct, such as speech and organization, that is deemed by the legal authority to tend toward insurrection against the established order.

(Not to be confused with seduction)
I'm a musician, and I ridicule the athletic group I hate the most using my music. 'I play at the soccer team'.
I think "Former Linux Journal Editor ..." would be a more accurate headline; AFAICT Hughes no longer works for them ( http://www.linuxjournal.com/staff ).
IOS 8 WebKit changes allow all apps to have the same performance as Safari
Hexadecimal floating-point literals
I'm 18 minutes in and I have no idea what they're actually doing.

I get what they seem to think they're doing.

But "storing arbitrary" data is a problem everyone in the world is trying to solve. It's what a filesystem is. It's what backup tools do. It's a pretty well attacked problem.

A bunch of SHA1 hash addressed data is almost as useless as a raw disk with no filesystem.

Similarly, I'm seeing a lot of JSON. Who says JSON will be remembering in 80 years? It's ASCII! But that's not much of a guarantee.

There's a lot of claims here, which don't seem to translate into something which seems actually useful. For example, "immutable" sounds good till you run out of disk space because you have 1000 copies of a sightly different VM image in the system. It's pretty easy to build a system which stores "everything". It's a lot harder to build one which is useful.
Large Open Datasets for Data-Science
A very good compilation of the datasets for data-science, usefull for machine-learning, statistics etc...
Aha, that's what I was thinking of. I believe it's mentioned in passing in TIHKAL.
Are they the same every time or is there an element of randomness in the puzzles and codes?

It'd be interesting if they could be random enough that someone couldn't spoil it for others, and people could use AR or just wi-fi to research clues?
Uber Driver Kidnapped Her And Took Her To A Motel
It isnt really the drugs...it is everything else that comes with it, the people, the illegal trades, the raves....

And I am getting old, I need my 9 hours of sleep to performance max! :)

But I havent said "I will never take X drug again"

I just havent felt like it :)
Firefox is going to implement Audio&Video calling feature between two Browsers.