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.
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.
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
> "Frankenstyle is a no-build, fully-responsive, value-driven, utility-first CSS Framework."
It feels like Tailwind but simpler and some interesting design choice. And style wise, it feels very close to shadcn but again, framework agnostic, no build approach.
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