skysight-inc/HackerNews huggingface dataset:
Related to what you are saying, I read somewhere, many years ago, that the best thing to do in cases where you feel like being grumpy or dismissing something that was asked for was to, instead, ask 'why'.

The reasoning is that sometimes what the client is asking is his best guess as meeting a need he has. By asking why, chances are you'll get to the actual need and, oftentimes, find a better solution where both the client and you are happy.

Over the years as a grumpy developer, this piece of advice has served me wonderfully well.
I'm always surprised that Gitlab doesn't get sued. It looks so Github-like. But I have to say the logo is cooler. Octocat is really too much Ruby world for me.
The thing is that I'm genuinely interested in how people of certain groups regard themselves. I follow both of those individuals on twitter and they seem to an outsider to be talking sense. I would however like to know the opinion of people who are Muslim before I decide that though.

I agree that HN isn't the forum for this, but surely the best place to rebut such thinking is when it arises? You can hopefully see from my other comments on this thread that I certainly don't condone what the op said..
I see no advantage over using the --app flag on chrome. It does basically the same thing seeming as this is just a wrapper for whatsapp web anyway...
How about both? Taking BART into SF for an hour every day, then wearing headphones the entire workday because of the open floor plan.

I do this now -- pretty worried about my hearing...
Wow, what an insightful metaphor. Referring to that noise as spam (which it is) or a huge "Reply all" chain might get the message across.
Show HN Guidelines: https://news.ycombinator.com/showhn.html

"Show HN is for something you've made that other people can play with. HN users can try it out, give you feedback, and ask questions in the thread. [...] For example, blog posts, email signups, and fundraisers can't be tried out, so they don't count as Show HNs."
You can blow up the runtime with integer division by zero, however.

λ 1 `quot` 0
*** Exception: divide by zero

With `1/0`, it uses `Double` because `(/)` requires a Fractional type.

Also, partial functions like `head` or `fromJust` can burn you:

λ head []
*** Exception: Prelude.head: empty list

The latter is a legacy behavior that is generally considered undesirable. The former is more debatable; some would say that you should avoid integer division by an unknown value as much as possible.

In Haskell, exceptions in non-IO code (other than deliberate hard crashes) are generally considered a wart to be avoided and mitigated as much as possible (because they interfere with functional programming).
Probably based on personal experience. For me, whenever I start a project from scratch I usually start with the most dynamic environment I can find, then hack away until I have something that resembles the functionality I need, before locking it down. In the beginning of a project I don't care if something is 100% correct, I just want to see what my idea looks like, and what I actually need. I don't want to deal with synchronizing my types with a database schema, or make sure the JSON I send to the server satisfy the type system. I really don't care about interfaces or abstract classes or whatnot, I just want to retrieve the value I know to be in the object I got. Then, when I have a working'ish prototype, I can start nailing it down with types, assertions, tests and contracts.

Of course, people are different. Some people do all of this on paper before writing a single line of code. Others plan by making types and interfaces, then proceed to implement those. I just like making prototypes.
I have chronic ear infections and pain because of earplugs overuse. But I have no choice, some sounds literally drive me crazy, yes, literally.
It seems like you're assuming this was reactive?

Seems far more likely that this exchange was orchestrated between Apple and TS.
Would noise-cancelling headphones help address this? I imagine you can listen to music at a safer level if background noise is eliminated.
This isn't the time or the place.
Docker's Guide to Dockerizing Node.js Apps
Or just journalistic naivete and laziness of not thoroughly researching a sector. It looks like the author normally covers consumer technology, so she probably doesn't know much about the agriculture or GPS industries. I would give her the benefit of the doubt of not knowing (which in journalism isn't really an excuse), but either way it's bad journalism.
Sure, once a day or once a week. A cabbie is right on any problem. Or they don't get any custom. An auto-car could be disgusting for hours or days.
Sort of kicking it old school. Timing will be fun, there is a notion of 'lumped' versus not lumped circuits (and this is especially true of logic) where you want the entire circuit to fit within one wavelength of the fastest clock (where that is determined by the speed of light) otherwise you end up with really hard to debug timing skew problems. At 9 meters your CPU will be challenged to run at > 33 Khz but you will be able to do better than that with good layout and floor planning.

