Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

> It is also, indeed, early alpha and dealing with secret management for the owner and publisher are absolutely top of mind.

Awesome! Please keep building, for sure. :). Please just be bit careful about using security language in a way that people will misunderstand.



sort by: page size:

> One thing though: I hope the modding capability and freedom won't be diminished.

There was a video posted alongside with a lot of development interviews and one of them was very specific about mentioning they were creating a platform and they wanted to expose the framework they use to the community. Hopefully not just lip service but as far as signalling goes it was important enough for them to mention.


> I can say that early access builds will be available in a couple of months, and that I don't think it's too soon to take Loom into consideration if you're now planning a new long-term project.

That's great to hear. Can anyone contribute to the project to help out?


> Just starting our private alpha this week

I'm holding thumbs, I have been massively excited about your elevator pitch since your original announcement. Good luck!


> I thought the work with Lua was going well

The lua support is GREAT, and make a lot of complex stuff (standard outside authentication on multiple apps) simple as using a 20 lines lua script.

Let's hope LUA doesn't fall to second class citizen.


> I'm personally putting a LOT of effort to make our claims as accurate and truthful as possible, in every single place

Thank you. I understand in such an early irritation of a language there are going to be lots of bugs.

This seems like a very, very cool project and I really hope it or something like it is successful at making utilizing the GPU less cumbersome.


> Probably goes without saying, but this is definitely a beta project.

It indeed goes without saying, since you don't mention this on the site.


> Be aware that this project is still in an early alpha stage when it comes to software – its not an easy task to rewrite the whole Internet!

> about my language there's more info at https::/darklang.com.

I find it slightly reassuring that someone is actually working on a language/compiler with PaaS features built in. I'd thought of doing that and jotted it down in my notebook.. assuming it was just a crazy idea.

When do you plan to release an alpha version? I'd be interested in seeing it!


> Looks like a ton of hard work went into this and I think it comes across really well!

I thought the same. Too much for a lone developer!


> It seems a bit like a toy project right now.

Certainly not. However, I see how you might think that: the code base and design is deliberately small and readable. It's very far from being a toy, but it aims to be as auditable as a toy would be.


> We have code that has been in production for 20 years and as such has very few bugs left.

That seems optimistic!


> he is laying a good foundation (from what I have heard/read about his development process)

Could you please share some blog or resource to read a bit about his dev process myself? That stuff usually interests me, to improve my own process.


> releasing at such an early stage will make it hard to change anything when building up on this.

Why? Release early and get feedback. Backward compatibility isn't holy. And it's just an alpha. No one expects the api to be stable.


> I decided to open-source the version I built in September 2024.

I think this is the most impressive part!


> Wow, the future is here. In just 12 short years we made it to version 0.21.

I guess the next major release is going to blow your mind.


> I've also downloaded this software and my impression is that it is far far from 95% to be an outstanding product.

I couldn't parse that. Is this good or bad?

> At least I bumped into small ui bugs the author should catched himself before a release.

If you can point these out we can fix them. I'm still working on fit and finish in some places and rapidly iterating. I'm pushing 1/2 builds a week now based on user feedback so if something is broken let me know and I'll fix it :)


> Yes. Why wouldn't it be sandboxed?!

Famous last words.


> Any plans about how to develop and/or maintain this in the future?

Yes, I plan to continue developing and supporting it although I don't think I'll add too many features since I try to keep it focused.

> Is this anyhow involved in a commercial operation, i.e., where you or other devs can get paid to invest some (maintenance) work into it?

Yes, I use it professionally and can use some paid time to work on it. One of the reasons to post it here was to get some other devs eyes on it and to make it easier to bring on new hires by hopefully building a small community.


> Feels like unbaked software to me.

I mean... it is. A few weeks ago the user base was very small and there was very little activity on Github (bug reports, feature requests, additional developers). Now there is a flourishing community and a lot of pull requests from new developers, leading to many smaller and bigger improvements.

The timing could've been better as the Lemmy devs were in the middle of a bigger refactoring (getting rid of websockets), which hindered development and the release of new versions. But I for once are happy with how active the development is.

next

Legal | privacy