3 ms·
Serious response from Rails-land. Though this project is interesting, it's not really going to make much of a dent in my daily workflow. There is a metric shit
by alinajaf 14y ago
Serious response from Rails-land.
Though this project is interesting, it's not really going to make much of a dent in my daily workflow. There is a metric shit-ton of work being put into things that do. Over the past few years:
* The Rails queuing API (so you all queuing methods e.g. via Resque or DelayedJob have a common client interface).
* The asset pipeline (css/js concatenation + dependency management, plus precompilation for prod).
* Profoundly, bundler. I dread doing anything without having bundler there to declare, manage and allow me to browse the code of all my dependencies.
So yeah, the stuff that makes the news on HN isn't where the goodies are at in Rails.
> I've always felt the strength of the Python community is that it was able to let the idioms and cleanliness of Python stand for themselves while they advance of the state of the art for the work-a-day programmer.
:%s /Python/Rails/g<CR>
- heretohelp 14y agoRails volken: Do yourselves a favor, stop promoting stuff like this. It makes you look like Baby's First Web App. I'd seen the Resque/DelayedJob stuff. The equivalent in Python-land are Celery and Carrot. They're probably not much different. >* The asset pipeline (css/js concatenation + dependency management, plus precompilation for prod). Creating defaults for this stuff is definitely cool, but OTOH, it's something we solved at my company with a single bash script ;) >:%s /Python/Rails/g<CR> Vim user. Pffffft. ;) All hail the hypno-Emacs! >it's [action.io] not really going to make much of a dent in my daily workflow I would hope not. I would think most serious programmers have a pretty smooth/fine-tuned pipeline for "save file, run script, see changes in $SERVER(s)"
- alinajaf 14y ago> I'd seen the Resque/DelayedJob stuff. The equivalent in Python-land are Celery and Carrot. They're probably not much different. I'd expect as much. > Creating defaults for this stuff is definitely cool, but OTOH, it's something we solved at my company with a single bash script ; Good for you guys! That's going to be one hell of a bash script though, enjoy maintaining that. > Vim user. Pffffft. ;) All hail the hypno-Emacs! Err, OK.
- heretohelp 14y ago>Err, OK. No sense of humor? Oh right, HN. >Good for you guys! That's going to be one hell of a bash script though, enjoy maintaining that. Nope. Catenating files has been the privilege of Unix users since the 70s, that we would believe this to be difficult or complicated is embarrassing. The trickier part was sedding the query string that invalidates the old versions.
- alinajaf 14y ago> No sense of humor? Oh right, HN. I'll start laughing when you start being funny. > Nope. Catenating files has been the privilege of Unix users since the 70s, that we would believe this to be difficult or complicated is embarrassing. The trickier part was sedding the query string that invalidates the old versions. Ooooh! Colour me embarrassed, you got me there champ!
- heretohelp 14y agoLose the hostility man, it's not needed. What about rolling up assets seems so irreducibly complex that you want to rely on a shake-n-bake to get 'er done?
- RegEx 14y agoYou just need to learn the key to winning debates against other software devs: The first to snark wins!
- gkop 14y agoUsing the query string to bust cache and replacing your assets on deploy is the simple solution that Rails' asset pipeline replaces. Rails' asset pipeline doesn't delete old assets. That way you don't get inconsistencies when not all of your servers symlink to the new assets at the same moment.
- heretohelp 14y ago