Quite the project, I look forward to the final report.
> What would you have him/her do?

Choose a name and icon that make it clear his client is a third-party product.
I think it's super attractive to new businesses to push their wares via a generous free plan. But in the end, unless you think word of mouth is going to take off. Validating your business model by charging is much more important.
It compares the minified files so no comments. You raise a good point about gzipping though. I was operating under the assumption that the libraries would be compressed at the the same ratio so minified file size would be a good comparison. This probably isn't entirely accurate though. I'll have to look into it a bit more. Thanks for your feedback!
Still not a replacement for silence. Do you find your ears becoming fatigued over the day?
That seems like the natural way to carry it, but if you do this then you don't solve the "I'm dripping water everywhere" issue (the video implies this design addresses this).

So you can choose: either carry it the traditional way (hold the handle, with the umbrella pointed at the ground) which allows the "cup" pour all the water down onto the floor, or hold it "upside down" so the "cup" doesn't spill out.
Brilliant indeed albeit with one caveat, this news story gonna die off in matter of 72 hrs top unless Apple or one of its stooges pours more gas to the fire to sustain the action and publicity.
For what it's worth, IMVU has used Haskell in production for years and it's been great. Lots of people bring up the problem of laziness space leaks, but I think they caused a problem once? maybe twice?

It got to the point where, in the Haskell training classes I gave, I simply stopped bringing up laziness. It just doesn't matter much in practice, especially if you use data structures like Data.HashMap.Strict.

Feels like my new role is to help stop the spread of misinformation about Haskell by people who've never actually used it in production.
John Oliver shows why the Internet is a terrible place for women
Co-founder here -- happy to answer any questions!
All his points are speculative. He basically said "I think they probably have it - either directly or from the journalists". Why do most people believe the journalists are the easier target? They have certainly, at any point in time when stuff was in their possession, been more paranoid and careful than the NSA was before Snowden's reveal.
There is a term for it. It's called managing scope. I'm surprised the article didn't mention this.
I like how:

- first, the ClojureScript REPL whines at smelly coercions out of the box

cljs.user=> (+ 1 "2" nil)
WARNING: cljs.core/+, all arguments must be numbers,
got [number string] instead. at line 1 <cljs repl>
WARNING: cljs.core/+, all arguments must be numbers,
got [number clj-nil] instead. at line 1 <cljs repl>
"12null"

- second, the author kind of hints you should be using schemas & coercion already (so as to desmellify)

- third, you can typecheck a codebase incrementally

Also, I really thought I'd see that quote about 100 functions operating on a 1 data structure easier to grok than 10 functions operating on 10 different data structures. Of course, it's nicer when that 1 data structure (or even the 10) has a schema instead of being void *.
Bought by Facebook in 3...2...1...
I promise you that most of us, regardless of our faith (on HN, that will mostly be Pastafarianism), are embarrassed by bigoted comments like those.
>are still considered "Linux Scams"

This is the biggest concern. The linux community is crazy hostile. Heaven forbid your game doesn't work on some wonky setup that would be 100% unreasonable to support. We also see this in Android where reviews for games are sometimes, "Zero stars, doesn't work on $49 $obscure_chinatablet."

Even if a company picked a reference Linux distro, like the current Ubuntu, it would be still displease a lot people, especially if the game only worked correctly on closed video drivers. There's really no winning in such a fragmented environment, unless you're willing to invest a serious amount of your budget here. Its not just "push a button."
Could you describe on the technical capabilities of your current and past managers. How the team members view your managers? Does the managers are only interested in getting the work done and not bothered to look at implementation ?
Still requires a proprietary platform-specific plugin to work. No thanks!
Maybe it's a matter of taste, but I found the GoF book really boring (and a little self hyped TBH).
In my case, it's the "lot of work" issue that is the problem. It's really easy for me to ignore the work I don't understand very well (marketing) or don't enjoy very much (which is largely a function of not understanding very well) for raw programming.

