It's rather ironic that a discussion on what Christians believe would be based entirely on quotes from before the birth of Christ.
I think though that he did say something relevant to the question at hand: "The kingdom of God is inside you" (Luke 17:21) (ἡ βασιλεία τοῦ θεοῦ ἐντὸς ὑμῶν ἐστιν).
Sorting has a simple local optimum implies global optimum property. If a list is sorted than any (not necessarily sequential) sublist is sorted, and the converse. No such property applies to TSP.
I think that the best way to think about why some combinatorial problems are hard and others easy isn't to ask what makes a problem hard, but rather what makes a problem easy. Combinatorial problems seem to be hard by default. It takes some special simplifying property to make them easy.
That still seems like a major issue, because I and probably quite a few other people rely on the security page to decide when to look into upgrading.
I hope there is some rationale for why the security fixes in later releases were not serious enough to warrant an advisory on the security page, rather than it just being an oversight.
Yeah, that might work with a default keyboard layout but it doesn't work with a polytonic Greek layout. How would you type a lowercase alpha with an acute accent and a macron that way ?
Yeah, I was hoping to find some general information on how the Compose key is (or was) supposed to work. It's easy to find info on how to assign the Compose key to a particular key but I haven't found anything on how to actually use it to input more or less complex character codes.
Part of the problem may also be the difference between precomposed and non precomposed glyphs in Unicode, which I don't really understand, but it seems that if a keyboard layout is designed to use precomposed glyphs it may not allow you to further compose those with other code points.
For example there is a character that is a lowercase alpha with both an acute accent and a macron on top. With the right font it displays correctly (it probably wouldn't if I tried to copy-paste it here) but I don't know how to enter it on the keyboard. I suspect that's because there's no precomposed Unicode codepoint for it and my keyboard layout only seems to work with those.
The correct encoding for it is "GREEK SMALL LETTER ALPHA WITH MACRON" (Unicode name) composed with "'".
Does anyone know of a good resource explaining how the compose key is supposed to work in general beyond the simple cases like those discussed in this article ?
I have an interest in some less spoken languages like Ancient Greek and Sanskrit and though there are specific keyboard layouts that mostly work there are still some less common combinations of diacritics used in writing Ancient Greek, for example, that don't seem to be covered.
Is there some way to use the compose key for entering general Unicode sequences for example, that would work for different applications ?
I'm a Linux user but I'd be interested in seeing a solid exposition on this topic even if it was for a different OS.
Yeah, what I said isn't completely accurate, because I didn't take into account the tax rate. But the factor is still larger than 1, assuming you have any revenue at all, because in addition to what you payed them in salary you have to pay tax on the 4/5ths of their salary you couldn't deduct in the current year.
If in your example you hired the construction workers as employees and, for what ever reason, kept them on the payroll, wouldn't you still be able to deduct the salaries you pay them each year ?
If not it seems like a colassal disincentive to employment, which is the opposite of the result usually sought by government policies.
I've seen previous discussions about this on HN but there seemed to be disagreement about whether this change required developer salaries to be treated as R+D or only allowed it.
If this is really the way it works, defining some salaries as necessarily not being deductible from revenues, then it makes no sense for multiple reasons.
First the developers are still paying income tax on their salaries so that money is getting doubly taxed in the year the revenues are received.
Second the government generally seeks to encourage employment. This would have the exact opposite effect because any employee you hire who's doing software development would cost you (1 + 4/5) times their salary in the near term.
I wonder how much of the downturn in tech employment this year is being caused by this.
I have a hard time understanding why this so bad and the article does nothing to explain it. As I understand it companies only pay taxes on their profits, which generally speaking is what's left after expenses, including salaries, are subtracted. If that's the case then why would higher taxes on profits force a company out of business or to layoff staff. If anything layoffs would tend to have the short term effect of increasing profits, which would only further increase taxes.
I can understand how a sudden unexpected change to the tax code could catch people off guard and cause short term problems but overall I don't see why this particular change should be so devastating once any transient effects have been absorbed.