menu

We need tester

Leader posted 1 min read

is there anyone would like to test our project ?

we accept any kind of comment like scathing review, critiques or something.

but we just hope you can try it .

13 Comments

•

i would love to.

2 votes
•

@[Nera_of_Web3]

Thank you Madam.

May I ask you some questions ?

What do you think of Vibe Coding?

And do you prefer vibe coding or building something with your hands?

1
•

@[Transpective Dev Team] I genuinely lean toward vibe coding it lets me move from idea to working prototype way faster but I think the magic is in the back-and-forth, because that's what turns a good first draft into something actually worth shipping.

2
•

@[Nera_of_Web3]

sorry Madam.

we forgot to send you our link.

https://github.com/transpective-dev/Ribbon

so sorry

2
•

@[Transpective Dev Team] no problems checking it out now

1
•

I would also like to test

2 votes
•

@[LegendsDaD]

Thanks! here is our link

https://github.com/transpective-dev/Ribbon

1
•

https://github.com/transpective-dev/Ribbon

I have visited the link, I like the idea you have presented, will properly test and put a feedback

1 vote
•

@[Gift Balogun]

Thanks!

1
•

I’d be happy to take a look and give you some honest feedback! Drop the link or DM me. Always down to test new tools and break things (respectfully, of course ).

2 votes
•

@[abarth23]

Thank you for the replying!

https://github.com/transpective-dev/Ribbon

1
•

@Transpective Dev Team

Here's my initial thoughts without spend too much time using it:

  • Solid core concept: The portability angle is generally useful since decoupling command macros from shell RC file is well, less than fun.
  • Safety rails: Incorporating an execution-guard as a first-class feature is great. You don't know that you need it until it's too late and having in place from the start is great positioning. However, I don't see a list of the "destructive keywords or patterns" as a separate, editable list. Is it configurable? Are there false-positives on legitimate commands?
  • Type slot system: Very interesting and thoughtful approach here.
  • Extensibility model: Clean approach of the distinction of scripts vs. commands.
  • Bun runtime: Having this as a hard dependency adds friction.
2 votes
•

@[Ken W. Alger]

You can set keywords in config.json.

I haven't provided a separate way to edit them yet because we are currently in beta. The first priority is to gather feedback on how people use it.

Thanks for trying it out! I will add an edit feature in a future update.

Regarding Bun, I'll add a detection system to switch between Node and Bun for users who prefer not to download extra dependencies. However, as you know, npx takes more time to launch, so Bun remains our top recommendation.

1

More Posts

TypeScript Complexity Has Finally Reached the Point of Total Absurdity

Karol Modelskiverified - Apr 23

Your Tech Stack Isn’t Your Ceiling. Your Story Is

Karol Modelskiverified - Apr 9

I’m a Senior Dev and I’ve Forgotten How to Think Without a Prompt

Karol Modelskiverified - Mar 19

Merancang Backend Bisnis ISP: API Pelanggan, Paket Internet, Invoice, dan Tiket Support

Masbadar - Mar 13

Comparison: Universal Import vs. Plaid/Yodlee

Pocket Portfolio - Mar 12
chevron_left

More From Transpective Dev Team

Looking tester for TS-script-scheduler software!

No more Task Scheduler! run your ts.script any time

now ribbon support launching by bun and npx!

Related Jobs

View all jobs →

Commenters (This Week)

4 comments
2 comments
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!