News for hackers. Stuff that matters.
Re:Running GitHub on Rails 6.0 by StreamBright on Monday September 09, 2019 @04:50PM (#20922334)
I am pretty sure. If you developing the next Basecamp these are essential. However, I rarely see Rails succeeding in other aspects of web development. I spent some time on trying to make Rails work for use cases that are not the perfect match for this ecosystem and failed. Yet, it is quite possible that there are millions on web applications out there, running on Rails happily. It is just not a great fit for things I do.
Re:Running GitHub on Rails 6.0 by t0mbstone on Monday September 09, 2019 @05:33PM (#20922692)
And how, exactly, are you differentiating a "Basecamp-like" startup from a "non-Basecamp" startup?
Re:Running GitHub on Rails 6.0 by hderms on Monday September 09, 2019 @10:02PM (#20924494)
Basecamp's problems seem particularly well suited to a batteries included CRUD framework. There are plenty of problems out there that aren't CRUD-centric
Re:Running GitHub on Rails 6.0 by StreamBright on Tuesday September 10, 2019 @03:15AM (#20925803)
Exactly.
Re:Running GitHub on Rails 6.0 by StreamBright on Tuesday September 10, 2019 @03:15AM (#20925802)
non-Basecamp startups:

- processing images

- providing API for warehouse fulfilment for online retailers (peak load is 100x of base load, latency goes out of the roof before Rails just crashes with OOM)

- real estate indexing with huge amount of data (we could not make the full text search work reliably with Rails)

These were pre 6.0 and I am pretty sure many things changed since, I am just saying it is easy to run into these situations. The bigger your framework the more assumptions are built in that are hard to come by. It is good for Basecamp startups not good for non-Basecamp startups.

Re:Running GitHub on Rails 6.0 by t0mbstone on Tuesday September 10, 2019 @01:57PM (#20931134)
Image processing: Spin up sidekiq workers and do your image processing in parallel in background processes.

Providing API for warehouse fulfilment with peak load 100x greater than base: Run your Rails APP in any number of possible auto-scaling configurations.

Real Estate Full Text Indexing: Use ElasticSearch alongside Rails to provide highly performant full text indexing/searching

Re:Running GitHub on Rails 6.0 by StreamBright on Wednesday September 11, 2019 @02:38AM (#20937185)
Are you suggesting that there is more to it than just Rails and an amazing ecosystem? I agree.
Re:Running GitHub on Rails 6.0 by Lordarminius on Monday September 09, 2019 @05:13PM (#20922543)
I'd be interested in knowing what areas you found Rails lacking. Care to elaborate ?
Re:Running GitHub on Rails 6.0 by malloryerik on Monday September 09, 2019 @11:53PM (#20924899)
I might be wrong but aren't real-time areas like WebSockets not really strong points in Rails? I do see that Action Cable appears to have improved, and I don't know at what point performance issues would get in the way, and I also probably don't know about some potential solutions. Should one choose Rails for an application with significant real-time / reactive functionality?
Re:Running GitHub on Rails 6.0 by StreamBright on Tuesday September 10, 2019 @03:23AM (#20925847)
For me the most important one is performance and the lack of trust in my code (run time errors).

- https://blog.codinghorror.com/performance-is-a-feature/

- http://www.nicolas-hahn.com/python/go/rust/programming/2019/...

Re:Running GitHub on Rails 6.0 by gls2ro on Tuesday September 10, 2019 @11:09AM (#20929028)
I totally agree that app performance is important.

But I really think there is a difference between framework/programming language performance and acceptance-level app performance.

It is possible to have a good performance app (Github, Shopify ) even if you don't believe that Ruby is good enough in this category.