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

Ruby Web Dev The Other Way

rwdtow.stdout.in

Post reply on HN
Print view View original

21–30 of 65 posts

Re: Ruby Web Dev The Other Way

#21

Post by andrei_says_ »

onetwotree wrote: post #9

Good work! On some work projects I've gotten a lot of mileage out of breaking with the traditional Rails patterns in favor of stuff like `Operation` objects. Too bad I didn't know about Trailblazer! I also agree about Rails making excessive use of Ruby magic. Just because it's possible, doesn't mean you should do it. Regarding non-ActiveRecord models, I use Sequel[1] exclusively at work - in addition to being decided…

Do you have experience of using sequel with rails 5?

Also, what do you use for authentication?

Re: Ruby Web Dev The Other Way

#22

Post by angersock »

heartbreak wrote: post #18
angersock wrote: post #11

The mention and link to Elixir scares me. Please, don't bring your ghetto over here. Keep your unwashed masses to yourself.

Your user page claims you're an 'all around cheerful human being', but this comment has determined that to be a lie.

How do you figure?

One of the keys to cheerfulness is valuing your own experience and in seeing the world as it is, faults and all.

My experience has been that a lot of stuff in the Ruby/Rails (and the Node ecosystem, a thousand times worse) ecosystem is due to well-meaning novices cranking out ever-so-slightly different iterations on the same ideas, cluttering up the package managers with not-quite-right solutions.

That, and a pervasive attitude of convention-over-configuration and self-aggrandizing that tends to place an emphasis on popularity over talent, and on talent over restraint.

I remain cheerful because that culture hasn't yet infected the Elixir community.

Re: Ruby Web Dev The Other Way

#23

Post by onetwotree »

andrei_says_ wrote: post #21
onetwotree wrote: post #9

Good work! On some work projects I've gotten a lot of mileage out of breaking with the traditional Rails patterns in favor of stuff like `Operation` objects. Too bad I didn't know about Trailblazer! I also agree about Rails making excessive use of Ruby magic. Just because it's possible, doesn't mean you should do it. Regarding non-ActiveRecord models, I use Sequel[1] exclusively at work - in addition to being decided…

Do you have experience of using sequel with rails 5? Also, what do you use for authentication?

I don't have experience with Sequel and rails 5 specifically. The thing is, models are really not very coupled to rails. We don't have to do anything special to use Sequel models - it has good support for Rails migrations and everything.

Regarding authentication, my company makes authorization and access control software, so authentication isn't something we just toss a plugin at.

Re: Ruby Web Dev The Other Way

#24

Post by crazydoggers »

begin minor rant...

Occam's razor is misused in the manifesto. The author indicates that it means "Prefer simple solutions", which it doesn't.

Occam's razor requires a hypothesis, and generally means "Among competing hypotheses, the one with the fewest assumptions should be selected".

For example, Special Relativity is exceedingly complex, especially if I try to explain it to you. Ontologically though (in actual fact), it's the "simplest" solution to explain the real world data that the speed of light is fixed regardless of reference frame. I could come up with other theories to explain the data that might be "simpler" in explanation, but they require more and more assumptions to be made about the real world. For example, I could say that the speed of light is fixed because aliens cause all of our testing apparatus to show the same reading. For sure, that's a much simpler explanation than explaining Special Relativity. But it rests on a whole huge number of assumptions (like aliens existing, that the aliens want to mess with us, that they have the capability of doing so, etc, etc). So here Occam's razor favors the more complex theory because it makes fewer assumptions.

So saying that something is better because it's simpler and then justifying it with Occam's razor is really an abuse of the concept.

... end rant

Re: Ruby Web Dev The Other Way

#25

Post by desireco42 »

I really love and understand a lot of choices here. I didn't realize that mindshare behind Hanami/Trailblazer is so big, this is excellent news.

I am a little confused on editor suggestion, but this is geared to starting devs. I would say SublimeText all the way. Next step, obviously Vim.

Re: Ruby Web Dev The Other Way

#26

Post by andrew_wc_brown »

I don't know whats wrong with vanilla rails. The most I have to do to organize large projects is used concerns.

For better performance I serve up json directly from Postgres.

All these additional abstractions makes it hard to migrate away later to another platform.

Re: Ruby Web Dev The Other Way

#27

Post by JonnieCache »

andrei_says_ wrote: post #21
onetwotree wrote: post #9

Good work! On some work projects I've gotten a lot of mileage out of breaking with the traditional Rails patterns in favor of stuff like `Operation` objects. Too bad I didn't know about Trailblazer! I also agree about Rails making excessive use of Ruby magic. Just because it's possible, doesn't mean you should do it. Regarding non-ActiveRecord models, I use Sequel[1] exclusively at work - in addition to being decided…

Do you have experience of using sequel with rails 5? Also, what do you use for authentication?

There's a plugin for Sequel::Model that provides ActiveModel compatibility, which should make it work with the usual rails gems.

http://sequel.jeremyevans.net/rdoc-plugins/classes/Sequel/Pl...

Sequel is my favourite of the tools I use.

Re: Ruby Web Dev The Other Way

#28

Post by iJackUA »

desireco42 wrote: post #25

I really love and understand a lot of choices here. I didn't realize that mindshare behind Hanami/Trailblazer is so big, this is excellent news. I am a little confused on editor suggestion, but this is geared to starting devs. I would say SublimeText all the way. Next step, obviously Vim.

Try to use Trailblazer. Even if you would not adopt it entirely - it is really a great way to broaden your perspective. An Editor is solely personal taste.

Re: Ruby Web Dev The Other Way

#29

Post by pvg »

crazydoggers wrote: post #24

begin minor rant... Occam's razor is misused in the manifesto. The author indicates that it means "Prefer simple solutions", which it doesn't. Occam's razor requires a hypothesis, and generally means "Among competing hypotheses, the one with the fewest assumptions should be selected". For example, Special Relativity is exceedingly complex, especially if I try to explain it to you. Ontologically though (in actual fact…

This is a pretty poor example since Special Relativity is not 'exceedingly complex' and as a theory that explains things observed in the real world it's drastically simpler than a theory postulating unobserved aliens.

Re: Ruby Web Dev The Other Way

#30

Post by ben_jones »

Let's be real RoR is not about learning, or perfect engineering, or being easy to learn. It is 100% about being productive in industry.

"Put this file in this folder with this name and your app will do x".

"Why?"

"Because 10 years ago this file structure made a lot more sense and some people liked it so we stuck with it".

Post reply on HN