skysight-inc/HackerNews huggingface dataset:
yah they should've done something like:

send(JSONSerialization.with(StringSerializer.class, DateTimeSerializer.class).serialize(JSONObjectFactory.put(PairFactory.of(String.class, String.class).getInstance("author", "system"), PairFactory.of(String.class, String.class).getInstance("message", "Only json is allowed"), PairFactory.of(String.class, DateTime.class).getInstance("time", new Date())).getInstance()))

no, it's just json4s dsl for constructing json. If you wanted, you could've used constructors yourself:

send(pretty(render(JObject(List(JField("author", JString("system")), JField("message", JString("Only json allowed")), JField("time", JString(new DateTime().getTime().toString()))))

usually scala libraries come with an easy to read/write DSL version of the API along with a more verbose java-style API shown above. Many libraries don't document with a plenty of examples. But, it really takes 10 minutes to learn DSL version in many cases. And, it gives you wings. There are plenty of benefits of DSL. You can research online about them.
Mars mission is a month away - The Hindu
I've heard very good things about this book:
"A Mentoring Course on Smalltalk" [1]

[1] http://www.amazon.com/A-Mentoring-Course-on-Smalltalk/dp/B00...

Edit: better link
Somehow I don't think the original poster cares about your criticism. Or will make it past the first sentence.
My two cents. You'll never be able to match the scroll smoothly listening for scroll events. Use requestAnimationFrame and listen for changes in window.scrollTop.
omg, just ran that in perl. epic.
Phonebloks - A phone worth keeping
Watch This Woman Age Decades in Just 5 Minutes [Danielle]
Very fun to look at :) Though I'm not sure about what novel insights one might get from this work.

Also, I wonder why there's a nice rectangular cluster of tweets around Japan.
Agreed. This article is very one-sided, and after posting a calmly worded comment regarding Linus's standpoint[1] on his attitude, it was deleted. The article is simply link bait and is not professional journalism.

That being said, I have more confidence in Linus's knowledge regarding /dev/random. Mostly because XOR in this context is secure:

1. XOR is an incredibly powerful encryption algorithm (not primitive); one of the best we have. The problem with XOR is that you MUST use a UNIQUE one time pad (that is the length of the data) for every message AND you need to be able to securely transmit that one time pad. AES CTR is effectively using AES to create a one time pad for XOR encryption, as an example.

2. The prior steps are effectively creating a irrecoverable OTP meaning that any malicious intent in RRAND is effectively encrypted away.

[1]: http://marc.info/?l=linux-kernel&m=137391223711946&w=2
Nice ad hominem. Using vi before any of us was born does not mean you avoided the classic "vim newbie" mistake.
Apple switched to Intel processors in 2006, but maintained support for running PowerPC apps on Intel processors up until OS X Lion shipped, in 2011. Apple kept compatibility with a completely different processor architecture for half a decade. When I got my first Intel Mac, I just copied over all my PowerPC binaries, and they ran fine. It was unbelievable.

And this wasn't even the first time. Recall the 68k emulator that shipped in all classic PowerPC Macs.

Both Microsoft and Apple deserve enormous credit for their compatibility work. But Apple deserves special mention for shepherding the Mac through three completely different architectures (68k->PPC->x86) while maintaining excellent compatibility at each transition. Windows has also gone through significant transitions, but within the same x86 processor family.
I think you are throwing the baby out with the bath water here.

Bruce Schneier can be presumed to have evaluated his risks; he's a very well known author on exactly that.
I agree that the comment of get_random_bytes should be fixed, it's misleading. However I don't think modifying code that has no known bug or weakness because of a rumor and some handwaving is good policy. It's more likely than not to introduce a regression and create real trouble.

If it's ain't broke...

Or in this case:

If you can't prove it's broke...

EDIT: I would also remind everybody that if they really don't trust rdrand for any reason they can just add the "nordrand" boot kernel param and disable this code. It's a non-issue.
lessmeme.com

reddit.com/r/worldnews
That's the whole point of consensus decision-making - to prevent usurping power in the UNSC by a US-lead coalition (or any other for that matter). The reason for the veto is lack of credible evidence that the use of sarin wasn't a terrorist's provocation. So, in fact, what we see is that UNSC system is actually working preventing an aggression agains a sovereign state.
I disagree with this type of form builder. In a previous job, we built lots of forms (for gov/banking sectors), had a formbuilder product, and used multiple commercial formbuilders too. They were all more complex but fundamentally the same: making you focus on layout and field types up front, not content. (think Powerpoint vs LaTeX)

What we needed, it seemed to me, was something that started simply with the list of questions the user wanted to ask, and elaborate on that, adding field types/lookups/help text after the fact. The type of response had to be something you could change without deleting the form control and replacing it eg; start with a text box. Change it to a date picker. Then change it to a selection when you realise that only Monday & Wednesday are valid answers. This kind of change happened pretty regularly, but is stupidly hard in most form builders.

The other mistake of allowing too much flexibility in layout doesn't apply to Formbuilder.js - but many products made it easy to design forms that were inaccessible, or that wouldn't work on different screen sizes, or couldn't be laid out well on paper (ultimately many of these forms had to be printed for archiving). The form builder should generate accessible layouts that worked on multiple devices, and very little of the layout should be in the hands of the end user.

A less visible aspect of what was wrong with form design was versioning the data model. A user may submit drafts of the same form several times, over many weeks (applications get rejected, plans change etc). Meanwhile, the regulations driving the forms would change, or bugs would be found, and the form would change. It's important to be able to load the old data in a new form, and not choke on validation failures. Particularly, if some piece of data is now missing that means large optional sections are no longer displayed, we should not lose the data that the user had filled in in those sections.

A final data model issue was that we were also creating xsd's for electronic submissions etc. At that time the best solution was to massage the data after form submission into a schema specified format; but this meant that validation code was essentially written twice (once in the form, once in the schema), and the two were out of step. I wanted to generate schemas for valid complete forms, and to be able to clean up the saved data (which may be out of step with the current form version, see last para)

Anyway it turned out all this was possible, but I was leading a different team from the formbuilder one, so they went with a more conventional design. Sadly part of this was commercial: producing complex forms layout-first is hard enough for non-techies that the company could offer this as a service...rather than producing a better UX :(
gvim comes standard with vim with

vim defaults to allowing the cursor keys and delete/backspace.

I mouse around my gvim with my custom font all day long middle click pasting snippets in from the browser.
Imagine bolstering your fantasies with evidence. Apple Writer was retired at just the right moment -- when something better came along. That's how technology works, and no one was more pleased than I was.

> The bitterness seething out of your every pore that your software has been consigned to the graveyard ...

Dream on, moron. Apple Writer belongs in a museum along with vi. What's astonishing is that people are still using vi when there are any number of much better choices.

> ... whilst Vim is growing in popularity is so tangible!

Based on that fantasy, you may want to resume your medication.
I am not sure I like how CSS gets bloated with special case behaviors like this. Sticky headers seem to me like animated gifs - something that is hugely popular for several years and then goes away silently because it is more eye candy than useful.
Art installation needed for Ticketmaster
Did you actually look at how the Linux kernel is mixing RDRAND output with other randomness, or read the comments by the author of the original change.org petition? Because of the way Linux mixes RDRAND output with other entropy using XOR, a malicious RDRAND implementation can easily make the output of /dev/random totally determinisitc whilst being completely indistinguishable from a correctly-functioning implementation except to the attacker.

All it has to do is detect the code sequence in question and XOR the output of RDRAND with the randomness from the other entropy sources before returning it. The two XORs cancel out, and this is completely undetectable because there's no way to distinguish between a true random bitstream, a good PRNG, and a good PRNG XORed with data you provided based on the bits themselves.
Primefaces shortcomings
Vim/GVim actually do support the mouse since a while. You can select, copy/paste, resize your split windows, etc, using the mouse. GVim even has typical menus, not so different than wordpad. However, I agree with you that for other features, like using different fonts at once, Vim is limited or feels constrained.
I know that the USA is blocking any Palestine solutions in the Security Council as well, but it only makes the same point - the concept of "veto" makes Security Council useless. I'm not saying that Putin is the cause of that, but he is one of them (together with USA and China) - his veto power is part of the problem. I was singling out Russia because of (propaganda-induced-opinion?) a pattern I've seen of Russia systematically supporting dictators against their own people.

If there is unilateral consensus, you don't need formal bodies to do stuff, since everybody agrees anyway. However, if we want the global community to be effective, then we need an ability to make decisions and do stuff even if Russia or USA or China is against that, if the vast majority of the world understands that, say, a massacre must be prevented.

Currently we can't do that. As I said, in a number of cases Russia has prevented any progress by using the veto or threat of it. USA has done the same regarding Israel/Palestine - my impression is that it's their major use, media doesn't represent others much. China has as well - often things are abandoned simply because it is clear that it will be vetoed anyway. In essence, only trivial and unneccesary things can be decided there, but any serious things that matter - can't, as definitely someone with some interest will veto that. So the veto powers should be reformed.
Teenagers and the Internet
No extra keystrokes required, which was your original argument, moron.

Please fuck off, actually learn to use vim properly (its changed a lot from the ancient editor you used) and then come back with some arguments that are accurate and based on facts.

I guarantee you will learn a few things that you can out into that crappy editor that you maintain (you know, the one that needs an ENTIRE JRE TO RUN)
My approach:

I take the contract to the lawyer, discuss it with them, decide what is worth negotiating on and not. I do the negotiations. The lawyer advises.

Most contracts don't require me taking them to a lawyer. I read them 4-5 times over, annotate them with questions, talk with the client, see what we need to clarify, and go for it. Those that do involve questions I want to clarify with a lawyer before clarifying with the client (where raising a question may make me sound greedy or dramatic, etc).

Most contracts are designed to cover one or both sides in the event that something goes wrong. The boilerplate can usually be quickly identified once you have some practice. The rest is going to be operational stuff and you don't want to sign the contract to find out what is in it. These sections establish expectations on what is done and how you interact.

But whatever you do, don't have your lawyer do the negotiation for you. Madness lies that way. Business negotiations are not the same.
I can't drag you kicking and screaming into the early twenty-first century. You have to make that trip on your own.
get_random_bytes() documentation:

This function is the exported kernel interface. It returns some
number of good random numbers, suitable for key generation, seeding
TCP sequence numbers, etc.

Here is the accepted commit that makes get_random_bytes() use RDRAND directly:

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.g...

Note that this was version 3 of that patch. Versions 1 and 2 also took control of /dev/urandom. Here is v2:

http://thread.gmane.org/gmane.linux.kernel/1173350/focus=117...

A year later, Ted Ts'o made get_random_bytes() go through the usual entropy pool and added get_random_bytes_arch() for a consumer that doesn't want to go through the entropy pool. (The core kernel does not currently use get_random_bytes_arch() anywhere.)

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.g...

Note that the heated discussion came before v3 of Anvin's patch, and thus /dev/urandom was included. Matt's objections were perhaps not expressed very clearly, but Linus was pretty cavalier in overruling Matt Mackall (the /dev/random maintainer at that time) and I think his retort to George Spelvin's very rational objection was unreasonable:

http://thread.gmane.org/gmane.linux.kernel/1173350/focus=117...

I find it scary that these commits made it as far as they did. Note also that on the day of the leaks (ironic timing), Ts'o had to shoot down a RedHat engineer proposing to once again make get_random_bytes() bypass the kernel entropy pool.

https://lkml.org/lkml/2013/9/5/212

As for other locations, the point is to be undetectable while deployed at massive scale. Keyloggers and active backdoors are much higher risk. Great for a targeted investigation, but terrible for untargeted passive surveillance.

https://plus.google.com/u/0/117091380454742934025/posts/XeAp...
Careful with that. perl -c still runs the BEGIN blocks so don't rely on it for safety (ie. if you're handling untrusted code).
You'll need to provide explicit examples of where any of those operations requires more keystrokes in vim than any other editor - I can't think of any.

You're calling vim commands "modes" to deliberately make it sound more complex than it is.

I want to change to next 3 words. I type 'c3w' - you're saying that's modal - which it sort of vaugly is. I could have done 'v3w' to highlight the next 3 words (something you would do in any other editor). Then I hit 's' to substitute them for something else. No mode involved (other than the selection - which is the same for any editor).

I stand by my assertions - it's up to you to provide the counter examples to back up your claims.
I like the spirit, but how will Vim's marking system help me jump to a CSS selector in an unbuffered stylesheet?

I'm really curious; missing this feature from heavyweight IDEs.
I'll point out that any modern version of vim uses mice just fine. It also uses the system clipboard just fine.

The reason most vim users stick with the keyboard is because using a short key combination to select and manipulate text is measurably faster than moving your hand off the keyboard, manipulating a mouse or touchscreen, and then moving it back to continue typing.
]p does, though.

That pastes with adjust indentation.
Previous discussions:

https://news.ycombinator.com/item?id=4108557

https://news.ycombinator.com/item?id=1702200
yah, it required me to install a JVM. And JVM required me to purchase a personal computer that can host the JVM. And electricity and stuff. Such an unnecessary barrier to entry.
I feel the need to point out that everyone else is talking about vim, but you're talking about vi. Could that explain some of the differences in how you remember things based on how they are?
I'm not sure how you came to that conclusion. From your tone I suspect you're simply biased against Macs.
This is probably a paid promo site, I'm sure there are many more startups in Seattle then those listed. Also, most of them on this site are pretty lame.
Sure, no license key, except for the key used to decrypt protected binaries only on authorized hardware.

There is a license "key", it's the whole computer.
I more wrote it as a comment in the form of "if you read this article with no previous experience with, or knowledge of, the mental effects of Lyme disease; and now think you do know something about those effects; please take this complementary wet blanket." :)
Very nice! Had a look at this a year or so ago and it would be a great base for mocking up backends IMHO.

