Except when 0xDEADBEEF happens to be the memory address overlaying the custom hardware registers, and setting it to 0x42 turns the blinky light on. There are some cases where manipulating static memory locations is not only a good thing, but the only way to do something (at least for embedded programming). Not saying that your point is invalid, btw.
Which works great if you use makefiles, but for those using Visual Studio for build management, it can be a bit more tricky. First you have to make sure you have perl, then you have to make sure you've got the appropriate build rules in place, then you have to make sure things get built at the right time, etc. It really is nontrivial.
I think he missed the point as to why exceptions are expensive. It's not (only) the setup and teardown. It's mostly the throwing of exceptions. Throwing an exception is expensive when compared to returning a status code and checking its value.
My sister was Teacher of the Year for LAUSD, and if she doesn't spend her own money on supplies for her students, they simply have nothing to write on or with. She has never had a class size under 35 that I'm aware of. Yet, her job is on the line based solely on the test scores of her kids, many of whom are mainstreamed special Ed kids. In what way is this a recipe for success?
Considering this was developed in 1997, this is actually an ingenious way to get "Joe Q User" to call tech support. They boot up their computer, and music randomly starts to play, they get scared, shut down and call tech support. It certainly won't work every time, but considering that this has to happen all within BIOS while the CPU is melting, it's a reasonably good idea.
In case you're wondering what this has to do with the topic at hand: Jose Lima was a well-known baseball player who died last year. His wife became an internet meme before he died, but I'm guessing someone at facebook decided to use her image was likely a legal violation, not to mention in poor taste.
I was walking alone in the woods one day, and I thought they were pretty. I thought, "I'd like a house here some day." So I bought the woods. Sadly, I never had time to build my house there. So now I'd like to sell my woods to someone else who may get enjoyment out of them.
While asking real estate agents the best way to go about selling my land, a developer overhears my conversation and says, "You should just give your land away. You've already prevented people who could have done something better with it for the past few years while you did nothing with it. Why should you profit too?"
I don't condone domain squatting for the sake of making quick and easy cash. But I bought the domains with good intentions of how to use them, and just never found the time to do what I had hoped. Now I'm looking to see who else wants them. I've not prevented anyone from implementing their own good ideas somewhere else.
Ah, yeah, when I'm writing code, I frequently do something like:
Foo *f = Other Foo();
They're so confusingly similar. ;-) But more seriously, I do agree with your point, if there's confusion (or the possibility), they would have to defend the trademark. I guess I just have a different bar for "confusing" than others.
No offense, but web tech on the desktop has been tried before (a la Java) and the user experience sucked everywhere. I'm not convinced this will be any different from the user's perspective.
I agree -- that ATS stuff is hard on the eyes. The goal is laudable, but the medicine is worse than the disease with the way they implemented it. The MS approach is a lot easier to get people on board with, I think.
Oddly, at my last job, we used ventrillo. I happened to have a server from playing WoW, and so I just had the rest of the team use it. Cross-platform, low-bandwidth, and worked awesome.
When I read about these sort of hacks to get performant JS code, it reminds me of how things used to be thirty years ago. Sacrifice code readability to get a speed increase because of poor tools...
The basic gist of the story is this: a year ago, GameFly filed a formal complaint against USPS for treating its game disks different from competitors like NetFlix and Blockbuster (a disproportionate number were broken, lost, etc). This was after already working with USPS to try to resolve the issue before the complain process. It's taken USPS a full year to respond to the complaint, and their response is in the form of a wild goose chase.
"A simple 'Hello World' app created in Flash and compiled to work on the iPhone is substantially larger in file size, and it would take up 3.6 MB when it should be no larger than 400K when made with Xcode..."
Am I the only one that finds both scenarios to be ridiculous? 400k or 3.6MB doesn't matter -- both are stupidly large just to put up hello world...
Which is actually a pretty big deal because it means the integration into VS will be greatly improved. I've not tried the VS 2010 F#, but the plugin version was pretty clunky within the IDE.
The reason I put marketers on that list (and higher than users) is because Apple sometimes goes with "shiny" things which are marketing fodder instead of things which truly improve the user experience.
But you expounded on my point nicely -- Apple and MS have different philosophies about developers.
Apple's focus is and always will be: 1) Apple, 2) Marketers, 3) Users, 4) Developers, and #4 has always been a distant one at best (anyone remember the Rhapsody fiasco?) Keep that ordering in mind, the latest changes make perfect sense.