skysight-inc/HackerNews huggingface dataset:
Thanks for those video links.

Cracking quote from the end of the YouTube link.

"Autocomposition, and computerized composition are already with us. Designing types and letters for the new technology will increasingly involve mathematics and the laws of electronics…. Tradition and progress must be logically united. Does the new technology mean the serious lettering artist will be dispensable? No. The alphabet remains. But we will have new tasks to learn. But in learning them, we must take time to observe the world around us, and remember above all the artist’s challenge: to ensure, despite technology and mass production, that beauty is never lost."
> The amount of hassle involved in planes is definitely more though

This is very much post 9/11 though. It was not as much of an hassle before that.
In England some coaches (long distance buses) have tables (seat four people); power sockets and WIFI. They might have a fridge with cold bottled water.

Some buses have WIFI.
I wouldn't really say they are optional. The two do different things. (int) foo (or (int)(foo)) is a c-style cast. int(foo) isn't a cast. Instead it invokes the int constructor with the argument foo.
You know, the Culture of Socialism does not always need the parties to be called Socialist. Look at the spending of Japan governments and please tell me with a straight face that this is not the spending of a Socialist state. Have fun.
Are there any important changes to the system here, or is it just a new presentation?

After a few years using mGSD, I'm now using CueKeeper (http://roscidus.com/blog/blog/2015/04/28/cuekeeper-gitting-t...), which I wrote based on the first book. Any new ideas here I should incorporate?
I wish I hadn't thought about scaling when my [last] startup was small.
Articles like that are needed to give Apple its wake-up call.
It's better than Google Docs when you have 10 levels of things, which would be unmanageable with most text editors.

Also it's not linear, as you can close/open items and zoom in on an item, so that you're looking at the right context, which I personally find really helpful.
It's a visual thing. Frontend isn't very similar to programming for the backend (except for high quality javascript). Most people who can do wonders for frontend tend to be more like designers.
Was discussed on HN back in '09 as well: https://news.ycombinator.com/item?id=794116
I think perhaps what the parent comment meant was more that trains aren't inhibited by normal traffic lights; upon approaching a crossing with a road, the train is immediately given the right-of-way — i.e., the lights activate, the gates close, the cars stop and allow the train to pass.

True, there is a separate signal for the train, though it's more if the train(s) ahead of it are keeping to schedule than the train itself. (Rush-hour trains here are regularly delayed due to the train ahead of the one I tend to ride being so delayed.)
Fair point. I've always used the approach of dedicating a machine to one particular application (using virtual machines once those became available), so the impact of upgrading the a global JRE is limited.

I did once work on a system where we installed two JREs in parallel, and selected which one to use for the app based on an entry in the manifest file. That let us upgrade Java versions under application control, without requiring sysadmin intervention. Took a couple of lines of shell script.
Which is more-or-less exactly the same as saying "freemium", 99% of the time.
Are those both public transit? Both of those, but particularly the bus, put anything I've seen here in America to shame. (Even private bus transit doesn't look that nice…)
You quite obviously don't know what you're talking about.

Try and write something complicated in js and you'll hit performance problems far quicker than other languages even today in 2015.

HTML is a complete disaster.for any thing other than documents and woefully inadequate for applications. You can't even do something as basic as encapsulate a snippet as a control to reuse.

And CSS is plain stupid, the very foundation of it is quite obviously broken. The precedence of operators is a constant annoyance. And let's not even get started on how it lacks basic inheritance, making it a nightmare to maintain.

I can't understand how any programmer who had actually used the alternatives could claim such things. I suspect you have little experience in programming so aren't even aware of the alternatives.
I can't verify this particular story, although it sounds true. However, all the general stuff about norwegian policies and ways of thinking are correct.

Interestingly enough, the government involved norwegian philosophers when making plans for all the oil-money that was going to come in. This in turn lead to the oil-fund we have today, where the government can only spend the returns of it, and never dig into the actual fund itself.
For the avoidance of doubt, my comment was intended as a humorous way to point out to the parent that they had got their code snippets mangled, and i am not seriously advocating Markdown-compatibility as a language feature.

I'm curious, though, as to how you could possibly think i was being serious. Do you spend a lot of time interacting with people with insane ideas?
Yes but in cities like LA which are planned around cars the major arteries are 3 lanes in each direction, so you can put up signs saying $200 fine if you use the bus lane, give buses priority at traffic lights, run articulated buses with pre paid tickets and you have buses that operate pretty much like trams ('light rail') at a fraction of the cost. In most European cities this won't work as streets are too narrow to accommodate seperated traffic so you need a combination of congestion charging with streets restricted to public transport and/or expensive tunnels. Trams make sense if you have sections of tunnel in denser parts of the city and grade seperated sections in outer areas; buses can't run in tunnels. They also reduce pollution at street level. Diesel fumes from buses are a significant problem in dense European cities.
Fair enough. I certainly agree that Go is an excellent language for people incapable of doing basic stuff like this.
Seemingly, a compromise is required, since "$1.99 for unlimited use, forever" is unsustainable if there are on-going costs.
> Just one idea: you don't come across things in multiples of 7 that often.

