A _very_ intriguing resource! A little outdated, but still super fun to read
All the Ways to Make a Web Component - Feb 2022 Update
Compare coding style, bundle size and performance of 61 different ways to make a Web Component.
Looked at TeamSpeak today. Man has it fallen from grace. Like, a lot. xD
wai u broken? :< image
So I just spent some (WAY too much...) time looking at the Yii 1.x API (.../framework/base) and it's components and thinking how I would do those in Go. Some of the interfaces are almost straight copies, but some of the actual components - like CCache, IUserIdentity, IWebUser - are a little different. So instead of doing _everything_ myself, I went and looked at AuthBoss and some other libraries. Honestly, having sat here for a while now, it isn't actually unthinkable to do this...which is SHOCKING. xD At least to me...lemme hab mah lil world. uwu So I think I will just ... do it. Yii, on the frontpage, reads as "Yes, it is!" - so my version is nii: "No, it isn't!". - No, it isn't a good idea to write a Go application this way... - No, it isn't a modern approach to things - it's literally MVCC from 2010... - No, it isn't the most performant; in fact, it might be genuenly slow especially on startup since I use reflect to build the router off of your controller's Action*()-methods, kebab-casing them and going from there. Its nasty, okay. xD - No, it isn't going to change the world. Although I use components with either a good reputation or ongoing maintenance, it is a hobby project and a stupid one ontop. - No, it isn't for everyone. This is largely for the idiots - of which I am one, mind you - that could never mentally move on/out of the bubble they were in. If you liked MVC, then you might like this project. Using templ, htmx and a few other tricks, I plan on leaning on the Yii 1.x API in parts, but change it into proper Go-isms where it makes sense (return error instead of bool in many instances). Oh and you bet I am making sure there is a Nostr integration somewhere in this LMAO XD I am just dicking around...but, also, kinda not. I want to see how far this can go, or if it even should go. But here I am - partially stuck in the past, partially excited about the future and somewhere inbetween a giganerd who's just like, "amma do it cuz uwu" XD
So as it turns out, the guys behind the Yii framework support 1.x still - and it has 8.x compatibility. what.... o_o This is breaking me, on so many levels. What the hell.
GitHub
GitHub - yiisoft/yii: Yii PHP Framework 1.1.x
Yii PHP Framework 1.1.x. Contribute to yiisoft/yii development by creating an account on GitHub.
 <- NOT archived, and check the issues, people are using it on 8.3! My mind is broken.
...FactoryInterface? yeah, yii3 lost me. xD
GitHub
GitHub - yiisoft/rbac: Role based access control
Role based access control. Contribute to yiisoft/rbac development by creating an account on GitHub.
BRUH YII IS ACTUALLY STILL ALIVE WHAT THE FUCK???
Yii Framework
Yii Framework
fuckfuckfuckfuckfuck I am reading Yii 1.x docs again and not just do I see where I had oversights back in the days about the things I did... No, I am realizing that using gorilla/mux, I could feasibly re-implement certain things from Yii, in Go. xD Oh god help me I can't stop thinking about this. I might just commit and do it and never EVER use it - because it sounds so wrong ...but it feels so good... aaaaaaa X-X