Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rails for everything

literallythevoid.com

Post reply on HN
Print view View original

161–170 of 250 posts

Re: Rails for everything

#161

Post by rednafi »

iovrthoughtthis wrote: post #153
WuxiFingerHold wrote: post #108

Earlier quoted context omitted.

I was looking for a mature, complete and powerful statically typed stack as well. ASP.NET was my clear answer (not Go or Rust). There's a lot of noise coming from Microsoft to sell their new products (this year: Aspire.NET). But don't be mislead by this noise: .NET Core (C#, ASP.NET Minimal API or MVC, EF Core) is more batteries included and reliable than most other options. The only gripe I have is the need to get i…

c# (and the project i was working on) destroyed my love of programming

Microsoft Java

Re: Rails for everything

#162

Post by pjmlp »

rednafi wrote: post #47

Rails is awesome, and so is Django. I’ve built mission-critical apps in both and still do with Python. That said, I’d love to switch to Go for building large monoliths since it has a tighter type system and better concurrency constructs. The problem is, Go community has never really filled that gap. I love Go, but the whole "Go doesn’t need a Rails or Django" mindset is part of why it hasn’t taken off in this space.…

It isn't the anti-frameworks mindset, it is also the anti-modern-features mindset.

Java, Kotlin, Scala, C#, F#, OCaml, Haskell, D, are also much better for networking tools and CLI.

And nowadays people can't even complain the Java AOT options are commercial, or .NET is stuck on Windows.

Re: Rails for everything

#163

Post by pjmlp »

jilles wrote: post #14

If you replace the title with Django it still works. I’m doing the same as the author, but with Django.

Likewise I keep doing the same but with Spring and ASP.NET, depending on the project.

Re: Rails for everything

#164

Post by VeejayRampay »

Ruby and Ruby and Rails are really having a revival recently

I guess the work on performance and tooling has paid off and people are starting to realize that if python can have the spotlight then ruby (overall a better language) might deserve it too

Re: Rails for everything

#165

Post by anarwhal »

aantix wrote: post #125
nomilk wrote: post #76

> if you follow (the Rails Guides) start to finish, you'll have a Rails app in production. And it isn't just hello world. Your app will have authentication, caching, rich text, continuous integration, and a database. That's a real application. These features are great for established apps like GitHub and Airbnb, but if you're making a tiny startup, and want to test ideas quickly, I wouldn't spend time on CI, caching,…

If you're looking to build a SaaS app, start with a professionally curated Rails template. It will save you months of development time. Payments/Auth/etc are built in and there are solid patterns in place to extend from. Jumpstart Pro is great. https://jumpstartrails.com/ So is Bullet Train. https://bullettrain.co/

These are great recommendations, thank you! Gives me a reason to spin up a new project I've been musing about for a while in order to play with this

Re: Rails for everything

#166

Post by rednafi »

pjmlp wrote: post #162
rednafi wrote: post #47

Rails is awesome, and so is Django. I’ve built mission-critical apps in both and still do with Python. That said, I’d love to switch to Go for building large monoliths since it has a tighter type system and better concurrency constructs. The problem is, Go community has never really filled that gap. I love Go, but the whole "Go doesn’t need a Rails or Django" mindset is part of why it hasn’t taken off in this space.…

It isn't the anti-frameworks mindset, it is also the anti-modern-features mindset. Java, Kotlin, Scala, C#, F#, OCaml, Haskell, D, are also much better for networking tools and CLI. And nowadays people can't even complain the Java AOT options are commercial, or .NET is stuck on Windows.

> It isn't the anti-frameworks mindset, it is also the anti-modern-features mindset.

Touché!

> Java, Kotlin, Scala, C#, F#, OCaml, Haskell, D, are also much better for networking tools and CLI.

Maybe. But I wouldn't touch any CLI written in a Java, Kotlin or Microsoft Java with a 10-foot pole. YMMV.

Re: Rails for everything

#167

Post by pjmlp »

rednafi wrote: post #166
pjmlp wrote: post #162

Earlier quoted context omitted.

It isn't the anti-frameworks mindset, it is also the anti-modern-features mindset. Java, Kotlin, Scala, C#, F#, OCaml, Haskell, D, are also much better for networking tools and CLI. And nowadays people can't even complain the Java AOT options are commercial, or .NET is stuck on Windows.

> It isn't the anti-frameworks mindset, it is also the anti-modern-features mindset. Touché! > Java, Kotlin, Scala, C#, F#, OCaml, Haskell, D, are also much better for networking tools and CLI. Maybe. But I wouldn't touch any CLI written in a Java, Kotlin or Microsoft Java with a 10-foot pole. YMMV.

So you dump every executable before making use of it?

Re: Rails for everything

#168

Post by bluecheese452 »

dismalaf wrote: post #45
rich_sasha wrote: post #12

As someone who doesn't do enough web dev to justify learning Ruby just for Rails: how does it compare to Django? That's the only batteries-included web backend framework I'm familiar with... Asking out or curiosity.

Ruby doesn't really have a learning curve... Maybe block syntax but that's super easy. Rails gives you way more structure than Django.

Not my experience

Re: Rails for everything

#169

Post by bluecheese452 »

shortrounddev2 wrote: post #90
rglover wrote: post #38

> Rails is not dead; It's better than ever. Try using it to make something new this year. I hope as an industry we can move away from this "___ is dead" talk. The OP shouldn't even need to say this. If something is being worked on (in any capacity) and has at least one user, it isn't "dead." "Is it dead" is groupthink questioning that leads to great ideas being swept under the rug because they're not perceived as pop…

Many people choose what language to invest time in based on the labor market for that language. Companies shouldn't be so religious about the languages they use, but for small teams they usually pick one language for the entire company so that devs can hop between projects without any linguistic learning curve. Hence why there are so many Node + React companies out there; you hire a bunch of react bootcamp grads and…

I would suspect the same in any job.

Re: Rails for everything

#170

Post by mstipetic »

out_of_protocol wrote: post #152
peteforde wrote: post #147

Earlier quoted context omitted.

Kudos: I find this to be an exceptionally helpful and concise description of the Go meta. I would offer that Erlang did a good job of capturing the [concurrency?] space, though some of the tooling is showing its age. It's therefore interesting to see Elixir straddle the divide between Erlang and Ruby. I'm still Rails all day, but I've never stopped thinking Elixir is cool.

Well, i think Elixir/Phoenix is better Rails than real Rails - great developer experience (and developed by rails contributors)

Every time I step out of elixir I feel like I’m coding with some cumbersome construction gloves and everything is kinda coerced to work together. But for some reason it’s not picking up a lot of steam and the job situation is rough
Post reply on HN