 | Logseq: Feedback | 4206 Members |
| Discuss improvements to Logseq here. Want to propose a feature to the team? Please use the forum as this chat is not actively monitored by the Logseq team. https://discuss.logseq.com/c/feature-requests/7 | This is the feedback channel of the official Logseq Space on Matrix, which you can find at #logseq:matrix.org. | 19 Servers |
| Sender | Message | Time |
|---|---|---|
| 25 Apr 2024 | ||
 generalchaosdaemon | the word choice of "refactoring" is not a great choice. Many inexperienced developers use that word when they are deep in the middle of rewriting a piece of code. And typically in my experience they really are in over their head and all hell breaks loose after release, at which point the experienced developers need to step in and put out the fires | 00:06:01 |
 .luhmann | * There is one major task: the refactoring of the backend. After this big task is done they will likely go back to more incremental updates. Before you jump ship I suggest looking at some of the previews of what will be possible after the refactor. You can jump to about 14 min in this video: https://www.youtube.com/watch?v=fRWwznJFkJM | 00:06:12 |
| generalchaosdaemon | * the word choice of "refactoring" is not a great choice. Many inexperienced developers use that word when they are deep in the middle of rewriting a piece of code. And typically in my experience they really are in over their head and all hell breaks loose after release, at which point the experienced developers need to step in and put out the fires. I don't know why it always plays out this way, but it does. | 00:06:20 |
| generalchaosdaemon | * the word choice of "refactoring" is not a great choice. Many inexperienced developers use that word when they are deep in the middle of rewriting a piece of code. And typically in my experience they really are in over their head and all hell breaks loose after release, at which point the experienced developers need to step in and put out the fires. I don't know why it always plays out this way, but it does. I suspect because when young devs "refactor" they don't have a list of tasks. | 00:07:11 |
| generalchaosdaemon | * the word choice of "refactoring" is not a great choice. Many inexperienced developers use that word when they are deep in the middle of rewriting a piece of code. And typically in my experience they really are in over their head and all hell breaks loose after release, at which point the experienced developers need to step in and put out the fires. I don't know why it always plays out this way, but it does. I suspect because when young devs "refactor" they don't have a list of tasks. so far, nothing I've heard in the last few minutes points me away from "disasterous rewrite of main app" scenarios I have seen in my past. | 00:08:30 |
| generalchaosdaemon | * the word choice of "refactoring" is not a great choice. Many inexperienced developers use that word when they are deep in the middle of rewriting a piece of code. And typically in my experience they really are in over their head and all hell breaks loose after release, at which point the experienced developers need to step in and put out the fires. I don't know why it always plays out this way, but it does. I suspect because when young devs "refactor" they don't have a list of tasks. so far, nothing I've heard in the last few minutes points me away from "disasterous rewrite of main app" scenarios I have seen in my past. That's a shame. I hope they can figure out how to launch despite the red flags. | 00:09:27 |
 blogbourri | do they have a task list that they are burning down? Are they communicating their progress towards their milestones to their users somewhere? there is a roadmap. https://trello.com/b/8txSM12G/logseq-roadmap I am going to jump to the first app that has similar capabilities as logseq because I do not believe this development team is experienced enough. when you find one, feel free to share it in #tools-for-thought . unlike on reddit, where people treat the software they use like some kind of dog fighting ring, i think most people on this server are of the mind that more tools doing innovative things in knowledge management is a good thing. logseq isn't a polished product. it has issues. in fact, it has systemic issues that resulted from the way it was pieced together early on. those systemic issues are being resolved. you can call that a red flag. i'd call it kinda typical for most software that starts out as a personal project and goes open source. most open source software i use went through at least one, sometimes more complete rewrites, in order to get the foundations right for long-term development. this includes era defining open-source software like vlc and firefox as well as smaller projects. if another local-first queryable, block-based open source outliner comes along and manages to nail all the details before logseq, i mean .... cool! hell yeh. i don't know of any other projects even attempting what logseq is, but if they're out there and showing feature maturity anytime in the future i'll give them a spin. all of the apps you listed above as working perfectly with icloud have results if you just google "appname problems with icloud." icloud kinda just sucks if you regularly have to read/write anything to it regularly and are relying on that transaction to happen reliably. | 01:03:43 |
