I've been asked to write an article for the #RakuLang advent calendar this year. I have a simple tutorial idea that I think will be good for beginners, and I swear to god I spent half the effing day yesterday fighting with ORM libraries and now I'm thinking "Fuck-it. I'll just write raw SQL."
Personally, I love SQL, but it feels kinda bullshit that that's where I ended up, and it's terrible for a beginner tutorial. Never-mind the fact that dramatically complicates the amount of code I'll need.
@masukomi yes, you are right, that’s the reason. I really need to find a way to fix that. But if you are not going to use Postgres (and you are going to use SQLite) you could install it with —force…
any python geeks wanna explain this to #unicorn thing to me (not a python geek) at like a super high level? what does it mean to have a full-stack framework for a framework that was already full-stack? Did Django succumb to the nodeJS virus like Rails did?
Is this bad marketing or is this a 2nd full stack framework on top of Django's full stack framework?