|
Yeah, those zeroes caught my eye as well. I'd compare it to TFS pricing but they make is so freaking difficult to just find the CAL pricing. Still, that's less than 1 license of VS Ultimate, so I'm guessing Atlassian will end up cheaper.
Ah, here we go[^]. $667CDN/user. Ouch.
Marc Clifton wrote: everyone uses it differently, and one has to know how the lead dev wants it used
Oh yeah. This is one majorish problem with Git, and probably why there are so many "use Git without using Git" tools out there: they just incorporate a process.
TTFN - Kent
|
|
|
|
|
A new claim from noted Microsoft reporter Paul Thurrott states, via unnamed sources, that Windows 8.1 Update 1 will be made available to download April 8th for the general public. However, MSDN subscribers will still get access to the final build ahead of that date, although not as early as usual. Because I know you're all waiting for it
|
|
|
|
|
I found this quote funny: "mostly for its use by desktop PC owners who work with the old fashioned keyboard and mouse". Who is this guy and what universe of computing does he live in?
|
|
|
|
|
Kent Sharkey wrote: Windows 8.1 Update 1
Why does that remind me of Windows 3.11 ?
Marc
|
|
|
|
|
They are the masters of horrid names.
TTFN - Kent
|
|
|
|
|
That is the short name; its actual name is "Windows 8.1 Update 1 The Reimagined SuperExciting Higher Cadence update"
|
|
|
|
|
No compromises, fast and fluid! 
|
|
|
|
|
Fortune today released its annual ranking of the world’s most admired companies. Apple topped the charts yet again, but on the lower parts of the list something interesting happened: Microsoft fell from 17th in 2013, to 24th in 2014. Well maybe it can win Miss Congeniality
|
|
|
|
|
Mads Torgersen have commented on two language feature suggestions on uservoice. Noting that they are actively working on them. ?.? C# is turning into C++ with all the magic characters
|
|
|
|
|
I got notice about the ?. operator on Tuesday since it was an enhancement I'd voted in favor of. I'm more ambivalent about the second one; since I've never gone constructor crazy setting a default there hasn't ever been a real problem for me. Not a complaint; but more wondering if there aren't bigger fish to fry.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Both will be a big boon for me. The default values will allow me to be consistent between using automatic properties or not.
|
|
|
|
|
Except in the case of interface implementation, I don't see the value of auto properties over data members if there aren't also other things to support the auto properties. Things such as "property changed notification", or invariants or pre/post conditions, etc
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
|
|
|
|
|
Not breaking the API when I need to add something like that in the future is worth making all public values properties even though I'd guess that probably >90% of them never go beyond public Foo Bar {get; set; }
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Agreed. That's why I said "except in the case of interfaces"...
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
|
|
|
|
|
I do it universally even if I don't have an IMyClass because 99% of the time I only have a single implementation and until there're at least 2 implementations an interface is almost impossible to design that won't undergo major revision as soon as it's used for a second implementer.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Hmm, with auto properties that became more palatable, and now with allowing default value assignment it's even better (although, I don't see the big deal about setting the property in the ctor).
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
|
|
|
|
|
I could only see it being one if you've got multiple ctors, because you either need to remember to chain them down to the base ctor that sets default values, remember to call an init method everywhere, or copy/paste/keep in sync the same init code in every ctor. I suspect having fubarred the latter is what makes some people twitchy.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
yep
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
|
|
|
|
|
I really like C#, but to me it always felt like everything that went beyond generics made the language unnecessarily complex, given the fact that most of the features that were introduced since then are just syntactical sugar. I mean, it's nice to have all these features available because they certainly serve a certain purpose, but they also made the code harder to read and maintain for people who are less familiar with them. Maybe I'm just too old-school C# as I used the language from day one, and I seem to have the habit to prefer to go the long, sometimes "ancient" way; I still explicitly define a backing field for every property, for example. I don't know why, maybe because I like to be in control of such subtle things, don't leave it to the compiler to do it for me and I like to have it written out in code. It's almost like modeling a piece of art: if the code doesn't look well and complete, it doesn't look right to me even if it works just fine. Sometimes it's hard to leave it like that all the same. 
To come back to the point: The language designers should become careful with what features they add to the language, because every iteration seems to get more and more overloaded, and I don't like to see it happen up until the point where stuff that could also be solved with two or three additional lines of code gets standardized. I know it's all about time, productivity and rapid development cycles, but things like default property values are just going a bit too far IMO.
|
|
|
|
|
sevenacids wrote: I still explicitly define a backing field for every property, for example. I don't know why, maybe because I like to be in control of such subtle things, don't leave it to the compiler to do it for me and I like to have it written out in code.
I only recently started using C#, and I started off with backing fields because at that point I hadn't learnt about auto properties. Now I find it far easier to read and write with auto properties than go through the process of making the backing field, less lines of code and all that.
.-.
|o,o|
,| _\=/_ .-""-.
||/_/_\_\ /[] _ _\
|_/|(_)|\\ _|_o_LII|_
\._. |\_/|"` |_| ==== |_|
|_|_| ||" || ||
|-|-| ||LI o ||
|_|_| ||'----'||
/_/ \_\ /__| |__\
|
|
|
|
|
Sure, if you like them it's OK. I mean, the good thing with all these features added is you can still decide which way you want to go.
By the way, what's interesting about properties is that it looks like you don't really need fields at the language level anymore at all, just public or private, static or non-static properties. For example, imagine you could do something like this in C#:
public Double X {
get { return value; }
set { assign value; }
}
Where in the setter the "assign" keyword would be responsible to store "value" (or the result of whatever expression follows) in a hidden backing field, while in the getter this field would be accessible by the "value" keyword.
|
|
|
|
|
I'm confused why you'd want to create a new keyword for that verbose style when the auto property syntax has created hidden backing fields since v2.0
public Double X { get; set; }
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Kent Sharkey wrote: ?.? C# is turning into C++ with all the magic characters
At least there is some way to go before it turns into APL.
|
|
|
|
|
That was the startlingly blunt answer Google's head of Android, Sundar Pichai, gave when asked about the prevalence of malware on Android during Mobile World Congress in Barcelona this week. Thanks guys, great plan
|
|
|
|
|
Looking for a job or a promotion and worried that your age might be an impediment? Don't be. Age really is just a number, and especially in IT, that number isn't as important as your accomplishments, your adaptability and willingness to learn. "Age is strictly a case of mind over matter. If you don't mind, it doesn't matter."
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
