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 2 years ago.
Improve this question
Are there any software versioning standards? Or i can change version of my product, when i have made some changes to it?
Is there any percentage in changes, by which i can say, what version this product will have?
Some people have proposed software version number conventions. Here are two:
Semantic Versioning
Apache APR Version Numbering Concepts
No rules. You decide.
There seems to be a common agreement:
You increment the version number when you make significant changes or the amount of service packs and updates makes the application noticeably advanced over the original version.
The smaller a change is, the smaller the increment in subversion numbers. Bug fix -> behavior change -> new feature -> service pack for lots of features -> some big change or a new module.
Related
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 1 year ago.
Improve this question
I recently created a Vue.js project. I've added a few packages, including Firebase (I have the modular v9 package, so it has tree shaking enabled), and Rive. When building my application, I see that my final bundle is about 800-900KiB, while webpack suggests keeping it under 240. I created a report and I saw that Rive and Firebase were the main culprits of the big filesize (together they were about 750KiB). Rive is a package still in early development so it wouldn't surprise me if it wasn't optimized for production, but the fact that firebase also used so much space (specially considering I used v9) made me wonder whether I did something wrong?
Anyway, my question is, is having a bundle of around 1MiB bad? How badly would it impact user?
1MB isn't bad, it may take slightly longer to load initially, considering most jpg images you see online can be up to 1MB each easily. most users with modern bandwidth connections will not notice any negative side effects.
It's just something you should keep in mind.
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 6 years ago.
Improve this question
I have looked around and have not found many opinions on if it is important to update your R software as soon as a new version is released.
Any opinions would be welcomed!
As with any software, you should carefully evaluate what is included in any new release. If the release consists only of bug-fixes, it is usually expedient to install it as soon as it is practicable for you to do so. If the scope of the release is more expansive -- new features, etc. -- you should review the release more carefully.
If you're in the middle of an important project with a killer deadline, it's quite reasonable to wait a little while before applying any update.
Also, you should as a matter of routine re-run a selection of jobs, that you know the answers to, in order to be sure that the answers are still the same. "No, mistakes of this nature don't happen often, but they do happen."
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 6 years ago.
Improve this question
Since ~1999 everyone has been saying that TCP/IP v6 will replace v4 within then next couple of years. When might the change actually happen and what will be the implications?
No one can answer that question.
Valid answers may be anything from "any day now" to "never". What do you expect people to say?
IpV6 is actually gaining pretty good traction if you bother to take a look at Googles graphs and the number of AAAA hosts being published in the global DNS. And all mainstream operating systems (Windows, OS X, Linux, FreeBSD) support it out-of-the-box.
What more do you want? You cannot get any guarantees or (realistic) promises.
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 7 years ago.
Improve this question
I have been using prepros for a while. It's a easy to use precompiler that pretty much does everything I need. I heard it is not good for team work but didn't know why.
Why would you spend time to set up gulp to for minification, concatenation, uglify/mangle, live reload and live server when you can simply press one button and do all of these works in 5 secs?
I've never used Prepros and therefore have nothing negative to say about it. However, I think:
a) Your point is somewhat reductionist. Gulp isn't just a precompiler, it's a task runner and can likely do a lot more than what Prepros is able to do out of the box. It's great if Prepros fits your needs, but what happens when you run into something that it can't do?
b) Gulp/Grunt/etc. are free (limiting proprietary software purchases is often beneficial in a team setting) and open source (easily tailorable to your needs)
As an aside, I'm not sure if Prepros allows settings to be shared by different members of the development team, but will gulp/grunt/etc. you check your gulpfile/gruntfile/etc. into source control and build tasks/etc. are available to all developers with access to said repository/project
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 8 years ago.
Improve this question
Is there a way to remove some uneeded locale to reduce the size of Qt Core ?
You'll need to be more specific about what your application requires. Regardless, I'd recommend reading through this thread on the interest mailing list, as it has some interesting information regarding slimming Qt Core. In particular, you can reduce the size of ICU:
I'll leave it for others to pass comment on the standard configure
options and size, but if you're really desperate for every last saving
then removing the locales you don't need can save you 230 KB (on Linux
64bit it reduces my default release build from 5.5MB to 5.2MB), but
it's a manual process:
Download http://unicode.org/Public/cldr/24/core.zip and unzip
Run "../path/to/qt5/qtbase/util/local_database/cldr2qlocalexml.py
core/common/main >> qlocale.xml"
Edit qlocale.xml to remove all the locales you don't need: only
remove groups from inside and nothing else, I
suggest you always keep C and en_US in addition to the locales you
require.
Run "../path/to/qt5/qtbase/util/local_database/qlocalexml2cpp.py
qlocale.xml ../path/to/qt5/qtbase/"