skysight-inc/HackerNews huggingface dataset:
At the limit, `unsafe` blocks would still be necessary for any FFI used to call into C code, which is trivially proven unsafe.

It's mistaken to think of `unsafe` as a novel language feature. All other languages merely defer their unsafe shenanigans to native C calls. I can just as easily write a memory-unsafe program in Python. In Rust, we use `unsafe` to hoist logic out of C wherever possible, to make our code even more safe; even the unsafe dialect of Rust is safer than C.
Yeah, those are layers in the image. That image [1] (727MB) is built on buildpack-deps [2] (695MB) which is itself built on the base jessie (154MB).

It would be pretty straightforward to adapt those Dockerfiles to create an image which includes only the dependencies for building node. It would end up looking a lot like 'node:slim' [3] (288MB).

Ideally, Docker will eventually have the functionality to more easily strip out transient requirements like build dependencies from the final images.

1: https://github.com/docker-library/node/blob/013858ac35afb9ca...

2: https://github.com/docker-library/buildpack-deps/blob/a201b1...

3: https://github.com/docker-library/node/blob/013858ac35afb9ca...
The Grand Budapest Hotel / Büyük Budapeşte Oteli
A fair observation. In the example of handling HTML input, I would suppose that's not a problem with individual developers, but a problem with the industry. Such a relaxed format should not have been allowed to exist, if the industry cared about its software products being as robust as possible.

I'm failing to think of any avionics application that might handle HTML, but avionics systems do have their own formats to deal with. ARINC 661, for example, is an XML file format for transmitting graphical display elements:

http://en.wikipedia.org/wiki/ARINC_661

Of course, all uses of ARINC 661 data are thoroughly tested. I'm not sure I would go so far as to describe it as a "toy problem", but it certainly does intentionally limit the problem domain to exactly what needs to be dealt with. Malformed ARINC 661 data received would just be discarded, not tried to be displayed in the best possible way even if it wasn't quite right, because that would be unacceptable; the problem would be with whoever was sending the malformed data.

Anyway, you're quite right though; without a precise and unambiguous format definition, you can only go so far down the path of robustness.
> I don't think most people believe in climate change

True in the US. Not true in countries where the political system is not to such an extent corrupted, poisoned and perverted by Big Money.
edit: Nevermind - you're totally right, and I'm totally wrong - I didn't think it through, and didn't realize that since relativity helps you less and less as you decelerate, the amount of fuel required does increase hugely if you actually want to stop at your destination.

Unedited original post follows:

> to actually stop yourself you need an exponential amount of fuel, because you need to accelerate half of it just to stop yourself

Hang on, I don't understand this part. First, you're right, I didn't think about deceleration - but that only doubles the trip length at most, since you have to accelerate halfway, then decelerate halfway. And probably not even exactly that if you're carrying your fuel, since deceleration will be a little bit easier - you've burned some gas, so there's less mass to push around.

And you're right, I didn't think about the drag - but that actually works out better for extragalactic visitors! There isn't as much stuff there to stop them when they're taking off, and once they hit a galaxy, it actually helps them decelerate. (Again, my dreamy eyes are ignoring the practical hazards of this "help" which might just turn them into a fast moving gas cloud.)
Talking about Deep Learning, Geoffrey Hinton did a AMA on Reddit not too long ago: http://www.reddit.com/r/MachineLearning/comments/2lmo0l/ama_...
At the Bay Area Vision Meeting in 2013 [1], Fei-Fei Li and Olga
Russakovsky gave a related talk on, "Analysis of Large-Scale Visual
Recognition" [2,3]

[1] http://bavm2013.splashthat.com/

[2] video: http://www.youtube.com/watch?v=DK6KfUsVN8w

[3] slides: http://bavm2013.splashthat.com/img/events/46439/assets/a10b....
Yep, I generally use the amazon app store on mine since it's reputable and has the main android apps I want e.g. Netflix, Shazam ...
Content:

