Hacker Newsnew | comments | show | ask | jobs | submit | wmil's comments login

Rebinding system shortcuts makes life difficult for application developers. They have no idea if they can use CTRL+L for their shortcuts or not.

In-app rebinding also makes life difficult for the developer in the future, because any new feature added may have it's key rebound by some users.

Look at Emacs. Technically users can rebind things, but it's easier to learn the defaults since every other key is already bound to something else.

Generally everything is rebindable internally, but users are only offered compatibility modes with other popular software.

I've played more than one game (Freespace, Tribes, Warframe) that had more than 30 keybinds. Managing keymaps can be challenging, but it's not impossible.

And discussing this reminds me how much of a pain it is. What we need is a system where we set our own defaults in an XML file or some other common format (or use a software tool to do that). Then we can select this keymap when we install applications.

That's not the way to help people with low bandwith or very high latency connections. They need more javascript, not less.

SPA designs can actually make CRUD apps significantly more useable on slow or unreliable connections.

[Citation needed]

I've run across far too many "mobile-friendly" websites that start by loading many MBs of JS libraries. And just flat-out fail to load if any of said libraries fail to load.

I'm talking about bad connections, not necessarily mobile. This applies especially to situations that companies like G-Advetures face. In South America they have to deal with perfectly fine desktops, but very high latency internet connections. Submitting a form can take 20 minutes or more.

A text only version like the one described would be far worse than a JS heavy one. JS free forms are naturally synchronous. So each edit would kill the ui for a full refresh cycle.

On the other hand a SPA type page can send data in the background white you're doing other work in the app.

Sure there are crappy mobile friendly sites, but that doesn't invalidate the idea.

On a side note I'm not really sold on the whole CDN idea, it just looks like another HTTP request and another point of failure. Concatenate / uglify seems like the better solution.

The idea would be that for a web app, posting or fetching little bits of JSON every time an action is taken would be less intense than getting a whole page every time. Of course, as you have experienced, that's not helpful if the initial page load is too heavy. Also it's not too helpful for sites that have content to read, rather than actions to take.

ps. "citation needed" is kind of obnoxious when it's something you can think through for yourself.

In general, not unless the judge rules the claim was made in bad faith. There are some specific exceptions.


It's in "marketable securities" so not exactly cash but close. The other issue is that much of it is overseas money, so Apple will take at 35% tax hit if they repatriate it.


Repatriation is somewhat of a red herring. Money is fungible. Even if it is technically (on the books) "overseas", it can be (and usually is) invested in U.S. markets.


Yes they are waiting for their employees (congress) to pass another "one time" tax break that will let them repatriate all that cash tax free.


It should be tax free. The money was made overseas from products made overseas and sold to overseas customers by overseas entities.

Taxing money coming into a country is really bad economics and amounts to just pure greed.

Countries should want money coming into their markets. Not punishing it.


Remember every dollar not paid by Apple and the like is an extra dollar that some other poor US tax payer has to pay. Given that everyone wants the services that taxes pay for (if not move to Somalia) then the taxes should be raised in a way that causes the least amount of distortion to the economy. Letting some companies pay no tax and others 36% is highly distortionary.

I would also be more convinced of the idea of not taxing the money coming in to the USA if it had actually been taxed in the countries where the profits had been made - let me introduce you to the Double Irish Arrangement [1].

1. http://en.wikipedia.org/wiki/Double_Irish_arrangement


then payments from child companies to parent companies that end up as profit should be taxed in those other countries.


Production of water inefficient crops would shift to states with water, Cali famers would shift to more efficient crops.

The US is a big country, there's no need to grow almonds in the desert.


It can happen in a few languages, but PHP is notably more aggressive in trying to convert to int.

Actually a common way to grief new websites is to try to register '0' as a username. `if (string)` is a common way to check for null, and '0' will often fail.


One theory is that the US is big on white, mild tasting food because people had to purchase a lot of food from strangers. There were frequently no deep family roots in most cities.

White mild foods (mayo, white bread) can't hide spoiling or contamination as well, so they were safer to buy.


Another theory (at least on this side of the pond) goes something along the lines of: After people got access to refrigerators and freezers and such it was no longer necessary to hide the taste of spoilt foodstuffs, and thus it became high fashion to make your food as mild as possible to show off your fancy new fridge.


Open an incognito window and google the article title. Usually cookies and referrers trip the paywall.


The problem with supporting a "mixture of incomes" is that some people end up paying a small fraction of the price for equivalent real estate.

That doesn't square well with some people's values.


those values are greedy and shitty, and we shouldn't respect them.


Lumping both cities together as "warm-weather" seems lazy. Miami is hotter in January than San Fran ever is.



Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact