6 ms·
Had the same response, but would have said "Django" not "Rails". Hardly matters tho. And htmx is worth exploring. As is HTML over the wire tools across various
by factorialboy 4y ago
Had the same response, but would have said "Django" not "Rails". Hardly matters tho.
And htmx is worth exploring. As is HTML over the wire tools across various languages.
- ilrwbwrkhv 4y ago100%
- drdaeman 4y agoSometimes it matters a lot. I'm a Pythonista who had to work with Rails just today (because I had to mend some Rails-based API project I had to interop with) and cussed a lot. Rails remind me of Perl's metaprogramming beauty (code is almost literature or even art) but also its worst sides (unique situational DSLs for everything and then some more, with TIMTOWTDI). It takes a lot of research to figure out where things are coming from because everyone seem to really love metaprogramming the whole kitchen sink, magically converting :symbols to ClassNames to autogenerated helped methods to generated attributes. And nothing is ever implicitly imported in the file you're looking at. Surely, it's all pretty simple after you learn how the particularly selected gem is used, but almost incomprehensible before you do. E.g. I just struggled for good 15 minutes before I learned that expose(:foo) is from a `decent_exposure` gem (and read that gem's source to understand how and why it does all its magics) - and there seem to be hundreds if not thousands of such gems in any sufficiently large and old Rails project. Oh, TIL that Rails doesn't implement If-Match at all (only If-None-Match for GET and HEAD through some Rack middleware). Every other toolkit I've used had something for that.
- willbudd 4y agoGood luck talking to cloud infrastructure such as Cognito-authorized AWS S3 buckets on the client side with a last century mindset like that.