skysight-inc/HackerNews huggingface dataset:
The (amd.com) in parenthesis clarified the title somewhat, for me at least.
Swift was designed for coding user-facing applications, not internet utilities.
It's not as mature. Doesn't have the library and third party support. Does Apple use Mac OS for all its servers? They use Azure for some servers? That would imply they need the language to be cross-platform.
> typeof String('abc')
'string'
> typeof new String('abc')
'object'

Oh dear, I think I'm getting a migraine.
A liar's paradox, stochastically
As the famous misquoted saying goes, build it and they will come. Since the quote is always out of context, allow me to add, brag about it, and they will laugh. This is vaporware. This, whatever this is (more on that below), will not be ready in six months, and when something will be demoed in some future, we will all laugh at how it neither does all the grandiose promised bag of features, but whatever little it does, it does badly.

Hasn't Canonical learned not to overpromise and underdeliver? Examples are multiple, Juju, the Ubuntu Phone, etc.

Oh, and speaking about Juju and what Canonical hasn't learned, it appears it still hasn't learned that when it announces something, it has to explain in clear terms what it does. In the same vein that "Juju is DevOps distilled", LXD is everything and nothing. It's a hypervisor, but it's not really a hypervisor. Now I did my own research, and after heroic effort I think I understand what this supposedly is. Mind you, I am not sure, but here goes nothing.

LXD is tooling over Linux namespaces, cgroups and associated technology that uses CRIU, or something like CRIU (is CRIU even production-ready?) that manages containers, and can move containers between different hosts.

Now this is one phrase that I think everyone understands. Instead of this we got vague statements evoking delusions of grandeur, unwarranted comparisons to virtual machine, inappropriately and misleadingly using the word hypervisor, and mentions of Ceph and OpenStack. And we still haven't learned what the supposed hardware-integration is. They say they can't say because of contractual obligation. That sounds lame, but whatever, if they can't tell us what it is, why mention it at all? To check a buzzword from the list of used buzzwords?

Now what is the purpose of this thing? I genuinely don't know. What's wrong with docker? Docker can't move containers. Surely that can be solved (IFF it can be solved) easier than creating all this contraption from scratch. Docker is supposed to run processes while they seem to want to run full Linux distributions. Is that it? I don't know. Why do they even want to run full Linux distribution? We don't know. It might have something to do with the fact that this is what Juju expects. It might not, who knows.

I'll stop speculating here because we have very little to work with.
A requirement of a successful project/product is visibility. Ex-Googlers does not imply much more then "used to work there" but if it drives more attention to them, it's good MarCom.
I agree with this other than the lunch and learns. Leave their one break in the day out of it.
MySQL provides strong consistency when run on a single machine, but that breaks down when you handle failover using asynchronous replication between DCs.
CES 1994
This is the same security fallacy as I mentioned twice before, just reworded. Removing code does not leave you with secure code. There's still a memory allocator, I/O layer, a tcp/ip stack, DHCP protocol+service, HTTP protocol+service, HTTPS protocol+service (edit: sorry, there's no HTTPS support in Mirage), and all of the miscellaneous parts required to run those bits, which all have security concerns.

These are the exact same things you expose to vulnerability in a regular Unix OS, and have the exact same potential flaws. Code doesn't become more secure just because you have to use an ABI. Computers (and security) are not magic.

And provable security, really? First of all, proofs have bugs. Second, no real-world attackers have ever been stopped by a provably secure design (partly because implementation is never provably secure). And finally, Mirage was only written to be a statically-typed low-overhead binary that encourages more code reuse. It was not designed with security in mind. That shows that it's nowhere near provable security to begin with, and real-world attackers won't care either way.
What I've seen work is a combination of code reviews and ongoing continuing education.

----- CODE REVIEW SIDE -----

