skysight-inc/HackerNews huggingface dataset:
I agree to an extent. In corporates etc. you're going to be building from scratch because these things won't fit in with guidelines and it's easier to build from scratch. However, it's good for quickness when working on personal projects. That being said I do find this one a little overkill and more than what you'd probably want without creating custom builds etc. also some of the behaviour and styling doesn't work as I'd assume. For example, drop down isn't drop down, it's more like drop on.
It goes without saying that you have more leverage before signing a contract than afterward, and the contract is obviously open ended... I was just pointing out that it's a risk of the unknown that would be weighed against compensation by both parties so it's not totally clear to me that Zeni is out of line yet.
I quite like checked exceptions. They're actually one of the few things that keeps me writing java for more projects instead of switching more of my time to golang -- golang takes the far opposite approach, and with either returning error codes, or using golang's borderline untyped panic (yes, yes, you can panic typed errors... but it's an incredible PITA to try to construct an error type hierarchy and impossible do terse typed catch blocks with it) doesn't scale well for projects more than about 4ksloc in my experience.

Exceptions signatures, like anything else, need aggressive refactoring to remain a useful part of an API. Always remove throw declarations that aren't needed. Always refactor the exception type hierarchy as your project evolves to keep it sensible.

The worst of typed exceptions I've felt recently is the JGit API (don't get me wrong, JGit is an amazing piece of work; but its sharpest parts are the error handling). There's inchoate masses of IOExceptions from some pieces, JGitAPIExceptions in others, and none of them compose nicely so that when I do large amounts of work I can summarize the error handling up to a few types of conceptually similar problem. And several JGit commands throw checked exceptions for what are essentially fuck-ups in builder patterns, which have been compile-time issues every time I run into them, thus a source of huge irritation (these are prime examples of where you should use unchecked exceptions).

