skysight-inc/HackerNews huggingface dataset:
Of course you're always going to have a bunch of annoying people who feel entitled. However, this is not the case here: somebody reports a regression, in a helpful and polite way. "No" is not an appropriate justification, especially when it comes to such a widespread, widely used feature. I don't even understand how this would trigger such an emotional reaction wrt to removing a feature (presumably) he hasn't coded.

Gnome is not a throw-it-on-Github-and-see-if-it-sticks project. Development shouldn't happen in a vacuum, and antisocial behaviour shouldn't be the norm.
Apps that Sync Music Across Devices Prompt Copyright Concerns 
Thanks to Rob for his interest!

We demoed the app for him at event last Saturday and it worked as it always does for us.

Bummed during his personal demo he didnt have same success. Thus we are testing the heck out of it and if interested helping test let us know in the comments here. We'd appreciate it - thanks!
It looks like it's a datatype limit, as other python json libraries have a similar issue:

http://deron.meranda.us/python/comparing_json_modules/number...

It's probably not a trivial fix/addition and might end up costing the library some of it's speed.
Factories only make economic sense if you are planning on building a large number of widgets.

For small applications, dynamic form generation infrastructure dwarfs the actual business logic. It means writing a lot of code which isn't solving your business problem.

Your project has an extra layer of 'meta'. It's harder to debug. It decreases flexibility. Validation is hard for multi-field relationships. Special-casing that one form can require major infrastructure changes. The approach tends to be slower and buggier than the naive approach for all but the most form-heavy applications.
I upvoted it because the discussion here might make other maintainers of software aware of how their attitudes are seen by others.

But on this one, is it documented? There are lots of valid reasons to make a tradeoff like this. If you've made it, and put up big warnings about it, then failure to respond to those bug reports is quite reasonable.
One of these days, the blogging classes will notice that web development is just another specific application (though obviously now a very popular one) of much more general fields like software development, graphic design and typography, HCI, technical management, and so on. So is, say, iOS app development. It's strange, and I think very unfortunate, that a new generation is growing up as if these are entire industries in themselves or as if specialising in the current tools and trends in an even smaller, more specialised part of web work or mobile app development is somehow all there is to know or learn from. It means many enthusiastic newcomers aren't benefiting from the decades of collective experience we've gathered in the wider fields, and without that wisdom they inevitably repeat many old mistakes that could have been avoided.
I do not subscribe to the common belief that it is better to minimize the shortcomings of people to a greater degree after they have died.

I'm not sure why dying confers greater respect upon people. Perhaps it's the fear of death in the minds of the living?

https://mobile.twitter.com/sneakatdatavibe/status/2901109457...
Linus is talking about userspace binary compatibility. Your graphics drivers are relying on kernel module binary compatibility, which is not guaranteed.
How to Code an Expanding HTML5/CSS3 Search Input Field
They're not minor problems. Please don't underestimate the epidemic of hacked sites that are a direct result of end-user unwillingness to upgrade and possibly break their site. This is a problem that can't be solved without significant architectural changes. Customers are more willing to risk getting their websites pwned than to risk an upgrade that may take their site down, so upgrades often aren't done for years.

It's not a small problem, its a huge one, and the primary reason why I can no longer recommend Wordpress.
Thanks Hacker News for all the awesome
I didn't realize looking for SSIDs was an active process. Why wouldn't it just listen for broadcast SSIDs? Is this only for hidden ones?

Regardless, headline should not single out iOS unless this is iOS specific - maybe it is? Readme says: "iPhones, iPads and other wireless devices"
From the limited accounts I've read this doesn't explain well the US homeland experience, except of course by the late '50s the population was likely quite a bit healthier. The research on the recovered strain that reproduces in monkeys the "classic symptoms of the 1918 pandemic, and [dying] from a cytokine storm" is of concern (http://en.wikipedia.org/wiki/1918_flu_pandemic#Spanish_flu_r...), as are the intensely lethal strains that keep popping up, but fortunately with little to no human to human transmision.
How identical twins develop different personalities
Bases and military relationships = wars? LOL!

That site is ridiculous.
It is stated in the previous talk he mentionned that removal of that feature was planned. In they eye of 'Persch' this is not a bug, it is an improvement to GNOME.

It's not a bug, it is the removal of a feature. Is a bug tracker really the most appropriate place to discuss in which direction a software is to go ?

'No' and a link to the relevant reason and workaround should be fine in that case but apparently that had already been discussed before (and a reason was given).

I don't know if removing it through so much commits is good practice but if the feature was to go it doesn't make a difference in the end, he sculpts his piece of the software any way he likes it as long as it's feeature oriented, right ?

