skysight-inc/HackerNews huggingface dataset:
In case you see this:

Our background is PL/SQL and Oracle Forms. We were annoyed with the way web applications are supposed to be built nowadays. We wanted to build the Forms for the 21st century, and Formspider is just that. It is an intuitive, elegant framework that just feels right to build applications with. A framework that empowers you, eliminates all the drudgery of the Web but embraces all its beauty. Once you start using it, you will never want to build with anything else.

NB: I just removed one extra word, changed "build" to "built" in one instance, and combined a sentence. I didn't do a full re-write.
True, mobile is another thing I didn't cover in my comment. The trello app on iphone works like a thrill, given the fact it's a daunting task to get all the information on a small screen.

Asana had constant issues with syncing the data.
I actually looked up what it would take to get a support job in McMurdo years back. The appeal of the type of person who would seek out that desolate place is a fascinating thought. To look at what draws a person to that frontier, both the science aspect and the social one. I thought it'd make a good blog.

Harder than I first assumed. Apparently even dishwashers there have PhDs. And my idea wasn't completely original. There are of course plenty of documentaries about the place. And more than a couple of blogs by specific teams about what they're doing. I just rarely see ones about the people. And I'm curious if it really does take an Antarctic state of mind.
I do not see how anybody might think it would have iPad-like edges

An edge to place your thumb on must be about an inch wide. A 7 inch diagonal screen is 4 by 6 inch or so. With a one inch edge, the edge would be 16 square inches, or about a third of the area of the device. I do not see how they could sell you that (well, maybe, if they used them for solar cells and managed to power the device from it)
Dependency problems on Red Hat? News to me, and I admin various RHEL servers.

I do know that there were issues maybe 10+ years ago. Bringing things up that were solved 10+ years ago is a bit pointless.

Also regarding your systemd summary is inaccurate. You give the impression you just don't like Red Hat, because you don't really say anything concrete about systemd aside from some very generic remarks.
You should not refresh the "top post" list if nothing has changed (not nice to "watch" it blink every 3 seconds)
Developers, please think wider
Uhm, the largest "html5 boilerplate" actually uses normalize. Normalize.css straightens the subtle differences in the default stylesheets for the different browsers. It is css only, not really a template. It is like giving different car manufacturers specs and designs to build a car. They all build the same car but slightly different. Normalize tries to make them look all exact the same (they still behave different though)
LaTeX for Beginners - Presentation in Beamer
A nice short introduction in LaTeX made using LaTeX beamer class
> 1. At Google, code has to be designed, written, tested, and reviewed. You
> can't just start writing and shipping stuff, partly because there's so much
> infrastructure, and partly because you pay for shoddy code later. Google
> has long outgrown the kind of "start-up" velocity that you feel at
> Facebook.

you are assuming it's impossible to design, write, test and review a small change or a small set of changes and get it into production quickly. The assumption is wrong, all you need is good people, the right processes (formal and informal, i.e. discipline) and the right tools. That's what continuous deployment is about
Silp.com launches social job recommendations
Systemd on opensuse as well as Mageia is pretty damn reliable. It is not 'test bed'. Various distributions have been using this.

As a result, there are way less differences now between distributions. Which means configuration becomes easier.

In any case, if you really care about things not changing, then I assume you're using a distribution which doesn't change this suddenly. So I don't see why your so awfully negative.
This being my primary problem with the current upheaval in Linux system organization. Its instigators have mostly made it clear that they consider everything not Linux (or possibly preferably not their favorite flavor thereof) to be obsolete - throwing portability out the window.

Frankly, it's getting old.
Interesting comments. Like in so many other instances where an article criticises, explicitly or implicitly, the way some nerds make money, the reaction is to downplay it.

There's nothing really shocking here. As Cringley pointed out in an earlier blog post, it's common for publishers to overcharge for advertising. This was true long before the web existed.

But the thing that's different is nerds have the power to change the way things are done. Everyone knows how annoying (and generally ineffective) ads are. The question is, are you going to make the situation better, or worse?

Steve Jobs actually sought and was granted a patent on "serving ads upon booting". No internet required. Sad, really.
World Links works to bridge digital divide in Zimbabwe
World Links works to bridge digital divide in Zimbabwe
Scalex - find Scala functions quickly
Serious question: When did IBM/MSFT/"SOAP Vendors" start saying that REST is simpler?
"What I hate about those working at Facebook"
I "watched" the first lesson or two. I think they've missed an opportunity to tighten the watch-try-watch loop with the student. This tachnology seems like it would support a mode like "here is how you draw a box" then "you try drawing a box that overlaps with the box on the screen". Maybe they do that later. I hope so, otherwise I think they're missing a great opportunity for engagement. Even without that level of interaction, I still plan to try this out with my children. Really impressive.
Traditionally, the public literature is how scientists communicated, which is what made republication possible in the first place. Lab A, perhaps in Germany, works on a research project, and gets some results. They write up their methodology and results, and communicate them to other scientists by publishing the write-up in a journal. The journal will have the write-up peer-reviewed before publishing it, but that doesn't mean verifying it's correct, only that it's a contribution to the scientific literature worth communicating to its readership. For example, it would make sure the paper has done appropriate data analysis, has cited relevant existing work, is not outright kookery, etc.