On the other hand, the project I was using that same JGit API in has been one of the best examples of why typed exceptions can be a good idea. This project grew out of a python->java rewrite, and so in the original translation used completely unchecked exceptions as a holdover from the python form. (Why rewrite? It needed to go cross-platform and I needed a stable git api; libgit2 still couldn't clone at the time, so it was jgit or gtfo.) And as I kept working on the project and writing test cases... time and time again, converting things to typed exceptions and refactoring the exception hierarchy paid huge dividends in code quality, huge improvements in API consistency, and raised the quality of tests and final product alike because similar error cases ended up with similar exception types, and tended towards similar handling as I refactored similar exceptions types into one... #wining.

tl;dr being irritated by methods that claim to throw too many exception types is good and healthy. The fix isn't to toss checked exceptions out the window: the fix is to take the pain, and use it to fuel a good API with a tightly controlled and easily understandable set of failure modes.
I nearly turned down my current job because they were using a default contract that had clauses like that in it. It also said that they have control over everything on my computer, despite the fact that the laptop I bring in for work is my own personal laptop.

I ended up spending about an hour with their lawyer reviewing and amending the contract until those kinds of clauses were completely taken out. Lucky the lawyer was very amenable to the changes.

Always read the fine print, and don't sign anything if you're at all uncomfortable with it.
Unless I'm misunderstanding what you are saying, this is not true. Instruction selection and data dependencies play a big role in the performance of a routine.

What is indeed true is that the x86(-64) ISA alone does not give you enough information to predict performance accurately. Furthermore, due to the interactions between the different subsystems (e.g, caches, OoO buffers, etc) it is essentially impossible to determine performance with cycle-accuracy. But it is still possible to have a first-order approximation, for a given microarchitecture, of what is going on underneath the CISC mask.
> If you tell me that I can experience live behavior changes in the browser as I type and all I have to do is defonce the reference to my program state I’d call that a clear win.

But your codebase is only ~20 lines.
AngelList darling MakeSpace raises $8M Series A
SpaceX, Hawthorne, CA (US citizen/permanent resident only, INTERN)

If you follow HN, you've heard about us. We are revolutionizing the "space space", launching spacecraft to the ISS:

* http://youtu.be/65zDaDSvIww

* http://youtu.be/3fDzvdEfSgc)

and developing a reusable launch system:

* http://youtu.be/0UjWqQPWmsY

* http://www.spacex.com/news/2014/04/29/first-stage-landing-vi...

and we need software engineers! If you want to work on real hardware that makes fire, check out our openings at http://www.spacex.com/careers/list
Graceful reload for uWSGI vassals
From a legal perspective, yes, there are more things to consider.

From a common sense perspective, ZeniMax AFAIK wasn't even working on VR at this time period other than Carmack dabbling in his own "free time", so this is a pretty naked attempt for them to make the claim that anything he worked on even remotely related to games is owned by them, which I have a huge issue with (even if it is a concept that holds legal water in some states).

I'd have more sympathy for ZeniMax if they were bullish on VR and Carmack was working on an official project for them in the VR space and then left for another company, but this doesn't look like that at all, this looks like a game company owned by a lawyer trying to get a big payday on an opportunity they previously missed the boat on, using tenuous legal technicalities.
I love how most of the HP calculators produce the same result, even between ones with different processors. This is because it uses an internal interpreted language, SystemRPL, to do most of its complex and trigonometric math functions. As long as the simple interpreter is correct, handling complex math functions is portable between models.

http://www.hpcalc.org/hp48/docs/programming/
Facebook will ban this almost immediately.
Robert Altman (CEO of ZeniMax) is an attorney. He knows they have just enough of a claim to muddy the waters and make life difficult for Oculus. He also knows Oculus is very likely to settle for more than they were offering him previously. This is exactly why people hate lawyers. Robert Altman of ZeniMax is an asshole.
No, it doesn't. Under the currently accepted, legally binding definition of Intellectual Property, that category includes far more than just code.

Note, I'm not saying ZeniMax owns a bit of Oculus or their IP. I don't have enough information to speculate meaningfully either way, and neither do you.
Chicago (remote possible) Full Time

Front-End Engineer at MarkITx

MarkITx is a growing startup looking for a front-end engineer to help us build web apps that will track, value and trade the world's datacenter hardware. We are disrupting the $312 billion secondary IT market and helping to make sure that equipment gets reused, not just recycled. We do that by bringing simplicity and transparency to a process that is currently painful, ugly and untrustworthy. We've got significant traction and funding, and have built one of the best teams in Chicago.

You'll craft readable, maintainable code that delivers a great user experience. You'll have primary responsibility for everything we send to the browser. Our team will support you with thoughtful UI/UX design and simple JSON REST APIs. You'll manage your projects and collaborate with the team primarily through GitHub and chat. With a fully automated test and deployment infrastructure, you'll ship several times a day, including your first day.

More details at http://jobs.markitx.com/#frontend
You make a good point. I was just hoping to lower the boundary between people thinking about reading more, and actually going to read more.
Sorry to hear you're having trouble.

Please email in to support @ agile bits . com, and mention my name please and that I asked you to email in. I'll get this all fixed up for you. Give a brief description of the error to jog my memory.

Kyle

AgileBits
I have only ever used it for the feature set similar to Splitwise, so I can't comment on the Mint like features. Sounds like a good plan though. I hope it works out for you!
Heads up, the domain in the email appears to be missing a u.
It's pretty obvious that they did this because people were being advised not to use IE - without specifying a version.

If they didn't update IE on XP then even IE on Win 7/8 would get hit by advice not to use it.
for help on APIS, go on API Craft Google Group or on APIscene.com
Right, the way I would read the Armadillo thing isn't as "Carmack knew he needed a documented exclusion clause to work on other stuff," but as "ZeniMax acquired id NOT Armadillo and that made a document setting the exclusion necessary.

Obviously, without seeing Carmack's contract, it's impossible to ascertain if he did agree that all work, in our out of the office, including ideas, belonged to ZeniMax.

And even then, the definition of work product could be argued in all kinds of ways. Is it only committed code, does it also include research and sketches. How does it extend to what is shared with others, etc.

Carmack has a good lawyer, I'm sure. Hopefully that lawyer also looked over his ZeniMax contract.
But it allows people to move forward using the syntax itself.

The implementation can be optimised at any point.
The mystery of the misaligned window widgets
(IANAL etc)

I don't think "work hours" is really an applicable concept for someone in Carmack's position - he's not a 9-to-5 worker, his life and work are surely much more entangled.

It's hard to deny that Carmack's involvement in VR was linked to his position at id (Zenimax by extension) in a way that Armadillo for example was not; if nothing else, he did talk (show?) Rift versions of id properties. However, his image, popularity, visibility and even open promotion of Oculus are not really at issue here, at most they would have been grounds for disciplinary action from Zenimax at the time.

It's up to Zenimax to prove exactly what sort of tangible, protected IP and 'know-how' was transferred to Oculus. During 2012 he tweeted often about his research on lag, and I imagine his work was more extensive than what he publicly disclosed. If there's any link between that work and any properties of Zenimax, say a computer, email address, code or assets owned by Zenimax and used in any way to do VR-related work that Oculus took advantage of (even if it's not in use today), then there will be blood, pain and tears.
I would assume Carmack did the usual programmer thing and just expected them to not be huge unreasonable assholes about future situations after his ZeniMax employment had ended.

This is a common mistake programmers make when dealing with lawyers and other corporate types who stand to gain money from being huge unreasonable assholes.
What I'm wondering is how many times is this going to happen? Where they're more-or-less forced to continue emergency patch mode for major vulns?
I don't think the unbundling is succeeding (or will succeed). I like them all in one place, though fb mgmt seems to have convinced itself that unbundling is a better user experience somehow..
A much better rule is something like "act as if you are deciding for everyone who can be expected to make similar decisions for similar reasons". This avoids that particular pitfall, because everyone who might decide to be a programmer for similar reasons is still not too big a fraction of the total world population, while still giving the right answer re: voting
They were going to stop selling it much earlier, but they became terrified about Linux getting a foothold in netbooks, which at the time were starting to become quite popular.
On the other hand, Linus is one of a handful of people in the world who may be in a position to get results by yelling at Intel engineers to 'make it go faster!'. This isn't because Intel is too ignorant to do things on their own, but because practically everything can be optimized further, and Linus may have enough sway to focus the engineers' attention on the problem that he wants solved.

Personally, I don't care much about the speed of the Linux kernel build system, but I do care about the speed with which page faults are handled by the CPU. Even if the chances of success are lower, if he is able to succeed in speeding up every page fault on future Intel processors, I would consider that a much greater good.

The real problem (as I see it) is that I think he's trying to optimize the wrong thing. His worst-case test is based on trying to repeatedly fault in an uncacheable page: every lookup TLB lookup fails at every level of the cache. Likely, Intel has chosen to optimize the real situation where page translations are cached when they are repeatedly accessed.
Too Many Tabs in your Browser? Try this cool trick to manage them
now if Yelp bought them for cheap..
If OpenSSL was written in a managed language, someone would need it in an environment a managed language wasn't suitable for, and end up porting it to C.
Out of curiosity, what are your apps?

I don't have any iOS devices--I'm just curious.
Indeed. Just like this:
http://thedailywtf.com/Articles/Serial-Port-Pit-Bull.aspx
Even if Zenimax is claiming to own John Carmack's work, under what supposition do they make the claim that they own the knowledge in his head. Assuming he did not break a non-comptet e clause, how is it that they can claim that because he gained knowledge of how VR systems work, while working for them that they own that knowledge in his head?

I understand typical IP policies, that they definitely own any code he wrote and are capable of patenting ideas generated by him in that work. This seems to step beyond that however (if indeed he used no code from id software at oculus).

Perhaps I am being naive, but as a software developer, this seems to me that they are attempting to set a dangerously non-competitive precedent. Under this logic, because I learned how to do advanced SQL queries over an internship (assuming a similar IP policy), I could never write SQL for any other company. That is a much simplified analogy and is likely missing some specifics, but I would honestly like to know the basis for this type of lawsuit.
I'm here ..

oh, axIon...
Good point. But I'll say that with React and ClojureScript you can make a very large code base where all the components manage their lifecycles in a way that is completely reloadable with little effort going into thinking about reloadability itself :)
That's nonsense. If anything, governments are guaranteed to break their own laws whenever it's most convenient for them. We absolutely need a communication system that cannot be governed by any government. It does not need to have an altruistic DRM implementation to work. It needs security so pointlessly difficult to break through that it'd be cheaper and easier to do analog surveillance.
Moreover, the Guardian is a news service with a relatively high standard of quality. They're not your typical CNN.
Load balancing with Vulcan and Etcd
As someone who was just thinking about this concept a week or two ago, I can tell you how I viewed the use case. (And kudos to the developer who actually followed through with building it, unlike me!)

To me, it's about subverting the chilling effect that occurs when you're about to say something online and you think "could someone potentially use these words against me?" Not only governments or enemies with grudges, but even future employers with hair-trigger sensitivity doing some kind of background review. Many of us (if not all of us) have opinions or perspectives that may make others uncomfortable, and it seems unfortunate when we censor ourselves for the sake of maintaining a pristine public image.

One solution is to simply say whatever you want and then, if you reach a point where you sense that your persona may come under scrutiny (perhaps you're applying for jobs), go back and remove any material that you feel might be used against you.

The other solution is this concept of self-deleting messages. Instead of having to go back and find all the things you said that could be liabilities, simply give these comments a maximum lifetime when you make them. It's an efficiency thing. You save yourself the worry of "ah god what if I forget I said this and someone finds it down the road" and you avoid neurosis keeping you silent when you should be able to speak your mind. It seems like a win-win to me.

Sure, if somebody REALLY wanted to preserve your statements on the internet, they could do that. And this tool would basically be useless for celebrities or anyone with a significant following. But most of us aren't those people. Our public faces rarely come under scrutiny, but it would be helpful to have a tool that makes it easier to manage when they do.
I'm not so much concerned that they may make a mistake and close a legitimate account. I think not paying for ads already served, and not responding to queries about it, is enough grounds to take them to court. If Google wants to respond and make an argument as to why they shouldn't be paying for the ads the publisher has served, then they would be free to do so- the problem is they have refused to do so, and I think it is perfectly legitimate for a a publisher to take them to small claims court and demand that explanation.

So yeah, what I probably should have said is, "It smells of fraud, plain and simple". I am open to hearing Google's side of the story.
Essentially, yes.

We figure that we can only really teach one thing: immersion and empathy with the communities we are trying to help. We can't really teach people how to develop products that people will really use, so we are trying to optimize for fellows who already have that skill.

We haven't selected the fellows yet, however, our fellows applicants include successful tech entrepreneurs, senior product owners at large tech companies (usually with engineering backgrounds), etc.
Thanks! Try it out and let me know what hit/missed. There are a surprising number of techniques for affecting IQ on iOS, so specific feedback is great.
YouTube actually offer to fix videos that the algos find to be shaky; I wonder if they are choosing not to run the fix or if it's failing (the vid I viewed has some really fast transient wobble that doesn't seem like normal camera shake).
Back to the future of databases
Lawrence Lessig starts a super PAC
Do what you love. Right now you're a kid: your room and board are taken care of; you have the freedom to try a million different things and see if you like them (heck, you might discover that you don't want to code for the rest of your life: that's alright too).

Read lots of code, and write lots of code, and have fun. If you're suited for it, you'll know.
Supreme Court ruling expands police authority in home searches
Timecube?
Exactly, if it isn't networked then it is basically just an appliance. Just as you don't need to update the software in your microwave oven, you probably don't need to update your CNC machine. The exception to this is probably new features, such as supporting new file formats perhaps.

There might be a slight concern that the CNC machine could be infected by USB-borne malware. The worse case there is probably just infecting other computers through additional USB sticks. That, or industrial sabotage, but that sort of threat was relatively unheard of until recently.
On the Brink in Brownsville
It may sound weird.. but these kind of tradeoffs work to our advantage. There are fundamental limits to performance, filesize, bandwidth that everyone has to deal with. The fact that it's such a high-dimensional space means we can find a niche and optimize for cases that current cameras are missing.
Microsoft is going to have to take a stand and make this the last XP patch (for anyone not paying for extended support like certain governments) forRealThisTime if they ever want to move on.

In this case, I can understand the reprieve, if only because it came like 20 days after the EOL. In fact, you almost wonder if this wasn't publicized until after the EOL in an attempt for malicious parties to do maximum damage.

But this won't be the last hole. Others will exist and if Microsoft doesn't stop from now on, it won't disappear until web standards change to such an extent that all versions of IE that run on XP won't render modern sites at all.

Kind of a good reason, in retrospect, to decouple the web browser from the OS, huh?
As long as we're sounding off, I grew up in Brandon. I'm over in Seattle now, though. What's the tech sector like in Winnipeg these days?
Yahoo ends support of “Do Not Track”
i only ask for slightly shorter class names
The link to the actual icons is non-obvious, and there's no preview.
> Tweeting that Oculus doesn't use any code written while Carmack was at Id is all well and good, but it's got nothing to do with the core issue. I'd hate to see Carmack accidentally admit to something that'll screw him over later.

I'm actually kind of shocked that he tweeted anything at all. Wouldn't his lawyer basically tell him not to say anything?
Very nice !

Is it worth having the code on github where people can do pull requests, track issues etc ?

It seems like this could use a bit more exposure.
Cheers for sharing.

Why didn't you guys focus on a mobile product vs rehashing stuff from a decade ago? Imagine a version of Facebook's AppLinks cross linked with your Call to Action. That would have been a big problem to solve.

The mobile is where the future is at when it comes to engagement.
I guess I can't edit a comment after a certain period of time but I wanted to augment this description with a similar position in another group at Exa (working on post-processing):

http://exa.com/software-engineer---application-development-c...
Dunno, probably a generic HMAC-based one if for some weird reason I felt the urge to implement a crypto system that worked this way. Could probably use KDF1 or another KDF in that family too. (Honestly, there's probably no good reason to do things this way, it's just not obviously broken or infeasable.)
Right. Of course, the fact that that advice came from DHS, which still has a ton of XP/IE6-based internal apps probably made it that much worse. The government is a big client. Having them move to another browser, even if they haven't agreed to upgrade all the clients to the new Windows yet, is just a bad idea.
I've heard good things about Leanpub[1], which recently announced Github integration[2] as an option alongside Dropbox and web-only.

[1] http://leanpub.com/

[2] http://blog.leanpub.com/2014/04/github-integration.html

There's also Gitbook[3] which encourages you to write in Markdown using the Git/GitHub workflow. They did a Show HN recently[4].

[3] http://www.gitbook.io/

[4] https://news.ycombinator.com/item?id=7524956