This can include automated tools, human interaction, and computer-assisted human interaction. To start with, pick a set of command code standards and style guidelines. Google has nice ones for many languages that you can use as a starting point (https://google-styleguide.googlecode.com/svn/trunk/).

Secondly, enforce them through automated tools (e.g. in a Java shop, these might include PMD, FindBugs, Checkstyle, etc). Have everyone install the IDE plugins for those tools (along with your common config). Incorporate them into your continuous integration build process. Perhaps put in place a static analysis tool like Sonar to send regular reports on code issues.

The human element would start by having someone review committed code before it's allowed to be merged downstream. Git's pull requests, along with diff view systems like GitHub's, make this easy... but you can use workable practices with Subversion or whatever also.

There are limits to "pull request"-based code reviews, though. When change sets grow too large, it's difficult for the reviewer to understand the high-level vision for the changes. You start reviewing the trees, rather than the forest. So I think you still need periodic in-person code reviews, to walk through the state of a codebase at certain milestones and discuss higher-level issues.

----- CONTINUING EDUCATION SIDE -----

The thing that I've seen work best here is a regular, ongoing lunch-and-learn type series. Take any of the standard code quality treatises (e.g. "Pragmatic Programmer", "Code Complete", "Clean Code", etc), and tackle a chapter per week. Better yet, split up the chapters and have the team members themselves present a chapter. It's great experience for them (if they're not TOO freaked out by public speaking), and you'll never learn something as deeply as you do through the process of teaching it to others.

The problem with lunch-n-learns is that you MUST have buy-in from management to make them a serious and ongoing part of your team culture. When deadlines are tight and there are fires to put out (and when are there not?), a lot of companies are quick to cancel that week's lunch-n-learn. When that happens, they lose traction and fall apart.
I am doubtfull Apple wants to compete with Google in search.

Or maybe it's a way for Steve Jobs to get a revenge post-mortem on Google for Android!
> the biggest one is probably performance, `new Foo` will always outperform `Object.create(FooProto)`.

He's right, `new` is more than 10x faster in Chrome and Firefox for me at least:

http://jsperf.com/create-new

Why would it `always outperform` though? Seems like an implementation detail. Object.create should be faster since it doesn't run a constructor.
A /24 for a company of their size is nothing - they actually have the entire 17.0.0.0/8 to themselves: http://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_addres...
It's legal. Ignore the people here saying it's "bad karma." What does that even mean? Presumably you'll be working for this company for a few years. You should pick the one you like the most. It's your next couple years, not the company's. They can always extend an offer to the next person in line.

That said, be careful, because there are extenuating circumstances. People do talk, especially in the same industry and city. Still, I highly doubt hiring manager at Y would reneg your offer if he heard from X that you chose Y over X. If anything he'd be happy!

Also note that if you got this job through your school's career network (alumni or otherwise), they may have policies in place that prohibit reneging on offers, and blacklist you if you do. Even then, though, you didn't sign anything.

I'm of the opinion that you should do what's best for yourself. This is your life, and the job will affect its foreseeable future. Make whatever decision you will regret the least in two years.

"If you can project yourself out to age 80 and sort of think, “What will I think at that time?” it gets you away from some of the daily pieces of confusion."

- Jeff Bezos on deciding to leave Wall St to start Amazon [1]

http://bijansabet.com/post/147533511/jeff-bezos-regret-minim...
Can you explain what that means? Which language features is Swift missing?
>The takeaway for me was that Apple has a whole /24 subnet to themselves. That's just ... immense, for a single company. Gaah

(I think you mean /8.) Brace yourself: http://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_addres...
Does anyone else read these articles and feel a tinge of jealousy? I'm hoping that someday one of my businesses will generate the kind of money that would make tax-hiding worthwhile.

As an aside, it's kind of nice to see the government's over-complicated tax code used against them.
I am an inactive member of (what could be categorized as Metafilter's tiny little brother - Monkeyfilter). MoFi is now, sadly, essentially dead but not gone.

The interesting thing about MoFi is that there are people there that I know more about from an online relationship than I know about most of the people I know in real life (that's an awkward sentence to parse, I know and I'm sorry about that). I once flew to LA for the weekend and hung out with a couple of them and am still in contact with them on Facebook. Their lives matter in ways that people whom I see on a daily basis don't.

Still mulling that over several years later.

We had an IRC channel for a while.

We tried starting our own radio station for a while.

The meetups are much rarer, but occasionally still happen.

Just thought you might be interested.
87 free online CS courses (MOOCs) that you can start this month (November 2014)
Emacs: The Software Engineer's Swiss Army Knife (1997)
> So far, I have seen requests from two IPs: 17.147.18.33 (7 on 2014-10-15) and
17.147.18.33 (7 on 2014-10-15)

One of these should be .35, judging by the logs that follow ;)
Venture capital is changing,and that’s giving tech entrepreneurs a big advantage
Personally I don't see anything wrong with suggesting to add a few hints, but the basis of that suggestion in this case was that "there's a lot more of us who could probably get the joke" with the hints. If making it approachable to more people is inherently a good thing, the logical conclusion is to make it approachable to everyone.

With code like this, the readability obviously isn't a high priority consideration and sometimes the exact opposite of the goal, with the impenetrability sometimes being part of its charm. This is Hacker News after all, and if your reaction to of a piece of code that describes itself as "an exercise in minimalism" is to leave a snarky comment about the lack of documentation, you should probably check your news elsewhere.

If you have any interest in the subject, the initial comment "just enough features to allow self-compilation and a bit more" should give the purpose of the code away. If not, it ought to have been a clear sign of dragons.
Perhaps a proxy designed for iOS testing?
A /24 is only 255 addresses...
Collection Data Structures in Swift
Soundcloud's UX Design
GitHub as your project management tool
Why shouldn't it be also usefull to track users ?
You can set up a weekly code review where you take turns letting each developer present a piece of code they wrote to the team, and then discuss and give feedback about that code.

Also direct them towards resources where they can learn clean code practices. Perhaps institute a monthly "book club" where you select books about good coding practices. I would suggest starting with Clean Code by Robert Martin
Go is a fantastic language for writing a crawler. I wrote the Showyou crawler in Go and it's both one of our highest load processes (and it's very efficient, trust me) and most stable.
The ever-wonderful Vyacheslav Egorov has a nice article on this:

http://mrale.ph/notes/constructor-vs-objectcreate.html
NAR Explains the Qualified Residential Mortgage Rule
Nexus 9 versus the iPad Air 2: Which is best for you?
If you're converting 5% of new visitors into customers, you're already doing well - setup some paid search on long-tail terms. Unique anniversary gifts, unique birthday gifts for outdoorsy folk, etc.
I bet this is because most of JS compilers are optimized in lower level for certain "popular" tasks, developers use to do.
Swift was designed to do everything - one language to rule them all. To quote from Apple's Swift page: "Swift is a successor to the C and Objective-C languages."

My guess would be that the webcrawler was started before Swift was allowed to escape from the Developer Tools enclave.
This is the best advice in the thread. Straight-forward honesty is often the best move in situations where you (think you) might be hurting (inconveniencing) someone. If you're worried about saying this, consider the fact that it means way less to your hiring manager that you spend the next two years at his/her company, than it does to you.
Because it's much easier to handle a cube-shaped baby.
I saw that as well. I was expecting a bad product pitch ("Whatcha need? Doesn't matter, don't even answer: our new $Thing does it all")

(Such a cynic)
I like Go, but fail to see how Swift and C++14 don't fit the bill as well.

EDIT: changed to a more constructive comment.
I think the issue for some (including myself) is that this revelation shows that the vulnerability of a compromised document is greater than the apparent contents of the document. It includes all keystrokes, which could expose other ideas the writer might have had (but discarded), etc. This fact makes me even less inclined to use Google docs.
This all depends on the environment you're working in. When we used to do lunch and learns they were on Fridays which were blocked off for side projects.

Plus half the time we did lunches it was as a team and we always ended up talking shop.

We also welcomed free food and had other people in the community come and speak. Now if you're in a culture where it's 100% coding 9 to 5 then I'd completely agree with you.
You’re forgetting Google is a global company. If they get a specific tax on content their simply going to drop the market to avoid such taxes spreading. They might even simply decide to avoid doing business in Germany entirely. Net result a worse compeditor shows up discuraging users and Bild loses even more money.
I find it odd that you rail against absolutes and then immediately turn around and defend your own.

If you meant that new is faster today, say so. That's not the same as "will always outperform".
Anybody else find that text shadow on the headings unbearable?
Awesome, bookmarked like it's 1999.

Seriously though the snippet for the forgetting-new protection in a constructor seems quite handy. It's always good to hear arguments from both sides of the fence.
Any chance I get I make an effort to suggest this book. There is also another book by Robert C. Martin which I suggest called The Clean Coder[2].

[2]http://amzn.com/0137081073
Back around 1990 I had a class /16 and I was just a 14 year old. Before the web explosion it was a different time. Domains used to be free back then too!
I spent 10 years "coaching" (that word... blech...) teams, and from my experience there's no easy answers. What works for one team at one point in time might be horrible for other groups. Having said that, here are some things that have worked for me:

* If some of the people on the team have more skills than others, you could try asking people to pair program for part of the day. You could try setting up a lab space for this if people are interested.

* Weekly brown bag sessions where you talk about a technical topic of interest. Let people on the team nominate ideas. Do it over lunch and have the company have food delivered. The better the food, the more people will want to attend.

* You should get an automated build in place, and encourage people to do some level of automated testing if they aren't already. Some people take this a step further and use the automated tests to help drive out the design (Test-Driven Development by Kent Beck is a good book on this topic).

* You could try starting a technical book club where people read a chapter a week, and then get together and discuss it over lunch. Given your situation, I'd strongly recommend starting with "The Practice of Programming" by Kernighan and Pike. Again, it helps a lot to have the company get good food delivered.

Don't make a million changes at once. I might start with the book club if I were in your position. None of this stuff will magically transform your team, but these kinds of things can start creating a culture where people start to care more about the quality of their work. You'll encounter people who have very strong religious feelings for or against any one of the things I listed above, usually based on some past experience. I've seen each of the above succeed big and fail hard with different groups. Just try what seems to make the most sense for your team.

One last note: when you try things, don't do stuff in fits and starts - talk with the team about what you're going to do, see if there's buy in, and if there is, commit to trying it for, say, four weeks. After the four week period is done, talk with the team about whether or not it's working for them, and if they'd like to stop or continue. Over time, you can add/remove/change more things in the same manner.

Good luck!
Why? Being an ex-googler could just as easily imply they were incompetent and fired.
I recently had an interview which was the worst of both worlds.

I was given a take home problem under the guise that they did not do live whiteboard coding interviews. I did the problem, and it was impressive enough to get me on the phone. I was impressive enough to get from the phone to an on-site.

What do you think happened at the on-site? Yup, standard whiteboard coding interviews. Nervousness and pressure means I didn't have a very good showing, although I did solve the problems.

Was told that very day that I wasn't going to be a good fit. Any feedback from the interview where we finally did talk about my solution to the take home problem would not have been taken into consideration as I was told it wasn't a fit right after that interview and nothing was said between the two people.

I really do think that the only thing they found out about me was that I can not do those sorts of problems while nervous and under pressure. What they didn't find out was anything about my actual abilities.
Ok, Google will face less damage than a possible publisher cartel. That's probably true.

But how is that supposed to 1. justify Google as a monopolist 2. legitimize the cartels rent seeking ambitions and 3. make that "a point"?
if they provide such an implementation and allow others to freely modify/adapt, them they can get more competitors, so is a risky business.
I work at a place that requires code review and has automated checkers for "code quality". Let me tell you the obvious : the best code I see has these problems, because the best code is the best code because it uses the language to it's maximum effect, which often precludes having perfect "style". The best code is tested in functional ways, which means that it doesn't have "good coverage", nor does it really use unit tests more than a little bit.

And the worst code I see, by people who learned to code a month ago or worse and don't know any algorithms (but feel like they know better than people who've studied algorithms and languages for years) almost without exception perfectly styled. It contains moronic errors like swapping variables around (because these programmers do not know how to use the type system), it contains 5 unit tests for every single little function, because that increases the lines of code metric that is so universally used. And the reason for half the lines of good is "good practices".