Days of the week?
Well, it is "spatially linear". Maybe if you could reference one part of text in some other parts it would be better.
What I mean is that context you are saying about is linear, which doesn't happen often in thoughts. If you have several deep bullet hierarchies and your context happens to contain some items in their leaves, there is nothing that will help you see this context at once without destroying current structure...
That's not generally true. Another C++ dev here. I wish Dart had more success... If I were forced today (to do front-end) at least it should be TypeScript.
Buses around here do.
I would argue that it hurts customers too, at least for some apps. If a developer doesn't get constant revenue there'd be little incentive or resources to update and maintain the app.

The customers are then stuck with an app that might have been good but decays over time.
The only time I used Amtrak there was a child in the opposite seat. Staff put a sticker over his seat announcing that he was alone, which I thought was odd.

Meanwhile round here in London children get free bus travel, so it's very common to see them on local buses, and sometimes trains (tends to be wealthier kids on trains).
Pointers are only real if you ignore MMUs and cache lines and imagine that C actually gives a good model of real modern hardware.
int(foo) and (int) foo(int(x), int(y)) are not legal syntax in C. However, they are in C++ [0], which is my whole point.

[0] your method declaration has a small problem, it apparently cannot have parenthesis around returned type.
Was a pretty good mix of barbecue, beer and talks. I don't remember many details - but I suppose after 14 years the technical contents aren't relevant for the most part anyway...
Unix is not an acceptable Unix
I've managed developers for years, thank you very much.

You're right about that being one of the challenges, but it's still an easy challenge compared to everything else.

(BTW, the biggest issue within the emotions category is that developers tend to deny, even to themselves, that an issue is an emotional rather than a rational one.)
I have never read up on app business models but intuitively I'd say in app purchases create unneeded extra friction. Additionally if you pay up front you have a sense of ownership.

My guess is that I'd only use freemium when network effects matter. The app described in the article doesn't rely on network effects at all but it's nice to see my gut instinct corroborated experimentally.

I'd be interested in seeing this repeated for Android because I'd suspect iOS users are generally more likely to buy stuff.
Why is it underhanded to let out people whose government has locked them in cages? Sounds like freedom to me. Now where's the nearest maximum security prison...
The hidden history of SEAL team 6
Sounds similar to the 4-quadrant system of important / not important and urgent / not urgent. I forget the name of that, but it always seemed like a decent idea for guiding prioritization (if used as a hard rule, it would inevitably lead to not-urgent-but-important things never getting done).
Do you know jhipster?
Whole lotta folk from San Marino! May as well mention sea land then.
As Dale Carnegie said:

"Even in such technical lines as engineering, about 15% of one's [financial] success is due one's technical knowledge and about 85% is due to skill in human engineering, to personality and the ability to lead people."

In this sense a few books about mastering that 85%:

http://www.amazon.com/How-Found-Freedom-Unfree-World-ebook/d...

http://www.amazon.com/48-Laws-Power-Robert-Greene/dp/0140280...

http://www.amazon.com/How-Win-Friends-Influence-People/dp/06...

http://www.amazon.com/Long-Walk-Freedom-Autobiography-Mandel...
Google Play App of the Week: Palabra
I'm launching an app in a couple of weeks and I'm really worried about the revenue model. It's an app that acts to an client to an other service and they'll probably start charging for the API in the near future.

I felt like I had a few choices seeing as I'm foolishly doing this full time and need some kind of revenue:

1) Free + Ads

2) Free + Freemium for "pro-features"

3) One-time fee

4) Subscription fee

I have a distaste for ads so I really didn't want to go down that road.

I don't like freemium because looking at "pro features" and valuing them based on them alone it seldom seems worth it. Also keeping useful features away from non-paying customers seems lose-lose.

I could go with a one time fee but then I won't be able to support it over time and the API fee's will eat away any revenue, no matter how small, over time.

So I've decided to launch with a subscription yearly fee (through a in-app purchase). From all examples I've seen of changing revenue model to subscription model after you've launched it seems almost impossible without the mob getting out their pitchforks. It also seems more honest to have the subscription carry over than launching a separate new app that you have to buy for future OS versions.

Still, mentally users aren't really used to paying subscriptions for an app so it remains to be seen if its successful. Also since most people don't pay for this service itself already there's another mental barrier.

Actually if the app wasn't dependent on a service I'd rather see you'd own the app and subscribe to updates, it seems like a much better model since you never lose "ownership" even if you don't pay, but unfortunately app stores don't support that model.

