skysight-inc/HackerNews huggingface dataset:
> Why should anyone pick Rust over Swift when Swift will be able to do everything Rust can do and is also positioned as a systems programming language?

Well, honestly, that's just what I thought about C/C++ in comparison to some 'newer' programming languages like Go, Rust (and also Swift, maybe? I don't know enough about Swift yet).

Personally, I would only use Swift if there was an easy way to write cross-platform (mobile) software with it. It's as simple as that.
"Grindhouse Wetware"

...that company name
I don't even go that far, I usually just add a field hidden with CSS that rejects the form if there's anything in it. Works perfectly.
It was my discussion topic for a security extra course. I am curious to hear some more discussion:) In particular about the key-pinning, I think Bizantine Consensus should be the only way to handle the public keys delivery. Trusting "at least" one of pinned CAs looks only mildly better than what is out there now.
> The problem is that you never find out because if someone bombs the coding part you simply chuckle and say "well that person is clearly a liar, or something!" and they don't go any further in the hiring process.

This. I've been job-hunting lately and getting asked to do "technical challenges" and such like, which are useless to me because they are entirely asymmetric. They tell me nothing about the company except they are following the latest fad in candidate screening.

I pointed out in feedback to one of the testing companies a while back that they had no empirical basis for believing their evaluations didn't reject more qualified candidates for less qualified ones in terms of ability to do the actual job, I got a reply saying, "No, we have all kinds of empirical data! Our clients save $TIME in the hiring process!"

Which is great until you realize that perfectly competent engineers are being locked out of the hiring process by this nonsense. We saw a fad for this kind of testing in the mid-90's, just as the dot-com boom was starting to roll, and it didn't end well. The few companies I interviewed at that used coding tests of one kind or another all failed quickly, although it did give me the opportunity to ask an incompetent hiring manager at one of them how I'd managed to get a PhD in physics while having "below average mathematical abilities" according to one of their tests (which I swear had been written by an innumerate.)

HR people will simply assert that anyone who fails these kinds of tests is incompetent, and anyone who complains about it is just expressing sour grapes at their own failure, but that all side-steps the issue that there is no significant empirical validation on the quality of hires that such tests produce.

Their only real use from my point of view is that if the "interview" process is heavy on "coding challenges" and the like, I'm a lot less likely to bother with going through it, because it speaks to a company that has bought into policies that have no empirical basis and that provide the least amount of information to job seekers, and I'm not all that interested in working in the kind of monocultures such processes produce.

For senior people my favoured interview form is to mostly talk about a few obscure language features in their language of choice, and then have a free-form discussion about language design. Senior people who are any good care about languages, and have thought about languages, and can have nuanced, intelligent discussions about languages and the trade-offs involved. It acts as a good foundation for talking about other kinds of design issues as well. For junior people, some basic test of coding competency may be useful, but over the intermediate level they are very likely testing for the wrong thing, and either way we have no evidence.
Amen. I do fairly decent on a whiteboard given some practice, but I still feel stupid compared to sitting and coding on my own without massive time pressure.
Your language changing literally every other day is a problem unique to a pre-1.0 language. You're right that technical debt in general is not.

> And presumably Rust will continue to evolve, will it not?

Right, but it will evolve in a backwards-compatible way, rather than in a "the fundamental semantics of the language have changed Yet Again" kind of way.
OpenBSD was amazing when it still fit my server needs. I was very impressed. I would go back in a heartbeat if I could.

Any old and generic box will love it. It has ridiculously low resource demands and generic hardware will ensure you have no esoteric driver problems.
SO THESE INDIANS MAN. YOU EVER WORK WITH INDIANS?! THEY SAY YES TO EVERYTHING! DOESN'T MATTER IF THEY UNDERSTAND IT OR NOT. OH MY GOD, NEVER AGAIN.

Actual quote from an interview ^
This is so dumb cheap Mark! This is an open source project and everything is open in the wild while we stated several times there is no source code protection on our Github page.

