skysight-inc/HackerNews huggingface dataset:
Samsung's yearly revenue is in excess of $300 billion/year and growing. About 2x Apple's.

Samsung Electronics is a division of Samsung and accounts for $186 billion/year.

Put another way, Samsung's Electronics division earns more revenue that all of Apple.
Grow your own dot colony
Since Google Reader shut down, I've basically switched my behaviour to subscribing to sites via email and especially looking out for good curated weekly emails.

Here are my favourites at the moment:

iOS Dev Weekly : https://iosdevweekly.com/

Data Science Weekly : http://www.datascienceweekly.org/

Clojure Gazette : http://www.clojuregazette.com/

Ruby Weekly : http://rubyweekly.com/

Green Ruby : http://greenruby.org/

Founders Cabin : http://founderscabin.io/

SaaS Weekly : http://hiten.com/issues/

Also, shameless plug, I just started a weekly newsletter about Machine Learning, Data Science, Data Engineering:

http://datacoder.aidanf.net/
Posting your company salaries does a few things:

1) It promotes mediocrity.
2) Creates a political cesspool.
3) Ties the hands of hiring team.

1 - Excellent people want to go places where they can make more. When excellent people learn about public salary postings the first thing they will worry about is the perception of other employees. I suspect they will just avoid conflict and work somewhere else. Really think about the current open salary systems: state governments, federal systems (cia, fbi..), school teachers, college systems, military..

2 - Will you help the "next" person above your salary grade? Why? Your goal is to be higher than he/she - so this promotes extremely bad behavior. This is how yahoo is setup. People will be trained to create little moats to protect power, inflate budgets, hide data, hurt other employees.

3 - Really want that new hire? Well, now you have no negotiation power. If you pay this employee salary X. Anyone who gets less than X (Call this Y) will be pushed down in the employee chain. So now, instead you want to minimize Y. Sublimity, you will hire less and less capable people to avoid conflict with the current team.
This is generally the position of the Rust team as well. It's also why the zero-overhead interop is important to us.
Looks uncomfortable and unhealthy. The wrists rest on the table and you hold your hands up.
They will have checked in. On any airline I have flown in the past 10 years, when you check in a multi-hop ticket, you are automatically checked in to your final destination.
Love coffee - used to work at a coffee related startup as well where we had access to the nicest machines and best, freshest roasts. I got extremely geeky about it for a few years. I have since calmed down on my consumption but have no plans on ever giving it up.

The one negative is that I become quite a miserable person if I don't have my morning cup before 9am. At that point it almost feels too late to recover with onset headaches almost inevitable. Even with that in mind I have no plans on trying to quit. Went cold turkey for about 3 months once just to prove I could do it, sucked for about 2-3 days then felt fine.
Thanks for the link, and here's one for you:
http://www.merriam-webster.com/dictionary/condescension

I neither believe nor wrote that if we can't start with a blank slate we might as well give up. Since I specialize in working with legacy code that's actually pretty much the opposite of what I do.

What I meant by "I won't hold my breath" is that C has an enormous lead in maturity, programmers, and installed software base. Displacing it because a writer at TechCrunch thinks C sucks and Rust is better is a different kind of fallacy. I'd be happy to see a safer language that didn't sacrifice expressive power, performance, and memory footprint. Many, many candidates have been floated since C made its debut, so either they have all been found wanting, or the obstacles to moving beyond C are bigger than just inventing a safer language. That was my point.
True, and if this story is true, it also surprises me in a nasty way because

a) I am Indian, and until now had largely thought that we were largely a privileged class within tech, if not outside it -- and consequently weren't affected by race issues within it.