| blogbourri | * do they have a task list that they are burning down? Are they communicating their progress towards their milestones to their users somewhere? there is a roadmap. https://trello.com/b/8txSM12G/logseq-roadmap I am going to jump to the first app that has similar capabilities as logseq because I do not believe this development team is experienced enough. when you find one, feel free to share it in #tools-for-thought . unlike on reddit, where people treat the software they use like some kind of illegal dog fighting ring, i think most people on this server are of the mind that more tools doing innovative things in knowledge management is a good thing. logseq isn't a polished product. it has issues. in fact, it has systemic issues that resulted from the way it was pieced together early on. those systemic issues are being resolved. you can call that a red flag. i'd call it kinda typical for most software that starts out as a personal project and goes open source. most open source software i use went through at least one, sometimes more complete rewrites, in order to get the foundations right for long-term development. this includes era defining open-source software like vlc and firefox as well as smaller projects. if another local-first queryable, block-based open source outliner comes along and manages to nail all the details before logseq, i mean .... cool! hell yeh. i don't know of any other projects even attempting what logseq is, but if they're out there and showing feature maturity anytime in the future i'll give them a spin. all of the apps you listed above as working perfectly with icloud have results if you just google "appname problems with icloud." icloud kinda just sucks if you regularly have to read/write anything to it regularly and are relying on that transaction to happen reliably. | 01:04:02 |
| blogbourri | * do they have a task list that they are burning down? Are they communicating their progress towards their milestones to their users somewhere? there is a roadmap. https://trello.com/b/8txSM12G/logseq-roadmap I am going to jump to the first app that has similar capabilities as logseq because I do not believe this development team is experienced enough. when you find one, feel free to share it in #tools-for-thought . unlike on reddit, where people treat the software they use like some kind of illegal dog fighting ring, i think most people on this server are of the mind that more tools doing innovative things in knowledge management is a good thing. logseq isn't a polished product. it has issues. in fact, it has systemic issues that resulted from the way it was pieced together early on. those systemic issues are being resolved. you can call that a red flag. i'd call it kinda typical for most software that starts out as a personal project and goes open source. most open source software i use went through at least one, sometimes more complete rewrites, in order to get the foundations right for long-term development. this includes era defining open-source software like vlc and firefox as well as smaller projects. if another local-first queryable, block-based open source outliner comes along and manages to nail all the details before logseq, i mean .... cool! hell yeh. i don't know of any other projects even attempting what logseq is, but if they're out there and showing feature maturity anytime in the future i'll give them a spin. all of the apps you listed above as working perfectly with icloud have results if you just google "appname problems with icloud." icloud kinda just sucks if you regularly have to read/write anything to it regularly and are relying on that transaction to happen reliably. the premise that this is a uniquely logseq issue is dubious. | 01:04:55 |
| blogbourri | * do they have a task list that they are burning down? Are they communicating their progress towards their milestones to their users somewhere? there is a roadmap. https://trello.com/b/8txSM12G/logseq-roadmap I am going to jump to the first app that has similar capabilities as logseq because I do not believe this development team is experienced enough. when you find one, feel free to share it in #tools-for-thought . unlike on reddit, where people treat the software they use like a dog in some kind of illegal dog fighting ring, i think most people on this server are of the mind that more tools doing innovative things in knowledge management is a good thing. logseq isn't a polished product. it has issues. in fact, it has systemic issues that resulted from the way it was pieced together early on. those systemic issues are being resolved. you can call that a red flag. i'd call it kinda typical for most software that starts out as a personal project and goes open source. most open source software i use went through at least one, sometimes more complete rewrites, in order to get the foundations right for long-term development. this includes era defining open-source software like vlc and firefox as well as smaller projects. if another local-first queryable, block-based open source outliner comes along and manages to nail all the details before logseq, i mean .... cool! hell yeh. i don't know of any other projects even attempting what logseq is, but if they're out there and showing feature maturity anytime in the future i'll give them a spin. all of the apps you listed above as working perfectly with icloud have results if you just google "appname problems with icloud." icloud kinda just sucks if you regularly have to read/write anything to it regularly and are relying on that transaction to happen reliably. the premise that this is a uniquely logseq issue is dubious. | 01:05:20 |
| blogbourri | * do they have a task list that they are burning down? Are they communicating their progress towards their milestones to their users somewhere? there is a roadmap. https://trello.com/b/8txSM12G/logseq-roadmap I am going to jump to the first app that has similar capabilities as logseq because I do not believe this development team is experienced enough. when you find one, feel free to share it in #tools-for-thought . unlike on reddit, where people treat the software they use like a dog in some kind of illegal dog fighting ring, i think most people on this server are of the mind that more tools doing innovative things in knowledge management is a good thing. logseq isn't a polished product. it has issues. in fact, it has systemic issues that resulted from the way it was pieced together early on. those systemic issues are being resolved. you can call that a red flag. i'd call it kinda typical for most software that starts out as a personal project and goes open source. most open source software i use went through at least one, sometimes more complete rewrites, in order to get the foundations right for long-term development. this includes era defining open-source software like vlc and firefox as well as smaller projects. do rewrites sometimes fail? sure. jumping from that to the concept of a refactoring being a red flag, is dubious. if another local-first queryable, block-based open source outliner comes along and manages to nail all the details before logseq, i mean .... cool! hell yeh. i don't know of any other projects even attempting what logseq is, but if they're out there and showing feature maturity anytime in the future i'll give them a spin. all of the apps you listed above as working perfectly with icloud have results if you just google "appname problems with icloud." icloud kinda just sucks if you regularly have to read/write anything to it regularly and are relying on that transaction to happen reliably. the premise that this is a uniquely logseq issue is also dubious. | 01:10:47 |
| blogbourri | * do they have a task list that they are burning down? Are they communicating their progress towards their milestones to their users somewhere? there is a roadmap. https://trello.com/b/8txSM12G/logseq-roadmap I am going to jump to the first app that has similar capabilities as logseq because I do not believe this development team is experienced enough. when you find one, feel free to share it in #tools-for-thought . unlike on reddit, where people treat the software they use like a dog in some kind of illegal dog fighting ring, i think most people on this server are of the mind that more tools doing innovative things in knowledge management is a good thing. logseq isn't a polished product. it has issues. in fact, it has systemic issues that resulted from the way it was pieced together early on. those systemic issues are being resolved. you can call that a red flag. i'd call it kinda typical for most software that starts out as a personal project and goes open source. most open source software i use went through at least one, sometimes more complete rewrites, in order to get the foundations right for long-term development. this includes era defining open-source software like vlc and firefox as well as smaller projects. do rewrites sometimes fail? sure. jumping from that to the entire concept of a refactoring being a red flag, is dubious. if another local-first queryable, block-based open source outliner comes along and manages to nail all the details before logseq, i mean .... cool! hell yeh. i don't know of any other projects even attempting what logseq is, but if they're out there and showing feature maturity anytime in the future i'll give them a spin. all of the apps you listed above as working perfectly with icloud have results if you just google "appname problems with icloud." icloud kinda just sucks if you regularly have to read/write anything to it regularly and are relying on that transaction to happen reliably. the premise that this is a uniquely logseq issue is also dubious. | 01:11:06 |
| generalchaosdaemon | logseq engineering team has a systematic engineering culture issue. Experienced software professionals, like myself, can recognize this in their output. | 05:33:20 |
| generalchaosdaemon | * logseq engineering team has a systematic engineering culture issue. Experienced software professionals, like myself, can recognize this in their output. Experienced software professionals know what other experienced professionals look like and this aint it. | 05:34:05 |
| generalchaosdaemon | * logseq engineering team has a systematic engineering culture issue. Experienced software professionals, like myself, can recognize this in their output. Experienced software professionals know what other experienced professionals look like, and this aint it. | 05:34:28 |
 random8 joined the room. | 07:05:18 | |