Second time you are doing this the same cheap way. Congrats!
+1, Im confused why this is "The maybe worst..."
So you want super laid back people who surround themselves with productive geniuses.
Fast Functional Lists, Hash-Lists, Deques and Variable Length Arrays (2002) [pdf]
It'll probably make a lot more sense when you have a majority of cars that can act as a swarm rather than having to tolerate irrational and unpredictable human drivers. I can imagine there will be eventually some sort of standard for near field communication of autonomous drivers that can give hints about behavior rather than needing to infer them. Doesn't even need to be trusted or authenticated, a driver can just make more detailed signals than the human readable yellow and red lights that we currently use. Even just being able to say that you'll be turning in 1KM would make things significantly more efficient to navigate around. It extends even further if you want to have drivers like ambulances and fire trucks to have "sudo" powers, autonomous drivers can get themselves into a formation to allow the vehicle through before it is even visible over the horizon.
Apple removes games with Confederate flags
Come by some time and see :)

We also give free bootcamps and lectures here, as well as have occasional guest speakers (Chef, CoreOS, etc).

The only real downside is sometimes all the available seats/tables get occupied by people working on stuff, so it helps to get here when we open (10am).
Do you mean that they should "get ready for dry season" or "do it quick before it's too late"?
Sequencing the Black Rhinoceros Genome
Apple has used them for "real" purposes since the dawn of the very first Internet services offered by the company. It's not recent.
You can do much more easier, automated filtering: Ask candidate to submit link to any of the followings:

1. Github a/c

2. StackOverflow a/c

3. Their blog

4. Anything they made online

If candidate fails to submit link for any of above then just don't interview them. I would guesstimate this simple check filters out 70% of the junk resume and probably 20% of the good resumes. It can scale like crazy and expanded even more (for example, use APIs to get their profile information and rank resumes).
That makes it sound like https://github.com/ProjectMAC/propagators
Microsoft has private offices with doors, or did when I was there. Some offices were shared with two desks on opposite walls. On the other coast, I had an office at DuPont too.
I understand your base viewpoint. Nevertheless, you are still incorrect; many hundreds if not thousands of executable programs provide you with your experience, if you're using linux, osx, or windows; every executable on your system is capable of interacting with outside sources of malevolence, be that the network, usb drives, bluetooth anything, files that you got via e-mail; and if anything, personal machines need even more vigilance and patchability, as their attack surface is radically larger than your average server.

The ability to update common components is a boon. Seriously. Not without concerns or flaws, as you correctly note. But overall, it's radically better than the alternative.
Nope! You can work on whatever you want, and keep it to yourself if you choose.
Here we go again, coding with Emoji's
Apple pulls Civil War games showing the Confederate flag from its App Store
As a matter of interest, does your company also ask managers to go through a management test as part of the hiring process? Let them run a team for twenty minutes or an hour and evaluate them on that basis? If not, why not? :-)

I think "take-home" style tests are the only reasonable way to evaluate this kind of technical competency. They are the closest to realistic. Throw people a small problem of the kind they'll actually be asked to work on. Let 'em deal with it--including documenting their solution!
There is a whole bunch of implementations of The Little Schemer (and other great Lisp books) in Clojure here: http://juliangamble.com/blog/2012/07/13/amazing-lisp-books-l...
When i consulted for microsoft i expected an office with a door i could shut. what i got was quite literally called the boiler room. it was worse than the open plan in that the other consultants were all on unrelated projects so we had little we could talk to each other about.

there were no windows, and so many computers that it was very noisy and hot.

Now when i interview i ask to be shown where i would sit.
Amazon landed the largest address transfer that I'm aware of to date (a /10) when du Pont chopped up 52/8. Reddit mentioned it, but I didn't see news on it:

https://www.reddit.com/r/networking/comments/2tc4ss/looks_li...
I would argue that body hacking is when you experiment with the functions —and metrics— of your own body.