In a similar vein is Google SiteBricks:
http://sitebricks.org/#home

Slightly heavier weight but with more features (templating, annotations, etc). Depends on Guice.
I agree with you, there are many truths in this letter that can't be ignored.
I think many people would get upset with it because Putin is using the same propaganda the US government (and many others) has always used, both hypocrites governing through lies, manipulation, intimidation, coercion, persecution of activists, violence etc. All in the name of "Democracy".
If there is something capable of making me drop everything and read an article right at this very instant, then that something is using a quote from "Flowers for Algernon" as the title.

Thanks to Waldo for sharing his being Charlie Gordon. I hope he recovers.
Bookmarked, thank You.

Mind sharing a bit about Your experiences? Are the initial investments cost high or low? Are there any drawbacks which inhibit any other functionality (what to do to avoid memory leaks)? Is the end-product really mantainable? Does compose easily?

I'm eager to learn :)
As the developer, I can see the source tree. The company owners can see the source tree. As such, everyone who has access to the program also has access to the source.

GPL allows this, as do every type of open/free software license. Either this mean that your word choice of "closed source" lacks meaning, or we are not talking about the same thing.
The sentiment is that many of them live on Western grants and would never bite a hand that is feeding them.
Indeed it does! Excellent
> No, to switch from entering text, to deleting text, to searching for text, to copying and pasting text, to saving a file, to loading a file, all require switching modes. Let's be honest.