Note: I have no advice on wether that feature should have been removed or not in the first place.
Maybe use the car analogy. How much does a customized (length, width) version of a given model cost that fits better in your garage?
Thanks to Rob for his interest in our work and this space!

We are bummed the app didn't work during his personal/private test like it did when we demoed it at a conference last week to him and attendees.

His private test is helpful, as we are now looking for services to test the heck out of our product before our upcoming release.

If interested in helping us in this regards, please leave a comment. Thank you!
Many people would have been displaced in 1918-19 (though I can't find a good number). I think mostly they would have been soldiers since it was largely fought outside of cities. In any case in 2013 there are more than 1 billion people [1] who travel internationally each year so that condition isn't unique to the spanish flu.

[1] Wikipedia - tourism
The value restriction is a rule that governs when type inference is allowed to polymorphically generalize a value declaration. In short, the value restriction says that generalization can only occur if the right-hand side of an expression is syntactically a value. [...] The value restriction prevents a ref cell (or an array) from holding values of different types, which would allow a value of one type to be cast to another and hence would break type safety

http://mlton.org/ValueRestriction

It can be annoying to work around this, because there are potentially ML programs that would be type-safe and would otherwise compile if they were not hindered by the value restriction.

I got my answer, though:

Ii is interesting that in ML, the presence of mutable ref cells and parametric polymorphism requires the whole language to be dominated by a "value restriction" [1] to ensure that the type system remains sound, whereas in Haskell, because IORef's can only be created (and used) in
the IO monad, no such restriction is necessary.

http://www.haskell.org/pipermail/haskell-cafe/2007-July/0292...
Sit down and let me tell you a story about Gnome of old - a very happy little linux desktop with a bunch of happy users. For nearly ten years I was a gnome user and there were many like me who looked at their DE and smiled because it was good. but as time progressed, the desktop ecosystem got stale and most of the other DEs were unchanged in any noticeable way for more than ten years because people were happy enough.... then people started talking and decided that this year or next was the YEAR OF THE LINUX DESKTOP and something had to change to make it so.

So the gnome developers had a plan. "Linux needs a desktop for all of these people who don't use linux". We need to build something for the non-users.... and the other developers looked at each other and agreed. "YES! Let's throw away our current user base and focus on the users we don't have". The developers were very happy with themselves.

We can focus on tablets and touch... everything can be round and safe and nobody will be able to change anything because they will simply love our environment so much.

and since that sad day, the gnome developers pretended that nobody actually uses gnome and everybody who did were less than human. They waited for the billions of people on the planet that would really really love using gnome once they find it.

So I left..

Classic gnome developers and their little man syndrome.
The open data issue and the paywall issue are separate issues. Even if the publishers opened up the papers for public access, people would still not have had access to the R&R dataset.
> Persch was very devious with this one. He hid the removal among very unrelated
changes (gtk to gsettings switch) and spread the rmeoval across more than one
commit. Such that you cannot easily revert it.

What is wrong with these people?
My personal favorite zsh specific feature is the REPORTTIME environment variable. When set to a nonzero number it'll automatically print a summary after a long running command.

My own http://imgur.com/6LCS1cj
Not much, really. Anything that scrapes the disk image should be able to recover the images. There's already a "free" open source application or three.

I don't work in the field, but I've had some classes with local forensics engineers. Forensics teams buy software almost solely because they are able to reliably cite the software's use in court, and the developers could be subpoenaed easily to explain the function if the defense decided to call its use into question. Open-source solutions likely will never be used for that reason.
Like I said, calling those "touch" screen is streaching the definition and as far as I'm aware, none existed pre 2001.

"But the biggest factor that changed the game were the concessions $Launch_carriers made to Apple." O2 made some pretty massive concessions in the UK too. Android came along and screwed that pooch well and truly! Don't get me wrong, there has been a lot of good that has come from Android, but handing the control back to carriers is harming consumers long term. Data limits are criminally low, and the reasoning behind them is based on fallacy.
> "The linux desktop" is not a meaningful phrase.

Sure it is. It's an umbrella term for Gnome, KDE, etc.

> "The competition" have just screwed the pooch with Win 8 as well.

Nah. Not enough that people are leaving it in great numbers. People who want a Windows 7 experience download Pokki or Start8.

> I'm not an Apple user so you'll have to tell me how they're doing.

As a Mac user, I'm perfectly happy with Mac OS X, out of the box. Haven't upgraded to Mountain Lion yet, though.
No, i`ve tried to say that WordPress is simple enough (for a non-technical person after a short training) to deal with the majority of tasks. I don`t know easier open source CMS comparable to WordPress.
17 Design Feedback Techniques that Influence Others and Win Meetings
> FOSS is free as in "free to break software that depends on your code."

I think this is a little unfair; the specific example is the Linux kernel where enormous emphasis is placed on never breaking userland.
If you want to beat yourself out of using them (or /gasp/, arrow keys) instead of more appropriate commands, (and can afford the productivity hit and fits of rage when starting off), try using medium-mode[1] (or, if you're really silly, hard-mode[2])

[1] https://github.com/kbarrette/mediummode

[2] https://github.com/wikitopian/hardmode
See also Notational Velocity in plain text file mode pointing to Dropbox.

When on mobile, sort the folder of text files by date modified.
You know, this is where conciseness comes in handy. Another suspicion that I have (in addition to the one I've voiced elsewhere here) is that complex, inflexible languages almost force people to write stuff "by hand". What exactly is the reason for a simple, small generative layer to be so complex that it can't beat hand-written stuff for two dozen tables? I'd understand if you were talking about Java and Cobol, for example, but I'd think that such languages as Ruby, Smalltalk, and Lisp will have the threshold for "now it's worth it to be generic" quite a bit lower. I'm not sure where exactly, but certainly lower.
There's a bug in your code, the chance of deleting is less than 1/6.
Sorry for the mistake with the link. my bad
This probably breaks TOS somehow. There once was another very similar service that swapped followers between two Twitter users. That was taken down as breaking Twitter's TOS.
It isn't only iOS devices that do this. All operating systems probe for SSIDs that they have been previously associated with, thats what makes devies like the WiFi Pineapple possible [0].

[0] http://hakshop.myshopify.com/products/wifi-pineapple
It does work. The amount of GDP that the US economy gained from 2009-2011 is some positive value. If you look at the share of GDP gains that was captured by the top 1% earning households over that same time period, it's 121% of that value. I can see why you say the semantics are messy, but it is a sound analysis.
I once read that the chance of Russian Roulette is NOT 1:6 but more like 1:600, since you play with one bullet and the weight of the bullet makes it relatively unlikely that the bullet stops next to the top position in the barrel when you spin it.

Don't know if this is true but in the end, it doesn't matter for this stupid game.
By "talk" you mean the link to the "prefs redesign" bug, right? That bug was a good place to discuss which way the redesign would go, but Persch had already decided and made a branch to remove the code.
World's shortest commercial flight
This is great, but why oh why do people still use HAML over SLIM[1] as their templating language?

% is unnecessary, and I find slim's attribute handling far superior to clunky haml, and to top it all off slim compiles faster than haml.

1: http://slim-lang.com/
as far as I remember this is a feature, the wifi connection stack on osx is trying to connect to recent wifis first with the mac address because that is much faster than trying to get a new lease and so on
Ask HN: How do we split ownership of a startup between cofounders?
We are three engineers who decided to work together on an idea of mine. Initially, the idea was to split (rather naively) the eventual company between the three of us equally.

Forward a month later and here we are. I have pulled about 70% of the work, another engineer 25% and the third engineer a "generous" 5%.

Yesterday, he asked me to put everything on paper to see if he would move forward with the project.
In terms of interest, all three of us are pumped. We all love the idea.

At this point, I really need your help and advice. I want this to succeed and be fair. How should we proceed?

Note: None of us have any experience incorporating a business.
Do tell me, oh, enlightened one, what I should be using if I have 10K idle network connections and I can't really use IOCP, because I need keep things reasonably portable. That's not even considering that IOCP is a great example of premature optimization at cost of clarity and simplicity. It tries to solve a problem that I don't have and it doesn't offer a simpler solution that would just do. It is not a "hole" for my square peg, it's a freaking snowflake.

And expecting a modern OS to have an uncomplicated O(1) API for monitoring sockets is clearly too much to ask.
> I don't think I agree with the people who seem to think of transparent terminals as massively important feature, though I do find them nice.

I don't like transparent terminals myself but the bottom line is that Linux users spend a lot of time in their terminal. Terminals are the #1 productivity tools for Linux. You just can't remove features from such tools willy nilly without consulting with your users.
Going beyond the design and layout to actually writing a website for the client using Rails for example, how can you explain this? Unfortunately, clients have no idea about the technology behind what they actually see on their screen. The server side application and database which makes it all possible.
mseepgood's argument is that terminal transparency always makes things worse. None of your ironic statements illustrates a comparable case, or constitutes a rebuttal to that claim. I can't see a worthwhile use case for terminal transparency either, but I'm happy to be corrected.
Steganography in Python
Ahh, thank you. This was very informative. I have no experience with ML. I thought you might have been referring to the mixing of values and types which occurs in dependently typed programming.
I don't know about 'better', but I remember it being a lot more fun to use various Linux desktops 5 years ago.
Yes! I never understood having transparent terminals before, but one day I discovered that configuring a slight amount of transparency, together with the blur, can be really useful. The terminal still stays clear to read.
Forking doesn't fix the issue at hand here, which is the lack of communication between Gnome developers and everyone else.
Also, the original title of this thread was about a thousand times more informative.
How can I (a webdev) improve my personal website?
WTF?

I wrote this slide deck. It was a presentation I made for a monthly "tech lunch" my team has.

I made it after a couple of weeks of messing with zsh. It was for an audience of 4 other people who knew less about zsh than me. I can't believe someone posted it to HN!

That explains the "this slide deck is getting traffic" email I got from Slideshare this morning.
A friend of mine works on gnome, and I asked him about it. The actual explanation for this is a lot more reasonable:

"Him: OK, I figured out what happened.
It wasn't ideal in terms of commits.
So, we have an old configuration system GConf, and we replaced it with our new one, GSettings, for N reasons.
GSettings was missing a feature for gnome-terminal to implement, so it went without GSettings for a long time, until the 3.8 cycle, when we ported it over with a workaround.
The port wasn't 100% complete, so it landed with the intention of adding feature parity, like with terminal transparency support.

However, after asking our team, we decided it wasn't worth it keeping the support code around for terminal transparency, and dropped it.

It's an unfortunate thing that happened where the reasoning wasn't relayed entirely in commit messages, and you're right -- it was dropped in a seemingly unrelated commit.
But that's after intentions changed -- a broken port to new tech with the intention to fix it, then that changed, and thus it got dropped under the guise of "Remove dead code"

me: fair enough.
so the only wrongdoing really was persch's response.

Him: Yeah. So, it turns out that he was just tired.
That was the 7th or 8th bug report about it, and he didn't feel like explaining it again."
While the code could use streamlining by only drawing one randint and comparing it to a static number, the probability of orangethirty's way of doing it still gives the correct probability of 1/6. Think of it as two dice, the chance of rolling doubles is 6/36 = 1/6.
Drive with Lynk
Yes. This title changing business is infuriating.
Stop Discriminating Against Both Sides: The Reverse Regression Effect
Brilliant - I've love that gag.
Basically. Except that there is no need for a "smart TV" plan, just charge that much for the wire itself. Apple TV isn't going to do Verizon any good other than build a dependence on Apple like what the recording industry did with iTunes. If people want an Apple TV they can buy one from Apple and hook it up to the wire. Or they can get a gaming console instead, or roll their own Linux box, Verizon shouldn't have to care. They're in the wire business.
We all know these things never work as well as the demos. Well... this worked as well as the demo. Better, actually--I was literally finished before I knew it because I didn't see the real-time update on the right at first. A deceptively simple UI and beautifully implemented. Useful, well conceived--I'm quite impressed.
Because mentioning that it's Gnome 3.7 is so much less important than the bug number. (The original submission title did include some editorializing perhaps, but at least the reader had a chance of knowing that it was about Gnome 3.)
Arguing about HAML and SLIM is pretty useless. Easy to write, hard to read. Plain old ERB for me any time.
A note to myself
I wrote this a few weeks ago and I keep it open on my desktop at all times.

---

That would be cool. But you know what else would be cool? Actually finishing an idea that you started. How many times do you start to work on something and never finish it? EVERY time. You've been doing this your whole life. Somehow along the way you have learned many things and even became a master in a few different areas. But that is not what you want. You want to create. It's not really creating when you never finish.
How do these systems compare to traditional cluster task schedulers like PBS and SGE? Is it that Mesos/Borg/etc have tasks that are managed within the program as opposed to the PBS/SGE model where you write separate programs that can then be scripted to be distributed? (Not counting MPI).

Are these like the next generation of task schedulers, or are we talking about a higher abstraction level?
Indeed. Any idea about how to explain to non-technical people what this difference is? This is the kind of question I'd like answered.

(Otoh, concerning WP, you can, unfortunately, fit almost anything into the WP mold, or "around" it - at least when you are past the point of having read and understood most of its source code and you know the db layout by heart... yeah, it's terrible and the whole thing works against you if you want to write good, clean, testable code, but it still ends up the cheapest option you can give to a client if you want to be honest with him)
Depends on if you're re-spinning between turns. Otherwise the first guy might get a 1/600 chance, but everyone afterward has better (or worse?) than 1/6 odds.
Freelancing and Lifestyle Design
Show HN: MoneyCollector, Accept credit card payments on any PHP enabled server
The ustream link seems to be the one that works on Android. The HTML 5 one just tells me that I should be using an iOS device.

Does anyone know what technology is being used in the suit cameras and why it is so different from the ISS cameras? The former seem to have far greater interference.