The idea was supposed to be that you wouldn't have to do this yourself as the OS would terminate metro app processes itself if you did not use them for some period of time.
EDIT: Apparently this is the long/manual way of doing it.
238 karma · joined June 30, 2010
The idea was supposed to be that you wouldn't have to do this yourself as the OS would terminate metro app processes itself if you did not use them for some period of time.
EDIT: Apparently this is the long/manual way of doing it.
So to clarify, my opinion is that they're probably pretty safe as far as maintaining their position in the PC world even if Windows 8 bombs as a PC OS. Losing entrance into the tablet world for two extra years on the other hand is a lot worse since it would be very difficult to get those two years worth of tablet buyers to switch to their platform after having already bought into another during that time.
How the second part actually plays out in the real world is really hard to predict since a lot of it will be based on the hardware that runs the OS. For example, I personally think Windows 8 is a pretty poor Desktop OS, but I'd definitely consider it when buying a tablet. So my problem isn't so much the OS but their current flagship device; the Surface RT looks to have too many deal breakers for me and I don't think I have a need for the Pro version.
How exactly do you figure that Microsoft is one of the largest players in the tablet market? PC market, yes, but they're a late new comer to the modern tablet world.
Now as far as asking whether they would release a tablet that runs hot and has poor battery life -- I don't know, would they release a tablet that suffers from 5+ second delays while typing: https://www.youtube.com/watch?v=VTtf_BgFS08 ?
Delusional is the only way to describe this statement. It almost resembles the garbage Fox News has been giving for reasons why Romney lost the election. First of all, developers in a "corporate" (I emphasize "corporate" because this has nothing to do with windows development) environment generally aren't the ones with the "kill off the competition/brand" mentality. This mentality lives higher up in the corporate chain where business decisions are made. Developers themselves don't make these choices, they simply execute them because that's what the business has decided needs to be done. If the claim was instead that CEOs, VPs, etc, are switching to Linux and getting involved in the management of Gnome, the claim would still be wrong, but at least it could have made some sense.
I've worked on a couple of these applications, they almost always end up having some fake-class system that provides mechanisms for encapsulation, code sharing, and namespacing. There's often almost a hundred of these fake classes defined with thousands of instances living in memory. I grant you that you can use things like the module pattern to accomplish those requirements -- in fact, if you couldn't, then I wouldn't be here talking about it because I'd be writing Java applets instead. But the lack of having static typing to catch simple errors and enabling basic refactoring tools (like renaming something without having to use a regular expression which took 2 hours to "perfect", or simply switching argument orders, etc) was the absolute worst. I've spent countless hours debugging problems that occurred because something like a string was accidentally passed when an array was expected, and only having the actual runtime error occur 50 function calls later because something like "cat"[0] was working fine up to that point. Static typing would have caught that before I even ran the app.
Anyway, these types of apps perhaps aren't as common as websites, but they exist and therefore there is a need for statically typed languages for the browser.
Besides that, I still get feelings of discomfort when thinking about rewriting JS to coffeescript when knowing that the compiler will just write it as JS again.
EDIT: Tried it. In this case it seems to works.
On one hand, I can definitely look at C# right now and see how it is a vast improvement upon C# 1.0. I'll even go as far as to say I would probably refuse to write code in C# if it had not become what it is today.
On the other, I think you can only really change a language up to a certain degree before creating an inconsistent mess. If trends in the future dictate the need for a shift in paradigms, the extent to which existing languages can accommodate this shift is probably limited. I mean, you can often incorporate features that are based on the new approach to thinking about a problem, but once you start changing the core semantics of the language you're probably going to be better off with something completely new.
EDIT: Or step outside the tech field into something unrelated, and see if there are any areas that might benefit from some tool you could create. Though I guess a month might be too little time for this.
* This is based on most browser vendors not being supportive of it.
If you're going to ask me if I had worked on any OS kernels or distributed version control systems, the answer is no. But I would also never degrade people who might otherwise be willing to help contribute to my projects based on some idiotic notion of programming language superiority.
At this point I don't even expect anything better out of him because he did something great for the world. I expect better just because at this age he should be an adult.
It does make me wonder though how he's able to get away with responses like that, when most other "founders" (not sure what the proper term here really is) would have the majority of their users/supporters just go elsewhere.
EDIT: ... Let alone have supporters who get defensive enough to start downvoting someone who stated the obvious (he did act like an ass), while asking a reasonable question too.
Inheritance in JS is at best awkward and unintuitive; if this wasn't the case you wouldn't have so many people trying to fix it. And let me just add that it's not this way because it isn't "classical", it's because it's also not really "prototypal" either. The awkward in-between mix of the two approaches means that no one can decide which, if any, direction is the "true one" to go in.
You have a bunch of people claiming theirs is the fastest and how JS is designed, but then others are claiming theirs is more elegant and fits better with JavaScript's semantics, then another focusing on how inheritance would have been had they probably not decided in the last minute that "oh no, this is too weird, it needs to be more like Java".
I just find it quite ridiculous because I can't think of another language that has these types of problems over something as fundamental and basic as inheritance in an OO language.
I'm not saying a design like that can't be done, but the only way I can think of making it work would involve much better use of the grid system and much better spacing than what they have in these pictures. Considering how limited they are for space though, I think they were just better off with the 2010 look.
The "no fault of their own" part is obviously being challenged by those who claim that the data should have been saved in multiple places. Though I think this just avoids the real issue of the bust having negatively affected users that had legitimate use cases for the service.
Personally, the whole thing made me realize syntax is more or less meaningless to me. I was never really spending that much time making, or correcting, syntax related problems when writing JavaScript in the first place. Though when using CoffeeScript, I was spending a substantially larger amount of time trying to find ways of doing things that I knew were possible in regular JS, but generally avoided in CoffeeScript -- things like mixins, using closures for restricting access to internal members, having members named 'on', etc.
In the end I was spending too much time looking at the JavaScript output to see what was going on continue with CS. Its idioms make the popular subset of JS really great, at the cost of making things outside of it less 'natural' than they are in plain JS.
var outer = 2;
var btn = new Button()
{
Text = "Click Me"
};
btn.Click += (obj, eventArgs) =>
{
var local = outer + outer;
};
How is the above any different/better/worse than what javascript can do?1) I don't program on a whiteboard. It's 2012, I have tools, and they beat the whiteboard setup every time.
2) I will never implement something that I have not implemented before without at least first consulting with a search engine. You see, I am not a genius that will come up with the best algorithm for a calculation every time I am put up to the challenge. My amateur attempts will be no where near as good as what others have collectively accomplished over the years that the problem existed.
For example, in this particular case (I have never had to implement a function that generates Pascal's triangle before), I can guarantee you that anything I came up with at a whiteboard right now would be completely inferior to what the result would be if I was allowed to do a search first. So unless you're trying to see if I am capable of writing any old crappy code so long as the result is correct, your test isn't adequate.
3) Interviews still make me nervous, doesn't matter how many times I have them, I never feel comfortable going through the process. This often leads me to simply draw blanks when given a whiteboard assignment of this nature. You may think this means I am just incapable of solving your problem, or that I perform poorly under pressure, but I can tell you that this type of "put you on the spot" pressure is much different from the type one generally feels in a work environment.
Domain Management > Tools Tab > Exportable List > click Add New Export button > All your domains > and make sure to select "Authorization Code".
As for locking or unlocking, in Domain Management you should be able to just click the select all checkmark, and click the Lock button to set the lock level on all of them.
None of that should be an issue, even when transferring in, a bunch of registrars offer a bulk transfer option. The real pains start to set in if you have gTLDs which have special gotchas when transferring or changing contact information/ownership. I probably wouldn't even have been able to transfer my .it domains out of godaddy if not for the fact I have a dual citizenship which gave me some freedom with the regulations -- though it still took me hours of trial and error.
* They even do so on the homepage of the project: http://code.google.com/p/v8/