221–230 of 346 posts
Earlier quoted context omitted.
Not sure if that makes it a gateway, but some tools for iOS/macOS development use it: fastlane and cocoapods are the most prominent ones. It's a great scripting language and good to develop DSLs.
Ah yes! Homebrew, for example.
Earlier quoted context omitted.
I think Django comes close to Rails with regards to productivity. Granted, Django has slightly more overhead to get started, but Django also includes an admin interface and a built-in auth system, which Rails does not.
I work in a lot of Django shops and my Ruby is nowhere near as good as my Python but I'll pick Rails every time if I'm working on a side project. Why? Because the development velocity when using it is unparalleled. I can have an MVP up orders of magnitude quicker than I can with Django/Flask/Twisted. You're absolutely right on the Admin interface and auth, but auth is a gem install away [1] and Django's admin won't f…
They are.
Django Channels: https://www.djangoproject.com/weblog/2016/sep/09/channels-ad...
Earlier quoted context omitted.
An advantage of Celery is that it doesn't require payment for an enterprise version to add things like scheduled tasks.
If you're talking about Sidekiq there's free open source solutions for that in Rails world. https://github.com/moove-it/sidekiq-scheduler https://github.com/ondrejbartas/sidekiq-cron Besides Sidekiq is just one out of many.
Rails really nailed the problems of web development as it was 10 years ago by (rightly) pointing out that 97.2% of web projects were all about making an application server talk nicely to a relational database and then generating a front end that reflected the data model and that had javascript that Just Worked (everywhere). Web dev is in a different place now. Developers don't generally install and maintain applicati…
Rails is good for two things: Fast iterating and fast on-boarding new employees. If you want to start a startup, and you know Rails, use Rails with Postgres. Do the complicated shit (data science, video uploads, etc) in your other language if you have complicated shit. Use a different subdomain or get nginx to fork the endpoints for the complex shit if it needs to be public. I've known plenty of people, myself includ…
> I think it should be JSON-first, not HTML-first
Isn't that the case in Rails 5? https://guides.rubyonrails.org/5_0_release_notes.html#api-ap...
To me, every framework or web oriented language out there should have a big tutorial similar to https://railstutorial.org/book because it covers a lot of things regarding classic everyday web development which is extremely useful to beginners. So just for the existence of that book I'd say yeah, Rails is still relevant. There is also this one for flask which builds an web app from start to finish for people who like…
> I would keep learning plain Ruby, Elixir, Phoenix and JavaScript as my side tools > I wouldn’t spend too much time learning programming languages outside that list as you need more tools in your toolbox but too many tools may get your toolbox cluttered You suggest not cluttering your toolbox, but your recommendation is a list of completely interchangeable dynamic languages?
Javascript, Ruby, and Elixir are emphatically not interchangeable. Elixir is compiled, the other two are interpreted. JS is supported natively by all browsers and is at its core an event-driven functional language, the other two are not. Ruby is probably the comfiest OOP language out there, and certainly the one with the best standard library. These are not the same languages.
What does Ruby's standard library have that makes it superior to Python's?
Elixir doesn't really compete with Ruby. It may be technically superior, but will never supplant Ruby because it's just not very accessible, and the timing was bad. So it attracts different sorts of people. Same with Clojure, although they really, really tried.
Javascript is the opposite; it gained and held the popularity advantage early on, but is inferior to Ruby technically in painfully obvious ways.
Python is very close to Ruby technically, syntactically, and philosophically.
Earlier quoted context omitted.
I think he means "C++ in 2018" to build a standard webapp, which definitely is masochistic because you can be much more productive on e.g. Rails. Just like how using PHP to build a real-time graphics engine is also probably masochistic.
People who don't know say these things. Try writing web applications in C/C++, it's a deluxe development situation. Where do you think web browsers come from? Everyone afraid of C/C++ are shooting themselves in the feet.
Is the situation in C++ frameworks very far off?
Earlier quoted context omitted.
> These days if your chosen language doesn't have things like strong typing, interfaces, good debugging tools, a good compiler, etc, then you should definitely be asking yourself if it's the right tool for the job. All of these things existed long before Ruby on Rails gained in popularity. Unless the popularity of Rails, Python, PHP, and Javascript was all just collective insanity, dynamic languages do offer benefits…
> Unless the popularity of Rails, Python, PHP, and Javascript was all just collective insanity, dynamic languages do offer benefits in some circumstances over languages with stronger type guarantees. with strongly typed languages it's harder to perform exploratory coding. This drives a kind of backpressure on the design stage of development where it becomes more prudent to design your classes and interfaces before yo…
Quite the opposite. With strongly typed languages, it becomes safer to make changes, because the compiler will catch mistakes. On top of that, with mature strongly typed languages, there is tooling which takes advantage of the types to help you avoid mistakes in the first place.