skysight-inc/HackerNews huggingface dataset:
> I don't know Scala or Erlang, but based on the results I would assume both are allocating a posix thread for each thread in the software and so it is using the kernel scheduler to switch between them with all the overhead that entails.

Incorrect.

> I have been considering threading in Rust vs Go and that is the biggest difference I see between the approaches. However it should be possible to implement Go style goroutines in Rust using custom dispatch code like old C coroutines. I think I have already seen libraries like that, but I haven't dug in the details to know for sure.

There is https://github.com/dpc/mioco for I/O-based coroutines. For CPU bound tasks you want something like https://github.com/nikomatsakis/rayon.
So smart. Maybe he planned a trip for the next day?
Supporting a different direction is one thing. Making a deliberately incompatible API and refusing portability patches so as to force adoption of your preferred direction is quite another.
In this case fixing the issue required knowledge of how certs work in order to guess that there is a date issue. That's probably pretty rare at fix-your-computer shops.

It's pure luck that I'd seen this type of issue before because I'm one of those mere civilians: my Windows machine at work loses BIOS settings on power down. I've seen that until the date is restored, DropBox and several other things don't work.
> If we’re being honest, it’s not that hard to imagine doing something similar ourselves. Most of us use GPS as a crutch while driving through unfamiliar terrain, tuning out and letting that soothing voice do the dirty work of navigating.

It is very difficult for me to imagine driving 250 miles out of the way (especially when I'm tired and really want to get where I'm going); or driving into the ocean; or driving off a bridge because I've ignored all the road closed signs. I don't even shut my brain off to this degree when another human is helping navigate.

The article is saying our cognitive maps are deteriorating because navigation software provides the information instantly at hand. For some people that may be true. I've noticed this effect in other aspects of my life, though not with navigation. But even if true, that does not explain people ignoring all other indicators that something is not correct.
https://news.ycombinator.com/item?id=11078717
"Schooled" is in fact, just ancient click-bait for wrong.
I heard Hawking's exact explanation in the late 80s (a copy of the bet was on display in Bridge Hall as I remember), but there is also documentation from Hawking himself in '97 long before this article was written. I suspect Kip would be annoyed by the implication, since they are pretty good friends. It's even more sad that they don't mention the girly-magazine part of the wager since that adds a human and salacious twist to it... although out of Discover's G-rated range.

Hawking's explanation for his position was that if black holes didn't actually exist much of his research would be incorrect, but at least he'd have the consolation of winning the bet.
Stephen Hawking (1997). Black Holes (VHS). New River Media
The Yahoo Problem
Assuming grid computing ends up cheaper, any problem that doesn't depend on high availability.

Why grid computing might be cheaper: people could rent out excess capability that would otherwise go wasted, so their marginal cost of computing is 0 or close to 0. The question is how much overhead would be, but building on a marginal cost of 0 is better for costs than any dedicated solution.

It's not obvious that those considerations outweigh the cost efficiencies of centralization, but it's by no means obvious that they wouldn't or can't.

Think the power grid as an example. If power wasn't fungible in close to real time (like cloud computing today, unless you specifically set it up that way) our prices would be more expensive, because less participants would be producing energy. The fact that anyone can, in theory, produce energy and sell it on a market which accepts the best bid improves the market for everyone. This seems similar.
Alismajean.blogspot.com
visit us at
> A Go program runs as a native binary, whereas Erlang and Scala/Akka run via their respective VMs. Wouldn't these results be expected?

No? Erlang and Scala both have JITs. The JVM does quite a bit more optimization than Go's compilers do.
> But in what sense are the flash drives base 2?

In the sense that the memory chips inside are base 2 capacity and the sole reason you are seeing less is because the flash control chip just reserves some space.

What's the point of pretending you don't understand someone's comment and asking for clarification?
Ever tried cutting a hose? They're tough, have to be.
That may be your opinion, but I do think we should have a discussion around something as important and complicated as the TPP.