b) All of the articles about how oh-so-wonderfully Automattic does their remote work had always led me to believe they were a forward-thinking, "good" company. If they are bringing up race in an interview it completely destroys this perception.
Tips to Help You Find Your First Apartment Rental
It's not only new, but there wasn't any user-facing documentation until a few weeks ago. I'd been waiting to make changes to the book until after beta, and the re-organization of the TOC I did made me realize that I was missing a few things, this and UFCS being the primary two.
Yeah, thanks for linking to this: the reason I didn't use it was mostly because it was longer than 18 lines :) Nice not to have to track and maintain a version of other people's code when you don't have to.
I wonder how Haskell DSL (I think one is called Atom) would fare on this.
Market value is the important metric here
Yes, wanting to put money in a physical asset which has utility value (like a property people can live in), especially when it is in genuine (rather than artificial) and difficult-to-reverse short supply (like property in London), does make financial sense.

I think of the Right to Buy as being a bit like giving away the family silver in return for a few transient votes, and in doing so committing your children to a future where they'll have to rent expensive stainless steel cutlery.
Google should insist on a browser without a back button.
> Personally, I don't find typing on a flat surface to be a very pleasant experience. As a touch typist, I depend on a certain amount of feedback to my fingers to identify when a key has been actuated, and I'm not always looking at my screen when I'm typing something out. With this device, how could I know the spacebar registered properly, and didn't accidentally send my cursor into another location due to an errant swipe of my thumb as it rests on the spacebar?

Well, you kind of answered yourself there

> Like [...] every tablet/phone in existance ?

Haptic feedback solve that particular issue. From what I understand some haptic technology like the one planned to use on steam console's controller also handle the "I need to feel where the keys are without looking", although I personally never experienced any of it first hand.

I agree with you that I still prefer an actual keyboard and space key on a laptop though
The World's First Innovation-First VC Firm
The table doesn't contain the location in the file, only a mapping of bit sequence to original sequence. LZW also doesn't contain information on where sequences are.

However, you could construct the compressed version of your search string and search for it (or in the case of LZW, generate it as you continue to search and decompress only small portions as needed).

Either way, you still have to go through the file. at least once.

EDIT: Actually, if your search string falls inside a compression block, it may be more difficult without uncompressing (and then discarding).
Rust can work with C without problems. It misses some low-level things (I can speak of allocators) but generally it should be possible to write Linux kernel driver with Rust for example.
I had the same experience as jtolj. A urinary tract infection that wouldn't go away, even after a couple of months of antibiotics (first one I don't remember, then cipro). Ejaculation would sometimes make it feel better. Sometimes worse. Finally saw a urologist that said he didn't believe it was caused by infection and that I should try pelvic floor Physio therapy. After the first week I felt so much better that I was convinced.

Whenenver I see someone mention it now I try to preach the physio gospel because when I was going through it there were a lot of negative sufferers posting to message boards saying it will never go away, etc.

Also women can suffer from a similar condition - chronic non bacterial urinary tract infections, and most of the pelvic floor physiotherapists are used to dealing with women. Maybe it is more common in women or the option is less known for men, or maybe men are more embarrassed to go see them.
So I've played this game a few hours yesterday, and more on the day it came out here.

I logged in this morning again for a quick game, and it appears you've considerably shrank the "worlds" into smaller spaces. The game has changed completely for me, as it's about 50/50 that I will survive the first 20 seconds. It's gotten extremely tight in there and there's no more room to maneuver. If you're a big cell, it's almost impossible to die, as there is now always a stream of little guys that get trapped, then sucked in.

I really had a lot of fun "exploring" the worlds and occasionally bumping into another cell, or just crossing paths yesterday. I could go on long chases that would last a few minutes, which was a lot of fun. As of now (I tried the 4 regions), it's basically a reflex game. Splitting in half to "attack" I think is the cornerstone of this game (if you want to get big, you have to risk a bit), but it's so crowded now that it's prohibitively expensive/risky to do so, which sucks.

A small thing to consider for user retention: if I've carefully built up my cell to a respectable size, I will try to play smart and not leave my computer, grab water, go to the washroom, because I'm invested. If I die every 3 minutes, it's easy for me to drop it, forget about it and move on. I spent 60-90 minutes in a single game yesterday, and didn't want to "lose my work", if you see what I mean.