I think my app is better than the competitors but will people choose a competitor because of the subscription model? It will be interesting to see.
That is a political problem. We had a considerably more reliable railway system before the whole faux privatisation nonsense.

We screwed it up exactly because the political obsession with creating a more Americanised version of capitalism, partially forced down our throats by the divide and conquer strategy of the EU.
Different people have different problems. For a web dev HTTP is "basically OK" as author says, but for a network engineer it is very much not (to the point that 2.0 was created to be completely different). I personally don't see how some new html/js/css dialect could efficiently solve the problems for everyone out there. How do you make both CoffeeScript and Dart user happy with a single syntax? I prefer to have a bunch of specialized high-level tools to choose from depending on a situation, than forcing them all into some one-size-fits-all mishmash (which almost always fails)
Ah, I got what you mean. We've thought about the idea of linking a list item to another and may implement it in the future.

Another way to solve this problem is to have tags, like #project, and when you click on the tag all list items that don't contain this tag will be filtered out.
This is a really good point.

However, there are some apps that do have a model of $xx for unlimited use, even where there are ongoing costs.

This is sustainable if the app continues to gain new users, hopefully at an accelerating rate. It works like a pyramid scheme where the new users coming onboard subsidise the cost of the existing users.
The passwords I create myself are secure enough. But holy hell, entering them on devices with nerfed keyboards (phones, TVs, etc.) is a royal pain in the ass.

So: do I make my passwords less secure and easier to enter on a nerfed keyboard?

Avoiding this pain has been the strongest motivation for me to explore password managers.
No kidding. I don't know how many time I've tweaked my code after starting to write some docs (docstrings/JavaDoc/etc.) and realizing that my abstraction boundaries were wrong. If writing those docs were somebody else's problem, my code would have been crap. This is after 10+ years in industry.

On the other hand, end-user documentation can be a lot of really tedious screenshotting in some markets, and it can't always be automated.
Yes, but I linked to McConnell v. FEC, which was a challenge to McCain-Feingold much like Citizens United v. FEC. The issue was already on the table, the decision just happen to go the other way.
Yep, the examples are not convincing. Some even make to code worse.
Why India’s Favourite Maggi Noodles Is Banned? Trust Me, It’s Not “Excess Lead”
I don't view freemium as a business model, I view it as a distribution model. The distribution model changed from paid to free. This usually results in a user base that grows faster but pays less. By making the app free you've set an expectation of not having to pay. This attracts a certain type of customer, which are usually much harder to convert. If you're trying to build traction for investors this might not matter. If you are trying to monetize then this does matter.

The business model changed from a one time purchase model to a micro payment model. My recommendation would be to try a monthly payment model for v3. Let the users pay to access the service (setting an expectation to pay for value) but allow them to pay less than what you perceive to be the cost barrier (the amount you believe is the maximum amount they would pay to give it a try). I'm going to agree with others that you are priced too low. One of the best lessons I've learned is that it's not what you think it's worth, it's what your customer thinks it's worth.
Olacabs.com Hacked
> Some developers aren't great at gathering requirements, estimating costs, triaging requests, saying no, or any number of other things...

To be fair, nobody is great at those first two.
I agree, it's a really complex interaction.

You have to consider:
1. The number of users that would never pay for your app, but are happy to download it for free.
2. The number of users that would never pay for your app without trying the free part first.
3. The number of users that would pay for your app without trying it for free.

You then have to consider the amount of revenue you lose from Type 3 to support Types 1 and 2. Hopefully you come out ahead, but you may not.
You got me there!

But just thinking around weeks, apart from a fortnight do you actually count the days in multiples of 7 or just think about months or a period of weeks?
Nobody seems to care about that on the web.
So what if she did base the amount on her husbands debt? She believes she's in the right about the discrimination suit and wants to further the case. She is, however willing to stop for a certain amount of money.