I have a couple of friends doing a startup in the same space in which I'm writing some software, and their software is nowhere near as far along as mine, yet I don't have anywhere near the "business development" that they do. I'm not there because it's too much work for one person and I've focused on the tech. Their tech isn't that great because it's too much work for one person and they've focused on the biz.

Aaaaah, I just don't know. They're pretty inexperienced, mostly just straight out of college. I'd like to find one person who is as passionate and experienced about business development as I am about software development. Instead, I mostly get contacts from guys who've worked in government offices all their lives, looking for a free programmer to boss around on their "1 in a million idea".
So did any of Google Moon-shoots actually had ANY impact on society so far besides being a cool news story?
It looks like most of their cool projects got to the point, where they stale and cannot move ahead.
Yeah. They are not really necessary in a Javascript VM that is optimized for these sort of languages anyway.
I'm wearing earplugs from time to time (when music distracts me from really compex task for example). But if you think about it - it is so ridiculous. Why do I need to wear industrail grade ear protection in the office environment only to be able to do my job well?
I think religion hacking is something that can be cool, and there is a lot of room for innovation with religion. It is my hope that some people will try this out and give feedback, which I believe is in line with the guidelines
In theory, yes, but in practice, that's the entire government apparatus that requires security clearance which is suddenly not eligible for getting a new job (or even keeping their current one). So nothing is going to happen there.
Is there a link to the database?
The problem with "real" micro-offices is that a lot of SMBs don't own the physical property, and instead they rent. These properties often have drop ceilings, so even if the "walls" of the office(s) hit the ceiling, sound would still very easily travel up and over (and removing the drop ceilings is expensive/hard).

Companies had an alternative: Cubicles.

They were modular, relatively inexpensive, and gave the experience of an office but without needing building work or cooperation with the landlord. But people "hated" those and companies that utilised them were seen as dinosaurs (see the movie Office Space). Then a few companies did open plan, and every said they were young, forward thinking, and trendy so of course a bunch of companies are going to follow suit...

Ultimately micro-offices would be wonderful, but they have practical and cost problems. Plus let us not forget fire codes. That alone can dictate how an office will be laid out (so fire exits are visible, etc).
Hey guys, head of engineering at Layer here. If you actually try to go down the road of building a platform for other developers then you are very quickly going to discover that you need to build a bunch of other stuff totally separate from the core messaging service. You are going to need solutions for getting data in/out, dashboards, billing systems, sample code -- on and on. Plus you have to provide an SLA to close any meaningful business. And you'll need a pro sales team to get those opportunities interested and through the funnel. We are 35 people and I could easily keep another 5 engineers fully loaded to attack the roadmap as aggressively as we'd like. And we've been at this for 2 years. There's a lot of surface area and you need to be very good on both technical and sales dimensions to make a platform play work.

My best advice for you is to either find a unique value prop in the consumer space where you can perhaps gain a foothold and access virality or focus on finding a nice home for your engineering team and technology. I've seen a lot of advice here about how you should start consulting to create runway. This is terrible advice and you should face reality. Nobody is going to build an app and a business on top of a messaging platform that is a part time project of a handful of developers without any runway. It's just not a rational business decision and nobody who is capable of paying you real money would make that call. You are in a market with existing well funded players that are rapidly evolving their product and addressing that market through sales and marketing. You either have to build something that you can give away for free and generate traction that you can raise money against or you need to focus on selling the core assets that you do have: the people and the tech. You may want to reconsider releasing that code if you want a shot at an aquihire outcome. Best of luck.
Free plans make sense for new businesses that are trying to get users to test a product or service, but once it's been built and is working seamlessly SaaS companies really should start charging.
Ubuntu virtual machines on Hyper-V
Learn How to Maximize Your Event Sponsorships with Mobile
There's a pretty big difference between "private for the businesses, but Facebook continues to know All, as is usual for them" which is what you basically describe, and "actually private, including from Facebook" which is probably what a reasonable person would understand from "designed for privacy."
Actually it is trending on Twitter. Don't know about FB.
A major point is being missed here, and it is fundamental to how F1 cars evolve - rules lawyering.

