logsuck VS dflex

Interesting! I have it in the backlog that I want to support structured logging via JSON at some point. It's pretty far down the list right now though since I personally haven't used structured logging very much.

I added an issue about it: https://github.com/JackBister/logsuck/issues/7 - if you want to chip in with any comments or even help out with implementing it it'd be much welcomed!

I think it's a little bit beyond "half" baked, but I built a thing I call Logsuck last year: https://github.com/jackbister/logsuck

The idea is to have a free Splunk alternative which you can set up with just one binary. I use Splunk at work and love it, but it just doesn't seem like a product for solo developers (I can't even find a pricing page on splunk.com), and the primary free alternative, the ELK stack, seems a bit complicated to set up.

I am sure that I'll never be competitive with Splunk or Elastic in terms of features or scalability but I'm trying to build something that is at least useful for my own projects.

I built it in Go and use SQLite with the FTS (https://sqlite.org/fts3.html) extension to store the log events in a way where they can be searched quickly.

I built DFlex to push drag and drop capabilities further and handle complex interfaces at scale without compromises. The project is MIT licensed and open source on GitHub.

I'd love for you to check out the DFlex website to see examples and live demos. Let me know if you end up building something cool with DFlex! I'm always looking for feedback to help improve the library.

So I haven't tried it, but someone posted https://www.dflex.dev/ a few days ago, might be worse a look.

View on GitHub

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.

This is what I have been through while working on DFlex (https://github.com/dflex-js/dflex). 1- I want an open-source solution and free usage. 2- I want it to be sustainable. So I made a dual license. GPL with a commercial license. It's open-source with a paid option.

I'm working on DFlex: JavaScript Project to Manipulate DOM Elements (https://github.com/jalal246/dflex) Also, I'm looking for contributors! If anyone interested, please let me know.

I'm working on DFlex: JavaScript Project to Manipulate DOM Elements (https://github.com/jalal246/dflex)

Also, I'm looking for contributors! If anyone interested, please let me know.

I wrote about it here about why Dflex and how It's different: https://dev.to/jalal246/dflex-javascript-project-to-manipula...

The work is still in progress but can't achieve the desired outcomes without community support.

Obviously, you are :) considering you take a look at the source code.

I have another algorithm for connecting DOM nodes: https://github.com/jalal246/dflex/tree/master/packages/dom-g...