What is wrong with that amount being the amount needed to get out of a tough financial situation? She wants something for giving up being right, and if that debt is a big strain on her family, then why not equate that strain with vindication and equal them out?
Open your eyes. It was on the front page and the comments were terrible.
Haskell has GC and lazy evaluation. It's not even relevant.
I like the general idea of defining protocols that can help password managers work more seamlessly. But this seems too low level. Most online services run HTTP services, and afaict, this protocol wants to run on TCP/TLS (though it doesn't specify); seems like it would be more sane to define it as a HTTPS/JSON api for password rotation, given all the online account providers generally have https servers and could easily add a new https endpoint.

But I think the more interesting problem, which this totally ignores, is how to plug in to account creation. If I'm a normal user, and a page presents me with a sign up form, I want to autofill the choose / confirm password fields; if I don't I'm probably going to choose a weak password - or worse, one I'll forget entirely. I suppose you could say "just tell your password manager about the account later and let it choose a better password" but the proposed protocol doesn't work at all if your password manager doesn't know about the account (or doesn't know the password). Whereas if you can plug into the creation flow - possibly via some html / js api - the password manager can be like "hey I see a account creation form that wants you to create a new password, want me to do that for you"? And boom, you are always generating strong passwords.

And ideally we'd have a similar standard for login pages so password managers could slurp up your existing logins as you use them. 1Password does decently at this, but every once in awhile I encounter a bank or some other service that decides to ask verification questions or have a two-page login flow, that 1Password just can't deal with.
Yes.. till the time your work speaks for you, you need a voice to be heard!
That's great to hear! I haven't ridden it in years, you are right. Back then they made a survey on how much it would cost & the price tag was something ludicrous. Hundreds of millions or maybe a billion? I dunno. That was when I formulated the idea that this is lame. Much poorer countries manage electric trains. etc etc. Good to hear they are making the switch.
Why not speaking about it ? It will give you contribution (you can refuse if you don't like it) and no one is going to steal your idea : https://news.ycombinator.com/item?id=9663203
Wow, Cunningham's law in action! Thanks for posting, that sounds like a fascinating study. May simply be a case of bad toilets, though; from the article: "Those with a government-built toilet were especially likely to choose a bush instead."

EDIT: All cultural change is just slow. Give a European toilet to someone who's been using squat latrines all 40 years of their life and they'll perch. Give it to a younger person, and they'll learn the new way.

Also, it looks like the cited statistic is a bit dramatic; only 21% of individuals who live in a household with a latrine practice open defecation. 80% efficacy is pretty good in social interventions. The household stat basically just says to me, "most Indian households include elderly members, who don't want to change their ways".

EDIT 2: Link to paper: http://riceinstitute.org/wordpress/wp-content/uploads/2014/0... the graphs of age by defecation rate on page 6 support my age-related guesses.
Have you tried scrolling landing page? There's more info on the bottom of the page :)
Thanks for the comment @RMarcus.

> I'd be interested to know what kind of policies there were to control the
> cache size (will it just expand to fill up Redis / memcached?), as well as
> how cache TTL is handled.

Currently, there are no policies. Yes, the cache size will expand to as much data you put into it (without expiring). The nice thing about the way I wrote this is that any options passed to the decorator that are not handled by supycache itself are handed over to the `backend` (ie: your memcached or redis connection object), so that is one way to pass on configuribles to the backend.

> Being able to determine which parameters "matter" is an interesting feature.
> It doesn't immediately seem useful (if the value of the parameter won't
> change the return value of a function, why does it matter?).

So, the thing is that it is not the 'parameter' that 'matters' it is the value of the parameter that makes this interesting. Actually, this use case came out of necessity -- I felt the need to add an `lru_cache` for a method that operated on some parameters but instead of caching the return value to a key created by the hash of all the parameters, I needed to create a new key on just one parameter (actually, one attribute of one parameter -- kinda similar to the ^user^ object example in the readme).

> It'd be interesting to see some kind of dynamic support for the keys. For
> example, having a cached value for if parameter `a` is larger than parameter
> `b`, or for if the first argument of a function is "None".

Sorry, the docs have not been clear about it but the 'cache_key' can also be a callable which is only called at run_time (with the args/kwargs) passed to the decorated function. That'll allow you to define your own cache-key-creation rule ! I'll update the docs to mention this.

Thanks for your comments ! Glad you like it.
I'm with you.

I really don't think people with that mindset could put together the sort of shit we do on the enterprise mindset side of things. The tools are carefully picked to be entirely the opposite to the contrarian mindset.

So we have a system that has about 500 HTTP endpoints, 600 service endpoints, 4MLoC, several TiB of data, several TiB of documents, handles 5000 concurrent users 24/7 ramping up to 2 million euro consumers (not concurrent) and 10 full 42U racks of kit in two facilities. Oh and strict security isolation through several layers.

Java+c# is the only answer.

But 50 times a day someone says, hey rewrite it all in Ruby and Monogo. That's a joke.
Let's build something to help solve this privacy problem. Who else is in?
You were called upon to give some examples. Yet all you offer is more hyperbole. One is beginning to suspect that despite your assertion that you "know" Powershell better than most who use it daily, you are actually just a troll.

Yes, I am calling you out. I am challenging you to provide concrete examples where Powershell has less discoverability than bash or zsh. I am challenging you to explain why ISE - an environment designed specifically to combine REPL with script authoring - is "unacceptable".

And please, no more hyperbole or condescending remarks.
Then it's not $SPURIOUS_GARBAGE, is it?

My point is that it's not exactly rocket science to add an if/case statement in the Submit script that checks whether the URL being submitted is on a list of domains for which the '?' and anything after it should be disregarded.

'Twould also be great if it recognised that www.bbc.co.uk and www.bbc.com are effectively the same site.