Here's how you recognize good code : firstly it is not possible to shorten it without causing a MAJOR disaster in the readability area. Every concern is properly separated out into it's own pieces of code, and aside from the (short) main function there is very little single-purpose code. The typing system is used well. Prices and amounts are NOT the same data type, for example, and cannot be obviously switched. Unit tests exist for core algorithmic pieces only and other than that there are system tests that confront the code with real-world situations while running almost the entire program, ideally under heavy load with half the backend unresponsive, and has a statement that says the test fails if it takes longer than 1/10th of a second. It implicitly follows and beautifully implements a design document that is not written in word, but in a 10 to 15 line comment on top of the file/class.

Note the issues :
1) hardcoding things
2) naming mistakes

Both of the issues you complain about can be fixed mechanically or with absolutely minimal supervision through refactoring. Yet next to all the comments below suggest DOUBLING the manual effort needed to get code into the repository. While automated fixing might be problemating, writing linters that detect these problems is trivial.

Unless of course the problem is that you feel that you need to fix how others program because you "know better", but can't actually write code checkers. In this case, why are you leading them ?

So well in that case I'd advise a slice of humble pie, and a compilers course.

> I review commits now and then and find some of these issues - but due to the nature and timeline of the project cannot do it for each and ever commit of course.

You sound like someone with an MBA. A programmer would recognize this for what is is : a problem screaming to be automated. Code commits can be made dependant on code checkers succeeding - just write the ones you want/need. Can't do that ? You're not a programmer - or at least not a good one - and stop whining about how difficult programming is - learn it first.
The name suggests that this is a dating app, was surprised that it wasn't.
Less about 'of their size' then about how long they've been around, since back in the days when a large company could get a /8, and just about anyone could get a /16.
You might find this guide to calculating subnets helpful. ;)

http://www.dslreports.com/faq/cisco/30.1_Quick_subnet_calcul...
It's absolutely awesome. It beats the typical crap on here about some start-up coming up with a not-really-needed solution to a millienial's already-cushy life.
People are curious simply because Apple is so damn secretive. I'm not sure I'd ever want to work there because it seems I would be unable to talk to anyone about my projects, ever.
Recap of Networking event held November 4th, 2014
I don't think so, it's only requesting HTML.
HP has two /8 subnets.
What's even weirder is that Eli Lilly (the pharmaceutical company) and Halliburton (the oil company) also both have one.

(as others have said, you mean /8)
How to Design an Embed Script