- Lose the weaknesses paragraph, and all the personal stuff. It makes you look amateurish

- In the work experience section, talk about specifics of what you personally did, not about the companies

Design:

- The text under your name at the top looks cut-off

- Lose the white-text-on-pastel buttons. Use columns to spacially organize prose vs keywords

- clicking on a named anchor makes the section I clicked in be hidden underneath the floating top bar
It means that caching is often more trouble than it’s worth.
Queues help you scale horizontally. Basically, you can put a lot of kitchen sinks on the right side of the diagrams. Of course, this is done with careful design of the application and not just adding a queue alone.

OT: The hardest part I have found with queue design is task cancellation. How does one 'cancel' tasks that are already in the queue or being processed? I haven't come across a good framework that solves this cleanly. For example, if I queue up a task X in the queue. The task now need to be 'cancelled'. How can I ensure this? Looks like I need some sort of messaging bus?
Are you implying it's not fair that the KKK doesn't have some way to uncloak the identity of the person who uncloaked their identities?
I tried to get into various CAD applications at various points in time and never managed to "get it". It was mostly about the interface, you just have to invest a lot of time (more than I was willing to spend) to get even remotely useful results.

OpenSCAD on the other hand immediately clicked - at least for me as a programmer. I just had to look up the available primitives and combine them to my liking. This totally jibes with my mental model of the thing I want to build and parametrizing your models is pretty easy.

My main gripe with OpenSCAD is that it is missing good features to generate more "organic" shapes, i.e. beveled edges and rounded corners require a lot of work. They are possible (i.e. with Minkowski sums) but the resulting complex shapes quickly bring the engine to its knees.
Here's some rules that almost every designer I know ignores:

1) Map out your interface and interaction trees first

1-click - most common actions

2-clicks - second most common actions

3-clicks - power user level stuff

Put the most commonly used stuff at 1-click or interaction. If you don't know what goes at 2 and 3 clicks in, you don't understand how the application is used, because you don't understand what the most common interactions are. If you've run out of room for the 1-click stuff in your UI, then your UI concept is poorly designed. Keep iterating and collecting information until you can fulfill this.

Don't put anything at more than 3 clicks in.

2) Double the number of interaction points in the UI. Assume the application will grow and add features. If you optimize your design for the number of features you have today, you'll have no where to put all the stuff you're going to get over the application lifetime and it'll all just end up getting buried in menus. I've seen lots of gorgeously, carefully, designed applications die a year in because of this.

Double everything and see if that number of interaction points still fits within your concept, that way the interface has room to grow without getting messy.

3) Don't make your users interpret, make them understand.

If your concerned about how universally an icon is interpreted across cultures, you're doing it wrong. Interpretation is an additional step your users have to go through to use your UI, it's like putting everything at 2, 3 and 4 clicks in because they now have to not only look and scan the UI for what they want, they need to figure out what each interface item means before they can interact with it.

Even worse, as they grow to become accustomed to your UI, they're going to end up memorizing location and placement of options because the interface widgets take too long to interpret. Get 2 revisions down the road and you move a button and wham your tech support calls jump 50% because the users never bothered to remember what the symbol for their action looked like, just where it was on the screen.

4) Everything must be discoverable. This is why the world moved to GUIs from CLIs. Don't make your users play a 1990's era adventure game where they have to click every pixel on the screen to see if they can advance their usage. The Flat UI trend is notorious for this.

5) Consistency rules. Also see #3.

6) Eliminate Steps. Map out how many steps certain actions are. Cut them down to as few as possible. I remember one time going through a file import process with a tool, by the time you got the file imported the user had to navigate 27 different steps! Almost every step required minimal or no user input. Nobody had ever bothered to map out the interaction patterns in the tool before but users were constantly complaining about how difficult it was to use.

We reworked the workflow and got it down to 3 steps and user-engagement jumped triple digits.

