Swifton: Ruby on Rails-inspired web framework for Swift
1–10 of 74 posts
Re: Swifton: Ruby on Rails-inspired web framework for Swift
#2So many of these now. I wonder which one will eventually become the node of Swift.
Re: Swifton: Ruby on Rails-inspired web framework for Swift
#3You could have made it better by using protocols for the actions. So the methods for adding routes would ensure that the methods for new and update exists using a where clause checking protocol conformance.
There is potential here, I like a "full" package like "Omakase", granted its built using Swifts strength and a pipeline model like Express.js and/or Rails and its rack middlewares.
Re: Swifton: Ruby on Rails-inspired web framework for Swift
#4It seems that, outside of what's used in Cocoa, the Swift language is pretty volatile right now. I would hesitate to commit to a large project that didn't involve the App Store.
Re: Swifton: Ruby on Rails-inspired web framework for Swift
#5So many of these now. I wonder which one will eventually become the node of Swift.
Not which; if any, I think.
Node's tight coupling to JavaScript seems like more of an exception than a rule — look at Java, Ruby, Python, etc.
Re: Swifton: Ruby on Rails-inspired web framework for Swift
#6You could have made it better by using protocols for the actions. So the methods for adding routes would ensure that the methods for new and update exists using a where clause checking protocol conformance. There is potential here, I like a "full" package like "Omakase", granted its built using Swifts strength and a pipeline model like Express.js and/or Rails and its rack middlewares.
Seivan, thanks. Yes, Rails "Omakase" is driving Swifton development.
I'm not sure that protocols will help here, because Swifton supports before/after filter. Could you explain more your idea about how protocols could help here to implement actions with filters?
Re: Swifton: Ruby on Rails-inspired web framework for Swift
#7You could have made it better by using protocols for the actions. So the methods for adding routes would ensure that the methods for new and update exists using a where clause checking protocol conformance. There is potential here, I like a "full" package like "Omakase", granted its built using Swifts strength and a pipeline model like Express.js and/or Rails and its rack middlewares.
Seivan, thanks. Yes, Rails "Omakase" is driving Swifton development. I'm not sure that protocols will help here, because Swifton supports before/after filter. Could you explain more your idea about how protocols could help here to implement actions with filters?
What do you mean by Rails Omakase? All I could find is a blog post by DHH saying that "Rails is Omakase." Is there more to it than that?
Re: Swifton: Ruby on Rails-inspired web framework for Swift
#8Seems to me like the real challenge in those framework (excepting performance, of course) will be in the orm component. Having a library that can query a db in a typesafe way is a must.
Another will be in the concurrency patterns ( promises ? Coroutines ?, etc).
But i get a great hope that they will succeed. Having a strong open source community will help. In fact, i'm so fed up with the sad state of uikit right now, that i see a brighter future for swift on the server side than on the client. Maybe an android sdk for swift would be a great idea...
Re: Swifton: Ruby on Rails-inspired web framework for Swift
#9Earlier quoted context omitted.
Seivan, thanks. Yes, Rails "Omakase" is driving Swifton development. I'm not sure that protocols will help here, because Swifton supports before/after filter. Could you explain more your idea about how protocols could help here to implement actions with filters?
What do you mean by Rails Omakase? All I could find is a blog post by DHH saying that "Rails is Omakase." Is there more to it than that?
Re: Swifton: Ruby on Rails-inspired web framework for Swift
#10Seems to me like the real challenge in those framework (excepting performance, of course) will be in the orm component. Having a library that can query a db in a typesafe way is a must. Another will be in the concurrency patterns ( promises ? Coroutines ?, etc). But i get a great hope that they will succeed. Having a strong open source community will help. In fact, i'm so fed up with the sad state of uikit right now,…
I wish Apple had not ditched NeXT's EOF. It would make a fine open source project these days.