Do you have any insight into how many of your customers buy Sidekiq Pro for the extra features, as opposed to for the commercial-friendly license, or simply to help sustain the OSS development?
You've added new features to Sidekiq Pro over time -- do you think your business would have been viable had you started with no (or very few) additional paid features?
I could be wrong but it seems to me that only the latest two designs (A Robot Named Jimmy and Verde Moderna) are what would be considered "modern" designs and the rest are from before the relaunch.
What's worse is that the two most common languages on GitHub (Ruby and JavaScript) are represented by shades of red/orange. I almost thought one of my repositories was in some kind of error state when I first opened it in the new design.
This exact same situation happened to me in the past month. My login page and its assets were copied, right down to the Rails asset digest fingerprints in the filenames as well as the Google Analytics code, which is how I discovered them.
I sent a sternly worded "Notice of Copyright Infringement" email and two weeks later their whole site was completely redesigned.
It's not open-source, but Wheelhouse (https://www.wheelhousecms.com/) is my answer to not being able to find a CMS I could enjoy working with.
It's Ruby on Rails based, so that power is always there when you need, but it then adds a flexible templating system for generation of content-editable fields (example here: https://www.wheelhousecms.com/blog/2011/8/flexible-templates...).
One option would be to use a service object (e.g. UserCreator) which would encapsulate the action (saving a user) along with the action to be taken (delivering a signup email).
With external observers, it's not always obvious whether they are enabled or not. Service objects make this more explicit and are easier to test as well.
Google is one of many tools that can be used to solve problems. IMO it's generally one of the more efficient ones.
A before_filter is just a method that runs before an action - there's no requirement for it to set an instance variable or redirect. In Rails 4, this method has been aliased as before_action to make this clearer.
Since the behavior of this method doesn't have too much to do with showing a topic, I think it makes sense. Extracting it also makes it possible to move it up to the ApplicationController for wider use.
I don't mean to dwell on the technical issues, but I'd be very curious to hear more about the performance issues you encountered that the Rails Core members couldn't resolve. Was there ever any resolution apart from downgrading to 2.x, and are there certain things that should be avoided in Rails 3.x?
> I'm also north of 90% probable that I could weaponize it to turn any image tag on the Internet into "roots your local machine"
Definitely not saying you're wrong, but I'm not convinced this is doable. Every exploit I've seen requires a request body -- how would you do that with an IMG tag?
I was pretty appalled when I first saw those tweets. I held my tongue at the time (after all, who am I?) but as a member of the Rails community, seeing this sort of behaviour from community leaders is frustrating and kind of embarrassing, and I do think it needs calling out when it happens. I'm finding Twitter has become more and more depressing lately with similar incidents.
I don't know much of Dave or any others who stuck the boot in, but Steve and Corey are both involved in educational endeavours and should know better. Steve also recently railed against the idea that "you are not your code" (https://twitter.com/steveklabnik/status/279399353729286145) which makes his jab even more insulting.
I've often wondered why concepts such as MINSWAN even exist, but it seems some people actually have to be reminded to be nice.
If they haven't already, they definitely owe you an apology.
This is pretty much exactly what DHH advocates for, and for a simple case like this (creating a user, sending an email) it works great.
At some point though, your controllers are going to grow. Multiple code paths depending on the data submitted, depending on the current state of the application, etc. At this point, building service classes such as CreatesContact can become very useful, not to mention much easier to test and reuse.
Evan Light's article at http://evan.tiggerpalace.com/articles/2012/11/21/use-rails-u... advocates "Use Rails until it hurts" which I think is a very good mantra to keep in mind when working with Rails.
If you are wanting to properly support IE7 (as mentioned in the README), you may want to downgrade normalize.css to 1.0.2 as normalize.css 2.x only supports IE8+.
There are only a few edge cases that are affected but they can bite if you were expecting full compatibility.
This issue has nothing to do with DRM, and is simply the result of a system that requires an account to be in good standing (i.e. has a valid credit card) before any downloads can be made.
Obviously this is an issue that should be fixed, but there isn't even any evidence that any attempts were made to contact B&N - just someone encountering an error message in B&N's software.
I'm as against DRM as anyone else here but this is a non-story.
Ah. In that case I'd suggest extending the map downwards so that the background image is taller. My browser window is roughly 4:3 and the map cutoff detracts from what is a very nice design.
Not quite. You've added those to the body element (inline as well, which is a bad idea), whereas the background is on the #wrapper div. I'd suggest moving the background onto the body element, and adding the background-size definitions to the body element but within your CSS.
With that fixed, it looks very nice indeed.
I've been working on a Rails based CMS (Wheelhouse CMS - https://www.wheelhousecms.com) over the last few years as a side-business to my regular web dev consulting services (and slowly transitioning to supporting it full time).
It's able to integrate with existing Rails projects or stand as its own app, and its quite extensible so you can potentially use it as an admin area for the remainder of your app too.
If you're interested, email me (sam@wheelhousecms.com) and I'll set you up with an evaluation license.
I've found Guard::LiveReload (https://github.com/guard/guard-livereload) to work exceptionally well. It's Ruby, but should work alongside whatever development framework you're using.
I believe he refers to error correction as in it corrects errors in the code -- i.e. the code itself should have semicolons and is fixed through ASI.
Compared to onclick, it's certainly a performance benefit.
However the difference here is in looping over every matched element to add the handler (bind) versus adding the handler to a single element further up the DOM tree (delegate).
I recently released the first version of Wheelhouse CMS - https://www.wheelhousecms.com, which is a Rails-based CMS including WYSIWYG editing, template-based form generation, media library, plugins and a decent UI.
It's not free software but from my biased perspective its by far the best CMS I've ever used and my clients love it.
Demo here: http://demo.wheelhousecms.com
I'm considering offering a developer/personal use license but I still need to work out the details. Drop me a line privately and I can set up an evaluation account for you.
Wheelhouse CMS is a project I've been working on for a couple of years now (way too long for a first release, I know), which I've bootstrapped whilst freelancing building content-managed web sites. Many iterations and hundreds of private gem releases later, I'm finally confident enough to publicly release version 1.0.
You can check out a demo directly at http://demo.wheelhousecms.com/admin.
I'd love to hear what you think and what can be improved.
Gregg Pollack's talk at http://confreaks.net/videos/285-lsrc2010-decyphering-yehuda is fairly accessible and gives a good overview of some of the newer refactorings.
Even if it is gamed, it still proves the original point: that "the applicant cares a bit more about presentation than the average programmer that submits his resume in .doc format."
Firstly, MongoModel was started back in November '09 when both MongoModel and and Mongoid were much less mature than they are now. I spent some time contributing patches to MongoMapper but stumbled as I was working on edge rails.
MongoMapper in particular has come a long way since then but still has a few issues in my mind. For example, attributes are converted to/from their mongo representation every single time they are accessed, rather than only when the model is saved or loaded. I also believe MongoModel has a nicer model for typecasting property values (see http://gist.github.com/287379 for an example), and I disagree with the use of has_many associations for embedded collections.
MongoModel isn't perfect either, but it has been the path of least resistance for me in getting my app running on MongoDB.
I'd also recommend checking out my MongoModel project, especially if you have been dissatisfied with the way MongoMapper or Mongoid do things.
http://github.com/spohlenz/mongomodel http://www.mongomodel.org
It's not quite as mature, but more documentation updates are currently in progress.
I'm working on a Rails/MongoDB CMS called Wheelhouse: http://www.wheelhousecms.com
It'll be a flat-fee, self-hosted product. The main aim is for it to be easy and enjoyable for both designers/developers to build sites with, as well as for their clients to use.
Who says it would be in your area though? You could travel the country and probably find hundreds of instances of this sort of thing happening.
Maybe they could release a foot pedal iPhone app to go along with it?