3 ms·

There are a lot of reasons someone might have made this: - They're a new developer, and this was a big accomplishment for them that they want to show off - Th

There are a lot of reasons someone might have made this: - They're a new developer, and this was a big accomplishment for them that they want to show off - They've built a few projects this way, identified the repetitive boilerplate code and extracted it into a library - They built a small app as a way to learn about Svelte and Three.js and want to get others' feedback - They're excited about Svelte or Three.js and want to show off what it can do (this is what actually happened, since the author is also the creator of Svelte) - They realize that other developers who aren't familiar with Svelte or Three.js may have trouble starting a project like this, so they wrote the plumbing code to help them It might seem to you that this code does "what any developer would do", but I assure you it's not. Everyone is different, and things that seem obvious to you may not be to others. I also want to comment on this: > Like, I honestly would assume that I would get laughed off of HN if I ever "made" something like this and passed it off as an accomplishment. But perhaps I am missing something crucial here... To be honest, I think the tone in your comment comes off as dismissive, and comments like this perpetuate the assumption that people have that they'll get laughed off HN if they show something like this. Ultimately the result is fewer people will show off stuff they make. And that sucks! The community should be a welcoming place that fosters others' enthusiasm. If this doesn't interest you, or you think it's too simple, you're always free to not upvote and not read. Obviously, a lot of other people do think this is interesting, because it made the front page.

beepbooptheory 5y ago
You are right I'm sorry to perpetuate anything bad. Thank you for your views and wisdom
- KronisLV 5y ago
  Actually, that felt like a very valid question on your part! A question that would be answered by a small intro for the project, like: "Svelte Cubed is a component library for building Three.js scene graphs in Svelte apps. It was built because of reasons X and Y, attempts to solve the W problem and in practice will make doing Z easier thanks to this." Perhaps a bit like their Getting Started guide, but with the missing reasoning for the project to exist: https://svelte-cubed.vercel.app/docs/getting-started https://svelte-cubed.vercel.app/docs/getting-started Similarly, the GitHub doesn't seem to have an extensive README or anything yet, either: https://github.com/rich-harris/svelte-cubed https://github.com/rich-harris/svelte-cubed While having docs of any sort is nice and should be encouraged, at the same time i often find myself wishing that more projects would summarize what they are, why they exist and what problems they solve, much like a lot of software packages do (or should do) in the app stores. Do other people not do that sort of stuff with their Git repos for projects, so that everyone can understand what they're looking at, at a glance? Here's a few examples from repos that were a part of my Master's degree: https://git.kronis.dev/rtu1/kvps5_masters_degree_covid_1984/blob/master/README.md https://git.kronis.dev/rtu1/kvps5_masters_degree_covid_1984/... https://git.kronis.dev/rtu1/kvps5_masters_degree_astolfo_cloud_servant/blob/master/README.md https://git.kronis.dev/rtu1/kvps5_masters_degree_astolfo_clo... (admittedly the repos themselves no longer are relevant, though should serve as an example of what i mean)

beepbooptheory 5y ago

You are right I'm sorry to perpetuate anything bad. Thank you for your views and wisdom

KronisLV 5y ago
Actually, that felt like a very valid question on your part! A question that would be answered by a small intro for the project, like: "Svelte Cubed is a component library for building Three.js scene graphs in Svelte apps. It was built because of reasons X and Y, attempts to solve the W problem and in practice will make doing Z easier thanks to this." Perhaps a bit like their Getting Started guide, but with the missing reasoning for the project to exist: https://svelte-cubed.vercel.app/docs/getting-started https://svelte-cubed.vercel.app/docs/getting-started Similarly, the GitHub doesn't seem to have an extensive README or anything yet, either: https://github.com/rich-harris/svelte-cubed https://github.com/rich-harris/svelte-cubed While having docs of any sort is nice and should be encouraged, at the same time i often find myself wishing that more projects would summarize what they are, why they exist and what problems they solve, much like a lot of software packages do (or should do) in the app stores. Do other people not do that sort of stuff with their Git repos for projects, so that everyone can understand what they're looking at, at a glance? Here's a few examples from repos that were a part of my Master's degree: https://git.kronis.dev/rtu1/kvps5_masters_degree_covid_1984/blob/master/README.md https://git.kronis.dev/rtu1/kvps5_masters_degree_covid_1984/... https://git.kronis.dev/rtu1/kvps5_masters_degree_astolfo_cloud_servant/blob/master/README.md https://git.kronis.dev/rtu1/kvps5_masters_degree_astolfo_clo... (admittedly the repos themselves no longer are relevant, though should serve as an example of what i mean)