|
cjb110 wrote: I thought were more of a 'grab'em young, keep'em forever' strategy.
No, that's what Dreamspark is. Students can get VS Professional, the Expression suite, server OS's, and more for free. I can get multiple copies of most of those because my school also has a program with MS to offer a bunch of software free to its students (including the desktop OS's, the only thing Dreamspark really lacks). That's the real 'grab'em young, keep'em forever'.
|
|
|
|
|
cjb110 wrote: And given that they are free, we can't really complain!
If it doesn't do what I need it to do then free doesn't matter.
|
|
|
|
|
This might be the impetus that SharpDevelop needs to become BIG!
|
|
|
|
|
The current SharpDevelop 4.2 release is already ready for .NET 4.5 and async/await, just install .NET 4.5 and it'll appear in the target framework list.
Yes I guess this might boost our user numbers a bit 
Though I'm not too hopeful that that will translate into increased contributions - Windows developers tend not to think about contributing 
Unfortunately the reduced Windows SDK will also screw us over in some aspects, e.g. the XML documentation files (documentation in IntelliSense) for the .NET 4.5 BCL are no longer available without Visual Studio (previously these were part of the .NET/Windows SDKs).
|
|
|
|
|
are they going to give everyone touch-screen monitors?
no?
screw them.
|
|
|
|
|
No-cost desktop software development is not really dead on Windows 8[^]
Quote: Two packages were used in this mindblowing revelation:
Microsoft Visual Studio 11 Express (C++ compiler and toolset)
Windows Software Development Kit (SDK) for Windows 8 Consumer Preview (for Win32 headers)
Wiring this up to the ‘Express UI is a trivial exercise for the developers out there. (In response to Peter Bright’s story.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
In Windows 8 development, you have several options for building your applications. XAML is one. HTML5 is one. Platforms, distribution, and everything else being equal, I would pick XAML/C# every time over HTML/CSS/JS, and I’ve been a web developer for 14 years. Which would you rather use?
|
|
|
|
|
i would use XAML/C# instead of HTML5/JS
|
|
|
|
|
I would say XAML/C# for Windows 8...unless someone told me the HTML5/JS will properly 'just work' on other platforms.
|
|
|
|
|
XAML by far. It's by far my favorite way to develop. I really hope this HTML5="Greatest end all coding option" hype bubble bursts soon. Sure, HTML5 is powerful, but nothing close to XAML.
I realize this leaves mobile out of the picture, however I'm considering a desktop application only.
|
|
|
|
|
Are there only 2 choices?
|
|
|
|
|
|
Still, I'd happily go back to GDI-pre-plus if we only could agree on one UI technology.
|
|
|
|
|
Seems to me everyone here likes XAML/C#. I have to 100% agree. I have avoided ASP.NET as much as I can. WIth Silverlight and WPF I get the MVVM pattern, which I absolutely love. Not available with HTML.
In my mind JavaScript was one of the worse decisions made on the web. Almost anything would have practibally been better: VB, C++, .... Personally think they should have come up with a language that played nice with XML.
|
|
|
|
|
Clifford Nelson wrote: Not available with HTML.
Ahem: Yes you do[^].
|
|
|
|
|
So many developers my age have had plenty of chances to ditch coding and move into management, but we've stuck with coding because it's what we love to do. We'd earn more in management, but writing software is in our blood. We wouldn't stop doing it for anything. ...and more importantly, how not to code.
|
|
|
|
|
Some do. I knew 3 old farts at a previous job. One knew how to code (though he was really middle aged, and had no kids AFAIK), one was mediocre, and the other should not have been allowed near a computer. I suspect they didn't move into management because then they'd have to learn something new.
|
|
|
|
|
Another way to spell management is "S T R E S S" - I've been programming for more than 40 years and no way would I want to deal with all of the crap that department managers have to deal with; both with the people they manage and the people they report to 
Steve
_________________
I C(++) therefore I am
|
|
|
|
|
I imagine so. There's no way I want to get into management, especially with people like me to manage. 
Project manage, sure. People manage, no thanks.
|
|
|
|
|
Speaking as an Old Fart who started programming in machine code on LEO III/6[^] I tried being a manager for a while. I gave it up as soon as I found a technical post because i)I hated it and ii)I was useless as a manager. I won't claim to be a great programmer but I did manage to write some code that worked, and I was not bad at debugging others'.
Programming is work, it isn't finger painting. Luc Pattyn
|
|
|
|
|
I especially liked the "how not to code". When I started (1961), the goal was to write accurate, tight (even to the point of self-modifying) code. In 1998, I had a concussion which effectively put an end to my coding; I can't concentrate the way I used to and thus the pleasure is gone. I do miss it and, quite frankly, am astonished at how today's software houses produce and release shoddy, untested, user-friendly NOT! slopware and then have the sheer gall to charge for it.
Truth be told, however, we got away with a lot when users were unable to state what they really needed and regarded programmers as the ones who knew how to push the "magic" buttons.
BTW, some of the machines I worked on are, in fact, in the Smithsonian.
Vic. (I still think it was more fun with punch cards, paper tape and drum memory.)
|
|
|
|
|
Punch cards were fun (I started with the too) but a bitch when you dropped a box of source deck all over the floor 1 hr. before deadline. 
|
|
|
|
|
I have to agree. I did a bunch of other things, including Systems Engineering and management, and am now a contract C#/WPF/Silverlight developer.
|
|
|
|
|
The truth is this: web standards are often a tyranny to developers and designers alike. By themselves, they constrain just as much as they free, and they are designed not for our benefit, but primarily for the benefit of platforms and software on which our solutions run. Embrace them we should, but never in isolation, and never with a complete reliance on the standards process and manna from browser implementers. The big <picture> proposal and you.
|
|
|
|
|
Having previously been disappointed by the information available on the topic, this is my attempt at categorizing different ways to implement 2D platform games, list their strengths and weaknesses, and discuss some implementation details. The long-term goal is to make this an exhaustive and comprehensible guide to the implementation of 2D platform games. Ready Coder One!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