Awesome work (I think the small upgrades on the theme, names, etc. is awesome), keep iterating - but I think I'm going to get back to productive stuff now, because the game has lost most of its appeal to me.
You're missing a key point. What makes Linux usable is that it has numerous drivers written for it... written in C. An OS's core is not supremely difficult to write. But the drivers are... Much specialized knowledge is required.
Ask HN: How to avoid giving a scathing code review?
For the past several hours I've been struggling to unravel a pull request from a newly hired coworker. It was apparent from a quick glance that it needed some work but I underestimated how bad it was. The main logic is in a monolithic ~400LOC function (in a dynamic language, not verbose Java or C) consisting of a deeply nested if/else spaghetti code. I wouldn't dare touching it with a 10 foot pole without tests but fortunately there are some and the original test coverage isn't bad. So I've cut it down to almost half the size so far but there's still way to go until it reaches a somewhat maintainable state. I've also found and fixed a few bugs along the way so strict refactoring is not even a goal at this point.

So I'm wondering how to go about this. A few code review comments here and there won't cut it. If I was to be brutally honest, I'd outright reject the PR and tell him to rewrite it from scratch in a clean way but that's probably not the ideal response. How do you deal with situations like this?
Same here. But it seems to be a thing.

Best email I got from a start-up that wanted to hire me went something like this: "We are a team of 5 MBAs with an idea and need you to be our employee #1 to build it!"

I mean 5 founders seems rather excessive to me but all of them MBAs and the only technical person will be an employee and not a co founder.
Like the direction this is going in, but true that its combining space and gesture area, not getting rid of the space bar.

I've thought that it would be more efficient, if one could keep ones fingers on the keyboard rows, and use the some type of thumb gestures to move the cursor.
>> Basically, what the other side is saying is that yes, negotiating is a skill, but the reason why our economy works so efficiently is that we instituted division of labor.

Understood, but division of labor is largely gray and only really gets divided when you move up the income chain (ie, the wealthier you are, the more things you can pay others to do to free up your time). Why learn how to make your bed or drive a car since technically you could pay other people to do those things for you? Professional athletes, musicians, and actors pay agents to negotiate their deals for them because they have much more at stake and it makes sense to bring on somebody who is an expert in contracts for specialized fields since its almost certainly a net win for both parties (talent and agent).

Unfortunately, engineering doesn't really pay enough to warrant bringing on an agent to negotiate on your behalf. So people can choose to wish that complete transparency existed and that we all make the same amount at each level of ability, or they can choose to accept that the job market is just that- a market. If you accept a salary of a certain rate and on certain terms, you are selling your services at an agreed-upon price. Just because somebody else asked for more and got it, doesn't change the fact that you were happy enough with the amount you agreed to work for and got it.

So really what we are talking about is wanting happiness with the amount you are paid regardless of whether it is enough to meet your personal needs. If the next person is making 10% more than you, then suddenly you are unhappy. There was a famous psychological experiment that actually verified this same thing- that people would generally be happier to make less money so long as somebody else in the same position isn't making more. That is not a net win for employees. In fact, those who can negotiate up their pay are probably helping the entire field of employees in that domain, since even if you are the bottom 50% of wage-earners in a high-paying field you are doing better than if everyone's pay remained stagnant at a lower level.
Ditching the iPhone for a FlipPhone
Must Watch – Power of Sound – Water Experiment
My understanding is you typically bootstrap the runtime for C/C++ when you write an OS. This is a significantly larger task for Go, to the point where I'd say it's probably infeasible (Is it possible to write the Go runtime in Go? Even the GC?).
Yeah, I didn't put anything there yet, but thanks for the heads-up.
Of course this replaces traditional TV. The time I spend watching TableTop I might have spend watching a traditional game show a decade ago. I talk with other people about what happened in the latest episodes. Those shows don't fill a vacuum - they replace something else. And that something is a certain part of traditional TV.

You are right that content produced for Youtube does not in general replace scripted drama/comedy. But that is only a tiny part of traditional TV.
> Solr, last I check was a bit complicated to cluster