6) After you've addressed 1-6, make it look nice.
Yes definitely, and the thesis should discuss in detail the role of the Illuminati in getting systemd adopted, and provide a by-the-minute protocol of what went down at Area 51.
So, the right are a bunch of blible-thumping, big-business-loving, climate denialists, whereas the left are a bunch of GMO haters.

Maybe this species is too dumb to survive after all.
> I majored in engineering — it’s almost a badge of
pride to build something that looks awful.

I dislike this attitude, for me it is very reminiscent of the way people just shut down when math comes up. "I hate math" and that's it. I'm not a math person, my brain doesn't work that way. On and on. There is even a perverse sort of pride in it. Why not do the work, why not try to get better, why not try to expand into things we're not good at yet.
1920x1920, hands down. (higher numbers also accepted, as long as 1:1)
How is this PDF different from the info from the main site: http://www.deeplearning.net/tutorial/ ?
Did Philae drill the comet?
First, Little's Law[1] can be mentioned as a formalized version of the "red arrow" in the blog post. It's true you cannot increase subsystem capacity (peak throughput) by adding queues.

However, queues can "fix" an overload in one sense by making an engineering tradeoff of increased latency and additional complexity (e.g. SPOF[2]). Peak capacity handling didn't increase but overall server utilization can be maximized because jobs waiting in a queue will eventually soak up resources running at less than 100% capacity.

If response time (or job completion time) remains a fixed engineering constraint, queues will not magically solve that.

[1]http://en.wikipedia.org/wiki/Little%27s_law

[2]http://en.wikipedia.org/wiki/Single_point_of_failure
On https://www.hackerschool.com/faq they say
"International applicants
I'm not a US citizen. Can I do Hacker School?
Yes, assuming you can legally be in New York for the entirety of the batch (just under three months). We don't pay you, and we're not an official academic institution, so you shouldn't need a work or student visa. We've had people come from more than 25 countries to do Hacker School."

Alternatively, start your own?
http://hackerretreat.com/europe-alternative-hacker-school/
http://www.cnn.com/2013/07/17/tech/teenager-hacker-school-af...
Sci-fi framed as a murder mystery? There's a good bet it was an Asimov novel :-P
Stars are the best proof of how rare intelligent life is. Allowing such a conspicuous waste of energy is proof that no intelligent life is near the star - it is similar to the way that finding thousands of gold coins scatted on a street is proof that there are no humans nearby.
An easy way to play around with parametric or specification based custom manufacturing is by making custom food (like sandwiches) for people, but only accept orders in a standard computer readable format.

Interesting questions are raised. Is there a limit to topping counts? Is there an implied order to toppings? If toppings have a cost, do you calculate that as the supplier or leave that to the consumer? How do you make sure an order is vegetarian? What do you do if you can't fulfill an order due to topping shortage?

Also, if it's that kind of party, people will start making their own food order generators, raising another set of interesting questions.
> The criticism about allowing routes to repeat in the express array shows that even after doing all this work, the Netflix team still doesn’t understand how express works.

Wouldn't a better solution, in this context, be to aggregate values under the same key?
With some attitudes, no amount of evidence would be convincing.
A mechanical engineer knows about the properties
of the metals, plastics, etc. he uses. A
civil engineer knows about strengths of
steel I-beams, etc. An electrical engineer
knows about capacities of cables, switches,
etc. So, these engineers can do real
engineering and have transmissions run,
electric power networks provide the power,
and tall buildings and long bridges stand.

A software engineer knows about the capacity
of a server? With what I/O rate, TCP/IP data rate,
memory locality of reference, independent
threads, memory that can be effectively cached,
the memory usage, errors and their consequences?

E.g., one of the problems of doing optimization
of assigning programs to servers in a server farm is
knowing what (1) the servers can do, also considering
other programs the server is running, and (2) what
resources the software needs, and it's too
tough to know either and, then, in a significantly
large and complex server farm, fully to exploit
this data for full optimization.

