"If you ever suffer from Impostor syndrome, you should probably prepare even more, because the standard interview situation will make you feel like an Imposter in the worst way."
It may also help to think of that Dunning-Kruger study [1], according to that it would be normal for the competent to be full of doubt while the less experienced would be full of confidence.
The current limit (0x10FFFF) is the artificial restriction on UTF-8 to match UTF-16, not the upper bound. UTF-8 supports 2^31 code points with it's current encoding. So nothing needs to change until Unicode consists of 2.1 billion code points or so.
In my mind that will only happen as a result of extreme carelessness.
Interestingly, the home row issue you experienced on the phone is rather similar to the reason qwerty was invented in the first place, to avoid key jamming on mechanical typewriters.
Isn't a better solution to get software that supports PDF natively like Acrobat, then edit the documents there instead of doing a (poor) translation to Word.
I think this is especially true for a startup that makes little to no money, and where the users pay $0. If the users complain, just offer a refund. :)
I agree, and I also often find that the attached discussion that follows almost always takes up about half the page.
Usually directly skipping half the page takes you to the actual discussion. I think it could be interesting to add a pivot that moves that comment and it's discussion to the bottom (but probably above downvoted comments) when it reaches a certain length. It could still keep it's votes and so on.
I agree, but an application is not all content, it's also a machine, and the interface needs to be intuitive to use and separate it self from the content.
If depth, texture and so on can be used to convey functionality, but isn't in the name of fashion, then it's form over function IMO.
It's hardly unusual to find a 3rd party app that does something better than a system provided application regardless of platform, where better is in part dictated by personal preference and needs. What's a bit unusual is that the choices are google, google, google, google, google. Seems you have a bit of a bias there.
On die cache is orders of magnitude faster than regular ram. I have always thought that more cache would be a sensible addition when a process shrink give more available real estate.
On the other hand, I think that a prefix notation more closely resembles the way natural languages are spoken in the aforementioned parts of the world. For example (+ 1 2) if read aloud would become "add 1 and 2", which sounds like a verbal instruction. Reading infix notation aloud in many ways strikes me as less natural, perhaps it's something that is learned from an early age and thus appear natural.
But the issue here is not only the end users, but also publishers and others who could potentially make a business out of selling this authors work without paying him one cent. There is in my opinion little reason to want to get rid of ones copyright, it's better then to declare that it can be used freely without charge for non commercial use for example. Or if the intention is to sell it, simply not using any DRM schemes at all.
But by giving up his right as an author to decide how his work is copied and distributed, he has no way of enforcing that. Instead he relies solely on the goodness of his "customers" hearts. Most open source licenses understands this and keep a final say in how the work can be used, for example.
It's a personal preference, and it's still possible to pick a list view with no album art in iTunes 11. I often have a visual recollection of album covers, be it singles or whole albums as well as physical location (if it's real singles).
It's not really only albums that gains from album art, singles with remixes would still have a cover which I vastly prefer myself as compared to a blank square.
Still it's a critique of iTunes as such, while the submission is related to generating color themes from an image algorithmically.
What if you fail on line 20? Carrying on may cause cascading errors, what alternatives are there to return an error code directly apart from storing a return value in a variable, use a goto to the end and return once? (assuming this is C)
Me too, and if the surface is the same size as an iPad then the keyboard is not going to be fullsize. If I add the wireless Apple keyboard ontop of the iPad about 2 keys sticks out over the edge if I line it up on the other end.
How is that working exactly? If you are using custom graphics it needs to be stretched to fit a larger screen, or letter boxed to keep it's original ratio. If you are using nothing by standard UI elements it will adapt to the screen.
I've got the impression that most of the phone internals has been updated. I prefer that to cosmetic design changes for it's own sake and gimmick features that isn't yet established and/or used by many. I like what Apple bring with it's media expertise and the added hardware image processing and panorama photo.
No, because the article essentially asks: does the new iPhone have enough bells and whistles to keep it's position, and compares it to other handsets like Nokia Lumia and Galaxy Note. It's putting up iPhone 5's hardware features against a few competing phones. It does not take platforms, operating system or any software into account.
But Android is not a phone, look at market share by smart phone vendor instead of OS. It's a comparison that makes much more sense since there are many vendors, each competing with each other, all with individual market shares, all using the Android OS.
I agree, it seems to be the kind of value you can subscribe to in order to advertise your sophistication to the world. The irony is that the idea is not original so the effect is the opposite, instead of signaling sophistication it signals that you want to appear to be sophisticated and are someone who knows a lot about design.