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

What's new in Padrino 0.11 and 1.0

speakerdeck.com

Post reply on HN
Print view View original

11–20 of 20 posts

Re: What's new in Padrino 0.11 and 1.0

#13

Post by DAddYE »

Argorak wrote: post #10
diminish wrote: post #9

One more question; Could you name me some more reasons why I should use padrino 1.0/sinatra instead of rails for my next startup or client project? (I may reuse them with my team and clients). I am aware from your presentation of speed, non-opinionated aproach etc, but appreciate some more technical advantages/disadvantages for an HN discussion..

As someone who has multiple Padrino apps running at customer sites: - Almost nothing is activated without explicit choice (except security-related things and really default things, like sessions, mind you). This mitigates the risk of attacks that hit a component that you didn't implement without knowledge. See the XML-parsing attack on Rails (CVE-156) for that hit everyone, even if they were not conciously accepting…

I wouldn't able to explain better!

Re: What's new in Padrino 0.11 and 1.0

#15

Post by Argorak »

jacquesc wrote: post #14

Best feature of Padrino: multiple apps! https://speakerdeck.com/daddye/padrino-framework-0-dot-11-an... Having to deal with the jankiness of Rails engines on a daily basis (on a client project), this feature would have been a life saver.

So, you might either rejoice or be angry that we have a similar feature in the works. Currently, its for code-sharing only, not assets. See the discussion on how we address our personal pains with engines.

https://github.com/padrino/padrino-framework/pull/1007

Re: What's new in Padrino 0.11 and 1.0

#16

Post by jacquesc »

Argorak wrote: post #15
jacquesc wrote: post #14

Best feature of Padrino: multiple apps! https://speakerdeck.com/daddye/padrino-framework-0-dot-11-an... Having to deal with the jankiness of Rails engines on a daily basis (on a client project), this feature would have been a life saver.

So, you might either rejoice or be angry that we have a similar feature in the works. Currently, its for code-sharing only, not assets. See the discussion on how we address our personal pains with engines. https://github.com/padrino/padrino-framework/pull/1007

Rejoice of course! Would be really nice to still have the option of not wrapping of course, but distributing some apps via Gems is a nice feature too.

Re: What's new in Padrino 0.11 and 1.0

#17

Post by Argorak »

jacquesc wrote: post #16
Argorak wrote: post #15

Earlier quoted context omitted.

So, you might either rejoice or be angry that we have a similar feature in the works. Currently, its for code-sharing only, not assets. See the discussion on how we address our personal pains with engines. https://github.com/padrino/padrino-framework/pull/1007

Rejoice of course! Would be really nice to still have the option of not wrapping of course, but distributing some apps via Gems is a nice feature too.

No existing functionality was harmed in the making of this feature :).

Multiple apps are not going anywhere, especially because they are a very nice way of seperating things without the overhead of having a gem somewhere else that is hard to keep track of.

Actually, the initial commit didn't even touch any existing methods.

Re: What's new in Padrino 0.11 and 1.0

#18

Post by pekk »

diminish wrote: post #9

One more question; Could you name me some more reasons why I should use padrino 1.0/sinatra instead of rails for my next startup or client project? (I may reuse them with my team and clients). I am aware from your presentation of speed, non-opinionated aproach etc, but appreciate some more technical advantages/disadvantages for an HN discussion..

Why not make this decision on the basis of which way you prefer to build apps? That isn't technical enough?
Post reply on HN