Software engineers are working with at best rubber
specs on both the resources they have and
the resources they will be using.
So, can't really do engineering on the
work, e.g., really can guarantee next to
nothing. Or, would you want to bet
the life of your wife or daughter on
some software doing its work without errors
and on time? Neither would I!
Many Older Brains Have Plasticity, but in a Different Place
You can't misuse closed source APIs? How would you know something is O(n) without seeing the source code?
AtScript are working with TypeScript and supersets it.

If you look at that TypeScipr PR, you see it closes an issue and they reference (2 months ago) Flow there.
tl;dr:

* Netflix had a bug in their code.

* But Express.js should throw an error when multiple route handlers are given identical paths.

* Also, Express.js should use a different data structure to store route handlers. EDIT: HN commentors disagree.

* node.js CPU Flame Graphs (http://www.brendangregg.com/blog/2014-09-17/node-flame-graph...) are awesome!
>then other people have to maintain said things.

No they don't.
Do you still use it on a regular basis. I got mine on the first day it released and admittedly back then there were some issues e.g. lack of 4g and some software instability but it has gotten better and more stable with every update.

I obviously stuck with it where you decided not too and I can understand why but I would urge you to give it a second chance.
I'm not talking about the time it takes, but the mass of the fuel. Which is more than just doubled.

That is what equations tell you: http://math.ucr.edu/home/baez/physics/Relativity/SR/rocket.h... ( scroll to How much fuel is needed? )
How to Pull Off the Belted Scarf Trend
I am not saying the functionality is useless, but it already exists in other languages. Why force C# to look and behave like F# instead of just using F#?
Korg volca sample SDK – a sample and sequence encoding library
Also, catastrophic collisions with other bodies would be more frequent when those bodies are closer together. Even if there is no direct interaction, nearby massive objects could still perturb the orbits of distant objects--similar to those in our Oort Cloud and Kuiper Belt--enough to make them impact planets orbiting closer to the star.
Oh, no, I guess I didn’t express myself properly. It is obvious that they were slaves. I was asking if the significant would actually be necessary in that case. And if it wouldn't be, what is significant implying in this definition? Does current slavery allow for more personal liberties that old fashion slavery.
Takeaways from Knockout JS
I agree.

Some monitoring is needed, if spinning up additional workers doesn't help (the bottleneck isn't CPU), then profile one of your workers, and find out what the bottleneck is, and fix it. Is one job spending lots of time waiting on a DB query? Add an index.

I suppose queues aren't really the problem so much as using a queue to decouple your systems so you don't have to think about the slow parts. If you decouple things, you still need monitoring.
> It’s been 65 years since the invention of the integrated circuit, but we still have billions of these guys around, whirring and clicking and breaking. It’s only now that we are on the cusp of the switch to fully solid-state computing.

Am I missing something, or should it read "hard disk" rather than "integrated circuit" here?
"It’s a humiliating experience to witness that people have so much respect and admiration for an experienced male developer, but there’s no place for you because you’re female and a beginner."

This is where I stopped reading.
> Environmental scientists do have a habit of flying all round the world

Maybe because worldwide scientific activities would grind to a halt if we suddenly went back to three masted schooners and bullock carts.
Interesting perspective. Internally we don't consider ourselves an eCommerce company, we just happen to have our eComm capabilities up first. Thanks for bringing this to my attention. Knowing our path, it seems like a no brainer to us, but as you said to the outsider there's quite a different picture. This is the first time we've had to elucidate our intentions, it helps to have a new perspective on it.
this is why the express team actively rejects any features or support for dynamically changing middleware and routes during runtime.
It wasn't a personal insult if I was addressing the quality of the comment made, just as you are doing for me.
Ask HN: Got scammed by startup company, how to find a Delaware lawyer?
Group of 4 remote full-time developers including me got scammed by employer, a startup company registered in Delaware.

Employer haven't paid for 2 months using lame excuses about visit to a bank, sending fake payment references.