All I've heard so far is Jingoism, we should hold ourselves to a higher standard.
Did that. It did not set a date close enough to now to work.
Yeah because it has never happened before where a President of the United States got murdered (JFK).

I'm not saying his death is the only possibility but certainly its one of the possibility when you are talking about billions being put on the line.
Less buggy? See: https://news.ycombinator.com/item?id=11008449
the compiler will definitly inline this part:

if size == 1 {
c <- num
return
}
What rx are you using?
Install PHP 7 on CentOS, RHEL or Fedora
Low gas prices justify rethinking of fuel economy regulations
I guess a GPS navigator is not an excuse for not having a map or not knowing how to read one, at least on longer out of town trips. I've been burned a number of times when a gps navigator tried to take a 'shorter route' through logging roads and mountain passes that you could cross only on foot.
How to design a good API and why it matters (notes)
* You have one chance to get the API right

* API’s can make or break the company

* Everyone is an API designer. If you program, you are an API designer.

* Good API: Easy to use, learn, hard to misuse, just powerful enough, easy to evolve, appropriate for the audience (API terminology)

* Process

- Gather requirements - Be Skeptical - Hear the un-said.

- Convert requirements to use-cases

- Start with a short spec - ideally 1 page

-- Don’t create a long spec first time around - it gets associated with the ego and then iterate

- bounce it off of the stakeholders

* Write to your API early and often. Basically, write tests early.
- These probably will live on to become examples on how to use the API
- Make sure these are exemplary as the examples will be used by consumers to base off their code.

* Maintain realistic expectations
- You won’t be able to please everyone
- Aim to displease everyone equally

* Expect to make mistakes
- API design is hard
- Expect the API to evolve

* Principles of good API design:
- Should do one thing and do it well.
- Should be easy to explain.
- Should be easy to name

* Should be as small as possible but not smaller
- When in doubt, leave it out.
- It’s easier to add it later than to remove it.

* Implementation should not impact API

- details confuse users

- inhibit freedom to change an implementation

--- eg: catching SQL exceptions by the client

-- Do not let implementation detail leak into the API

--- Eg: implements serializable - all private fields are now public after serialization

* Minimize accessibility of fields

- Make classes, fields as private as possible

- public classes should not have any public fields, with the exception of constants

- Minimizes coupling

* Names matter

- Names should be self-explanatory

- Be consistent

- Be regular- strive for symmetry

--- If key and entry are two attributes, and addKey and removeKey are methods on ‘key’ then there should be ‘addEntry’ and ‘removeEntry’

* Document religiously

- Document every class, interface, method, constructor, parameter and exception.

- Method documentation : contract tween method and it’s clients : pre-conditions, post-conditions, side-effects

- Parameters : indicate ownership(can I modifiy it ?), units (size of blocks in bytes), form (String : XML ? json)

* Document state space religiously

---- 37 minutes in the video ----
To be continued...
The dubious effectiveness of D.A.R.E. and problems in nonprofits (2013)
Hmm, that's why I have spent every second outside work and my family working my ass off on a startup on the minute chance I create something of enough value that will free me from my m-f 40+. Huge motivator for me. Take that motivator away and I doubt you see nearly the # of people working hard to create value. I believe that's why socialism fails.. Every... Single... Time. But hey, we can do it better right?
I've always wondered why pharmacists still exist, yet TONS of articles say that there's almost no chance of that job being automated in the foreseeable future. I don't get it. It seems like a problem that's virtually impossible for a human to do, and not too tough to solve programmatically. Doesn't make sense to me. Would love to learn exactly why it will or will not be automated.
It seems obvious that tricorns are a much more stable design.
I often question the quality of articles on businessinsider.com, i.e. "this is news" vs "this is what i want you to think is news".

Picking from the top of BI list, do these jobs even exist today?:

3. Switchboard operators, including answering service