Now other scientists, anywhere in the world, will read this and decide what they think of it, which may include attempting to replicate it. If they find different results, or have a qualm with an interpretation or methodology, they can write a response, which will also (after peer-review) be communicated by the journal to its readership, either as another paper, or if shorter, as a letter. Thus the back-and-forth of claim/replication/critique happens, all in the open air of the journal's pages, with any lab anywhere in the world able to follow the conversation and jump in if they wish.

To me that's more transparent than doing all this in some kind of closed pre-publication process. Perhaps in the modern era, the open communication doesn't necessarily have to happen in journals anymore: perhaps it should happen on arXiv, and journals should become more conservative in what they publish. But I would like it to still be public.
A Brief History of the To-Do List and the Psychology of Its Success
One great benefit to stability is the amount of users. Sysvinit was different in every distribution. With systemd, almost everything is shared.

This results in way more users and developers looking at systemd. As a result, less bugs.
Time to get a new username
The problem is you don't need to actually do the calculations to determine the output of the program. It can all be optimised away to print statements. Is there any evidence iterate is actually running?
Write LaTeX - browser-based collaborative editor
I fail to see the problem. Either something is portable, or something is not. It is basically up to the developer.

If not being portable means way less time spent on development, then some people might choose that. Good for them.
You might find the below article from the Economist of interest/motivation:

Deathless data

What happens to our digital property after we die?

http://www.economist.com/node/21553011

"..Service providers have different rules—and few state them clearly in their terms and conditions. Many give users a personal right to use an account, but nobody else, even after death. Facebook allows relatives to close an account or turn it into a memorial page. Gmail (run by Google) will provide copies of e-mails to an executor. Music downloaded via iTunes is held under a licence which can be revoked on death. Apple declined to comment on the record on this or other policies. All e-mail and data on its iCloud service are deleted on the death of the owner.."
Fixing “fried brain” syndrome
This are very sound advices. I have arrived at very similar architecture in LSI environment.

From my experience, here are some advantages of this architecture:

- stages could be independently rewritten, so you could prototype in fast-writing language (perl in my case) and later rewrite whole stages or parts of them in fast-execution language if you need extra performance (C,C++ here);

- you could easily integrate third party software in your workflow - most of the existing tools in the field work with input and output files;

- you could reuse already written stages for different purposes - just pass them different options for input/output and parameters.
Good point. The clojuredocs version[1] is a bit better, but you're right, it could be better.

