You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I think i have a lot of question to be asked judging from Planka codebase, and just disclaimer, I'm not saying your codebase is bad or anything that is meant to offend,
Are you came from FAANG company or top technology company?
I just wonder, because most of devs that i know that came from there would have such nature to make something with a lot of dependencies in their projects
Are you planning to reduce the dependency used in the project in the future?
The problem here is due to maintainability of the project, if you have a lot of dependencies, i think that just made it hard to maintain every each of dependency used.
Also the problem with this is when you, let's take example, developing Planka using Linux, and then someone is tried to help developing Planka but using Windows, there's a chance that some dependency are incompatible with different OS, and me myself, had faced this with prop-types dependency in client when trying to deploy Planka using Windows 10.
Are you planning about restructuring your codebase?
Looking at the current codebase right now it's kinda complicated, I mean like, there's a lot of people trying to install Planka without Docker before, and most of them were failed because it's kinda complicated, especially because you split up client and server folder.
Maybe it could be much better if you just merge everything to the top-level folder instead of splitting client and server folder, and with this, you don't need to work 2 times, like putting a script on server folder and then putting a same script on the top-level folder too.
Are you thinking about using framework in the future? (Example: NextJS)
I've a lot of experience doing things with next, and i think using framework, vue, next, or etc, will help you develop it faster since you don't need to handle basic essentials things like backend routings, front end routings, etc.
Also NextJS support websocket, I've built a realtime chat application with it and it's work great, even with a very minimum dependency.
Do you plan on making Discord or any realtime forum to discuss about Planka in the future?
I think it'd be great if we had some platform to discuss things in realtime, in that way, we could also message you quickly if something vulnerable is showing up in your codebase.
Last note:
These are my question and also some suggestion you might wanted to think off, I'm sorry if there are some word error or bad English since English is not my first language.
Previously i wanted to help you developing Planka, and my first step was trying to add Markdown editor in the Card Modal description, but i can't even start development server. I think you are quite concerned about the number of enhancement requests, therefore I want to try to help you by making changes to the existing codebase, and making pull requests to reduce your workload.
Love to hear what you think about this, thank you 🙏
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi! I think i have a lot of question to be asked judging from Planka codebase, and just disclaimer, I'm not saying your codebase is bad or anything that is meant to offend,
Are you came from FAANG company or top technology company?
I just wonder, because most of devs that i know that came from there would have such nature to make something with a lot of dependencies in their projects
Are you planning to reduce the dependency used in the project in the future?
The problem here is due to maintainability of the project, if you have a lot of dependencies, i think that just made it hard to maintain every each of dependency used.
Also the problem with this is when you, let's take example, developing Planka using Linux, and then someone is tried to help developing Planka but using Windows, there's a chance that some dependency are incompatible with different OS, and me myself, had faced this with
prop-types
dependency inclient
when trying to deploy Planka using Windows 10.Are you planning about restructuring your codebase?
Looking at the current codebase right now it's kinda complicated, I mean like, there's a lot of people trying to install Planka without Docker before, and most of them were failed because it's kinda complicated, especially because you split up client and server folder.
Maybe it could be much better if you just merge everything to the top-level folder instead of splitting client and server folder, and with this, you don't need to work 2 times, like putting a script on server folder and then putting a same script on the top-level folder too.
Are you thinking about using framework in the future? (Example: NextJS)
I've a lot of experience doing things with next, and i think using framework, vue, next, or etc, will help you develop it faster since you don't need to handle basic essentials things like backend routings, front end routings, etc.
Also NextJS support websocket, I've built a realtime chat application with it and it's work great, even with a very minimum dependency.
Do you plan on making Discord or any realtime forum to discuss about Planka in the future?
I think it'd be great if we had some platform to discuss things in realtime, in that way, we could also message you quickly if something vulnerable is showing up in your codebase.
Previously i wanted to help you developing Planka, and my first step was trying to add Markdown editor in the Card Modal description, but i can't even start development server. I think you are quite concerned about the number of enhancement requests, therefore I want to try to help you by making changes to the existing codebase, and making pull requests to reduce your workload.
Love to hear what you think about this, thank you 🙏
Beta Was this translation helpful? Give feedback.
All reactions