It's fairly easy to design a car that is safe, fast and looks good. It is fiendishly difficult to create a set of rules that enforce those outcomes on designers. Unless F1 becomes a one-design formula, it is always going to have to deal with the cat-and-mouse game between the governing body and creative designers.

The obvious recent example is that of the ugly noses of 2014[1]. The nose height of F1 cars had been gradually increasing over the years, as teams realised that there was an aerodynamic advantage in channelling air under the nose. The FIA became concerned about the safety of these noses, and the risk that in a side impact they might over-ride the cockpit and hit a driver in the helmet.

The rule introduced to address this issue stated that an area of the nose no less than 90cm² must be centred no higher than 185mm above the car floor. Designers immediately realised that this rule could be exploited by simply having a 90cm² protuberance hanging below the main nose, minimising the constriction of airflow. These droopy proboscises weren't anticipated or desired, but they were an inevitable consequence of a rule that wasn't absolutely watertight and the competitive pressures or racing.

The modern era of F1 is practically defined by these creative interpretations of the rules - F- and S-ducts, exhaust blown and double diffusers, blown starter holes, tuned mass dampers. No matter what rule the FIA draws up, some very smart people will figure out a way around it. Adrian Newey, the greatest designer in the history of the sport, is fond of saying that "there is no such thing as the spirit of the rules". To many, that buccaneering spirit is an integral part of Formula 1.

[1]http://www.sanantoniof1club.com/wp-content/uploads/2014/03/2...
Spending 45 minutes working on "a contrived piece of legacy code" with an employee competent enough to evaluate your effort doesn't sound to me like "doing work" for the employer. I get what you're saying, though... I think if the evaluator were incompetent and you were solving an important problem for them (things that would be pretty obvious), it would be an awful interview. But hey, that's 45 minutes well spent if it shows you for sure that you wouldn't want to work there.
Typical. Nothing I said was untrue, nor even an opinion. They're all facts. Instead of reasoning with me and proving me wrong, you reach for the "bigot" card and refuse to have a conversation. That is being a troll.

No big surprise, though. Much easier to click a button and silence those who disagree with you than write a reasonable counter-argument. Well, at least the truth is out there for those who want to find it.
Linux+Kernel+4.1+unleashed,+brings+EXT4+file-system+encryption
I have the same model (QC20i). Ears do not get fatigued. Impressive technology to be honest, didn't think they were that effective before I used them. I do agree that it's not a solution, but probably the best way to adapt.
That seems highly unlikely, I have a hard time seeing this reflecting well upon Apple, more likely it will leave a sour taste in many people's mouth.

It's not like Apple desperately needs the PR and why risk bad one?
Could you outline the differences between Scala and Ceylon constructors, for readers not familiar with both?
Agreed, amazing project. One of his notes further in is an early performance test on the ALU. He mentions that the fact he's implemented a simple ripple adder design seems to indicate a maximum clock speed of no more than 25kHz.
Instead of self-driving cars, I'd say focus on eliminating the need for "going somewhere"/vehicles in general. Would be so cool if we could just 'beam' in to work. 3D virtual presence. But hey, its not my money they're investing.
Apple Planning to Release iOS 8.4GM and iOS 9 Beta 2 Today
How'd you do it if the keyboard wasn't working?
Pairing makes this seem less egregious to me, even if the company is getting some value from the process. In a traditional interview, both you and the interviewer would be spending the same amount of time, and arguably learning less about each other.