SolrCloud, with Zookeeper, is relatively new and not too difficult to set up.
They never stopped providing components to Apple.

Every few months for several years Apple-centric blogs announced (wit glee) that Apple had abandoned Samsung for the upcoming generation of it's mobile CPU (Samsung makes lots of other components for Apple, but the A-series chips were always the focus of these stories) but I think the most that happened was Samsung and other fabs splitting production on certain items, which is probably a good planning anyway when dealing with that size of project.
It definitely makes a sharp difference. Pair that with a very clean and uncluttered desk, office, and you are golden.
Whereas I want a keyboard with two spacebars. How much simpler would shell command lines be if we could hit an 'command space' key which would mark the end of a shell argument array string.
imo this will be nightmare for both hands fast typists. Spacebar provides "anchor" for your hand. When you have bigger hands you can also put your thumbs under the spacebar in natural position to rest your hands.

There is so many better things to work on to be honest...
I think developers of web apps should be able have more control when back is pressed, but i use it all the time during normal browsing.
Airplanes already have an elaborate schedule for mandatory periodic service. Pressing a "reset" button once every 30 days is pretty trivial compared to dismantling the entire engine every couple of years.

What made this bug dangerous is that nobody knew about it, that's the main problem that needs to be solved.
Or you just use a 64 bit variable and don't ever bother with this again in mankinds existence in this galaxy.
I don't think that's really true? Certainly Go has a much weighter runtime than those. Neither C nor C++ implicitly insert context switches into the runtime into the generated code, nor do they have garbage collectors that scan the processes memory.
Perhaps it's worthwhile to have a mild counterbalance to the tendency to spend an ever increasing amount of other people's money.

It's not like "better service" is a driving force behind any government, ever.
That would be pretty awesome. Mock up: http://imgur.com/k2Iee5B
More likely: 0.8 times what you'd make elsewhere but a significant chunk of equity (0.0001% or so, vesting over 5 years...).
The 17-Year-Old, Award-Winning, Rube Goldberg Parts Manufacturer
حيل بسيطة لتنظيف المنزل
Fiber to non-dense rural locations would almost certainly cost more than you are willing to pay, which is part of the reason you pay that much for the little you are getting now (the other being a lack of competition since the market is too small to support much diversity). There are plenty of bridges to nowhere that we can apply capital too, but they won't be good investments.
The Planck keyboard design splits up the spacebar into multiple meta keys. It's a much nicer use of space: http://i.imgur.com/7nSlhyQ.png
About how long does it take to create the index, maybe compared to a zgrep? Could it be parallelized with something like `parallel --pipe`?

I haven't tried yet, but this seems like a great tool.
Actually the two named example given, Napster and Kazaa, where out-litigated.

See http://en.wikipedia.org/wiki/Napster

> Initially Napster lost the case in the District Court but then appealed to the U.S. Court of Appeals for the Ninth Circuit. Although it was clear that Napster could potentially have commercially significant non-infringing uses, the Ninth Circuit upheld the District Court's decision. Immediately after, the District Court commanded Napster to keep track of the activities of its network and to restrict access to infringing material when informed of that material's location. Napster wasn't able to comply and thus had to close down its service in July 2001

And http://en.wikipedia.org/wiki/Kazaa (not quoting a particular paragraph in this one as the "lawsuit" section is very long covering several countries, but it basically turns to "kazaa lost, started settling with all plaintiffs and agreed to turn into yet another legal music selling service clone").
GitHub repo with all of the code: https://github.com/mrfloya/thesis-ba

Most interesting part of the thesis, for me, is page 42:

> In this case it was even an advantage that the Rust version was developed last since it revealed a critical error in the other implementations.

Null strikes again!
Why not get rid of the touchpad, and use a pointing stick like the Thinkpad?
Market value != buying power.