Please define a mode and define mode switching. It's obvious we use different definitions for those and so we can't have meaningful discussion.
Microsoft spends on average 50-60% more on advertising, marketing and promotions than Apple.
Earn money with Beta testing... Betalize now is open
> Typically, a good engineer prides himself on using The Right Tool For The Job ...

Do you also write Fortran? You may or may not be surprised to learn that I have nearly identical debates with diehard Fortran programmers who try to argue that Fortran is anything but a way to support a vast amount of legacy code that no one wants to rewrite (for very good reasons).

Fortran is not the right tool for the job. It once was, but now there are many programs of high economic value that for all intents and purposes cannot be rewritten, for example all the FAA code behind the air traffic control system, as a result of which Fortran will be with us for decades to come.

But no one voluntarily writes new programs in Fortran, at least not if they expect to remain employed. That's true, but try to tell a Fortran programmer this.

Those debates have a lot in common with this one.

My reason for engaging in both debates to to save young programmers from picking up a museum piece without being aware of its legacy status, and thereby crippling themselves and their careers.
Seems there is some misconception here:

1. I was not complaining that I did not get paid for this bug, but that different Bug Bounty programs have different thresholds on whether a vulnerability qualifies for a monetary reward. This seems like useful information for someone who would like to make a living out of bounty-hunting.