Asking for some work to be done off site before an initial on site interview, where the potential employer is getting something of value, would be a much bigger red flag to me, personally.
This is just another instance of western societies devolving from a high-trust environment into a low-trust environment. In the short term, cheating in the prisoners dilemma of social trust is beneficial for the cheater, but in the long run it ends up resulting in lower economic growth, making everyone poorer.

Social trust is the key to economic growth (by allowing de-risked specialization) and political liberty (by allowing minimal black-letter law.) It is too bad that it is rarely discussed, and has been casually jettisoned by the west.
His point about f1 being overly restricted by rules is legitimate, but I am neither a fan of his design, nor do I believe it is representative of a race car truly optimized for speed.

Full disclosure: I have a Ph.d. in Computational Fluid Dynamics (CFD), and I've also raced open-wheel cars at several tracks, such as Laguna Seca. While presently F1 cars are certainly arbitrarily restricted by rules, several of his design decisions strike me as just as bad.

For instance, the open-wheel design is going to create tons of pressure drag. If you were designing a car from the ground up for speed, I sincerely doubt they would not have the aero kit cover the wheels.

More than that, the open-wheel design is also dangerous, because if the tyres touch the results are often catastrophic, with the cars flying into the air and the flailing tyres creating a tremendous hazard. So that also discourages passing. In many motorsports, bumping into the cars nearby does not result in both being completely disabled.
I HATE open offices, but man is this article full of absolute nonsense. I mean that in a very literal way -- it has lots of stuff that can not be made sense of because it lacks context or any actual meaning.

> I stress to my patients and the parents of my patients that if you can’t hear anything going on around you when listening to headphones, the decibel level is too high.

This is just stupid. It ignores type of headphone entirely. IEMs like the ER-4P (https://www.etymotic.com/consumer/earphones/er4.html) have insane noise isolation (up to 42 dB). When using them, I can't hear someone talking to me, standing right next to me, with no music! They physical block the ear canal and create a seal blocking outside noise.

> As a rule of thumb, you should only use [personal audio] devices at levels up to 60% of maximum volume for a total of 60 minutes a day. The louder the volume, the shorter your duration should be. At maximum volume, you should listen for only about five minutes a day.

Again, idiotic. "60%" is entirely meaningless. It might as well be "Don't listen above FALASFDABURAGA". Headphones vary in sensitivity vastly, on some sets of IEMs -- 60% would be ear bleeding, deafeningly, painfully loud. On a high impedance, low sensitivity set of big headphones, 60% is a whisper. As a "rule of thumb" all it does is reinforce that the person who gave that quote is an idiot.

> If you listen to music with earbuds or headphones at levels that block out normal discourse, you are in effect dealing lethal blows to the hair cells in your ears.

... again, quotes from people who have no understanding that there are different types of headphones. MAYBE you could claim with fully open headphones this to be the case... but what is the level of "discourse"... sigh. Again, literally nonsense because it is impossible to make sense of...

> ... Music Is Distracting (entire section) ...

There exists multiple categories of music WITHOUT WORDS! Shocking I know. Most developers I know listen to these types of music because, lyrics are distracting. That isn't a cut against headphones.

> ... Feeling of Vulnerability ...

Getting to some sad points. Again, I hate open office plans, but come on -- really -- the feeling of vulnerability being caused by headphones? It is caused by an open office layout.
Hey guys.. I worked on this project for a while now. This is built based on this article: http://www.restlessprogrammer.com/2013/09/hacking-coding-int...
The other issue with judging sample code is the sheer amount of time it takes. The two of us took around 3 months (full time, effectively, doing nothing else) to select, interview and make offers to around 10 employees out of a pool of over 100 qualified applicants.

You can sort of understand why companies try to develop less time consuming methods, and why experienced developers prefer to hire from their network...