|
The world's largest Internet retailer is ratcheting up its courtship of apps software developers as it pits its Kindle Fire -- and potentially other mobile gadgets -- against Apple Inc and Google Inc. Games and apps are key to that effort, so Amazon is plowing a lot of resources into wooing this increasingly important community. On their Wish List: more devs, more apps, more money.
|
|
|
|
|
Nothing new here. Microsoft has been successful in a large part because is has been wooing developers. While Apple has been emphasising user interface and ignoring the programers, Microsoft captured the business market, and other developers. Thus businesses have depended on the Windows platform, and users have a ton of applications they can run on Windows.
|
|
|
|
|
Apple made big bucks from manufacturing appliances with minimalist/flat looks with sharp edges - what a shame PC manufacturers misses out on this entirely
dev
|
|
|
|
|
Apple has been great at marketing. Use to be a big Mac user, but think Apple dropped the ball because of pricing. In part because of Access and because of pricing, I moved to Microsoft Computers. Since then have not had a single apple device because I thought the price was too high. I really like the designs, but, not at the price.
|
|
|
|
|
Yep. Function first, then form.
I don't care how pretty it looks, if it doesn't do what I want, then it isn't going home with me.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
Clifford Nelson wrote: Apple dropped the ball because of pricing
did they ?
Looking at their profits and stable income and their 5 years stock market profile (going up) I would say that they are a succesful company releasing good hardware and selling them with a profit.
So they are good capitalist.
Watched code never compiles.
|
|
|
|
|
yes, i think aesthetic is very important (especially me here in Asia... offending objects/texture/color combination killing me) but I don't think I'd like to part with me money for an iphone (been using Samsung and most likely next phone I'd try one of those made-in-china no brand android phone which looks exactly the same)
I don't mind paying more for designer furniture however - because furniture last, iphone is a toy last no longer than a year or two and you get bored
dev
|
|
|
|
|
Yet, Amazon is notorious for making it hard for overseas developers/authors/ect to get paid.
|
|
|
|
|
So, here’s a quick summary, for those of you that need a cheat sheet. If you’re using C#, arrays start at 0. Unless you’re using C# with an Office application, because then it starts at 1. Unless that Office application is Access, a Data Access Object (DAO), or an ActiveX Data Object (ADO), because then it’s back to 0. Simple, no? I can think of a whole array of reasons.
|
|
|
|
|
Yes, getting hit with legacy issues. If I remember correctly, VB pre .NET was from 1, and so we suffer with this legacy.
|
|
|
|
|
Good timing just before the Games! I'll see every gold medalist raising their index finger as a VB person and those who raise their fist as C,C++... ... anti-legacy!
|
|
|
|
|
Clifford Nelson wrote: VB pre .NET was from 1
Which is strange because arrays in BASIC are zero-based.
|
|
|
|
|
Clifford Nelson wrote: If I remember correctly, VB pre .NET was from 1, Not really - you had a choice of specifying whether 0 or 1, but the default was 0.
|
|
|
|
|
Terrence Dorsey wrote: I can think of a whole array of reasons
Starting from 0 or 1?
|
|
|
|
|
0 isn't a real number anyway, how can you have zero of something? Oh I have zero cake (and I assure you, I don't).
Next you'll be telling me that I can keep counting backwards : 3,1,0, then ?,??,??.
What kind'o'crazy maths is this?
|
|
|
|
|
Zero is my hero.
|
|
|
|
|
Look at it this way: when you are born you are zero years old. It's perfectly natural to start with 0
|
|
|
|
|
You get used to it.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
Starting at 1 is just silly from a low level perspective...
array[n] is equivalent to telling the computer "I want to read/write the data at the start address of the array, plus n * the size of an item in the array". If you started at 1, you'd be wasting an item's worth of memory or you'd have to do "(n - 1) * the size of an item in the array", which adds in an extra operation for every array access.
One way wastes memory, the other wastes CPU time, or just start at 0 and be more efficient.
|
|
|
|
|
So to help you get prepared we have created a 6 week plan for you.The plan is based on a minimum of 10 hours study time per week. The better prepared you are the better you will do with implementing Windows 8 within your curricula or even simply having the discussion with students using Windows 8 next term. From a Microsoft perspective we have a massive amount of materials to help you prepare and create a very comprehensive application and we provide you with the suite of Tools and Documentation to help you create their very first Metro 8 App. Get ready to graduate magna cum app!
|
|
|
|
|
Terrence Dorsey wrote: Get ready to graduate magna cum app
If you are too lazy to strive for summa cum app.
|
|
|
|
|
Is it worth the effort. There are a lot of people out there still using XP. That should mean that I can continue to use Windows 7 until at least 2022 (XP came out in 2002 if I remember).
|
|
|
|
|
I am just now switching to Windows 7, I figure it has been throughly tested by now.
I have no intention of ever switching to Windows 8, I will wait for the new improved version after that.
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
I think you are right about decision to never switch to windows 8. Vista was bad, Windows 7 was a second version. Windows ME was bad, Windows XP was a second version. Windows 95 had issues, and 98 basically fixed them.
|
|
|
|
|
If you’re a software developer and you’re thinking about changing jobs, you’re probably at least a bit anxious (if not downright freaked out) about the prospect of facing a whiteboard armed with only a trusty dry erase marker and your wits while an interviewer fires a coding question at you. That’s not shocking because software development interviews are weird: the skills necessary to answer the technical and behavioral/situational questions that are asked don’t necessarily map 1:1 with the skills to be a good developer. Ask me the questions, bridge-keeper. I'm not afraid.
|
|
|
|