jimmy2020

Interactive web apps.

Thanks for sharing the link. Appreciate your feedback. I'd like to point out that the site is not fully updated. The last release is not included in the demo yet but I'm working on it.

DFlex has an infinite transformation mechanism even between containers. So you can transform indefinitely and if you want you can enable committing to DOM which will trigger a custom reconciler built specifically for transformation. It's also not just for React, you can hook it with your JS framework.

Hi HN, DFlex author here. I built DFlex because I couldn't find a comprehensive solution for interactive apps. All existing solutions depend heavily on HTML5 drag and drop to achieve interactivity despite the fact that the standard implementation is not designed to turn the apps into an interactive ones. So I started from scratch, built the transformation mechanism, and implement a custom reconciler built specifically to deal with DOM transformation. It also has a concurrent registration to prevent any blocking event and reduce initial loading. I also tried to take care of browser painting and scripting time. It's still in development mode but I'm glad it's shared here. Happy to take any questions you have and I'd love to get your feedback.

should read this comment before reading the article

I know. But it's not just about the community it's more about the commitment and consistency.

Do you think React will survive without Meta?

Is Meta moving away from Jest or is it still used internally?

Does Meta contribute financially to the foundation?

This is why I love HN.

MIT is the best for everyone and best for you because it gives you flexibility when you have contributors

hey are serious?

Hi HN, I am glad DFlex is featured on Show projects. Happy to take any question you have about DFlex and its roadmap.

I don't know about you. But if I am using an open source project in my stack I prefer to star or support, better do both.

Hint: This is the culture I need github to promote. Giving back to the community.

cool still, why hiding it? I mean you can add bookmark this project feature instead of introducing the anonymous user.

> I never understood why stars are public in the first place.

We star because we like the code, the idea, the execution and the maybe the impact of the project. And it's encouragement. You star a project you pushing it forward. This is the human experience. We are not machines worshiping code. We care about what others think and this is why github is different.

> Of course instead of hiding the stars it might be better to add a private similar feature instead.

Agreed. Hiding means giving more space to anonymous users do we want that?

> I'm using GitHub to develop open source software.

Same. And i am not coding for myself i also need other to be part of what i am building and that's supposed to be part of the mission. Increase interactively. Instead this feature does the opposite.

agreed.

You could do it when enable hiding private contribution. This features actually enable anonymous users. I don't think it has anything to do with using the code privately.

Yes. Enable hiding the user activity but keep the user active. Imagine someone spamming some repository with issues and still can't be known or detected because it's anonymous now.

More privacy is always good but why it's important to hide what I am staring and what kind of GitHub repositories I like? It's anti transparent and against what's github is and has been for a while not just for hosting the code but for sharing the development experience. It feels more like we can ship this feature so let's do it.

How did you discover that they were part of a cult? They just invited you to a group discussion and you didn't go to know if it's a really cult or just a bunch of people meeting and making new friends.

I've migrated from yarn to pnpm two days ago and I can tell the difference when I first hit install. I am working on a workspace so I have multiple packages with nested dependencies. For this case, I thought yarn (the classic version) is the ideal solution that was until I discovered pnpm. Thanks to its non-flat algorithm the packages have clean dependencies. Previously in yarn if you install `foo` in any package you can reuse it later in the workspace even if it's not listed in the package dependency. With pnpm it's not the case, which means a clean dependency tree and serving the purpose of what's workspace is meant for. If you want to share the dependency you can install it in the root which makes sense to me. Another big advantage is the recursive/parallel command something I couldn't do without Lerna. And it's fast. install once and it's there in the disk, so if you manage multiple projects, dependency installation is not something you wait for it's just there.

I know but the same goes for Firebase. As matter of fact, Supabase started as an open-source replacement for Firebase.

It feels the CDN edge functions are the new Jamstack. It's fast but comes at a high cost and the excitement shifted from static pages to literally data distributed near the user.

I am curious how the edge functions can replace Firebase?

Thinking of accessible no-code application needs a robust drag and drop library not just capable of dragging and repositioning the DOM element but also comes with high performance. So I made DFlex (https://github.com/dflex-js/dflex) where the DOM tree stays untouched, with the same order but the elements change their positions with CSS transform only. That's done without changing the element position to Fixed or absolute. I've added some features recently to handle huge numbers of rows up to 1k elements but still, there's so much to do.

Yes I have the same problem

Patriarchal culture is so deep into their history but not to the point where you ban non-muscular men. Chinese regime recently considered the pop culture CIA attempt to make Chinese men less masculine.

"oh sorry you are not manly enough for today's news"

slim is pro-coup and our guy here is obviously against it. it makes the situation a little bit difficult.