Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 5 years ago.
Improve this question
I've recently upgraded from Snow Leopard to OS X Lion and from XCode 3.2 to 4.1. But roughly said I'm unhappy with XCode. The reasons are many but the main one is I can't search the documentation installed. In 3.2 I used to be able to have incremental search-so as I typed class and other references where displayed and I could choose the one I needed. But in 4.1 most of the time I can't even type in the search area. It just freezes and won't let me type. Does anybody else have this issue.
Xcode 4 seems to require quite a bit more power to run smoothly. Since you're talking about something not specific to an individual project, I'm guessing it's performance in general.
For comparison: On a MacBook Air (not the latest but purchased earlier in 2011), it's "workable" but quite slow and seems to grow angry at the merest hint of the word "battery." It pauses frequently, doc searches are smooth if by "smooth" you mean "lined with brick walls." Conversely, on a (similarly next-to-latest) top of the line iMac with 16 GB RAM and a solid state drive, Xcode 4.1 has no apparent performance issues.
In other words, the new shiny might require a hardware upgrade to run smoothly.
It's quite odd but after a while the problem with the documentation just disapperared. Now I can look up any API reference. But anyway i still find the old style Xcode and Documentation nicer and easier.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
(Edited to narrow the question to Ada. Have posted other questions for Fortran and COBOL.)
I've spent some time in the past year dealing with changes to my code due to Python v2->v3 and R v3->v4 changes. It got me curious as to some of the older languages that are still in use.
I know Ada still sees occasional updates and functionality upgrades. I would assume that their mission-critical nature makes those changes smaller and more backward-compatible, but I don't really know and couldn't find it with a web search.
What and when were the last changes to Ada that was on the same rough order as the Python 2->3 changes?
Ada pays a lot of attention to reverse compatibility, to avoid breaking existing code, when making changes.
Last formal Ada release was Ada-2012, there is another one (Ada-202X) in progress.
Ada-2012 has a lot that Ada-83 doesn't, but I'd be surprised if there was anything more than trivial work to build an Ada-83 project (or Ada-95 or Ada-2005) in Ada-2012.
There are some differences though : from Ada-83 to Ada-2012 As you can see, there's really not much to say for 30 years of development.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I've been using R for 13+ years, and teaching R for 3+ years, and I still get blind-sighted by the timing and rationale for R's 'x.y.z' midyear releases. For the past few years they have tried to standardize it, with a new 'x.y.0' coming out each year in the spring, and 2-3 'x.y.z' updates during the following year. But the reality has been anything but predictable.
Specifically, for the 2nd year in a row, and the 3rd time in 4 years, the 'x.y.0' release was followed within a month or so by an 'x.y.1' release, ostensibly because there was some major bug or instability in the former. And this year they also released a 3.2.5, only 3 weeks before the 3.3.0. Normally, one would expect each 'x.y.z' release to last 3-4 months before being replaced.
My problem is, I have yet to find the place online where discussions, or at least some authoritative summary, of the issues involved and what R users should expect regarding upcoming releases, are posted. Either I am missing something obvious, or most of this happens somewhere very obscure or even behind closed doors.
To clarify: we do eventually receive a detailed list of all changes that took place in a release. But I cannot find the information regarding what's in the pipeline, whether there are major issues in the current release I should be aware of, etc.
Or in other words, I'm looking for the "Forest" level view, rather than the "Trees". Does the current release have major issues? If yes, is there a fix in the works and when? Regardless, are there grand changes planned for an upcoming release? Etc.
Any insight on the matter will be greatly appreciated.
Thanks, Assaf
It looks like one of the better ways to stay up-to-date is by following the R-announce mailing list. It also has a web archive if you find that more convenient.
Furthermore, the R developer page seems like a useful resource. It includes a regularly update NEWS file with the recent and upcoming changes to R.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
How are versions numbered? What is the proper idea behind going to next version, increments, etc?
For example, I often see v0.1, v0.2, v0.34567 etc. I assume these are softwares that are in beta, and haven't finished the first release yet.
But there are also many softwares that are v0.10.11, etc. how do they work?
There is not a specific standard - anybody can follow any scheme (or lack of scheme). It's up to corporate policy, development standards, or whatever guidelines you are under.
There are some popular standards out there. We try to follow the Semantic Versioning standard. The basic tenants include (quoted):
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backwards-compatible manner
PATCH version when you make backwards-compatible bug fixes.
Links:
Semantic Versioning: http://semver.org/
Other versioning schemes: http://en.wikipedia.org/wiki/Software_versioning#Schemes
There are competing standards, which saddens me greatly, especially in a world where git is popular.
SymVer, as mentioned, helps a great deal, but a lot of popular software doesn't use it.
Unfortunately, this doesn't help a great deal when dealing with distros, who apply patches to specific versions of software, effectively changing it's version.
The closest to "proper" I have seen yet is done by NixOS. Each version of their software is hashed, as are all patches applied, and each end result has a different hash, line any change in Git.
The resulting output will be different as well, uniquely identifying it against others.
Until that method is adopted, it's a free-for-all, and versioning is not a consistent thing.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Not sure if this is the right forum (and if so, point out to me and I will delete this post!).
I had been evaluating languages to replace a existing code written in R that has around 4k-5k lines(and used for live trading), primarily to get speed and I liked Julia (v0.2.0) - not only for its speed, but also because the language is easy to learn.
I would like to initiate a project to rewrite the existing R code in Julia, but since it can be a major exercise for me, I wanted to ask if there is any information available anywhere whether the future releases of Julia will be largely backward compatible with Julia v0.2.0?
For example, one issue I faced earlier with Python was that v3.0 onwards are not quite backward compatible with v2.7, and v2.5 codes don't often work on v2.6, v2.6 codes don't often work on v2.7, requiring significant rewrites because you have to carefully evaluate where the old code broke (and was almost always better to rewrite the code from fresh). I want to avoid the same issue with Julia.
While Dirk is right that anything is on the table for changing up to version 1.0, we do have some assurances about compatibility:
There is a release-0.2 branch that will contain only bug-fixes, so if you write code for Julia 0.2, it will continue to work on that branch
We try very hard to deprecate APIs that we change, rather than just yanking them out from under you. This means that your code will keep working, but you will get a warning telling you the new way to do something.
There have been very few basic syntax changes in the past year, and I don't really foresee any big ones. Most of the changes that still need to happen are standard library API changes.
"Maybe" but probably not.
Goals for the 0.3 to 1.0 transition are (among other things) to get all breaking changes out of the way.
In other words, between now and 1.0 changes are to be expected.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am looking for a basic and simple-to-install digital version of a Scrum board.
I do prefer physical index cards, but in this case logistics makes it hard. Thus, I need to have it on the computer.
No real need to share data between several clients. To us it is enough if it runs on one single machine.
Just need basic functionality. A drag-drop board and a sprint burndown would do fine.
Due to regularly constraints I cannot use an online SaaS, must keep the data local.
Time is short, so simple install and ready-to-go.
Does not need to be free, but of course price is interesting.
I have not had this set of constraints earlier, so I am unfamiliar.
I have done some research and have some general experience. For example VersionOne, Mingle and Hansoft seem to have a good reputation. Anyone can comment on how those fit the above list? Anyone have other recommendations?
This thread is a bit old now, but leaving my find in the hope to help others searching the same topic.
If you are looking for a simple tool for developers to collaborate on a Scrum project, http://trello.com/ is very simple and intuitive. Absolutely no clutter and easily lets a small team manage their cards.
I would have a look at Atlassian Jira with the GreenHopper plugin - it has a nice dashboard.
http://www.atlassian.com/software/greenhopper/
Have a look at Mingle from ThoughtWorks. A really great tool. Wall looks like this
Free download/install for 1 year / 5 users.
Excel (or OpenOffice) spreadsheet? Why do you need a special tool for this?
I had a similar decision to make a year ago and went for Version One Team Edition - which is free.
http://www.versionone.com/Product/Compare_Editions.asp
It's easy to deploy the SQL database wherever you want it - so locally in your case.
Our team found using the software easy and intuitive.
The free version (up to 10 users) has ample features - the sprints/stories/tasks are easy to setup and view. The burndown chart is good.
All in all, I've no regrets with choosing Verison One - it's easy to install, easy to use and free.