2. Even though I participate in these bounty programs as a hobby, which is about 1-2 days per month, I was already awarded generously. If I did this full-time, I would expect to earn a great deal more than when I would be working directly for Google (unless they have crazy wages)
German scientist wants to build electrically powered bird flight suit
I feel the need to point out that everyone else is talking about vim, but you're talking about vi. Could that explain some of the differences in how you remember things based on how they are? (redux)
I give replies like that to my brothers when I'm gaslighting them and they are trying find proof I'm lying.
What is a Maccard? I've never heard anyone say that pirating OS X was more ok than any other kind of piracy.
Note that compilation is often not deterministic-- i.e. compile it again (even on the same PC) and you could get different output.

The Tor project struggles with this, and is working on deterministic builds so anyone can verify that the source code actually matches the binaries provided.

See https://blog.torproject.org/category/tags/deterministic-buil... for more information.
Sticky table headers and columns: yes, yes, yes. That is very important for usability, and currently hard to do properly. If I could just add a layout attribute to a THEAD or COLGROUP, my life would be significantly easier.

We've spent a lot of time implementing this ourselves for a data table containing lab analysis values. It's a big requirement from our customers. You can imagine it's pretty important to be able to match rows and columns (sample types and dates) correctly when you're looking at these values.

The planning meeting about this was pretty funny.

Boss: "So, we'll just make the headers fixed, should be easy, right?"

Developer: "Heh-heh... Yeah, we could probably get that working decently in just a couple of weeks. We'll have to test it in all the browsers, of course, and do performance tests with big data sets. It's possible that we might not be able to get it to work well enough on all platforms, so we should have a backup plan."

Boss: "Sigh. This would be so much easier in Visual Basic..."