[1] http://clojuredocs.org/clojure_core/clojure.core/with-open
'The Internet is for Porn' – Blackmail in 2033
In my biased opinion, once you have gotten over the learning curve, nothing beats daemontools for running services. It is a fantastic set of tools. Why some OS doesn't just embrace djbware I'll never understand. It compiles, smoothly, in seconds. (There's no need for distributing binaries.) And the chances of the author initiating lawsuits (as some Linux foundations are known to do), over something placed in the "public domain" are close to nil. He's got better things to do.

BSD's rc system is fine. Sometimes the scripts are too verbose. But the whole idea is the system is simple enough to understand that you can write your own scripts -- more concisely, if you wish. You don't need to read a book (e.g. Linux from Scratch), keep most things disabled by default and let the user turn stuff on as they need it.

I recently used Debian's live USB, the rescue version, for a little while and was amazed at how much stuff is turned on by default. I guess if you understand each and every choice that's been made for you it's OK. But if not, that approach is not very conducive to learning.

As for Apple, never mind all the XML fluff, good luck trying to understand what's going on behind the scenes with their computers anymore. They can't even manage to let you have an nsswitch.conf or equivalent.
Please put a year on old posts. This one is from 2007.
Ah, that is much clearer, thanks.
What's the point of posting this five years old article without any context ?
Been using Pivotal for a few years and really love it. For Agile/Scrum software development it's close to perfect. But I'm not sure how it'd play with other scenarios.

My major plus points for it is how it automagically calculates velocity and adjusts the following user story schedule accordingly. I'm not a big fan of the right-to-left panel layout, but it's not a deal breaker. It makes my life easier, which is what I want in a software package.

I love the design of Trello and could possibly move to that, but I'd miss the scheduling/velocity/estimating features. Also, some projects have a ton of stories and feel that Trello would be unwieldy. I have used Trello for personal to-do list type stuff though.
It would seem unlikely that the UK government will grant him the safe pass that they refer to.

Asylum is meant to be used for political charges and while there is a suggestion that there are political motives around what is happening to Assange the charges against him are criminal ones. That means that on paper this is an abuse of the asylum process (and one which as a result actually damages it) so it's possible or even probable that the UK government will decline to grant him passage to Ecuador which leaves him exactly where he is now - in the embassy in London with no way to get out.

One thing I don't understand is the idea that the US want him in Sweden so they can extradite him to the US from there. Why not just extradite him from the UK? The UK has a very favourable extradition policy, the government are supportive of the US and likely to be more sympathetic than Sweden. It just makes no sense to me. Yes things can get tied up in the UK courts but I doubt that's different to Sweden.
This text is from 2007, and compares execution speed of Java to C on one single CPU-bound benchmark.

At http://shootout.alioth.debian.org/, an up-to-date list of the most popular languages are benchmarked. Tests are standardized, and code is optimized for the tested language and particular benchmark.
Also, for each benchmark, not only execution speed, but also memory consumption and code size are measured, and the processor architecture is taken into account too.
I have to respectfully disagree here - this is like saying you shouldn't use jQuery, as it will kill the idea of remembering basic JavaScript.

I'd rather just get shit done (tm) than spend time learning all the nuances of cross browser css.
From MongoDb to Riak
Really loving braintree, haven't checked out stripe, but I think for what we are doing braintree are totally awesome. There has to be a reason why basecamp and others are using them for example. I guess everyone has their reasons to like or dislike something, and valid to have both opinions but we love it.
Reinventing the wheel would teach me more, I think. But ANI is a useful reference for how to do some things.
Not quite as bad as the internal links: https://medium.com/r/?url=https%3A%2F%2Fmedium.com%2Fr%2F%3F...

But I actually really like the look and feel, so I've signed up. I'm sure they'll hammer the issues out.
I haven't heard of anyone's Air screen breaking, they can't be that fragile.

(But I have heard of several people destroying them with coffee or beer).
Wow. There have been many of these "Look what I can do in CSS" articles lately, and frankly, they are normally quite boring. However this is the first time I have ever gone "wow". Very impressive. Quite useless really, but good work.
Why did you send her Scheme tutorials if she asked for something as simple as possible? Lisp is generally thought of as a very unintuitive language. I think Python would have been a much better choice, considering what she asked for.
That is clever. What is the {1..5} syntax called? I am trying to figure out what the zsh equivalent is.
You're assuming that an iPad mini screen would be roughly as usable as a nexus 7 screen, but if the rumours are correct they would be very different. The Nexus 7 has a 'letterbox' widescreen aspect ratio compared to the iPad's chunkier 4x3 screen. Also the iPad screen would be 40% bigger. These are not small differences.
It is spoken way too fast. It's going to turn off almost all non-native english speakers, as well as confuse many english speakers.

That's what the 'rewind' button is for. There is nothing more frustrating for those of us who do understand English than a slow speech track on a video.
Yes

too bad there's a 'fence' missing between each page

Or you'll just reread every page until everything makes sense since you can read things very fast for marketing purposes
Event Aggregator: Coordinating Views In Backbone.js
Comparing execution times is actually very irrelevant. Speed is a matter of control. Any language with a VM and a garbage collector will be considered as "slow" because you can't always control what is going on. With C you can, and thus you can always write an ad-hoc implementation that will have the best performances on you execution platform. It is a great feature of C, now I don't think we need another language like this. There is nothing else to say.
Cheers, I didn't realise they'd released the Android app ... "This app is incompatible with your HTC Wildfire". Baws.
Thank you for your remarks, this is really helpful.

It doesn't seem to me that timing attack is feasible here: timing of comparison of a relatively short string vs network latency and everything else that happens during Apache's request handling would require a lot of repeated attempts and statistical analysis of very noisy data if it's at all possible to get meaningful results. Still, it's better to be on the safe side and I'm going to close it up.

Sanity check for idea of resolution: adding a random length sleep, 1 to 3 seconds, if HMAC is invalid. This would fuzz the small timing difference in string comparison, and at the same time tarpit any exploit attempts (invalid HMAC is more likely to be sign of manipulation attempt rather than a honest error). Does that make any sense?

Regarding user-controlled data: the context here is that usernames aren't under user's full control (they need to be entered into Google Apps by someone, and also validated). In general case this is a valid issue - a valid login could break the scheme here.

This is in no way an excuse, but rather explanation of my reasoning: the initial idea was to port GodAuth and be at least "kind of compatible", because some people use GodAuth and it might be meaningful for interoperability. Also, as I'm no specialist in crypto (as you can clearly see), I followed the route of not touching crypto-related code that is already written. The issues you've found are strong enough reasons to diverge from GodAuth - especially that GodAuth interoperability is way more theoretical than an actual security issue even if it may not be exploitable. Thank you for reviewing the code and your remarks.
> I'm also not much surprised that Red Hat, who've had such a historic problem with consistency and reliable dependency management within their packaging system (as compared to Debian/Ubuntu)

Yawn this again. Give an example please.
It would be possible to have an optional "reason"-field though. I don't think that's a bad idea really.
you mean for times when someone sends you code as plaintext email?
That is really cool, both your grandfather using a Linux laptop and the boot time. Could you name a few components you used?
Prevent being watched through your webcam
This is probably my favourite DF piece http://daringfireball.net/2003/05/the_problems_with_click-th... - the fact that it's from 2003 is telling and I'd like to see him do more like this.
> My wish list goes something like this: better wireless drivers, improved sleep/suspend/hibernate/resume, better power management, a better package manager, more up-to-date applications ...

Use a different distro. None of these is a problem on a modern distro with reasonably modern hardware.
It doesn't matter if systemd is written by Poettering or somebody else and it also doesn't mater that we don't have shellscripts any more.
The real reason systemd should never be accepted is that I need programs to configure or talk to other programs. I even need a special program to read logs. This is the replacement of files with APIs. It feels like an enterprise class product which means it sucks all the fun out of computing.
Judging from the success of this piece we have much more of it to which to look forward.
one of the best things Ive ever read on the topic, even better than the original post
Thank you! This will be closed up by end of this week. As I wrote in the article and in the presentation, one of main points of open sourcing it is to have people smarter than myself look at the crypto and protocols to find any issues like this. It should be fairly easy to close up.
I am totally in love with Jessica, the voice over girl.
all of the innovations and improvements you bring up ... come from areas that few, if any, regulators take issue with

They don't issue with them, but still no one in the regulated industry bothers doing them. And why? Because thanks to the government distortions in the market, you don't need to do any of that stuff to compete.

And that's what government interventions in markets almost always ends up doing: protecting a group of entrenched companies at the expense of consumers.

Good for Uber for trying to fuck over an industry that's been fucking over their customers for decades, with the full faith and protection of the governments those customers pay for.
The Invisible Bicycle Helmet
php is maintainable if you actually know it and not just put it on a resume, Drupal runs the whitehouse.gov, Wordpress runs 15% of all sites and Facebook has the largest member base in mankind history, PHP is not hieroglyphics it is actually has roots from C...
QWERTY or Touchscreen? Survey Reveals Input Preferences
This seems an interesting idea, but not sure the price is worth it
This video, along with many others I've watched from him, espouses the purity of data, and talks about not tangling data with functions (object orientation).

In this video, he seems to go along and say that values are great for software projects that use multiple languages, in part because values are universal meaning one doesn't need to translate classes into multiple languages.

However, regardless of whether you use an object oriented design or not, don't you usually have a set of functions you tend to perform on a set of data or values? For instance, you may not wrap your customer data behind a class and methods, but there are still going to be some rules related to all that data you're passing around. So in the multiple languages scenario, wouldn't you still have to translate those rules from language to language?
Getting started with OpenStack in your lab
Goroutines and Channels
Wet animals shake at tuned frequencies to dry - the wet-dog shake (video)
I don't like this idea as a main authentication system for a couple reasons, besides the logout problem. First, it requires team members to register every single browser they'll be using to access the panels – which may also mean being locked out during emergency due to not having a blessed browser nearby.

As I understand the scheme, distributing and deleting/changing clients' public keys to the web servers is basically the same challenge as syncing htpasswd across servers and trying to let users change their passwords. Syncing itself is not an issue, but making it possible (and EASY - any security that gets in the way of getting the job done will be circumvented by users themselves) to add / update / invalidate user's certs by users themselves is not trivial.

It also adds to the proliferation of credentials: Yet Another Key (or even Set of Keys) is just as bad as Yet Another Login And Password.

This is a good idea for a multi-factor authentication, though: require either token / SMS OTP / other out-of-band verification, or a blessed client certificate – basically, pre-authorize certain browsers. This might fly!
Donation Drive – Build infrastructure repair and capacity expansion
> HN is not a Q&A site, neither is Reddit.

True, but both have Q&A 'modes', e.g. Ask HN and IAmA AMA.
Features can sometimes only be visible in the aggregate. If facebook improves ranking of stories in a way that improves time on site and their user engagement metrics by 5% that will likely be invisible to nearly all users. Same for their ads. Plus they would be running many A/B tests, some making it onto the site, others only ever being seen by a small percentage of their users. Chat, integration of acquisitions, billing, APIs, 3rd party integrations, future products, etc.