Adding electronics should classify as body modifications or cyborging.
Is there anyone with a BGR subpixel-order monitor who has been able to configure Atom (or VS code for that matter) to do the right kind of antialiasing?
Literally every single person on this thread agrees: if you're going to rewrite code by hand, you wouldn't deploy something like Wasabi. Wasabi exists entirely to facilitate not rewriting.

You've also got several current and former FC'ers on this thread, all? of whom don't like Wasabi as a language, all saying that from a pure cost/benefit perspective, Wasabi paid off.
40-45, yes. I don't think drivers are going to like having all of these slow-moving vehicles around, but, it'll be good training for the cars to see how pissed off human drivers are constantly attempting to pass.
ICEs are not crashes due to memory unsafety, they are logical errors in the compiler code.

For example, here's about the worst rustc crash I've found: https://github.com/rust-lang/rust/issues/21946. It doesn't even give you an ICE, it terminates with a stack overflow.

So no, Rust cannot magically fix logic errors in large, complicated codebases, but that's not something that a complete beginner needs to worry about thankfully.
World accessible devices is a pretty scary concept. If you have your garage door controlled by an ESP8266 it would take a single host to denial of service attack it, maybe even just one server to denial of service attack every garage door in the united states.
Pretty cool intro vid. A breath of fresh air from the typical startup/product videos I encounter everywhere. I'm excited to see how this progresses. The development appears to be extremely active, with frequent + quality updates. Spotted the new-ish Office Code Pro[1] font in use too...

[1]https://github.com/nathco/Office-Code-Pro
However, I don't think there's a conclusion to be made about the actual method used here. I suspect that it worked because it was different, not because it carried a fundamentally strong signal. If everyone did this, project descriptions would be gamed even more than resumes—it would select for people who prepared for the selection process² more than anything else.

I find myself almost irresistably drawn towards the conclusion that people will game the hiring process, because it is a game. It has winners and losers. Everybody is trying to make themselves look better than everybody else, even to the point of making themselves look better than they really are: Job candidates, employers, internal and external recruiters, everybody who is selling a hiring product, etc. Everybody is trying to emphasize their positives and hide their negatives, while searching for the negatives of the others.

A drawback to "do your own thing" is that it is enormously inefficient for candidates, and the results may turn out to be based on the luck of a particular candidate guessing a particular employer's game is, or being generally better at games.

I don't know a solution. What strikes me is that as broken as the system seems, we still manage to hire good people most of the time.
Ohhh, I thought the target was CLR. I didn't realize it was a transpiler.
That would be for creating textures. Most 3d objects in games are really 2d images applied to 3d surfaces. Although photoshop has some pretty robust 3d capabilities these days so maybe that is part of the workflow.
Yes, the more I read it, the more I think that that the intent of the law (that is, the intent of the people who wrote it) was for everyone to get subsidies but that the law was written in a such a way as to basically blackmail states to get in line and set up their own exchanges. When that did not happen (that is, when the refusing states banded together and believed they could sink the legislation by doing so), the IRS interpreted it the way they saw fit to make the original intent of the law be in effect.

The more I read it, the more it appears that this is an example of the Democrats having it both ways. The backpedaling sounds like a way of avoiding saying as much.
"One reason is that the average skill level of programmers who know Ruby is higher than those who know Java, for example."

Had to double check the year on this one. Things must certainly have changed... For instance, Java is a staple of most CS curriculum. If not Java then often Python. /Never/ have I heard of Ruby being the primary language of choice by a CS department. (Nothing against Ruby, just an observation.)

On the other hand, what is the most popular language/framework for a beginning programmer to learn today? Ruby/Rails or Node? Whereas Java is the quintessential Corporate language.

I'm obviously making some generalizations here. But things certainly seemed to have changed a lot!
Photoshop 3D has been a thing for a while.

