Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Plane got to top spot in project management on GitHub in less than a year

plane.so

Post reply on HN
Print view View original

171–180 of 193 posts

Re: Plane got to top spot in project management on GitHub in less than a year

#171

Post by imhoguy »

dpoljak wrote: post #63
chx wrote: post #36

> See what 2,300+ folks in a forum get up to oh okay > Join our Discord sadness. where's the forum?

Its amazing to me that it has become such a default, similarly to Slack before it. At least some Slack communities tried and worked on getting the channels indexed so that it shows up during web searches, now with discord I need an account just to view the content... A hard pass from me, especially when an answer to a simple question requires me to drink from their firehose of a search...

Slack doesn't require phone number validation, Discord does. Try to login first time with FF on Linux and with uBlock Origin defaults and then pooof, insta ban! Guess what, your phone number is banned for validation too forever,

Re: Plane got to top spot in project management on GitHub in less than a year

#172

Post by IshKebab »

capableweb wrote: post #155
notlive wrote: post #104

The Plane codebase is a good read. If you want to see a well put together Django + Nextjs project you should check it out. There has been a lot of talk recently about what open source means. To completely side-step that discussion, I have plane starred on github because I learned a lot looking at their code without ever having run it or ever using the product.

I can't speak for the Python part (which another commentator also already did comment on), but I don't think the React part is anything to highlight as "code you should try to imitate". I just did a quick look, but it seems to suffer from common problems lots of UIs suffer from. Zero tests (unless I missed where they are located), even for things that doesn't even touch the DOM (like the "helpers"). Components filled…

IMHO UI tests are just too difficult to be worth bothering with in most situations.

Maybe AI will change that. But for now I think dev time is generally better invested in other ways of making code work properly, or just fixing bugs that have already been reported.

I know that sounds heretical.

Re: Plane got to top spot in project management on GitHub in less than a year

#173

Post by capableweb »

IshKebab wrote: post #172
capableweb wrote: post #155

Earlier quoted context omitted.

I can't speak for the Python part (which another commentator also already did comment on), but I don't think the React part is anything to highlight as "code you should try to imitate". I just did a quick look, but it seems to suffer from common problems lots of UIs suffer from. Zero tests (unless I missed where they are located), even for things that doesn't even touch the DOM (like the "helpers"). Components filled…

IMHO UI tests are just too difficult to be worth bothering with in most situations. Maybe AI will change that. But for now I think dev time is generally better invested in other ways of making code work properly, or just fixing bugs that have already been reported. I know that sounds heretical.

> IMHO UI tests are just too difficult to be worth bothering with in most situations.

Yes, that's because you're doing them wrong.

Don't mess around with the "golden master" testing (edit: seems the frontend ecosystem call that "Snapshot Testing" actually, but it's the same) you see bunch of projects do, that compare the old DOM vs the new DOM you accept/deny changes based on component render output. That's a waste of time and won't actually prevent bugs.

Instead, extract the logic-heavy parts out from your components, then put those under unit tests, like any other code you write.

Boom, easy to maintain, verifies your implementation and makes your UI easier and faster to refactor and build in the first place.

Re: Plane got to top spot in project management on GitHub in less than a year

#174

Post by alephnan »

guappa wrote: post #122
prepend wrote: post #50

Earlier quoted context omitted.

I read it as addressing the “who cares about stars” that I have whenever someone mentions stars. So it was like a developer saying “I know stars are a dumb and imperfect way to judge a project, but here’s what it is.” If they hadn’t written this I would think they put too much weight on what’s really not a very important measure.

If they hadn't mentioned stars we'd know they don't care. Now I'm almost certain they paid for them. There are several websites where it is possible to buy them.

9 months ago in this thread regarding fake GitHub stars, someone mentioned at the time that Discord was a better indicator. https://news.ycombinator.com/item?id=35208363

The fact that this blog post made sure to bring up their Discord engagement makes me think Discord is now also a negative signal

Re: Plane got to top spot in project management on GitHub in less than a year

#175

Post by whazor »

DrBazza wrote: post #119
luke-stanley wrote: post #43

Okay it's open source but self-hosting it is not straightforward. The repo's self-hosting doc link returns a 404. Then after manually finding https://docs.plane.so/self-hosting/self-hosting , I am warned that there is a dizzying array of 4 env files. I suppose they are in a tricky situation, in that while they want to stand out as open source, actually having people easily self-host it, is perhaps, not a goal that is…

Software installation, even for simple trials reminds me of this Stephen Hawking quote: "Someone told me that each equation I included in the book would halve the sales. I therefore resolved not to have any equations at all. In the end, however, I did put in one equation, Einstein's famous equation, E = mc squared. I hope that this will not scare off half of my potential readers." It just feels like that law can be a…

Some of these self hosted projects need five containers: frontend, backend, database, redis, and elasticsearch. Way too many if you ask me.

My preferred self hosted projects only need one container and has a embedded sqlite database. With the option to configure a external database.

Re: Plane got to top spot in project management on GitHub in less than a year

#176

Post by GauntletWizard »

whazor wrote: post #175
DrBazza wrote: post #119

Earlier quoted context omitted.

Software installation, even for simple trials reminds me of this Stephen Hawking quote: "Someone told me that each equation I included in the book would halve the sales. I therefore resolved not to have any equations at all. In the end, however, I did put in one equation, Einstein's famous equation, E = mc squared. I hope that this will not scare off half of my potential readers." It just feels like that law can be a…

Some of these self hosted projects need five containers: frontend, backend, database, redis, and elasticsearch. Way too many if you ask me. My preferred self hosted projects only need one container and has a embedded sqlite database. With the option to configure a external database.

Building an app that scales to enterprise size is hard. Building an app that does so while also scaling down to single-team size is hard. Every feature you build two backends for is one more thing to go wrong. Writing a sqlite backend for your redis usage, your search, etc... it's not insane, and it's a sign of good Faith, but it's not something that should be expected, either.

Re: Plane got to top spot in project management on GitHub in less than a year

#178

Post by tamimio »

GitHub stars are for bookmarking and most people add it and never open the repo again, I don’t know why it’s seen as some sort of an achievement or a successful IPO, it’s a bookmark, github should change it to a bookmark icon at this point.

Re: Plane got to top spot in project management on GitHub in less than a year

#179

Post by robluxus »

capableweb wrote: post #173
IshKebab wrote: post #172

Earlier quoted context omitted.

IMHO UI tests are just too difficult to be worth bothering with in most situations. Maybe AI will change that. But for now I think dev time is generally better invested in other ways of making code work properly, or just fixing bugs that have already been reported. I know that sounds heretical.

> IMHO UI tests are just too difficult to be worth bothering with in most situations. Yes, that's because you're doing them wrong. Don't mess around with the "golden master" testing (edit: seems the frontend ecosystem call that "Snapshot Testing" actually, but it's the same) you see bunch of projects do, that compare the old DOM vs the new DOM you accept/deny changes based on component render output. That's a waste o…

But then those are by definition not UI tests.

In an ideal world one might argue that everything testing-worthy (ie. the logic-heavy parts) is already factored out from the UI components but getting to that point either needs a good amount of foresight and discipline or some a lot of refactoring which is difficult to trust without existing UI tests...

Post reply on HN