Version 3
# Background This project started out as a small package. Over time, more and more features were added and it now provides many different things and is used by many developers. But I'm not 100% happy with the current version for the following reasons: - it depends on many different webpack loaders which has led to some workarounds and many features cannot be combined because the loaders don't work well with each other. See #84, #91 for examples. - those loaders also depend on other packages which have also introduced errors/bugs where we don't have the possibility to fix them directly (as in #75). - while this package grew, the installation and configuration became more and more complex and I think there is some space for improvement here. # Idea To make this package robust for the future and easy to maintain, I think the only way is to fix those issues. And this probably requires a rewrite of the whole package. It can be broken down into multiple parts: ### Webpack loaders This is the most important part of this package and is currently out of our control. To support use-cases such as mentioned in #84 or #91 and so we are able to provide a stable plugin, I think the only way is to write an own webpack loader which does the image optimizations. That would have the following advantages: - all features work together (e.g. you can resize a jpg, convert it to webp and generate a lqip all at the same time, which is not possible right now) - we have more control over the librari
Posted by cyrilwanner on Nov 6, 2019, 5:50 PM
Tags
Related issues
- The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
- I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
- I hate that I'm in deep enough to know what you mean.
- The biggest problem with “AI” is that big corps are shoving it down our throats.
- in the middel of a coding session with 5.6 sol.
- [Hero Run] 535B-A23B on 18T tokens
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
reliability (Other)
The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
I hate that I'm in deep enough to know what you mean.
The biggest problem with “AI” is that big corps are shoving it down our throats.
in the middel of a coding session with 5.6 sol.
[Hero Run] 535B-A23B on 18T tokens
I hate that this is how AI is being used..
inexperienced protobuf user here -- why do non-googlers generally use protobuf?
Version 3
# Background This project started out as a small package. Over time, more and more features were added and it now provides many different things and is used by many developers. But I'm not 100% happy with the current version for the following reasons: - it depends on many different webpack loaders which has led to some workarounds and many features cannot be combined because the loaders don't work well with each other. See #84, #91 for examples. - those loaders also depend on other packages which have also introduced errors/bugs where we don't have the possibility to fix them directly (as in #75). - while this package grew, the installation and configuration became more and more complex and I think there is some space for improvement here. # Idea To make this package robust for the future and easy to maintain, I think the only way is to fix those issues. And this probably requires a rewrite of the whole package. It can be broken down into multiple parts: ### Webpack loaders This is the most important part of this package and is currently out of our control. To support use-cases such as mentioned in #84 or #91 and so we are able to provide a stable plugin, I think the only way is to write an own webpack loader which does the image optimizations. That would have the following advantages: - all features work together (e.g. you can resize a jpg, convert it to webp and generate a lqip all at the same time, which is not possible right now) - we have more control over the librari
Comments (0)
No comments yet. Start the discussion.