| blogbourri | ok | 08:18:45 |
 philonmetal joined the room. | 09:06:46 | |
 Devin Hedge joined the room. | 10:34:26 | |
 papados | People who are not proficient in swe have no other means but post about their issues -- and I do get that. But if you have the tools (or in your case the experience) then by all means, do something practical about it. Its an open source project for a reason.. | 11:55:01 |
| papados | * People who are not proficient in swe have no other means but post about their issues -- and I do get that. But if you have the tools (or in your case the experience) then by all means, do something practical about it and contribute some code. Its an open source project for a reason.. | 12:23:20 |
 blueeee_dragoooonnn joined the room. | 13:44:39 | |
 _kaisd joined the room. | 16:32:48 | |
 b.l.t | A black hole of untouched bugs makes the confidence in one's contributions ever being merged less, not more | 18:24:24 |
| generalchaosdaemon | dont you wish they had written in something besides closure so it would be more accessible? makes me wonder if the problem is less difficult than I think ... because this might have been someone's side project | 18:43:09 |
| generalchaosdaemon | * dont you wish they had written in something besides closure so it would be more accessible? makes me wonder if the problem is less difficult than I think ... because this might have been someone's side project. I often think that I would love to fork it, but the whole closure issue is a showstopper. | 18:43:42 |
 tororutsu joined the room. | 21:35:35 | |
 @majestictwelve:mozilla.org left the room. | 23:06:44 | |
| 26 Apr 2024 | ||
 doommunky joined the room. | 00:15:05 | |
 android876 joined the room. | 02:00:34 | |