How about just being specific about those processes then? Like FreeBSD team is using a variant of the v-model, the upper community of the Linux kernel uses a unique variant of Agile or the Koffice team uses Scrum etc.
Defect resolution on many commercial software projects is very slow
I've not noticed any difference between large opensource projects and large proprietary projects through resolutions time. However, you're mentioning specifically 'commercial' projects and... I have to say, when it comes to commercial projects, I've had more responsive people through paid support channels despite the project being either proprietary or opensource. The resolution because of that responsiveness on occasion was faster.
Using a lot of closed source software and going through weeks of support hoops for each problem has made me a very big fan of open source software and searchable mailing lists.
Don't get me wrong, I use opensource software daily and I work with it, I just don't have this great experience with the community. Some of the most annoying support I've had from both Microsoft and Redhat, both on opensource and closed source technologies provided by both for enterprise level stuff.
There's also the different practices - tiny patch today for a single problem versus waiting up to three months for a huge patch for a long list of problems.
A tiny patch for a large project requires setting up a development environment which in my experience is often taking the piss in complexity (my luck is that I always end up in that stage when the environment setup instructions have just become outdated and I waste a week or two trying to find out what I need to do, by which the documentation is updated when I find out) and this is coming from someone experienced in working in large software projects. Then sometimes you find out the software which is opensource, is actually using proprietary libraries like Kakadu, fmod, Havok (and for actually good reasons) etc. and the licensing cost for at least two of those is something insane; so you're left dependent on developers.
I get really annoyed with some opensource projects, because you're encouraged to "join the community" and become part of it. So you go through the entire processes needed and in fact, forced, just so you can report a bug, provide a patch or such and then you end up having to deal with attitude (typically this is from unpaid volunteers, paid people generally seem a lot nicer) over your contributions. At least with proprietary software, typically I just fill out a form and the response I get isn't typically highly resistant and written in such a form that doesn't feel like someone told you to "feck off". But then, even if you were, you wouldn't feel the burn as much since you weren't forced to go through an entire process of be part of the community love.
Open source developers are willing and able to take responsibility for their own work instead of having to wait weeks to get it signed off.
To be honest, I've never seen that in any of the large projects I mentioned. If you wanted to do a release version, you had to go through the entire process. Perhaps you could give an example of a large project that has made an official release for a minor fix just for you while skipping all their processes?
It's a core element of IP law that a company that holds trademarks must defend those trademarks. Failure to do so becomes legal evidence against the validity of the exclusive use of those trademarks and can lead to their loss.
You're forgetting they can license the trademark to fans under a variety of conditions. Protecting trademarks can be as simple as licensing individuals using them.
However there is far more opportunity for something to be done due to more available developers being able to do something about it than the one or two people at a commercial software house that have responsibility over the portion of code with problems.
My experience in such matters has lead to disappointment. But, I guess experience can vary.
Open Source ensures that you can review the code at any time to ensure it does what you want.
When working with large code bases like Seamonkey, Second life, OpenOffice.org, SystemD etc. The amount of capability as user (or developer) has in order to do much on these can be extremely limiting.
All the coolest movies you've watched had CGI done on open source.
Are you talking about render farms that are running on a Linux based operating system while putting most of the work on the graphic cards which is being done by using proprietary drivers to do so?
If you are not using Git in a distributive fashion, then *how* are you using it? Locally? Shared file system?
As in, not everyone operating on their own forks and pushing to a single repository as opposed to doing pull requests.
My advice to you in this case is adopt the distributed approach and make the common repository a "bare" one.
I don't need advice. I just pointed out a way to lock files in git and also told you it was a bit pointless if you're using it in a distributed fashion.
In fact, the idea you suggest really doesn't do what I want in a multiple developer world where running in a distributive work flow which is unavoidable when using Git.
I've seen it done successfully in a large multi-national team (and I can't recall any issues we had) in my consultancy life. They did have a small wrapper script (and some simple scripts to lock, unlock files without needing to memorize everything) to ensure the repo was always kept up to date though. What I'm suggesting is based off something that worked.
Personally, I think if you want to prevent concurrent edits through some central management, you should use the tools built for that. But saying you can't lock files on Git is another matter.
Oh, I stand corrected. I switch currencies a lot, so I probably got confused.
Also, your friend must be a wasteful American who refuses to adapt to prices.
Nah, he's just a mechanic and works a little with electrical tools at his home. He has a big gripe over electricity costs.
Maybe try switching off the light when you leave the house
I don't think he's being wasteful though, I think he genuinely keeps to good practice with his energy consumption, using it only when he needs it.
That's like people who go out of their way to disable the power-savings feature for their home PC, which by now come enabled by default. And no, I'm not talking about the few people who actually have a use case for this, but about those who don't.
I recall having to do that for a friend, just so Facebook would be more responsive on their computer. I can't really think of anyone that didn't do that for a genuine reason.
I tend to plug xbox 360 controller in which typically deals with any issues like poor keyboard and mouse support. They also usually work better due to my beefier machine.
But developers can not write once and use anywhere.
They can with UWP. But you know, maybe I should rephrase to say that the effort is extremely minimal if that will make you happy.
the developer may want to take advantage of the many differences between Xbox and Window
Controller API is identical across all the platforms (you can essentially play the entire thing on PC using an xbox controller, touch screen), the fact they may add some branching code in release builds based on what platform you're using is of little relevence.
Alas, over time it seems Microsoft is even more mesed up than Sony or Nintendo.
Microsoft even set expectations for paying for online multiplayer usage, even if it was being hosted by your console on your Internet connection and now Sony has followed in their footsteps.
I've found it a useful tool for checking out day to day work documents (spreadsheets, etc), because it gives version control, as well as a decent hedge against ransomware (well, until there a variant starts purging Git repos.)
For Microsoft Office and it's formats, I find Microsoft Groove to be a better solution.
For Windows PC games whats wrong with just using whatever API windows has already?
Doesn't work on xbox (without expensive SDK requirements) or current versions of Windows mobile or current versions of Windows on ARM devices (like tablets).
Slashdot Mirror
How about just being specific about those processes then? Like FreeBSD team is using a variant of the v-model, the upper community of the Linux kernel uses a unique variant of Agile or the Koffice team uses Scrum etc.
I've not noticed any difference between large opensource projects and large proprietary projects through resolutions time. However, you're mentioning specifically 'commercial' projects and... I have to say, when it comes to commercial projects, I've had more responsive people through paid support channels despite the project being either proprietary or opensource. The resolution because of that responsiveness on occasion was faster.
I'm not very familiar with it, but that's still being developed. So this doesn't really make the point.
I didn't think any of those were amazing, honestly.
Don't get me wrong, I use opensource software daily and I work with it, I just don't have this great experience with the community. Some of the most annoying support I've had from both Microsoft and Redhat, both on opensource and closed source technologies provided by both for enterprise level stuff.
A tiny patch for a large project requires setting up a development environment which in my experience is often taking the piss in complexity (my luck is that I always end up in that stage when the environment setup instructions have just become outdated and I waste a week or two trying to find out what I need to do, by which the documentation is updated when I find out) and this is coming from someone experienced in working in large software projects. Then sometimes you find out the software which is opensource, is actually using proprietary libraries like Kakadu, fmod, Havok (and for actually good reasons) etc. and the licensing cost for at least two of those is something insane; so you're left dependent on developers.
I get really annoyed with some opensource projects, because you're encouraged to "join the community" and become part of it. So you go through the entire processes needed and in fact, forced, just so you can report a bug, provide a patch or such and then you end up having to deal with attitude (typically this is from unpaid volunteers, paid people generally seem a lot nicer) over your contributions. At least with proprietary software, typically I just fill out a form and the response I get isn't typically highly resistant and written in such a form that doesn't feel like someone told you to "feck off". But then, even if you were, you wouldn't feel the burn as much since you weren't forced to go through an entire process of be part of the community love.
To be honest, I've never seen that in any of the large projects I mentioned. If you wanted to do a release version, you had to go through the entire process. Perhaps you could give an example of a large project that has made an official release for a minor fix just for you while skipping all their processes?
You're forgetting they can license the trademark to fans under a variety of conditions. Protecting trademarks can be as simple as licensing individuals using them.
My experience in such matters has lead to disappointment. But, I guess experience can vary.
When working with large code bases like Seamonkey, Second life, OpenOffice.org, SystemD etc. The amount of capability as user (or developer) has in order to do much on these can be extremely limiting.
Are you talking about render farms that are running on a Linux based operating system while putting most of the work on the graphic cards which is being done by using proprietary drivers to do so?
Tell me more of Apple's amazing software that they abandoned.
It's not a movement, it's more of a mob.
As in, not everyone operating on their own forks and pushing to a single repository as opposed to doing pull requests.
I don't need advice. I just pointed out a way to lock files in git and also told you it was a bit pointless if you're using it in a distributed fashion.
I've seen it done successfully in a large multi-national team (and I can't recall any issues we had) in my consultancy life. They did have a small wrapper script (and some simple scripts to lock, unlock files without needing to memorize everything) to ensure the repo was always kept up to date though. What I'm suggesting is based off something that worked.
Personally, I think if you want to prevent concurrent edits through some central management, you should use the tools built for that. But saying you can't lock files on Git is another matter.
They could call it "release" instead, problem solved.
Oh, I stand corrected. I switch currencies a lot, so I probably got confused.
Nah, he's just a mechanic and works a little with electrical tools at his home. He has a big gripe over electricity costs.
I don't think he's being wasteful though, I think he genuinely keeps to good practice with his energy consumption, using it only when he needs it.
I recall having to do that for a friend, just so Facebook would be more responsive on their computer. I can't really think of anyone that didn't do that for a genuine reason.
You can heat rooms with air conditioning in Europe.
I tend to plug xbox 360 controller in which typically deals with any issues like poor keyboard and mouse support. They also usually work better due to my beefier machine.
Nah, its' not needed. I can capture it just fine regardless with borderless full screen and not have performance drop below 60fps.
They can with UWP. But you know, maybe I should rephrase to say that the effort is extremely minimal if that will make you happy.
Controller API is identical across all the platforms (you can essentially play the entire thing on PC using an xbox controller, touch screen), the fact they may add some branching code in release builds based on what platform you're using is of little relevence.
Microsoft even set expectations for paying for online multiplayer usage, even if it was being hosted by your console on your Internet connection and now Sony has followed in their footsteps.
Well, technically generation 4 reactors can, they can keep reusing nuclear waste over and over to generate power until it becomes fairly innate.
I knew a fair few apartments that were using airconditioning in Berlin... I don't really think it was that rare.
I have a friend who pays 400EUR/month in Germany for his electric bill. If we go back a year in exchange rates, I think that was worth over 1000USD.
Developers that want to write-once, use everywhere.
This technology is not cross-platform with non-Microsoft platforms.
Indeed.
For Microsoft Office and it's formats, I find Microsoft Groove to be a better solution.
As long as you aren't using Git in a distributed fashion, you should be able to do something like:
and then remove write permissions from the file, commit, I guess...
Doesn't work on xbox (without expensive SDK requirements) or current versions of Windows mobile or current versions of Windows on ARM devices (like tablets).
Is there still a genuine practical use for it in today's world?