Ruby 1.8 or no Ruby 1.8

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Ruby 1.8 or no Ruby 1.8

Emmanuel Bernard
Hey guys,

I have seen Jason's question on IRC wrt continuing support for Ruby 1.8.

There are a few reasons for me not to migrate:

- Mac OS X users are still by default on Ruby 1.8.7. Having a procedure
  to move them to later versions is not that trivial for Ruby noobs even
  with RVM.
- We had the encoding bug in metadata which I believe is fixed with some
  trick I have already forgotten.
- I don't do this on my main time, nor my spare time, nor even my spare
  spare time so indeed I am slow on these moves :/

About Awestruct 0.4 vs 0.2

- For some reasons, a couple of old Wordpress sites that I migrated into .erb
  files break and the fix is long and tedious AFAIR - I forgot the
  details to that is related to Awestruct 0.2 vs 0.4.
- 0.4 and the smart caching algorithm doe a few things very
  inefficiently and is blocking us on moving in.relation.to to
  Awestruct. Ruby crashes after ~30 mins. We have twicked it a lot and
  limited feed generation and pagination to make it usable

There you go for the feedback.

Emmanuel

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Ruby 1.8 or no Ruby 1.8

LightGuard
Administrator
I understand the reasons for staying on 1.8.7, and I don't feel like it's a good time to drop support, I know quite a few larger systems (GitHub for example) are still running 1.8.7 and probably will for quite some time. I don't foresee us dropping 1.8.7 support any time soon.

WRT the in.relation.to stuff, do you have it in a repo or somewhere you can share Emmanuel? It would be a great use case for us to optimize things better.


On Sat, Mar 9, 2013 at 1:51 AM, Emmanuel Bernard <[hidden email]> wrote:
Hey guys,

I have seen Jason's question on IRC wrt continuing support for Ruby 1.8.

There are a few reasons for me not to migrate:

- Mac OS X users are still by default on Ruby 1.8.7. Having a procedure
  to move them to later versions is not that trivial for Ruby noobs even
  with RVM.
- We had the encoding bug in metadata which I believe is fixed with some
  trick I have already forgotten.
- I don't do this on my main time, nor my spare time, nor even my spare
  spare time so indeed I am slow on these moves :/

About Awestruct 0.4 vs 0.2

- For some reasons, a couple of old Wordpress sites that I migrated into .erb
  files break and the fix is long and tedious AFAIR - I forgot the
  details to that is related to Awestruct 0.2 vs 0.4.
- 0.4 and the smart caching algorithm doe a few things very
  inefficiently and is blocking us on moving in.relation.to to
  Awestruct. Ruby crashes after ~30 mins. We have twicked it a lot and
  limited feed generation and pagination to make it usable

There you go for the feedback.

Emmanuel

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]




--
Reply | Threaded
Open this post in threaded view
|

Re: Ruby 1.8 or no Ruby 1.8

mojavelinux
On Sat, Mar 9, 2013 at 9:56 AM, Jason Porter <[hidden email]> wrote:
I understand the reasons for staying on 1.8.7, and I don't feel like it's a good time to drop support, I know quite a few larger systems (GitHub for example) are still running 1.8.7 and probably will for quite some time. I don't foresee us dropping 1.8.7 support any time soon.

Agreed.

I think when GitHub moves off 1.8.7 officially, that's a good indicator that it's time to drop 1.8.7 support (since they are a large user of Ruby).
 

WRT the in.relation.to stuff, do you have it in a repo or somewhere you can share Emmanuel? It would be a great use case for us to optimize things better.

We are definitely aiming to polish Awestruct right now. If there are issues, report them. If you know of possible solutions, propose them. Suffice to say, using Awestruct should not be painful. If so, then we aren't there yet.

-Dan
 
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

Reply | Threaded
Open this post in threaded view
|

Re: Ruby 1.8 or no Ruby 1.8

mojavelinux
In reply to this post by Emmanuel Bernard

On Sat, Mar 9, 2013 at 9:51 AM, Emmanuel Bernard <[hidden email]> wrote:
We have twicked it a lot and
  limited feed generation and pagination to make it usable

I completely agree that there is absolutely no reason in development mode that all these extra pages should be generated. It's just a waste of time.

I think we should even consider having a configuration option that handles pagination dynamically via JavaScript. That won't be for everyone, but for some people very useful. Something definitely worth exploring.

-Dan

--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

Reply | Threaded
Open this post in threaded view
|

Re: Ruby 1.8 or no Ruby 1.8

Emmanuel Bernard
In reply to this post by LightGuard
On Sat 2013-03-09  1:56, Jason Porter wrote:
> WRT the in.relation.to stuff, do you have it in a repo or somewhere you can
> share Emmanuel? It would be a great use case for us to optimize things
> better.

Yes.
Checkout http://https://github.com/hibernate/in.relation.to and use the commit
884bba60a790bf74daeab115017bef0d0d957d00

I will send to Jason and anyone interested infos on how to fill up the data. In
the repo the imported posts are not present as the import module is not
polished yet. Contact me if you want it.

Emmanuel

---------------------------------------------------------------------
Archives: http://talk-archive.awestruct.org/
To unsubscribe, e-mail: [hidden email]