Don't really care for it; too many developers use it as a crutch and wind up with server-side vulnerabilities due to counting solely on JQuery-based script for their primary logic. I work with several devs who think it is the end-all, be-all of web development, whereas I just think it's more of a convenience, particularly with respect to updating DOM with web service results. But you could replace it in an app with another library, and I'd care very little.
Becomes the big language that everyone uses for everything. Like server-side JS. I generally do not like loosely typed, dynamic languages. You lose static analysis capabilities and gain a ton of runtime errors. Try browsing the web with JS debugging on and see how many errors have been getting masked just for the sake of a non-obtrusive browsing experience...it's terrible.
I'd also say I fear shareware coming back, but that already happened with the "app" market. It's like people don't remember the bad old days where there were a million crappy little word processors and other half-assed productivity apps and are excited to have half a million of them to look through just because they cost $1.
No, a whistleblower revealed that AT&T gave a room in their main switchboard building to the feds back in 2007. It just wasn't reported with much fervor back then. In those days, news orgs were afraid of being labeled "unpatriotic" for reporting all the bad things our government was doing.
The easiest way is to have someone you've worked with put in a word for you, but seriously, use a job site. I haven't touched Dice in 5 years, and I *still* get emails from recruiters via that site every damn week (I can't even figure out how to pull my resume from it).
HOWEVER, make damn sure you can ace the tech screen and interview. Nothing is more pathetic than a middle-aged developer who doesn't know squat in a face-to-face; and for God's sake show enthusiasm and confidence. If that means going on a ton of failed interviews to get practice (and see what kind of questions you'll get - and they tend to get repetitive after a while), do it.
1. They have little expertise in something as complex as a multiplayer server infrastructure. iTunes it ain't. Microsoft has the benefit of owning an entire server-based ecosystem of software that they can leverage. Add to that the difficulties in preventing hacking (cheating), which Apple had relatively little experience with as well.
2. Gaming ergonomics. Tablets suck for gaming, and their controller looks like something from the 80s. They can catch up fast, but God help them if they come out with an Xbox controller clone, ala Nintendo.
3. Gaming development environment - they need an SDK, they need a language (gonna seriously expect game devs to adopt Objective C?)
4. What would differentiate their device? They need exclusive content, and this late in the game, it's going to be problematic trying to convince anyone to go exclusive with them given the risk and the presence of *two* major players with track records. Without exclusive titles, why would someone go with an Apple console other than brand loyalty? Would an Apple fanatic not have one of the other consoles, and if not, why would they suddenly decide to get into hardcore gaming?
5. No first party experience. Who would they buy?
6. Is Apple really willing to lose money on consoles like Sony/MS? That's never been their MO, and if they come out more expensive than MS (without a Kinect 2, mind you) who would buy it, other than some hibernating NeoGeo owners?
Kudos to you mentioning FDG. That book is a great read and an even better reference. I try desperately to get my coworkers to read it, as many of them have a somewhat shallow understanding of.Net; unfortunately, laziness prevails, but getting through that book cannot help but make a person a better developer.
I haven't used Java since.Net 1.0, but does Java have the syntactic sugar constructs, like the 'using' statement (for clean handling of unmanaged resources)? I don't recall it ever getting properties (although it seems to have something similar to auto properties with some new interface feature IIRC), but.Net has a bunch of those that make the source code a hell of a lot easier to read. I think it may have gained something similar to attributes (metadata), but.Net would have had about a 10 year head start on that.
Read as much code of as many different styles as you can. Eventually, you will hopefully start just getting a feel for programming much like music, where different code has different styles. You'll see manifestations of different patterns and start to gain a deeper understanding of it (it can have an almost zen-like quality to it)...why certain patterns get used, why certain developers use patterns that don't make sense to you, what kind of developers the authors are. It took me years before I started to get a feel for reading other people's code, but I have an idea as to how good a programmer is and even what kind of everyday personality they have from reading their code. It really is like music.
And one more thing: don't count on comments for guiding you through this; it's rare to come across well-commented code, especially in a professional environment (ironically enough).
Google's best innovations came in the server space, not the consumer one. They have dominated smartphones by buying a Linux variant, and their biggest contribution to 3rd party software development has been a purchased what is essentially reverse-engineered Java with some different libraries. If they had focused more on commercializing their server efforts, they could have been a major force in the enterprise, but it seems like they ceded that ground to Microsoft, much like MS has consistently ceded the consumer market to Apple by not adequately commercializing their own research projects.
We got the Congress we deserve, so we have no one to blame but ourselves. How many times did the electorate fall for commercials saying "vote for me, I'll make the country safe"? Time and time again, politicians go to the law and order/kill the bad guys card, and the public falls for it every...single...time. Instead of being outraged, the country should be planting a giant palm on its gigantic face.
I stick with it because the Windows ecosystem just works (I don't have the blue screens, etc people rag on MS about; I also don't keep old hardware; even IE hasn't crashed on me in over a year, while Windows hasn't crashed on me since Win7 released to MSDN).
Linux is too much of a hodge podge of mix-and-match for my liking. It reminds me of the shareware days, where there were a dozen word processors and other productivity apps to choose from, all written as pet projects and flakey as hell. I just want to put stuff on my system that all works similarly and well together without having to research which ones are decent.
That is INSANE. W3C moves at an absolute snail's pace to ratify anything, so handing over a market that is as bleeding-edge focused as gaming consoles would be suicide. The same would be true of just about any consortium formed to do the same. There would be too much red tape, and too many competing interests to make it work.
Why the knock on the One not being dedicated to games? The thing has nearly the same specs as the PS4, meaning it's got plenty of power, it's got a monster network infrastructure in Live, so why shouldn't we expect it to be capable of other things, like firing a warning shot towards AppleTV? Would those people who want a pure gaming system be happier with an Atom-based console with a monster video chip?
Slashdot Mirror
It's amazing what people will attribute to Apple.
Don't really care for it; too many developers use it as a crutch and wind up with server-side vulnerabilities due to counting solely on JQuery-based script for their primary logic. I work with several devs who think it is the end-all, be-all of web development, whereas I just think it's more of a convenience, particularly with respect to updating DOM with web service results. But you could replace it in an app with another library, and I'd care very little.
Becomes the big language that everyone uses for everything. Like server-side JS. I generally do not like loosely typed, dynamic languages. You lose static analysis capabilities and gain a ton of runtime errors. Try browsing the web with JS debugging on and see how many errors have been getting masked just for the sake of a non-obtrusive browsing experience...it's terrible. I'd also say I fear shareware coming back, but that already happened with the "app" market. It's like people don't remember the bad old days where there were a million crappy little word processors and other half-assed productivity apps and are excited to have half a million of them to look through just because they cost $1.
The Start button has an associated context menu - http://www.guardian.co.uk/technology/2013/jun/27/windows-81-review-hands-on. Just right-click it.
Yeah, and Sinofsky "left" to reflect and look ahead.
No, a whistleblower revealed that AT&T gave a room in their main switchboard building to the feds back in 2007. It just wasn't reported with much fervor back then. In those days, news orgs were afraid of being labeled "unpatriotic" for reporting all the bad things our government was doing.
There is no summer of learning; it's every day.
Wyatt's computer from "Weird Science".
It's also a preview build. Get over it.
Seeing as how he already made the trip successfully, there's not much to debate about the practicality of it.
The easiest way is to have someone you've worked with put in a word for you, but seriously, use a job site. I haven't touched Dice in 5 years, and I *still* get emails from recruiters via that site every damn week (I can't even figure out how to pull my resume from it). HOWEVER, make damn sure you can ace the tech screen and interview. Nothing is more pathetic than a middle-aged developer who doesn't know squat in a face-to-face; and for God's sake show enthusiasm and confidence. If that means going on a ton of failed interviews to get practice (and see what kind of questions you'll get - and they tend to get repetitive after a while), do it.
1. They have little expertise in something as complex as a multiplayer server infrastructure. iTunes it ain't. Microsoft has the benefit of owning an entire server-based ecosystem of software that they can leverage. Add to that the difficulties in preventing hacking (cheating), which Apple had relatively little experience with as well. 2. Gaming ergonomics. Tablets suck for gaming, and their controller looks like something from the 80s. They can catch up fast, but God help them if they come out with an Xbox controller clone, ala Nintendo. 3. Gaming development environment - they need an SDK, they need a language (gonna seriously expect game devs to adopt Objective C?) 4. What would differentiate their device? They need exclusive content, and this late in the game, it's going to be problematic trying to convince anyone to go exclusive with them given the risk and the presence of *two* major players with track records. Without exclusive titles, why would someone go with an Apple console other than brand loyalty? Would an Apple fanatic not have one of the other consoles, and if not, why would they suddenly decide to get into hardcore gaming? 5. No first party experience. Who would they buy? 6. Is Apple really willing to lose money on consoles like Sony/MS? That's never been their MO, and if they come out more expensive than MS (without a Kinect 2, mind you) who would buy it, other than some hibernating NeoGeo owners?
Kudos to you mentioning FDG. That book is a great read and an even better reference. I try desperately to get my coworkers to read it, as many of them have a somewhat shallow understanding of .Net; unfortunately, laziness prevails, but getting through that book cannot help but make a person a better developer.
I haven't used Java since .Net 1.0, but does Java have the syntactic sugar constructs, like the 'using' statement (for clean handling of unmanaged resources)? I don't recall it ever getting properties (although it seems to have something similar to auto properties with some new interface feature IIRC), but .Net has a bunch of those that make the source code a hell of a lot easier to read. I think it may have gained something similar to attributes (metadata), but .Net would have had about a 10 year head start on that.
Read as much code of as many different styles as you can. Eventually, you will hopefully start just getting a feel for programming much like music, where different code has different styles. You'll see manifestations of different patterns and start to gain a deeper understanding of it (it can have an almost zen-like quality to it)...why certain patterns get used, why certain developers use patterns that don't make sense to you, what kind of developers the authors are. It took me years before I started to get a feel for reading other people's code, but I have an idea as to how good a programmer is and even what kind of everyday personality they have from reading their code. It really is like music. And one more thing: don't count on comments for guiding you through this; it's rare to come across well-commented code, especially in a professional environment (ironically enough).
Google's best innovations came in the server space, not the consumer one. They have dominated smartphones by buying a Linux variant, and their biggest contribution to 3rd party software development has been a purchased what is essentially reverse-engineered Java with some different libraries. If they had focused more on commercializing their server efforts, they could have been a major force in the enterprise, but it seems like they ceded that ground to Microsoft, much like MS has consistently ceded the consumer market to Apple by not adequately commercializing their own research projects.
He left out wankers. And buggerers.
We got the Congress we deserve, so we have no one to blame but ourselves. How many times did the electorate fall for commercials saying "vote for me, I'll make the country safe"? Time and time again, politicians go to the law and order/kill the bad guys card, and the public falls for it every...single...time. Instead of being outraged, the country should be planting a giant palm on its gigantic face.
I stick with it because the Windows ecosystem just works (I don't have the blue screens, etc people rag on MS about; I also don't keep old hardware; even IE hasn't crashed on me in over a year, while Windows hasn't crashed on me since Win7 released to MSDN). Linux is too much of a hodge podge of mix-and-match for my liking. It reminds me of the shareware days, where there were a dozen word processors and other productivity apps to choose from, all written as pet projects and flakey as hell. I just want to put stuff on my system that all works similarly and well together without having to research which ones are decent.
Like the were drawn with a mechanical pencil
That is INSANE. W3C moves at an absolute snail's pace to ratify anything, so handing over a market that is as bleeding-edge focused as gaming consoles would be suicide. The same would be true of just about any consortium formed to do the same. There would be too much red tape, and too many competing interests to make it work.
Who wants to walk around being photographed by a bunch of geeked-out versions of Dog the Bounty Hunter?
I'm talking about "Xbox", which MS has had for over a decade.
The (current) owner *is* using MS' trademark in the domain name, so they've got a decent case.
Why the knock on the One not being dedicated to games? The thing has nearly the same specs as the PS4, meaning it's got plenty of power, it's got a monster network infrastructure in Live, so why shouldn't we expect it to be capable of other things, like firing a warning shot towards AppleTV? Would those people who want a pure gaming system be happier with an Atom-based console with a monster video chip?