https://helpx.adobe.com/photoshop/how-to/3d-overview-photosh...

Photoshop to generate lightweight mocks and objects -> C4D generates scenes (and/or objects) -> Unity for animation or interactivity
Not just other cars, but pedestrians too. It's common around here to see people trying to jam themselves into closing subway doors, often getting limbs or bags stuck in them. It's also not uncommon to see people try to help them by attempting to hold open or pry open the doors. One can imagine what some people will act like when they start to believe that cars will stop whenever they run out in front of them.
> The great tragedy is that since 9/11 Sikhs have often been mistaken for afgans/arabs wearing turbans & discriminated against.

The greater tragedy is discrimination against Arabs based on racism and faulty heuristics for what a 'terrorist' looks like.
I think perceived performance problems of today are caused by the incremental evolution of legacy systems leading to rube goldberg machines, not due to how fast a programming language can execute.
US Government credential dump discovered by Recorded Future
Show HN: SMS shoppable network for instagram, ads and products
This is great stuff. As VR design becomes more common I hope that there will be some more resources on the topic of 3D UX. can anybody link to any active forums on the topic?
What if I've never had a linkedin because of all their repeated data security issues?

Your comment sort of sounds like a shill post, fyi.
It is always best to be platform agnostic.

Web dev?

Try learning at various levels: Ruby/Rails, Node/Express, Php/Laravel.
Swift is an applications programming language where the runtime is non-optional (at least AFAICT) and memory is managed dynamically. It will be competing with .Net and Java, not with C and C++ (though, as ever, there are surely plenty of C++ projects that don't actually need C++'s level of control and could benefit from a rewrite in Swift).

Swift isn't going to penetrate to the bottom of the stack with pervasive reference counting. You'd either have to start managing memory manually (as per C) or implement a borrow checker (as per Rust), and even then your entire ecosystem is still going to use reference counting pervasively due to the language's defaults. One of the benefits of Rust defaulting to linear types and borrowed references is that it creates an entire package ecosystem where dynamic memory management is the exception, not the rule.

For the record, I think Swift is super fantastic as a language and I'm thrilled that it's going open-source. I think the two languages will work swimmingly together. :)
> "X doesn't do Y" "Did you really want Y"?

> Of course they do, they just complained about it.

It's just a rhetorical way of saying "I don't understand why that is a problem", and a request for explanation. I would say that's a pretty reasonable response to "I found this is a problem".
No.

I support the taxi drivers.
There are times when the plot changes and for example, in a romance, characters may switch from using surnames to first names. I've seen many low quality subtitles where the character will use another character's last name, but the translation will use the first name. While it does require some knowledge of Japanese (or other Asian cultures), it does contribute to the overall consumption of the anime, and only distracts from the attempted transition from Japanese culture to Western culture as translated.
Your Devices Will Soon Be Listening to You
Most crashes are in type inference, associated types handling, and error recovery, which are very complicated things, especially in combination. We also basically rushed features in for 1.0.0 (1.1/1.2 should be much better in terms of these).
Not the GP, but I focus on tradeoffs and roads not taken. Get them to talk about a project they've worked on, and then ask about alternative design decisions around some interesting feature and see what they say.

Example: I developed a little state-machine framework for managing complexity in a large, legacy code-base. It allowed me to refactor a lot of ad hoc distributed logic into the transition table and clean up a lot of weird corner cases that made the code fragile and difficult to change.

Questions might include: "Why did you write your own rather than use an existing state machine framework like the one in boost?" (for C++ frameworks there's pretty much always one in boost, so even if you don't know anything about the area you can throw this in for fun and see what they say). Also: "Why a state machine rather than some other approach to refactoring?" And so on. This process gets at taste and good judgement, it gives you a sense of how tolerant of alternatives they are, and so on.