We're located across the world and never thought about situation like that, have no idea how to protect ourselves.

We tried to contact founders, investors to solve this issue. Radio silence.

Should we look for a lawyer or a labor comission? How to find a good lawyer in Delaware?

Any ideas or help are very appreciated.
I wonder what the impact is on performance of routinely wrapping your types in Option<T>?

I am assuming it is minimal, because the struct would remain on the stack, and the object on the heap. There is just an unwrapping and wrapping cost but no more than Nullable? However this may be a naive view.

I like the syntax though. Where I work we use Code Contracts. This reduces bugs due to nulls but sometimes 25% of the code is Contract.XXX(...) which is annoying to read. And more typing too.
Dragon Age Inquisition, Controls, and Disability
This blog post is an insult to every developer out there. The blogger actually want us to believe that he just overheard a conversation, went home, googled what ever he said he heard and in 7 months became an expert and landed a job. So in my professional opinion, and i do get to say that as opposed to the blogger since i actually studied Computer science and been a developer for 20 YEARS, that his story is a work of fiction, or the company that hired him is one of those startups that just hires anyone that walks in the door like most of them these days. A developer needs time not just to learn a language, trust me once you learn one you learned em all, you just need to get used to the new environment and light changes in syntax. What you need time for is to learn the LOGIC of our trade and learn how to fix errors and how to improve/optimize your code. And all of these things come with time and effort and no amount of facebook posts or reading books could teach you that.
I'm involved with a 9 year old C# project, it has seen almost every version of C#. When generics turned up that was nice, then LINQ, very nice, etc, etc. I like to see how far I can bend the language in general, but that wasn't the main driver.

Over the past few years I've done some Haskell and also we've started creating satellite projects around our core project that are developed in F#. F# has been great to work with, and I love how a few key language decisions can make whole classes of bugs disappear. It's frustrating to run back into those bugs when returning to C#.

It's great to see the direction that C# is going in, it's clearly going toward a more centrist position midway between OO and functional. But a few key things won't go away, ever. null for example, won't ever leave the language. Mutable first won't either. And because of this I'm always trying to think of ways of removing those classes of bugs that hurt the most.

This library is currently just a pet weekend project (so it's exactly 5 days old at the moment). But I would like to take it further if there's enough interest. As I say in the introduction, I know it won't sit well with plenty of people, and that's fine.
V8 literally compiles regexps to X86 machine code the first time they are executed. They are not compiled into an FSA that gets walked in the traditional sense.

Hopefully that lowers your concern level.
> Programmers often get criticized for their fruit salad GUIs, but usually that's the result of having to present plenty of options and data.

Simplicity is only one kind of beauty. It's certainly possible to have a gorgeous interface that still presents a ton of options and data. You often see these in sci-fi movies, like Oblivion, and the aesthetic is in fact about hyper-complexity:
http://www.josephychan.com/Oblivion
not exactly highly endorsed https://twitter.com/tjholowaychuk/status/382084838179614721
An interesting corollary of that logic is that if suddenly this sovereign interest was spanning the whole Earth (instead of being fragmented into over a hundred countries), then there would be bigger incentives to strong-arm a solution to this problem more quickly.
You could use a VPN, or Picky Pint could encrypt its connection... does it?
> What this means in practice is that companies that use open source extensively in their operation, become slower and slower to innovate as they are carrying the weight of a thousand different systems of checks on code quality and robustness, which people using closed source will start delivering faster and faster as they effectively partition the review/quality question to the person selling them the software and they focus on their product innovation.

To contrast with what you said, I've worked at Microsoft, which is almost the company that invented NIH and we had the same problem. I think it's because, to paraphrase Alan Perlis, programming nowadays is less about building pyramids than fitting fluctuating myriads of simpler organisms into place.
rec.arts.sf.written used to be good for story IDs. http://www.steelypips.org/sfwrittenfaq/#01

I'm not sure if there is already a sub-reddit for story ids.