pkmiec

3

the new concurrency is part of ruby 3. matz says he wishes for it to be out by 2020. but who knows :).

AppFolio - Santa Barbara, CA - REMOTE

We're looking for a C-hacker with experience in just-in-time compilers, virtual machines, runtime optimizations, etc to work with the Ruby core team on performance.

We primarily use Ruby / Ruby on Rails on the back end side. Ruby is a great language, but a slow one. We'd like to help make it faster. So we've teamed up with the Ruby creator Yukihiro "Matz" Matsumoto on the Ruby 3x3 effort (http://engineering.appfolio.com/appfolio-engineering/2015/11...).

See more information details and apply at,

http://www.appfolioinc.com/jobs-openings?p=job%2FoZ1c2fwY

About AppFolio: We create easy-to-use, cloud-based software that helps small and mid-sized businesses more effectively market, manage and grow their business. Today, our products serve the legal and property management industries.

Thanks, Paul

Yes, we are going to hire someone. We now have the position open and are looking for candidates. We already have a couple of folks interested and we'd like to get a few more so that we can find the best fit.

[0] http://www.appfolioinc.com/jobs-openings?p=job%2FoZ1c2fwY (it says Santa Barbara, CA but really anywhere in the US is ok)

This is definitely a nice improvement which can lead to Ruby performance improvements.

It's also worth noting that Ruby 3 in general will have a focus on performance. Matz talked about performance and the Ruby 3x3 effort during his RubyKaigi keynote. The goal of Ruby 3x3 is to make Ruby 3 be 3 times faster than Ruby 2.

Full disclosure: I work for AppFolio which is helping to sponsor the Ruby 3x3 effort.

good for them to do a major city. i'm still waiting for pdx.

I love solid well tested technology. Let's try to make it faster :).

Images are fun. But I'd like to see a demo showing how http/2 can affect asset managers / web development. Perhaps show a site with 1-5 bundled css / js vs 100-500 individual css / js.

Does a demo like that exist?

how does this compare to uglifier?

I originally read about this patch here, http://samsaffron.com/archive/2014/04/08/ruby-2-1-garbage-co....

There hasn't been any activity on the upstream proposal for almost a year. Has the core team rejected the idea or is there still hope it will make it into a future version?

The pipeline features of gocd seems very nice. However, last time I looked at gocd it did not support feature branches. As far as I could tell, it was not due to technical reasons but rather due to the whole feature branch vs continuous integration philosophy differences.

Any idea whether feature branch support will be added in the future?

2048

I've been using passenger for quite some time and really appreciate its focus on operational tools.

Thanks for the detailed comparison. Good to know how it stacks up against the other options out there.

I totally agree about refinements being a terrible idea. Brian Ford (of Rubinous) makes an excellent argument: http://www.youtube.com/watch?v=BagNfTbXn3w.

What is the best way to let Ruby team know that refinements are a bad idea?

I'm still on the election. It took me a while to realize the title if referring to the university and not the presidential candidate.

Ditto on the bad uptime and data retention. I've also had issues with support taking a week to respond.

In addition, exceptional does not support looking at the data in interesting ways (i.e. exceptions from this machine, exceptions for this customers, how many customers are affected by a problem, etc). I have to configure applications to send exceptions to difference projects which is a huge pain when you need to change something.

Their 404s idea is useful, but inflexible, as sometimes I do care about getting notified about RecordNotFound, etc.

Thanks for the ratchet.io, whoopsapp.com, and sentry suggestions.

We implemented something like this at the place I work.

We have a tiny ruby process, based on event machine, that subscribes to various queues (we happen to use RabbitMQ). When a message arrives, the process makes a request to the passenger instance passing along the message data and waits for a response. The process limits the number of requests it makes to prevent background requests from blocking out front-end requests (for example, 20% of passenger_max_pool_size). We're also simulating priority by using different prefetch values for different queues (for example, 10 messages for high queue and 5 messages for low queue).

what's the ??? quest?

I just did 4 domains.