Additional edit: one of the things I look for in answers is people who say, "Yeah, that particular decision might have been a mistake... I always wondered what would have happened if instead I had..." Good developers are able to admit that not everything they do is perfect, and are willing to give alternative views a bit of credence.
How to Structure Stock Options for Millions in Tax Savings
Taxi drivers violence against UberPop
I am criticized far more often for being mentally ill than for being bisexual.
Fo’ shizzle.
You perhaps should give some hints on your field of expertise: webapps? phone apps? embedded programming? droids?
Also I would ask them to create it as a pull request on Github push it to a branch in a private repo. Another 10% of candidates gone. (There might be overlap with the guys who don't have Github presence and anything online but you get my point.)
well worth reading for the insight into behind the scenes at FogBugz - some depressingly clear headed and awkward discussions undoubtedly had. and one suspects another lesson - don't have your whole company dependant on one product.

I still adhere to the idea that LOC is debt and LOTests is capital.
That's just a vanilla "divergence" stack overflow - an essentially harmless consequence of the type-system's Turing-completeness.
No. There's no benefit that I can see to limiting yourself to a single language if you don't have to.
Working with more experienced colleagues, and having them code review my stuff. Not always easy on the ego, but it made me a much better programmer.

Note well, though, that they need to actually know better than you do, not just have different opinions.
It would be a better comparison if we knew across how many nodes they're sustaining that. Maybe they just have 4,000 nodes doing 1k TPS each.
What a clever idea! My very first thought was "bullshit!" when I saw the title on HN but after my actual brain had a real chance to think about it I immediately reversed course.

It's cool to think that an interpreted language running in a browser can actually fix hardware, for a certain definition of fix.
Linux, /etc/init.d/ or /etc/rc.d/init.d/
Fortunately there is a market where they can sell the parts they don't need. It could make for a nice quarterly bump if they ever do it.
I'm in California. A state with its own exchange.

If this ruling had gone the other way, it would have affected me eventually. I would not expect Congress to do anything, and the state of California may not have been able to react quick enough with state legislation to stabilize things.

There would have been a domino effect as more people in red states cancelled their insurance and left only the very sick with insurance. The effect would have reached the states with their own exchanges. The whole thing would have likely collapsed.
One may wonder why all these changes in Erlang/OTP 18.0? The reason, as the chapter by ferd states, is lock contention.

Often, when you enabled the `lcnt` subsystem to find lock conflicts in busy systems, you would run into the timer wheel lock. Removing that improves parallelism in the system considerably.

And once you decide to take a stab at the time API, why not solve other problems around it as well, now you are working on fixing parts of it?
I really wish all cars would drive 25 mph on residential streets. The big limiter on car travel time is timing of traffic signals and overall road capacity, not top speed.

It’s very common around me for cars to be driving on semi-arterial residential streets (with official speed limit 25) at 55+ mph at 2 AM, which is both noisy and potentially unsafe: there’s low visibility at night and at that speed it would be hard to maneuver out of the way if there was something moved into the road.

If we had smaller cheaper lighter-weight cars which maxed at 25 mph on residential streets, plus maybe some of those 15–20 mph electric bikes which are everywhere in China, plus fast, frequent, and reliable mass transit, there’d be little negative impact on routine chores and commuting, but huge improvements in pedestrian and cyclist safety.
Sikhs are the warriors of India - they have been India's guardians and the hardest working and friendliest people. They are revered all across India and referred to as "Sardarji" - which is an honorific meaning "Commander" or "Leader".
I feel lucky to have our little /27 colo block.

We added IPv6 support to our firewall product earlier this year and it was a big deal - lots of schema and code changes to deal with 128 bit wide addresses and address math. I'd encourage any devs working on new products to bake it in from v1 if you can.
Heaviside's name hasn't faded entirely. The step function is named after him.
Actually, I did the same thing as you.
Not sure what makes me happy, but I know what doesn't, and I don't think I'll end up working with code again.
That seems... less good honestly, but gotta start some where I guess. Friends-network effect should grow weaker with time (or at first big drama blowup).