1. Telephone operators
goroutine is not an actor. its a concurrency mechanism.
so a goroutine is not an actor, however a future (http://doc.akka.io/docs/akka/2.4.1/scala/futures.html#Use_Di...) is definitly closer to an actor than a goroutine. so you can't compare golang and scala/erlang. too bad, huh?

And when you are clever you would be comparing monads, which actually a goroutine could be. and a future/promise, too.

Btw. Even a Future does more than a goroutine do. it won't crash your whole program when it fails, which a goroutine does.
Which means you need to program with futures in order to not do blocking IO on your limited thread pool that the actors are multiplexed across. So at that point you need to write node.js style code.

Coming from an Erlang world to akka, this blew my mind.
I saw an interview with old Mikhail Kalashnikov once, they asked him if he regretted designing the AK47. No he replied, I designed it to fight fascism and defend the motherland.

There are always two sides to every coin.
I'd wager the same is true for personal laptops, though. There are certainly many more 3D games than 3D editors, and many more video players than video editors.
It's possible motherboards can be compromised as well, though I've not seen so many reports as such. Another aspect to this is for a regular PC, you often install your own OS, while the tablets have a pre-built customized android,many many features locked down.
One of the biggest benefits of testing comes from writing the test prior to the implementation (TDD). In a statically typed language, your test won't compile until the implementation is there, meaning this process is less accessible to you.

Type systems focus on making sure you write the code correctly. They help not at all whether you're writing the correct code. In the end, this is on you, the developer, to express correctness in the type system. So the theory goes if you can define the problem correctly in, say, Haskel's type system, (up front, mind you), you may not even need any tests. But most systems are built with incomplete information. You can't know everything ahead of time. Often what is ultimately "correct" is to ship sooner rather than later, learning what is systemically correct as you go along. This is where dynamic languages do well.
Details Behind Unicorn Financings
Convenience is an incredibly powerful feature.
Since when has free software been a "purely academic field"? Or for that matter "non-commercial"?

The whole point of the free software movement is to ensure that users have liberty. That's not something that can be done from academia, it can only happen in the field.

As for non-commercial, did the OP forget to read the zeroth freedom? The freedom to run the program as you wish, for any purpose - that includes commercially.

Hell, the FSF says as much:

> “Free software” does not mean “noncommercial”. A free program must be available for commercial use, commercial development, and commercial distribution. Commercial development of free software is no longer unusual; such free commercial software is very important. You may have paid money to get copies of free software, or you may have obtained copies at no charge. But regardless of how you got your copies, you always have the freedom to copy and change the software, even to sell copies.
I'm not sure why you post this..
Journalists are not loosing their jobs due to automation. They are losing their jobs due to the greed of their corporate masters - who value profit over delivering news that can be trusted.

Being a real journalist is a far more creative work then being a programmer. Especially in fields like investigative journalism - you must be a 100,000X programmer if you think you can replace Glenn Greenwald with a bot.
I assuming chargers were eating energy after the phone was done charging, if they're not then this wouldn't be energy positive and isn't as exciting.
> Consider the task of debugging any arbitrary error where you have little more than a line number to go by. You now need to refactor the line just to find out which method invocation is causing the error.

That's a tooling issue. The right thing is to enhance the stack trace to give more than a line number, and the debugger to allow a more specific breakpoint.

> There are also readability issues with lines like these.

Maybe, but the biggest readability issue by far is when a class or function spills beyond a single screen. Avoiding that is worth a lot of cramped lines.
With all the careful routing of the "signals", the author seems like someone who might enjoy doing IC design work.
Reasons to consider a cartogram
Kissing News Bloopers
Windows 7 Blue Lite Edition 2016 Crack in Aero Version Free Download
Flux irl, building an IOT Hue clone
> If you're used to writing in the likes of javascript, python or ruby, Rust is a wonderful gateway drug to systems programming, and it's probably the most accessible alternative.

So what do you think of productivity in Rust vs python/ruby/js? Is it a lot slower to implement something in Rust? While it has a lot of high level features, it doesn't strike me as particularly concise compared to, say, haskell or python..
Yes, I know, and that's terrible. But SysV init was flawed by design as it didn't prevent e.g. race conditions between services.
I'm sympathetic to the sentiment that trying to acquire market share has caused Linux to forget its roots and end up in a sort of uncanny valley. However it's important to understand the forces that led to it so that we can do better in future.

Amassing a large user-base is a highly misguided aspiration for a purely academic field like Free Software. It really only makes sense if you're a commercial enterprise trying to make as much money as possible. The concept of "market share" is meaningless for something that's free (in the commercial sense).

It took me _years_ to internalize the importance of status in human relationships. Even if no money exchanges hands, much of human endeavor is motivated by the gain of status.

We hackers have this strange blind spot: we pride ourselves on focusing on only what is real, but we forget that 'real' money is just a social construct, a reified form of status. It's utterly blind to focus on this one form and ignore the real thing.

Open source software is just geopolitics by other means.

Related link: http://www.ribbonfarm.com/2016/02/11/minimum-viable-superorg...
Was there a good reason for the secrecy? I feel like revolting against it as a statement of dissatisfaction with the process.
source discussed here: https://news.ycombinator.com/item?id=10995948

previous discussion of this article: https://news.ycombinator.com/item?id=11095127
I wonder if it was trip to Siglufjörður, and he got there a day early.
Ask HN: What questions would you ask your interviewers?
What are the most important questions to ask prospective employers at an interview?

Or what are some questions you didn't, but wish you had?
Wherever oil goes, the stock market goes
At this point this is boiling down a subjective argument on readability and tradeoffs in tooling, so no point in continuing. Have a great day!
This talk by Andrés Duany is quite interesting as well: https://www.youtube.com/watch?v=rwd4Lq0Xvgc
Do you think he would trade that for a horse?
If the Java compiler doesn't run on android phones then it's only because no-one actually cares enough to make it do so. There's no reason you couldn't run a full IDE on an android device with a keyboard, mouse and big screen tethered to it and use it to work on programs for that device (including updates to the IDE itself), except that it would be dumb; nothing technically prevents you from doing that.
I don't know of any code review tool that uses those.

But I'd love to know. I asked http://programmers.stackexchange.com/q/256789/108980 a while ago.
It's good to see this happen. In this day and age i think all of us and especially scientists should be more morally conscious about the ethical implications of their work and not sell themselves when their research and tech are financed by war money or when their work becomes intellectual property of companies that deal in war. It's a double edged sword I know, but it's such a great shame. End rant.
Ok so you are happy with this?

Model
.where(...)
.foo { ... }
.flatten
.bar { ... }
.join(...)

In Visual studio it doesn't really make a difference from a debugging perspective. However in other debugging tools perhaps it does, and in that case I would tend to agree. But then this is a minor point, something that can be covered with a coding standard and linting the source.
I felt the same way. IGN though, so I suppose you could expect as much.
An Experimental Analysis of Self-Adjusting Computation (2006) [pdf]
This is my favorite part:

If a project offered a value of 10 times its estimated cost, no one would care if the actual cost to get it done were double the estimate. On the other hand, if expected value were only 10 percent greater than expected cost, lateness would be a disaster. Yes it would be a disaster, but instead of obsessing over “What’s the matter with those software folks who didn’t deliver on the schedule we gave them?” we need to ask instead “Why did we ever kick off a project with such marginal expected value?”

The message for us software developers is: try to work only on what I call strategic projects: projects whose expected value is much greater than their cost could possibly be. That means they need to continue to pay benefits well into the future.
Tradition. In early times you were only able to signal one bit at a time on one wire.
At that time there were also no consensus on the size of a byte in bits.
Someone should hack together C coroutines using Duff's device and throw it up there. It'd win handily, probably around 1ms. You've got around 100 million instructions to use in 1ms on that i7-4770 and no cache to hit, go nuts.
Ask HN: What's your favourite music album?
The gold fortune hiding in the ocean
I would ask: If a watermelon costs $5 dollars plus half the cost of a watermelon, how much does a watermelon cost?
Typically, a syntax is specified by BNF or similar.

Every programming language has syntax, not every programming language has static types.

I think you can separate these pretty cleanly.
The SOSP paper: https://research.facebook.com/publications/holistic-configur...

(The blog post links to the ACM Digital Library version, which is paywalled.)
VMS did not share memories throughout the cluster.
You say it's greed but worrying about profitability isn't optional, particularly when revenues decline as much as they have been in the newspaper industry.

When customers stop paying, fewer journalists have jobs.
Travel with a Vintage Train Around Canada
Ex Army Bomb Technician (EOD) here, now doing enterprise java / intranet stuff. Disclosure: I also used to work for one of iRobots competitors, Roboteam.

My speculation is that they also sold because they lost a 25 million dollar contract to Roboteam. It's a 7 year contract to the airforce for 200+ robots. IMHO, unless more services drop out of the joint robotics program, as the airforce did, it will likely be the last large government robotics contract for a very long time.
You don't have to go all the way to Thailand. Eastern Europe (and I do mean the part within the EU!) is livable on that salary or even as low as 500USD if you're really frugal and literally eat beans, oats and rice all day.
It says right in the article how many of them exist today. ~12k is a vanishingly small number though.
Couldn't agree more. Sandi Metz has an excellent talk touching on this topic. Developers exaggerated willingness to keep things DRY and elaborates a bit on why: it's one of the easiest things for a not-so-experienced developer to identify and one of the easiest things to teach.

Edit: One of the best quotes from that talk is (paraphrased): "The wrong abstraction is a lot more expensive than duplicated code". https://youtu.be/OMPfEXIlTVE
Couldn't agree more. Sandi Metz has an excellent talk touching on this topic. Developers exaggerated willingness to keep things DRY and elaborates a bit on why: it's one of the easiest things for a not-so-experienced developer to identify and one of the easiest things to teach.
Obviously I mean sharing (and everything else) without installing some 3rd party application from who knows where. I remember looking into that when I was testing an Xperia for some security system.

See, this is why I bloody hate when people call everything "app". There's a distinct difference between "a driver" and "an application". A driver can interface with applications or it can be bundled with one, but they're not the same thing. And I'm quite sure that "driver" you linked to operates on one-way application level similar to sending an email to the printer which then does all the work itself. And it has to use that "share" function, but I guess that's expected as there's no "print" one, heh.

And really, having an own DNS server is not only different effect (because it works only if you use that server, plus it can be circumvented more easily), but it's also a completely new element. Not very practical.

Admin account is the default on Windows. That's what you get when you install it (by default anyway) and using it doesn't void any warranties.

And that's not even all the things, heh.
This sounds like a remix of one of the many "internet is making us dumb" stories. If anything the existence of GPS, satellite, constantly updated maps, and now detailed 3D city maps makes our "cognitive maps" (whatever that means) far better now than in the past where our navigation was done from printed Rand McNally folding map.

The reality is there are a lot of impaired drivers on the road. May be they have been drinking, have early onset dementia, or just a mixture of prescription medications with undocumented side effects. A lot have spent half the time sending text messages on their phones. Whatever the circumstance, some of the tools we have now let them survive longer or at least pretend they know what they are doing.
Show HN: Docker Cloud API PHP Wrapper
> any problem that doesn't depend on high availability

Do you have any specific examples of resource-intensive computing problems (other than SETI@home) that do not depend on high availability? Seems a bit like a solution in search of a problem.

I like your example of the power grid as an explanation for how owners of small amounts of computing power might interact with the larger system and have an impact on market prices. But if the analogy truly holds, it would be a good indication of how negligible rewards would be to smaller entities (individuals running computers or smartphones).
Flash drives are sold in base-10 units. Nobody gets to see the base-2 nature of the internals.