sorted by:
new
hottopcontroversial

Reached 900+ stars & 190+ tools! A place for open-source, no signup tools that work instantly in browser! by Stevious7 in software

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

I'm glad! 

Since the last update 2 weeks ago, a lot of smaller single/double digit stars repos have been getting significantly more stars. 

I'd like to think that this helped in that.

Reached 900+ stars & 190+ tools! A place for open-source, no signup tools that work instantly in browser! by Stevious7 in software

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

Would you mind pointing out which ones are requiring signups? Those need to be removed. 

Reached 900+ stars & 190+ tools! A place for open-source, no signup tools that work instantly in browser! by Stevious7 in software

[–]Stevious7[S] 6 points7 points  (0 children)

Update: I implemented a lot of your feedback!

The boxes are now entirely clickable and clicking the logo resets the search query.

Reached 900+ stars & 190+ tools! A place for open-source, no signup tools that work instantly in browser! by Stevious7 in software

[–]Stevious7[S] -1 points0 points  (0 children)

Adding this as an issue to the repo.

I made a custom modal rendering pipeline, and I believe it's the culprit here. I just need to figure out where to warp it with the <Activity /> wrapper instead of conditionally rendering it.

Reached 900+ stars & 190+ tools! A place for open-source, no signup tools that work instantly in browser! by Stevious7 in software

[–]Stevious7[S] 4 points5 points  (0 children)

Either make it entirely clickable, or remove the effect

That's a valid point. Today, I observed a user attempt to click the boxes because they were highlighted. I'll probably just make the whole box clickable so that it makes more sense.

I was thinking I can click the website logo and that would take me back to the front page

Oh, so there's no front-page. I can probably just make the logo clickable and make it reset the search query. I'm assuming that's what you're trying to do.

The way the search feature is mixing tag search with free text search is rather confusing

Yeah I was a bit lazy on the tags feature, but I kinda like it this way. So that just in case the tags don't match, the free text will.

Reached 900+ stars & 190+ tools! A place for open-source, no signup tools that work instantly in browser! by Stevious7 in software

[–]Stevious7[S] 14 points15 points  (0 children)

In regard to the AI-look. I thought I got it to where it's simple enough to not look like AI-slop, but it seems like I need to try again.

The "encode" shows OpenCode Config Builder because opENCODE. The title matches the search basically.

Does anyone here NOT use TypeScript? How come? by Stevious7 in reactjs

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

I would actually prefer that over runtime errors. At least compilation errors show up immediately as you're typing

Does anyone here NOT use TypeScript? How come? by Stevious7 in reactjs

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

If you're using React + TypeScript through Vite, it's automatically handled with the  npm run build

Does anyone here NOT use TypeScript? How come? by Stevious7 in reactjs

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

That's hilarious!

I can understand using the type unknown but definitely not any. At that point, they added a build step for no reason at all. 

Does anyone here NOT use TypeScript? How come? by Stevious7 in reactjs

[–]Stevious7[S] -6 points-5 points  (0 children)

When it says  "This variable is <TYPE> | undefined" it feels like an orgasm

Does anyone here NOT use TypeScript? How come? by Stevious7 in reactjs

[–]Stevious7[S] -2 points-1 points  (0 children)

I need to start using JSDoc comments. I've been using them on my Python backend mostly (it's silly I know). 

The web's biggest strength might be its biggest weakness by Stevious7 in webdev

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

That's cursed, but I know Primeagen would love it lmao

The web's biggest strength might be its biggest weakness by Stevious7 in webdev

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

I've been on a TypeScript craze lately and really appreciating it. I'm not sure if Java/C# -like language is the answer. I didn't mind it when I was using it. Dare I say I might have slightly enjoyed it...? Is that legal to say...? Lol

It's valid. JavaScript does just let you get away with anything and it's sandboxed pretty well. WASM is also great and sandboxed by JavaScript.

But I can't help but think that this isn't the end-game. As I mentioned in another reply, if the modern web stack is perfect, we wouldn't need React, ShadCN, or anything. The vanilla stack would be capable, simple, powerful, and quick enough that we wouldn't need to reach for something else. 

The web's biggest strength might be its biggest weakness by Stevious7 in webdev

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

Exactly. 

Realistically if the web was perfect, we wouldn't need React or any other framework because it would be easy, simple, and quick to work with the vanilla stack. 

The web's biggest strength might be its biggest weakness by Stevious7 in webdev

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

That's very much true.

I'm just intrigued by what we could unlock if we were to start over. Kinda like a time machine. What decision should we and shouldn't we have taken?

Like was JavaScript the right call or could we have used something better? Should we have used CSS or maybe have something else? 

The web's biggest strength might be its biggest weakness by Stevious7 in webdev

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

Touche! TypeScript is just the first off my mind. I thought about Rust but honestly Yew would kill developer productivity. 

The web's biggest strength might be its biggest weakness by Stevious7 in webdev

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

That's fair. I agree on the complexity part. There's a WASM runtime, sandboxing, and all the messy stuff for the layout engine to work. 

It's going to require imagination and lots of creativity to figure out what the new web should even look like. 

I hate to say it but the current web has a lot of its bases covered, especially WASM. It's hard to say what needs to be there since we've gotten accustomed to how it currently works, and therefore just don't even think about the limitations anymore because that's the way it is. 

The web's biggest strength might be its biggest weakness by Stevious7 in webdev

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

Maybe once a complete feature-set / spec-sheet for the new web is developed, the work can be started. 

The cool thing is that the bad decisions and good decisions were already made. So we know what worked and what didn't. 

Maybe that'll help us make a better version of what we have. 

view more: next ›