Meanwhile I can find and use the email address of your head of HR and include within my application a suggestion that I can help them move off archaic technology and attract candidates that want to work with forward looking companies.

Or I can just apply for a job with a forward looking company.

His wife is an idiot, she's driving away potentially great candidates with her artificial barrier to entry.

It launched for me after doing that, but didn't actually work. It ran in FireFox, using about 50% of one core of a 2.2GHz i7 (Haswell). The same game runs very happily on a 1GHz ARM core, but I don't know what percentage of the CPU it's using there. Aside from being slow, the UI really sucks (I managed to zoom in, but not to zoom out). On a touchscreen device, I really liked the Auralux UI.

DirectX came with some advantages as well though. Like OpenGL, you ended up with a slower game than writing specialised code for a specific graphics accelerator, but the trade was that you got to support all shipping accelerators (and ones that hadn't shipped yet) by allowing them to write the code once and get a speedup everywhere. With Direct2D, you got things like accelerated sprite drawing from hundreds of graphics cards that all had different interfaces for bit blits. This meant that your Direct2D game would often be faster than a DOS version that was talking to the VGA hardware (or SGVA via VESA) and doing the same thing entirely in software.

An abstraction layer that has a small cost but buys you acceleration support in exchange is worthwhile, because the net result is faster (and simpler) code. An abstraction layer that has a big cost and doesn't give you faster code much harder to justify.

If it's nondeterministic, yes. If it's 'you can change the stack pointer in this way with this sequence of instructions' then it may be easier.

Beyond a certain point, I agree. There's a world of difference in readability between code written by people who are comfortable typing and people who type very slowly. If typing is a chore, there's always a temptation to use very short variable and function names and avoid comments. If typing a comment is something you can do while you're thinking about what the next bit of code should do, then you end up with much more readable code because the tendency is to write a description of what the code should do (and, importantly, why) in a comment, and then write the code.

The 10 lines of code a day comes from an IBM report. Note that it's not just 10 lines written, it's 10 lines of bug-free code complete with documentation and tests, averaged over large projects. For each day that you're churning out thousands of lines of code, how many days are you (or someone else) finding and fixing bugs in that code?

It depends a lot on the data structures. There were a number of papers using TSX at EuroSys this year. The main conclusion was that TSX lets you get similar performance from simple approaches as you can get already from complex approaches. For example, you can protect a long linked list in a single lock and use HLE to get a big speedup with lots of concurrent insertions and accesses, but you can achieve similar performance with a fine-grained locking scheme. There was a nice paper about Cuckoo hashing where they initially found that TSX gave them a performance win, but then were able to get a similar speedup without it.

The big win with TSX is that it's pretty easy to reason about coarse-grained locking and much harder to reason about fine-grained locking. If you can make coarse-grained locking almost as fast as fine-grained, then that's a huge saving on testing and debugging time.

Possibly, although the described sequence sounds exactly like what happens in a ROP attach. In this case, giving the attacker the opportunity to incorrectly update the stack pointer may make the attack easier.

MPX doesn't help here either. It provides bounds checking by storing the bounds in a look-aside table that must be atomically updated if you have pointers that are visible to multiple threads, which means that every pointer store to a global must be wrapped in a transactional region (ooops, TSX doesn't work anymore, hopefully they'll have fixed it by the time MPX ships). It looks like the overhead of actually using MPX will be more - in terms of both speed and memory usage - than pure software approaches.

The only source I can find for that is Wikipedia, with the edit made by an anonymous user. Do you have anything a little bit more authoritative than that? 16 seems to be close to the sweet spot for integer registers, with enough that modern register allocation algorithms can do a good job, but not so many that context switches are overly expensive.

Not all ranges.

The club to which I belong only forbids uncontrolled bump fire. Meaning, if you have a bump fire stock, you can control it and it's allowed.

LK

The lady doth protest too much, methinks.

I greatly dislike prostitution. I regret that some people feel it's the only way they can earn a living. I would prefer that there wasn't a market for such services.

None of that makes me hate people that provide such services.
None of that makes me a bigoted twat that hates transgendered people for no reason other than my own ignorance.

I'd rather be a clown.

Terrorists in the newly declared 'Islamic State': 10,000ish
Terrorists supporting Hamas: 40,000ish

Lets assume that half the Muslim terrorists in the Middle East are inexplicably not aligned to either of the above causes.

Even those generous estimates leave the number of Muslim terrorists just half the size of the organisation actively bombing children, making people homeless and preventing a normal life for millions.

I guess I just have a different definition of 'terrorist' to you.

A lot of companies use Oracle E-Business Suite as their HR and/or payroll system. An EBS module is iRecruitment, which includes candidate web application capabilities.

Pretty much everything this article highlights as wrong with modern recruitment sites applies to iRecruitment. Even by EBS standards it's a horrific unusable mess and Oracle would do the world a favour if they deleted the code base and demanded all their customers remove the binaries.