The point is, people get too enamored with Apple and lose all sense of perspective. The notion of Apple buying out Samsung is so absurd that it provides an almost scary demonstration of this effect.
Why not store the log files in an FM-index? (https://en.wikipedia.org/wiki/FM-index)
I agree that this is a non-answer for most people, but my response was to read it RFC style, -- "The ACLU MAY delete the information you send" (i.e. implies that they will keep it for as long as they want, and at the current low cost of storage, probably forever).
Those times when C compilers did obvious translation to machine code are long gone. Now compilers are super-smart and can inline functions, throw away code _they_ think is not needed, replace loops with vector instructions and list goes on. It's really hard to tell what's happening at a low level for a given C code.
On a related note, //Mother's// Day is close at hand ..

http://mshop.nationalgeographic.com/html/catalog/photogaller...
> Writing Rust programs (vs. writing C programs) correctly is hard!

To be clear: getting Rust programs past the compiler is much harder that C programs: C doesn't incorporate much type-system/static checking so a lot more gets past the compilers. But writing truly correct C programs (i.e. don't crash horribly) is a harder task, as there's no computer assistance for avoiding large classes of possible bugs.

> failing to free a pointer is rarely one of them

> we can't be bothered to free our pointers

Solving this "problem" is not the goal of Rust. Rust aims to avoid undefined behaviour by default, e.g. derefencing invalid pointers, use-after-free, iterator invalidation are statically ensured to never happen, unless you opt-in at specific locations via `unsafe`. Cleaning up memory automatically is a nice feature, but the main draw card and the reason Rust might actually be interesting is that Rust offers memory safety without garbage collection.

In any case, I think you're being overly glib about the problems of C: it's so so easy to have a program that exhibits undefined behaviour, and so is theoretically operating with no restrictions.
Distributed Read-Write Mutex in Go
OpenBSD's privsep file(1) ported to Linux seccomp-bpf
This is great.

Reminds me of Game Dev Tycoon's developers releasing a cracked version of the game onto torrent sites where you'd always lose due to players pirating your game [0]. When I heard what they did I sort of thought it was stupid, but the chart at the end where they show that 90+% of the users of the game were playing the pirated version is somewhat chilling. Kind of makes me want to release a version of games I make to pirate sites (well, if I ever went indie... this would be a very hard sell anywhere I've ever worked), just to get similar usage information, although it's probably a mistake, as the information would only bother me.

[0]: http://www.greenheartgames.com/2013/04/29/what-happens-when-...
I wonder what would've happened with the results if biicode would've been used as deps/package manager for C.
Pachyderm (YC W15) is hiring our first engineer to build a modern Hadoop
Pachyderm (YC W15) - SF Bay Area

We're building an open source ecosystem of infrastructure tools for collaborating on large-scale data analytics. Learn what we're about: https://medium.com/pachyderm-data/lets-build-a-modern-hadoop-4fc160f8d74f

Looking for our first hire (company is just founders right now). Smart, ambitious engineers who think there should be a better alternative to Hadoop. Our codebase is written in Go, but Go experience isn't required.

pachyderm.io

github.com/pachyderm/pfs

Email: jobs@pachyderm.io
Surprise loser? I'd say surprise winner: now their citizens won't have large EU companies suing their government when it tries to, well, govern.
Cmder is great, I only wish I had more use for it
> always know your DB

True, but Elasticsearch is not intended to be a permanent datastore.
Interesting response. Loathe recuiters? Let's take it easy on the echo chamber cliche here. Yeah, lots of bad apples out there, but ask any reasonable professional: a good recruiter is extremely valuable.

You did forget that there are 2 types of recruiters: agency (outside) and corporate (inside).

I, the agency recruiter, do not want to "dislodge" the candidate for the minimum amount required. Not because my fee will be higher with a greater salary, but because I'm actually incentivized to do what is best for both the employer & employee. This is called sales. When you do good by all parties to the transaction, it pays dividends long-term.

So, no, we're not trying to "snag" them. I appreciate your paranoia, as you're not alone; many people dealing with bad recruiters probably need to vent.

But for the most part, your perception of the recruiting industry is different from the reality.