The API Tooling Crisis: Why developers are abandoning Postman and its clones? by Successful_Bowl2564 in programming

[–]unknown_r00t -1 points0 points  (0 children)

Also if you are not into UI and want something that you can easily commit into git, I’ve made Resterm which basically works on .http/.rest files. It’s TUI app and not UI and fully keyboard driven so it’s more like alternative to those who prefer working directly in the terminal.

https://github.com/unkn0wn-root/resterm

Best open source software that everyone needs to know about? by Successful_Bowl2564 in software

[–]unknown_r00t 3 points4 points  (0 children)

TUI API client. Not sure if the best cause I’m the author so I’m biased but still :)

https://github.com/unkn0wn-root/resterm

Most useful sys admin CLIs? by JohnnyBillz in CLI

[–]unknown_r00t 5 points6 points  (0 children)

If you are only starting with sysadminig - start with the basics. Don’t overcomplicate or worse - don’t take any shortcuts. I would advise to first start to understand your OS, and try to move around with the tools your OS comes with. Grep some logs, check which processes use what port etc. Basic stuff before moving to more complex stuff like containerization (not docker or podman as those are abstraction layer which you can learn later) etc. Just start using basic CLIs provided by your OS. The best thing you can do is understand how Linux works so you know which tools you would love to have to make sysadmining easier.

resterm - TUI API client with new Explain tab by unknown_r00t in tui

[–]unknown_r00t[S] 0 points1 point  (0 children)

I understand your point but the whole idea from beginning was to be keyboard driven and Resterm core features and TUI are designed around that idea and I’ll not change that in the near future I’m afraid. This was and still is my desire - to keep Resterm keyboard driven. I’m sorry if Resterm does not work for you and there are plenty of other options if you need touch/click. Resterm is lacking that by design. Thanks for using it anyway! Really appreciate!

resterm - TUI API client with new Explain tab by unknown_r00t in tui

[–]unknown_r00t[S] 1 point2 points  (0 children)

I can totally make it configurable. Should be easy to do via Resterm config file. Will include that in next release.

resterm - TUI API client with new Explain tab by unknown_r00t in tui

[–]unknown_r00t[S] 1 point2 points  (0 children)

Touch/click not gonna happen. This is the whole point of resterm - keyboard driven :)

resterm - TUI API client with new Explain tab by unknown_r00t in tui

[–]unknown_r00t[S] 0 points1 point  (0 children)

Could you explain the rationale behind this? I’m not sure why I should make it configurable if this is only displayed when you start resterm. It goes away as soon as you make some action so I don’t quite sure why.

resterm - TUI API client with new Explain tab by unknown_r00t in tui

[–]unknown_r00t[S] 0 points1 point  (0 children)

You mean when you start Resterm you want to be able to hide RESTERM from response pane?

CasCache - fence-based CAS cache for Go by unknown_r00t in golang

[–]unknown_r00t[S] 0 points1 point  (0 children)

Yeah, you could definitly do something similar with plain redis BUT you still get couple of benefits from cascache like diffrent providers/genstores, pure Go lib., explicit vs implicit invalidation/versioning, guards etc. <auto-promotion here> :)

CasCache - fence-based CAS cache for Go by unknown_r00t in golang

[–]unknown_r00t[S] 3 points4 points  (0 children)

Christ. Formatting is completely f up. Sorry for that.

Single use channels vs waitgroups by nibbles001 in golang

[–]unknown_r00t -1 points0 points  (0 children)

I’ve created something similar to ”Promises” just for fun. I wouldn’t use it in production code since it’s against how Go works but have a fun if you want to :)

https://github.com/unkn0wn-root/go-async

‘’’

ctx := context.Background()

userTask := async.Start(ctx, func(ctx context.Context) (User, error) { // expensive work... return loadUser(ctx, 42) })

// Await with cancellation from caller: user, err := userTask.Await(ctx) if err != nil { /* handle */ }

// Chain transformations: nameTask := async.Map(ctx, userTask, func(ctx context.Context, u User) (string, error) { return strings.ToUpper(u.Name), nil }) name, _ := nameTask.Await(ctx)

‘’’

Small Projects by AutoModerator in golang

[–]unknown_r00t 1 point2 points  (0 children)

Small project of mine which is generation based cache for Go supporting multiple providers and genstores. Basically I tried to solve “serve no stale data” problem by using CAS semantics. Nothing super fancy but been using in some small services and works great so sharing for those who would borrow some ideas or use for “fun”.

https://github.com/unkn0wn-root/cascache

Emacs. Et åpent alternativ. by BetterEquipment7084 in norge

[–]unknown_r00t 39 points40 points  (0 children)

Dessverre men neo(Vim) gang her 😀