Didnt see a thread yet but this was posted an hour ago:
http://techcrunch.com/2014/11/12/mic...ross-platform/
and
http://www.microsoft.com/en-us/openn...ault.aspx#home
Thoughts?
Printable View
Didnt see a thread yet but this was posted an hour ago:
http://techcrunch.com/2014/11/12/mic...ross-platform/
and
http://www.microsoft.com/en-us/openn...ault.aspx#home
Thoughts?
Only time will tell what it means in practice.
For all of the hooting and hollaring, Mono had been around for years in various forms and in the end never really mattered much at all. Perhaps this will be different.
Opening up Visual Studio and .NET to Every Developer, Any Application: .NET Server Core open source and cross platform, Visual Studio Community 2013 and preview of Visual Studio 2015 and .NET 2015
Makes me wonder how .Net application are going to work on OSX, etc?
Personally to me this looks like a good first step.
This is great -
Visual Studio Community 2013 - will be a free unrestricted version for use for hobbyist or even for small organisations, as you can use VSC 2013 for up to 5 developers if you are a small business for free ( small business defined as < 250 PC's OR < $1million Turnover) which is a big step in the right direction.
This is good but ....
The .Net Server side Framework will be OpenSource and ported fully for Linux in conjunction with Mono team, and will also be ported for OSX so you can write apps for OSX, Linux and Windows all from Visual Studio.
....... This currently only affects the Server Side .Net Framework, i would like to see them do the same with the Client Side Framework too, as then you will be unrestricted in creating apps of all types across the 3 platforms.
I know I havent been following the versions of VS lately but which version are they talking about for free use by hobbiests and small businesses? VSC 2013, what does the "C" signify?
I think its a first step in a much bigger plan to dominate the world -_-
C stands for "Community" ... I suspect it's a new edition that's coming out - Visual Studio Community. It's in the link NW linked to. And NSA just talked about it too.
-tg
Got time to read the article NW posted. So why create yet another version os VS which sounds the same as Express unless Express is dead?
How is MS going to make money if they give the farm away for free. No one will buy the milk anymore lol
It sounded like it's more than just Express... it actually sounds like they are releasing the Professional edition as part of this. What we're going to see is two product lines: Ultimate and Community, with VSC taking the place of Express, Standard & Pro.
At least that's how I took it. It might also be that hte Community edition is the OS version, while MS will still build & maintain Express, Standard & Pro... *shrug*
-tg
They wouldn't make moves like these or the Windows 8.1 OEM-giveaways (with Bing!) on small-screen devices without strong motivation. I suspect the main one has been the rapid loss in market share over the past several years.
But this isn't much more than preaching to the choir. I can't see it changing anyone's minds, so one can only wonder how long all of it can be sustained.
There are many reasons Mono failed to become all it could be.
When I dabbled in it the Mono compiler failed often, had no intellisense in the IDE and no native graphical form interface. Most of the development was on the C# side and the VB side lagged woefully far behind.
I do not know how robust it is today.
They shouldn't be trying to make money off the development tools. I've always thought they ought to give that stuff away for free, and the Express version confirmed that. They can still make a fair amount of money off of selling DevTools + Goodies, which is all that the paid versions of VS amount to these days.
The point of development tools isn't to make money for the company producing them (at least not in the case of Apple, MS, or Google), it's to get more people writing apps for your OS. If MS priced VS out of the reach of hobbyists, the next big thing would go to a different platform that gave them development tools that were cheaper. There are LOTS of those out there, especially for Android. MS has no big rival for VS anymore. Instead, they have a bunch of little rivals that aren't all that wedded to Windows. That's the bigger threat that MS is probably trying to address. They want people developing for Windows, using Windows, relying on Windows, and so forth.
On the other hand, they are talking about open source for Linux and Max, so it isn't all about Windows, but it could still be all about MS. This could be simply competition to get more people using .NET and trying to starve out competitors. They may not be so much thinking that people will abandon Windows, as that people who write for .NET are still in their constellation.
Whatever it is, I like it. Competition is great, but having a skillset that sudenly takes on broader appeal without me doing squat is even better for me.
But MS has been giving VS Express away for years. Perhaps they should have the higher dev versions available for a much reduced rate to put it into the hands of the masses for Windows prices. I mean who can afford to buy $5000 software just to develop on and hope you can recover that expense with the products you are writing with it. The ROI will be pushed out for a long span when you add the development time and developer salaries.
So make it free and open source so it can drown out the competition but then you need to replace that lost revenue with revenue from somewhere else. Where? Did Bill donate his entire fortune to fund MS for another 30 years? :D
I would guess that the bulk of the sales of VS are currently two sources: Academic, for which there are also discounts, or people like me who have some company buy it for them. The cost of that software is just the noise in the total contracts we sign with the agencies that fund our work. Compared to the gouging we get from certain hardware manufacturers, the cost for a subscription is tiny. We don't go for the full version, though, and probably don't really need whatever version we are currently getting (I haven't been keeping up on that, I just know that we went to a simpler subscription in the last cycle).
Express Editions are Dead, they are to be replaced by VS 2013 Community edition (which will be a single version rather than different ones for C# VB.Net e.t.c).Quote:
So why create yet another version os VS which sounds the same as Express unless Express is dead?
Reports seem to suggest that there would be little difference between it and the full professional edition apart from the licencing restrictions (so extensions for instance like re-sharper will work with the community edition).
They are essentially making Visual Studio FREE for small businesses.
As for making the .Net server side stack open source and cross platform what they are doing essentially is making it possible to make web and mobile apps using .net work across all the different web and mobile platforms.
All that leaves is .Net desktop development as the only part which will still ONLY target Windows.
Yeh but Mono was not a full working version of .net on Linux, it has a fair amount missing, so far this promises to be a full working version of the .NET server stack.Quote:
For all of the hooting and hollaring, Mono had been around for years in various forms and in the end never really mattered much at all. Perhaps this will be different.
I think these are all good announcements, you could argue that they should have done this a few years ago, but Balmer never seemed to really get Open Source.
They can open-source .NET, but can't VB6!
They are not open-sourcing .NET out of generosity. They are doing it for purely commercial reasons. They have no interest in giving away VB6 because their final target is to channel the developer into their new platforms.Quote:
Originally Posted by MikiSoft
Yeah. Businesses are rarely altruistic, and MS has never been accused of that.
Erm yep they can and have made that choice.Quote:
They can open-source .NET, but can't VB6!
Of course its a business decision they are after all a business and not a charity.Quote:
They are not open-sourcing .NET out of generosity. They are doing it for purely commercial reasons.
In this case though at least they appear to be making a good business decision, which should benefit both Developers and Microsoft
How do you mean?Quote:
Originally Posted by NeedSomeAnswers
Well i am sure i have already made these points earlier in the thread so i will repost themQuote:
How do you mean?
- Visual Studio Community 2013 (which replaces the Express Editions and doesn't have the restrictions) - Free for hobbyists, individual developers and crucially for Small businesses.
- As for making the .Net server side stack open source and cross platform what they are doing essentially is making it possible to make web and mobile apps using .net work across all the different web and mobile platforms.
As far as i see it these announcements are good for developers, and will in the longer run be good for MS as they will encourage more developers to there platform, and more companies to use there tools.
Since the Mono project really didn't get a huge following, I think making .NET open source really isn't a big risk for MS but executes a calculated gesture of good will. I don't expect a OS X .NET compiler of any use any time soon. We will still be using MS .NET rather than Bob's .NET. Open Source done right (for example the JavaScript libraries, like JQuery) is a very good thing for the developer community. Linux got into so many variations that it just got silly; like a graveyard of rusted out cars.
But it will generate a [good] stirring in the fringes, and generate a better understanding of how the framework works for those who really want to know.
As a small independent software vendor this announcement might have an impact of future decisions I make.Quote:
Originally Posted by NeedSomeAnswers
Currently I've taken most of my UI work into browsers for flexibility. My only MS reliance is the backend code running under IIS.
I've also got a potential new Winform type UI that I was looking to go with a non-.Net solution (maybe C++ talking directly to api's).
I think this could be the start of Microsoft divesting themselves of the entire .Net stack.
I would expect them to continue producing Visual Studio for a while, but even that effort might move over into Eclipse plugins as time goes by or thown out for others to take on.
Future versions of Windows will probably have applets and such all written in either C++ or HTML5 with JavaScript.
That doesn't mean .Net goes away as such, but you may have to go to a Xamarin or somebody else to get generic, mainstream .Net development tools and frameworks.
I read it today...and this is something I expected (and I wrote some days before announcement). But I surprised for a step ahead, to make Net as a platform for all OS. I have a linux (although I use it for one year), and my opinion is that have some raw benefits, you can lost the window manager if you do nasty things with command line but you have always the system and all drivers loaded so you can download and reinstall any window manager...without loosing your data and programs, from command line. Windows are more known and embedded to new PCs so Microsoft can sell without loosing profits, and it is hard to be break down now, so the easy restore of linux not needed (for many windows users). So the open source Net for all OS aren't for a straight profit from Os sales (although any good from Microsoft can raise the sales automatic). For what profit given an open source Net? For all, because an open source Net makes all programmers to involve the code to something better. So I don't think that we see Bob's Net but we will see some newer versions that represent the today level of knowledge. And this is the scope, as I understand..to neutralize knowledge in an area of tools and environment, and then the people's focus goes to application generation, for the programmers and the application use for the users. Users are lot but not programmers...
And where is the money?? This is obvious...The money for this "sacrifice" for Microsoft can come for trusties downloading of apps. So any user can get an app but how can trust a noname app? So Microsoft...."lab" I supposed can do for some cents this two things...check and describe the app and give a trusty site for downloading.
Another think is about the big content holder (movies, songs, data for any scope)...that wants to spread it everywhere but with an efficient way, a way that users choose by interaction in the process of development, for customization the final app. The content holder can make more money from streaming when the user uses an app that give him what he wants. Maybe Microsoft investors also are in that field;
What on earth would give you that idea?Quote:
even that effort might move over into Eclipse plugins
Microsoft aren't "divesting" themselves of .Net, they're strengthening .Net's hold on the development community. By making it freely available to small companies they strongly encourage those companies to continue to use it under a paid model if they grow. The idea is to push other development platforms out of the market by dominating the small developer market. It's standard "loss leader" marketting and is no different to what they've been doing with express editions for years - it's just a different (and slightly freindlier) way of packaging it.
Quote:
I think this could be the start of Microsoft divesting themselves of the entire .Net stack.
Yep agreed, it doesn't look like they are getting rid of .Net at this moment, if anything it looks like they are trying to strengthen its position.Quote:
Microsoft aren't "divesting" themselves of .Net, they're strengthening .Net's hold on the development community. By making it freely available to small companies they strongly encourage those companies to continue to use it under a paid model if they grow.
Time will tell how successful this is and if this is just the start of what i hope are further developer friendly moves by MS.
It is significantly better than express editions though, which is we are being honest wasn't really a good enough offering.Quote:
It's standard "loss leader" marketing and is no different to what they've been doing with express editions for years
What's it offering that Express didn't? I haven't followed this particularly closely but it looked to me like it was mostly just about combining the languages so you don't have to get each one separately. I'm guessing they've chucked in a bunch of the preoductivity features as well but they generally did that with each new revision of express - they generally just trailed a revision or two behind the paid version.Quote:
It is significantly better than express editions though
I personally don't see this as MS giving up anything that was making them significant revenue before. They've made life easier for small developers but they were mostly using express anyway.
Extension supportQuote:
What's it offering that Express didn't?
- which also means that you can download the - Visual Studio Installer Projects Extension and create Setup projects !
That is the most significant thing
I believe EXPRESS also doesn't handle web site development the same - options are missing in how you can work that type of project.
I believe the express editions were more than enough for most projects. You can do some real heavy duty lifting without any of the features that were present in the Professional and above editions. I think this may be why MS are 'divesting' themselves of the express editions. I've used the 'free' versions since VB5, but having said that, I currently use VS Professional for day to day programming.
I do think Dev Tools should be free when provided by the OS manufacturer, but I'm sure the business structure of Microsoft is a little different, and cannot support such a path. Even so, most companies are ok with the several hundred to tens of thousands they spend every year on dev tools with Microsoft. The ROI is still large.We all like 'free' but sometimes you get what you pay for.
Quote:
I believe EXPRESS also doesn't handle web site development the same - options are missing in how you can work that type of project.
This is from wikipedia - "Visual Web Developer Express lacks certain features, such as the Accessibility Checker, the ability to create standalone class library projects, third-party add-ins and macros."Quote:
I believe the express editions were more than enough for most projects. You can do some real heavy duty lifting without any of the features that were present in the Professional and above editions.
For web projects in particular the Express edition was hobbled.
Have you actually read this thread?Quote:
I do think Dev Tools should be free when provided by the OS manufacturer, but I'm sure the business structure of Microsoft is a little different, and cannot support such a path.
One of the main points in the thread is how MS are now going to be giving there dev tools away for free !!!!
Visual Studio Community 2013 is basically Visual Studio Professional with different licencing conditions!
[QUOTE=FunkyDexter;4792277]Microsoft aren't "divesting" themselves of .Net, they're strengthening .Net's hold on the development community.[QUOTE]
Wishful thinking aside, it is becoming very clear to Microsoft watchers that something is up. You might be right but don't be surprised when this cigar blows up in your face.
Not Dumping .NET - Microsoft's Method seems like a much clearer-eyed opinion with this series of subheads:
So what you have there is a True Believer trying to put the best face on it while admitting the stars do not augur well at all for .Net's future at Microsoft.Quote:
This has to be good news doesn't it?
What the gods wish to destroy they first open source.
Which is it in this case?
Microsoft in the past was strongly opinionated.
So the trust in .NET and its long term future declined.
Suddenly .NET looks like it's part of Microsoft's future plans.
At the moment it is difficult to tell if Microsoft is serious about .NET or just wants rid of it.
Now we have news that there will be a new version of WPF and its going places.
We will have to see how quickly things progress to get a measure of how much interest Microsoft has in .NET.
Windows on mobile is pretty much dead, but Microsoft on mobile has a really good chance of succeeding.
Microsoft Open Sources .NET? seems to take a similar view that this isn't really open sourcing at all.
I think there's two separate issues: 1. switching from express to community and 2. open sourcing.Quote:
this isn't really open sourcing at all
I'm pretty comfortable with my stated position on the first. I think it's just marketting speak. From what folks have said in this thread I think the only real difference is increased convenience. Extension Support, stand alone class libraries etc were all things you could live without if you were a small developer and you probably did if it saved you shelling out for a licence. I think think MS offering some of that stuff for free is great but I don't see it as a fundamental shift in their position.
The open sourcing issue is more interesting becuase it does look like a fundamental shift but, as yet, I'm not taking any of the articles about it particularly seriously. There's always an army of pundits on hand to tell you that every move MS makes is the inevitable final nail in their coffin just as there's a similar army of pundits on hand to tell you that it's the next big thing and will shine a coming dawn on all things Bill. I don't see it as them divesting themselves of ongoing development of the language though as, apart from anything, they're not accepting updates to any of it. So any future advances will either come from MS themselves or they're going to have to take a step further into open sourcing.
Why are they opening it up to read? I can't see a single killer reason. My guess is that they feel their intellectual property is safe enough even if it's freely visible (it's kind of like the debates on VB6 vs VB.Net in that regard:rolleyes:) and it does offer some benefits. It means advanced developers can delve right down into the core if they need to. It means there's an increased chance of some open source project picking up the cross platform ball and running with it (though I personally doubt it and I suspect MS probably doubt it too). And it paints MS as a caring, sharing member of the development community, whether they actually are or not.
Dilettante, because of you negativity about almost any MS move, that when they do something genuinely interesting your first thought is to look at the negative.Quote:
Wishful thinking aside, it is becoming very clear to Microsoft watchers that something is up. You might be right but don't be surprised when this cigar blows up in your face.
I read the 2 articles you posted which were both from the same site, but from what i have read they are not in the majority as to there take on MS's latest changes, they have a point about being a bit wary as some of them have been burned before by some MS decisions which make people more cautious but for me this does feel a bit different.Quote:
So what you have there is a True Believer trying to put the best face on it while admitting the stars do not augur well at all for .Net's future at Microsoft.
It appears that there has been a bit of a culture change since Balmer has left the company, i always though he was a hindrance to MS.
I thought this article certainly shows some of that culture change.
And this from Linux.com
Yeh look it is early days yet we cant be certain about what is going to happen BUT all the main guys at MS all seem to be speaking form the same hymn sheet, and for me it just feels like a more positive step for Developers than i have seen MS take for a very long time. Time will tell how this works out !Quote:
The open sourcing issue is more interesting because it does look like a fundamental shift but, as yet, I'm not taking any of the articles about it particularly seriously.
Finally
All the main guys in MS have said that there will continue to be MS teams developing the various pieces of .net BUT they will also be accepting changes form the Open Source community.Quote:
i don't see it as them divesting themselves of ongoing development of the language though as, apart from anything, they're not accepting updates to any of it.
Scott Guthrie has this to say..
Quote:
Open Sourcing the .NET Core Runtime and Libraries
Today I’m excited to announce that we are going even further, and will be open sourcing the .NET Core Runtime. This will include everything needed to execute .NET code – including the CLR, Just-In-Time Compiler (JIT), Garbage Collector (GC), and core .NET base class libraries.
We are releasing the source under the MIT open source license and are also issuing an explicit patent promise to clarify users patent rights to .NET. This morning, we published the public repository on GitHub where the project will be hosted: https://github.com/dotnet/corefx
Today’s source release includes many of the newer core .NET framework libraries (ImmutableCollections, SIMD, XML and MetadataReader). These libraries are fully open, and are ready to accept contributions. Over the next several weeks and months we will continue to transfer source (including the Core CLR which is not there right now but in the process of being moved) into the repository and likewise make it open for contributions.
and yet we have had the express editions for many years. Because they give away a tool for free does not mean they give away their development tools for free. Pay attention to the real world.Quote:
Originally Posted by NeedSomeAnswers
Pro, Enterprise, etc. are still costly for a lot of people, and the community edition, while appears to have a more lenient licensing, is still restricted.
Can you tell me what restrictions you think are on the community edition?Quote:
and yet we have had the express editions for many years. Because they give away a tool for free does not mean they give away their development tools for free. Pay attention to the real world.
Pro, Enterprise, etc. are still costly for a lot of people, and the community edition, while appears to have a more lenient licensing, is still restricted.
Who do you think these lots of people who still have to pay are?
Because if the only point your making is that business over $1m turnover and 5 dev heads have to pay then i made that point earlier in this thread in post 4. - here i quote myself...
the reality is this announcement means no individual should be paying for Visual Studio.Quote:
Visual Studio Community 2013 - will be a free unrestricted version for use for hobbyist or even for small organisations, as you can use VSC 2013 for up to 5 developers if you are a small business for free ( small business defined as < 250 PC's OR < $1million Turnover) which is a big step in the right direction.
You do appear to not have read the thread still!
I for one am looking forward to not having to purchase VS editions. Up until recent versions of express you could not work with solutions that had multiple projects - that's caused me problems...
I'm lucky that my customers give me access to MS SQL Developer's edition - for when I get a 10 GB database and SQL Express doesn't handle that.
What's this I hear about WPF coming back to life in the mind of MS??
OK, that really is interesting. I'm willing to bet they're still going to keep a tight control over what's in and what's out but accepting contributions at all is a huge step or MS. I'll be particularly interested to see the outcome of this:-Quote:
BUT they will also be accepting changes form the Open Source community.
That'll be where you see whether this has a real commitment behind it.Quote:
are also issuing an explicit patent promise to clarify users patent rights to .NET.
By the way SJW and NSA, you two have an amazing ability to run each other up the wrong way while basically saying most of the same things. Just sayin' :rolleyes:
I personally think there will always be some difference between what MS will offer for free and what they'll offer on the most expensive paid for licence and the free license will always lag an iteration or two behind. So there'll be some wizzy but not strictly necessary features in Enterprise 2015 (or whatever's next) that won't be in Community 2015 but will turn up in Community 2016 or 17. That's just a no brainer on their part and no different to how almost every company operates. What this represents to me is a narrowing of that gap for now. Whether that narrowing is permanent or temporary remains to be seen.
The thing is i actually think SJW normally has good things to contribute (as long as we are not talking about politics :)), even when i disagree with him. I actually quite like a good argument (can't you tell), it would be boring if everyone came on here with the same opinions.Quote:
By the way SJW and NSA, you two have an amazing ability to run each other up the wrong way while basically saying most of the same things. Just sayin'
I get frustrated sometimes when i have been saying something for a whole thread and then people comment without even bother to read it properly.
So far the only thing they are saying that will be missing is some Office tools projects, which to be honest we can all do without anyway.Quote:
I personally think there will always be some difference between what MS will offer for free and what they'll offer on the most expensive paid for licence and the free license will always lag an iteration or two behind. So there'll be some wizzy but not strictly necessary features in Enterprise 2015
Azure!, all of them (Guthrie / Nadella and Somasegar) are all banging on about Azure, and i think that seems to be the direction of travel. They want to give more access to dev tools, so they can then sell Azure service on the back of it.
Also Nadella was head of Azure previously....
Actually, the source code for the FW has been available for reading for some time. They published the symbols library link back in .... oooh... at least by 2009... so you could actually step into a Datatable.Update statement, and see the underlying C# code behind it (a for each datarow loop, calling a command.executenonquery) So reading has been widely available for some time now. What's different now, is that changes can be committed back to the FW. It also means I can pull down a copy of a class for the FW, add it directly to my app, and allow it to be a little more self contained. I could gut all the pieces I don't need or if I want to tweak something, I can.Quote:
Originally Posted by FunkyDexter
For most developers I think this is largely a non-event. It will have the most significant impact on the small shops and the hobbyist. For those who exceed the revenue limits for the Community edition - we probably already work for a company that has shelled out for the Pro or Ultimate anyways.
I think this may actually be a good thing for the likes of Mono and other non-Windows development tools. Previously, they would have needed to produce their own FW libraries (which is what has caused Mono to stall in my opinion) but instead can now use the published code as a base... it serves as a platform to begin with a running start (although the Mythbusters busted that, it doesn't really work).
Part of the issues I think people are having, is that, yeah MS tried to keep things close and quiet, and if Balmer was still running the show, this wouldn't be happening... but there's been a regime change, a new attitude, and so as they make these kinds of changes, it's being eyed suspiciously. rightfully so. I just hope that that suspicion doesn't cause it to stall... kind of reminds me of the dog that finally catches the car, but then isn't sure what to do with it now that he caught it.
-tg
WPF 5 is in development so its active. Wheter it will continue on along side of WinRT is anopther story yet to be seen. Guess it depends on Windows 10 as Windows 8 was a failure.Quote:
Originally Posted by szlamany
Good reading on WPF and its future:
http://pragmateek.com/is-wpf-dead-th...future-of-wpf/
http://greglevenhagen.com/is-wpf-dead-no/
http://blogs.msdn.com/b/dotnet/archi...p-for-wpf.aspx
I love WPF. The event model is great - treading is a breeze. XAML is really powerful
I just did some WPF coding that draws circles and ellipses on a CANVAS - connects them with lines. Puts labels around them - they are clickable - re-drawable. Had to use geometry I've not thought about since the 1970's.
Yea I love WPF too and looks to be in the mix for several more years at least.
I forgot to reply to the comment that the FW has always been readable so yea releasing it as opensource is not that big a deal in that respect but its surely big part of their underlying plan (to take over the world? lol ;))
My frustration with ASP.Net led me to write my own backend so I could customize it as my code base requires it. I can only imagine what I could have done with the source to ASP.Net backend - editable - in my project, so I could have tweaked it as needed. This has been a two year journey.
I've got need to do low level HTTP stuff - to the point where I'm looking at HTTP.SYS and what all else is available to me. Afraid of MS releases in the future that can damage legacy stuff as it gets left in the wake.
Source to stuff - that I can really use and edit and apply - seems like a really great offering.
You sound like a good candidate for Node.js, and even Microsoft is embracing it on Azure.Quote:
Originally Posted by szlamany
OmniSharp anyone?
While we also have:
Pity the poor Windows developer: The tools for desktop development are in disarray
Quote:
Analysis When Microsoft came up with Windows 8 a couple of years ago, the message was clear: the future is tablet-shaped. The Windows desktop is still there, but not much changed from Windows 7 - some things went backwards, such as translucent “Aero” windows, available in 7 but gone in 8. Now the company is scrambling to fix its desktop development tools.
This lack of attention to the desktop was also reflected in Microsoft’s official software development frameworks. Visual Studio 2012 and 2013 included a ton of new stuff for Microsoft’s Windows Store apps, the tablet-oriented app framework new in Windows 8, and plenty more for Microsoft’s cloud and mobile efforts, but little for desktop developers.
In Windows 10 Microsoft is putting a renewed focus on the desktop, and enabling Store apps to run there. But what of those developing old-style desktop applications? They have a range of unappealing choices.
dilettante, I received an email from Code Project entitled "Microsoft makes it less attractive for developers to create apps for Windows" however, there was not associated article link. Makes me wonder Windows is going to end up?
I think a lot of things are in transition at Microsoft.
Perhaps this is it?
Microsoft makes it less attractive for developers to create apps for Windows
If so, that meager blurb isn't about Windows as such but instead the tiny worlds of WinPhone & WinRT.
You seem to believe it's a lot more lenient than it really is.Quote:
Originally Posted by NeedSomeAnswers
5 developers is not a lot.
While yes, extremely small shops (i.e. as noted 5 developers) possibly won't pay for it, the reality is that there's a whole s*t ton of businesses with more than 250 computers, or >1million turnover, or more than 5 developers. It's not hard to have a company with $1million turnover. A company with 2 people can demonstrate more than 1/4 million, with significantly less profit. Adding a couple more engineers, a couple more companies on the books and turnover would exceed a million readily.
Indeed, a company with 5 programmers using visual studio would need $250 to 1/2 million just to pay those employees a gross salary. Add-on the overhead, accounting and all the other employees (programmers are notoriously bad at math), and you will readily hit a million.
Given that, $600 a year (or every two years, even) for a full blown VS Pro license isn't a significant part of that overhead. So, VS Pro for free is not a game changer in any way shape or form. Does it help the one-man bands? Sure. Is it going to create a larger developer base? Not really: anyone programming for Windows is already programming for Windows.
What it will do is slow the migration away from Windows: android and iOS are the major players in the mobile market, and that's where the money is. Remember, there's a lot of talk of the desktop 'going away' - Microsofts Metro interface is an example - and the natural platform is Android and iOS, both with free, fully featured, tools.
Further, while there were certain restrictions with Express, it had no restrictions regarding commercial application development, whereas VSC with the full blown Professional tools puts restrictions on its use, not necessarily commercially, but in an in-house situation.
Quick point - I've been doing Android development and still need a robust backend. I like to do that in VS and like to leverage .Net for that.
If I end up being able to code the Android side in VS - getting me out of Eclipse - and code and debug to the device (like I could with Pocket PC's years ago) - that would be all the better.
MS seemed to be embracing things like jQuery a while ago - if things like that stay on the agenda then maybe VS can be a fuller dev platform for use on my web apps as well. Currently I could not imagine leaving the power of Firebug for doing JavaScript debugging. Granted I always have VS running as well (the web methods are VB.Net).
I think you hit the nail on the head with that statement.Quote:
Originally Posted by SJWhiteley
Not Really, i am not saying that MS gave all there tools away for free, and i am well aware exactly how few 5 developers is.Quote:
You seem to believe it's a lot more lenient than it really is.
5 developers is not a lot.
Maybe i am wrong but you seem to take the view as to how this directly affect you, where as i was not. Non of it directly affects me really. I didn't pay for VS before, and i wont pay for it now.
I see how this will potentially affect those learning .Net now, in particular with development moving more and more to the web and mobile. Express Editions Web Developer was really hobbled to the point where it was really hard work to use for a proper web application.
The new VS is just much much better for Web Development and i think this move will make a difference in persuading new developers to try the .NET tools.
Right now for instance i am creating a web app in ASP.Net using responsive design which is usable on a normal desktop, Tablet and Mobile phone.
I couldn't have done this in the Express Editions due to the multiple projects issue and the fact i couldn't use some of the extensions i am using.
I don't see the problem with this, they can afford to pay and generally do pay.Quote:
While yes, extremely small shops (i.e. as noted 5 developers) possibly won't pay for it, the reality is that there's a whole s*t ton of businesses with more than 250 computers
What i was getting at is as bigger business tend to pay for their developers MSDN licences, no individual should really be paying for Visual Studio now.
Maybe in the windows desktop world you are right, very few new developers are going to start out today to become a windows desktop programmer, BUT ....Quote:
Does it help the one-man bands? Sure. Is it going to create a larger developer base? Not really: anyone programming for Windows is already programming for Windows.
The latest VS tools are much more geared towards Web & Mobile and i believe they do have an opportunity here to expand there developer base in that area.
Yeh the only way to write native Android (and iOS) Apps in .Net at the moment is by using Xamarin which costs a fair chunk, (i think around $800 - $900 a year).Quote:
Quick point - I've been doing Android development and still need a robust backend. I like to do that in VS and like to leverage .Net for that.
If I end up being able to code the Android side in VS - getting me out of Eclipse - and code and debug to the device (like I could with Pocket PC's years ago) - that would be all the better.
But if Visual Studio itself gets this feature (or the costs come down) - where you can build 1 solution, with a common business logic project and separate front end projects for Win Phone / Android / iOS that would be really cool. (that's what Xamarin allows you to do)
And retain - or at least more fully retain.Quote:
Originally Posted by NeedSomeAnswers
Actually I think it is quite a lot, at least if you're using it as a yardstick to judge whether the company can trivially afford to pay for VS licences. Software's a profitable industry and if you've got 5+ developers and still can't afford to pay for licenses then you're doing it wrong.Quote:
5 developers is not a lot
This isn't aimed at small development shops. It's aimed at one man bands and start ups for whom licensing costs would otherwise be an obstacle.
This thread was about the "open sourcing of .Net" and that hasn't even occurred yet, if ever.
.NET Core The Details - Is It Enough?
He also talks about the 6 separate ".Nets" that exist today (5 from Microsoft and the withered stepchild Mono), and how the speculative .Net Core will be yet a 7th one if it ever comes into being.Quote:
Now enter .NET Core:
".NET Core is a modular implementation that can be used in a wide variety of verticals, scaling from the data center to touch based devices, is available as open source, and is supported by Microsoft on Windows, Linux and Mac OSX."
This is wishful thinking in that .NET Core doesn't actually exist. All Microsoft have done is to start an open source project with the aim of creating something that fits the bill.
Nope, not an issue if you ignore the mobile world - where Microsoft is at its weakest and dying fast. Sadly, Xamarin mobile "solutions" are also quite bloated compared to actually native applications.Quote:
It is difficult to say how long we will have to wait for .NET Core and how much impact it will have. The project seems to be necessary mainly to clear up the mess that Microsoft has made of the .NET Framework. The only really new idea seems to be "app-local" deployment, which means moving away from shared libraries to code that is bound into every app. Well, in most cases storage and memory isn't an issue any more - is it?
This is yet another article form the same place as your last 2, where some guy basically interprets a blog he doesn't even link to to support his own bias.
There are precious few facts of any sort, but mainly a few images which are taken from another blog and the writer speculates around what they might mean which is mostly, DOOM i tell you DOOM !!
It says nothing new, it just speculates a load again.
Dillatente, with all your posturing about supposed .Netter posting on VB6 threads you seem to have no problem the other way!
Just saying ...