Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some Suggestions for the current version of the next theme are to be adopted [libs cannot be back built-in NexT ] #46

Closed
onxs opened this issue Jan 18, 2018 · 6 comments

Comments

@onxs
Copy link

onxs commented Jan 18, 2018

Program should do it out of the box, it is suggested that the next lib into source, avoid users touch not clear mind for the first time, but also caused some trouble to the person that often use, can download the lib

@ivan-nginx
Copy link
Member

Don't understand your suggestion. What exactly u want? In short words.

@wafer-li
Copy link
Member

@iiskei
If your English is not so good, please use some screenshots and pictures to express your view.

Don't make the mistake I've ever made.

@onxs
Copy link
Author

onxs commented Jan 18, 2018

I mean to put lib in the original next V5.1.4 into next 6.0. Is that clear?

@ivan-nginx
Copy link
Member

ivan-nginx commented Jan 18, 2018

😄 Yeah, it's clear but i change version mostly because this libs become separated and don't see any troubles to install needed. If u have bugs with this, issues are welcome.

Why it was maded? There are several reasons. And because NexT is growing up with each year, there are more and more external libs and:

  1. General maintenance became a harder for all who not only use it, but help with development too.
  2. Generation speed became slower and slower with each new library. Half of unused libs copied to public dirs for all users and search engines see all this libs too. It's mostly waste files for half NexT users.
  3. Full weight of NexT distributive at least decrease about 2x, which provides faster download & update speed.

So, was increased development speed, generation speed and download speed.

If this is uncomfortable for u, u can use old 5.1.x version, but without at least my maintenance.

@onxs
Copy link
Author

onxs commented Jan 18, 2018

I see, English is not very good, please forgive me, thank you.

@ivan-nginx ivan-nginx changed the title Some Suggestions for the current version of the next theme are to be adopted. Some Suggestions for the current version of the next theme are to be adopted. [libs cannot be back built-in NexT ] Jan 18, 2018
@lock
Copy link

lock bot commented Apr 1, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. It is possible issue was solved or at least outdated. Feel free to open new for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 1, 2019
@ivan-nginx ivan-nginx changed the title Some Suggestions for the current version of the next theme are to be adopted. [libs cannot be back built-in NexT ] Some Suggestions for the current version of the next theme are to be adopted [libs cannot be back built-in NexT ] Apr 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants