Ruby on Rails

Be kind to your elders. I built my first site for money for an ad agency in 1997. That was 21 years ago. It was entirely static HTML except for a CGI contact form and some sort of "interactive quiz" thing that was meant to siphon in the clients. Tons of inline JS rollovers, because we were very modern. At home I had a 56K modem, to be sure, but at work we had a T1.

Walter

> On Nov 14, 2018, at 8:54 PM, Joe Guerra <jguerra@jginfosys.com> wrote:
>
> what kind of websites were you developing 16 years ago?  where did you connect using a dial up modem? 56k?
>
>
> On Wednesday, November 14, 2018 at 8:10:28 PM UTC-5, Stefan Buhrmester wrote:
> I've been a professional web developer for 16 years now. "Professional" as in "receiving money for pushing buttons on the computer with a varying degree of purposefulness".
>
> After 3 years of working exclusively with nodejs on the server- as well the client side, I landed a Rails job again. And I have to say one thing: Nothing, and I mean NOTHING could separate me from the Ruby and Rails community EVER again. The Ruby and Rails communities are the most welcoming, loving people you will ever find. The only likewise welcoming community in the javascript world (in my opinion) is the Vue / Nuxt.js community. And with webpacker, you can now have literally the best of both worlds.
>
> Also, using ActiveRecord on the backend is still second-to-none in terms of ease of use. Good luck with ACID guarantees in all these NoSQL databases and transactions entangled in a labyrinth of asynchronous javascript.
>
> What I want to say is: I love Rails.
>
>
> On Wed, Nov 14, 2018 at 3:55 PM Jack Waugh <jv2a9...@snkmail.com> wrote:
> It's late 2018. Is Ruby still what managers are turning to for significant numbers of new web projects?
>
> Are there sets of requirements that are so simple, that almost everyone with any experience would choose some other stack not involving the Ruby language? E. g. a web site requiring a CMS and a 'blog and little to nothing in the way of custom tables?
>
> I'm not experienced with many kinds of projects on the Web, and so I have this maybe naive thought that with nodejs, at least people can use the same syntax for code that runs on the server and code that runs in the browser. Doesn't having that single syntax reduce the intellectual burden somewhat? If Ruby is still getting a lot of traction for new projects, what are said to be the benefits that outweigh the drawback of using two languages and so having to keep mentally changing gears?
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
> To post to this group, send email to rubyonra...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/b40750b4-8136-4f27-931e-c75950b5e9d5%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/a2e48076-2986-4f1e-856c-e0580d42375f%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/A54F9BC1-F7B1-4DF4-93EF-4C0C4BCB3F5D%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.