HN user

yashasolutions

297 karma

I build things on the internet

Posts4
Comments147
View on HN

I have found some nice middle ground with Frankenstyle [0] framework which take some inspiration from Tailwind (and Shadcn) but with no-build, which is the thing that I found really annoying with Tailwind. CSS with a build process is already not css anymore. But I understand the feeling of OP to want a cleaner code - without sparkling style details all over the html, though overtime I do feel it really gets out of hand and in the end having the styling in the html makes it less complexity to manage which class is where.

[0] https://franken.style/

Creating a nuisance is not a good way to go about it.

Some security practices sometimes feels like someone stabbing you just to prove you could be stabbed. Then they point at the wound and say: "See? You should be more careful."

Yes, the risk is real, but creating harm to demonstrate it isnt the same as protecting people.

That's an interesting perspective, and it does expand how we can interpret the Milgram experiment

That said the study has been replicated many times since the original, with researchers adjusting different parameters like participant screening, changing the gender balance, or varying the roles (teacher/student, researcher/technician...) Across these variations, the overall result stays quite consistent: under certain conditions, ordinary people can be led to do harmful things.

Other experiments have also looked at which factors make this more likely, and for example, diffusing responsibility seems to be one of the most effective ones.

Kagi Small Web 4 months ago

StumbleUpon is that you?

Jokes aside, it's really nice and I can totally see becoming addictive. Kudos to Kagi team for an other user oriented product. (as a side note, I am using Kagi daily and i didn't know about this tool)

Nice. Probably worth making a local copy before it gets taken down.

(Re: legal - why even bother with a court decision when it’s on GitHub? A takedown is much simpler. We've seen this before, like when Meta went after people reverse-engineering their API)

That said there may not be much here thats actually protectable. It's mostly a CLI orchestrating other tools, and the same functionality could likely be reproduced fairly easily, especially with AI.

Still, props to him for writing a proper blog post and explaining the process

"you won't be continually paying for access to this growing software library."

Well... the apple used to be sweet and has turn pretty sour with the years...

it is not - just a way to position design and untie it from the visual output that is also called design. Design thinking will not make you a logo (but a logo designer could pretty much do design thinking...)

I like the design, it's fresh and have good visual hierarchy (cool be improved in place but overall very nice). The content is fine for a first iteration I suppose. The tone is a bit aggressive sometime, I get you want to give a NO-BS focused mindset but maybe a tad over doing it. Also visually I think you could make more use the monetization impact of the game decisions - maybe that would help with "focused" branding without having to resort a condescending tone in some places. You probably will want a bit more nuance - businesses have multiple growth path and there isn't just once recipe for things but tradeoff are real and choices have impact - it is more important to understand the impacts of the tradeoff that to be locked in on some mantras. But again, all these are improvements that you will probably navigate yourself :)

the service business that will get fast turn over repair for a business to pay the premium they pay to levono/ibm isn't that easy to do. But yeah, I am sure they could create an ecosystem of reparability that would increase their sales

I have tried to use exclusively each of the libraries to better understand their limit, overtime I got to the following observations:

- htmx is more straightforward (because a lot of the magic basically happening in the backend) and helps a lot to keep some sanity.

- Alpine shines when you need more composition or reactivity in the frontend. But it gets verbose quickly. When you feel you are reimplementing the web, it means you went too far.

For pagination, page structure, big tables, confirmation after post etc. I usually go with htmx. Modals, complex form composition (especially when you need to populate dropdowns from differents APIs), fancy animations, I prefer Alpine. (I probably could do that with htmx and wrapping it in a backend - but often more flexible in the frontend directly.)

To me, the main reason why I use these libraries, is what I write today will still be valid in 5 years without having to re-write the whole thing, and it matters since I have to maintain most of what I write.

I have seen people rewrite entire application from React to htmx. It works. But the architecture required is a tad different. Also you need Alpine as a complementary library for the reactive parts. (I mean you could do a lot just with htmx but I find Alpine more convenient in many places when I need to work with json - since I don't control all backend and json isn't really a first class citizen of htmx)

nice! I would love some insights how you identify the the meaningful clips (how to explain to the LLM what meaningful mean for a given content) - I have to build a similar tool internally and that's the question I am trying to find a good answer to right now.

Regarding your UI, it's nice. I would suggest adding some basic control for audio level in the player. Else. adding some search bar with auto complete or suggested query can make the interface more engaging for new users and more practical for returning users.

Then next level, you can try to make TikTok for audio with scrollable vertical view and animated audio waves (listening to audio while seeing something nice is a good way to hook people in) and generated subtitles. Viewing the text from what you're listening increases focus.

Yeah, same here. I’ve got to the stage where what I write is mostly just for myself as a reminder, or to share one-to-one with people I work with. It’s usually easier to put it in a blog post than spend an hour explaining it in a meeting anyway. Given the state of the internet these days, that’s probably all you can really expect from blogging.

Pretty neat. I use Emacs a lot, and also do quite a bit of video trimming. For people wondering "why Emacs?", here’s the use case: trimming video is mostly about writing down start/end times, sometimes with a note. That’s all text.

If you can turn that text directly into clips without switching to a separate video editor, it’s surprisingly efficient. Of course, this only makes sense if you already live in Emacs, then it reduces context switching, helps to keep the flow. If you don’t, it just looks odd. But it’s not about making a meme out of "doing everything in Emacs" - it is just a small tool that fits the workflow of people who are already in that environment.

Love nyxt - I am just waiting for when I will be able to use sites like youtube with it (or other common site just not compatible yet with the web engine.) They have a road map to move to Blink/Chromium which would make the site compatible with today's modern web.