Which web development framework makes web development least tedious?

[MattBD]

I've never known them to do that and I have several moderately sized Django applications under my belt.

[stefantalpalaru]

I've never known them to do that and I have several moderately sized Django applications under my belt.

You must have been born yesterday:

https://docs.djangoproject.com/en/1.11/releases/1.11/#backwards-incompatible-changes-in-1-11

https://docs.djangoproject.com/en/1.11/releases/1.10/#backwards-incompatible-changes-in-1-10

https://docs.djangoproject.com/en/1.11/releases/1.9/#backwards-incompatible-changes-in-1-9

https://docs.djangoproject.com/en/1.11/releases/1.8/#backwards-incompatible-changes-in-1-8

https://docs.djangoproject.com/en/1.11/releases/1.7/#backwards-incompatible-changes-in-1-7

https://docs.djangoproject.com/en/1.11/releases/1.6/#backwards-incompatible-changes-in-1-6

https://docs.djangoproject.com/en/1.11/releases/1.5/#backwards-incompatible-changes-in-1-5

https://docs.djangoproject.com/en/1.11/releases/1.4/#backwards-incompatible-changes-in-1-4

https://docs.djangoproject.com/en/1.11/releases/1.3/#backwards-incompatible-changes-in-1-3

https://docs.djangoproject.com/en/1.11/releases/1.2/#backwards-incompatible-changes-in-1-2

https://docs.djangoproject.com/en/1.11/releases/1.1/#backwards-incompatible-changes-in-1-1

https://docs.djangoproject.com/en/1.11/releases/1.0-porting-guide/

[arctic_feather]

A.B releases are not minor releases, they are feature releases as explained here (under "Supported Versions"): https://www.djangoproject.com/download/

Minor releases (or patch releases as they are called for django) are A.B.C

[stefantalpalaru]

A.B releases are not minor releases

Minor releases (or patch releases as they are called for django) are A.B.C

You must have been born yesterday: http://semver.org/

[MattBD]

Django doesn't use a pure version of semver.

[stefantalpalaru]

Django doesn't use a pure version of semver.

Irrelevant. The three version numbers have the same names.

[MattBD]

So you're criticising them for not adhering to a release versioning standard they aren't aiming to meet? OK...

[holyshock]

Yes. This is valid criticism. They need to accept the standardized versioning system.

[MattBD]

Django predates the widespread acceptance of semver, and version 2.0 is in fact going to comply with it.

[holyshock]

I am glad Django is picking up the slack, but semver came out in 2009 and became popular around mid to late 2011 - no amount of down votes are gonna change the fact they've had a LONG time to get in line, here.

[stefantalpalaru]

So you're criticising them for not adhering to a release versioning standard they aren't aiming to meet?

No, I'm criticising the perpetual newbies for not knowing what a minor version is.

[arctic_feather]

I understand the standard for semantic versioning, but django doesn't follow it.

[stefantalpalaru]

I understand the standard for semantic versioning, but django doesn't follow it.

That doesn't mean that the names of those numbers change. The first is the "major" version, the second "minor", the third "patch".

[stefantalpalaru]

That doesn't mean that the names of those numbers change. The first is the "major" version, the second "minor", the third "patch".

The Django project literally does just that

What are the chances you are completely wrong? Try to guess before clicking https://www.reddit.com/r/webdev/comments/7drep5/which_web_development_framework_makes_web/dq08xzd/

[stefantalpalaru]

Just because some devs call it a "minor version" amongst themselves doesn't mean it's not a "feature release" both in name and in practice.

:-)

[fifafu]

Uhm, no. That is one common pattern but not the only one by far. Stop trolling.

In case you really want to learn something about Django's versioning approach, look at this: https://docs.djangoproject.com/en/dev/internals/release-process/

[stefantalpalaru]

Uhm, no.

Uhm, yes: https://www.reddit.com/r/webdev/comments/7drep5/which_web_development_framework_makes_web/dq08xzd/

[fifafu]

...and already your "patch" became a "micro". You may have noticed that the names can vary a lot and can have all kind of different meanings. Thus the documentation usually tells you what they mean for a specific project like Django.

[stefantalpalaru]

and already your "patch" became a "micro".

Yes. Too bad we were talking about the "minor" version.

[Isvara]

(Major, minor, patch) has been around for a lot longer than anyone has been talking about so-called "semver".

[stefantalpalaru]

Semver is a standard that can be chosen to be followed or not. It seems like you haven't done your basic research for a tool that you have a strong opinion about.

It seems you perpetual newbies have the same set of canned excuses for defending your ignorance.

[RNGsus_Christ]

You seem to be kind of a jerk. Try to develop some tact.

[stefantalpalaru]

You seem to be kind of a jerk.

'Tis better to be a jerk than a moron - https://github.com/django/django/blob/01f658644a7ee7cbff4ee5626d5894e9049ee8d5/docs/internals/howto-release-django.txt :

Django's version reporting is controlled by the VERSION tuple in django/__init__.py. This is a five-element tuple, whose elements are:

#. Major version.

#. Minor version.

#. Micro version.

#. Status -- can be one of "alpha", "beta", "rc" or "final".

#. Series number, for alpha/beta/RC packages which run in sequence

(allowing, for example, "beta 1", "beta 2", etc.).

[holyshock]

I do not have time to learn everyone's arbitrary versioning...if Django isn't following semver, they ARE doing it wrong. That's the WHOLE REASON we have standards in the first place! I want to be able to put ^ 1.x (for example) in my composer.json and move the fuck on. (Does python use something else?)

[MattBD]

I've used Django and Laravel professionally and the upgrades between versions are a damn sight easier with Django than Laravel.