598 karma · joined August 4, 2009
What we actually need are editors in which you can set you language (haml, slim, less etc), and then those are compiled and saved, in realtime to html, erb, css etc.
Not having used too much Coffee Script yet, I don't know what the transformation from CS -> JS -> CS would result in, but I believe HAML -> HTML -> HAML would be pretty much 1:1, and html2haml already produces pretty much exactly the same haml I would have produced if I had done the conversion manually.
A monopoly born through a superior product is not the same as a monopoly born through anti-competitive practises. Noone is forcing or coercing anyone to use Google+. Facebook and twitter are only a click away, and both are massively more popular.
Could we say the same if Facebook launched an email service? Or if Twitter launched some sort of search engine?
I'll definitely be waiting anxiously for you to finish.
Good luck!
One of the best things about LPTHW was the context it was written in, and if LCTHW is written in the same way, it should be a really awesome read!
No one is forced to use any of Google's products - Bing and Facebook are only a click away.
A monopoly born from having a superior product is not the same as a monopoly gained through the practises of price fixing or forcing people to install your web-browser with no way to disable it.
Edit: Thinking about his explanation, it doesn't really make sense to me. If that were really the case, those accounts would be more evenly distributed through the list - yet they are tightly clustered, which leads me to think they were created in groups (guessing the list has some sort of chronological order).
Having a closer look at the list, and assuming the dump is organised in some sort of chronological creation order, you can see that all the accounts which use that password are created in several tight groups, share a fairly common username theme (mostly female names), and use a fairly narrow selection of email providers. I would guess they were made by a bot.
My app which includes thinking-sphinx (which has a require '0.9.9'), breaks with it.
* Anonymous Metagenics Dockworker - MorganLink 3DVision Live Interview
You were perhaps aiming for a sound-bite, but saying "It works in very few cases" is inaccurate.
If I were doing an app with standard model authentication, a Forum for example, I would use devise again in a heart-beat, but for any other project where I expect to have any slightly customized behavior at all, Ill be rolling my own.
Devise is brilliant if you want something straight-forward, but it is big, complicated (internally), and not very flexible.
Possessing approximately 40% less food energy, xylitol is a low-calorie alternative to table sugar. Absorbed more slowly than sugar, it does not contribute to high blood sugar levels or the resulting hyperglycemia caused by insufficient insulin response. This characteristic has also proven beneficial for people suffering from metabolic syndrome, a common disorder that includes insulin resistance, hypertension, hypercholesterolemia, and an increased risk for blood clots.
However, he also says that sweet fruits in large quantities can still be bad for us.
One thing I cant remember ever having read is a horror story about people taking over a legacy Rails app, while those stories seem to be fairly common when talking about Java apps.
Seems to me that, for the most part, people who know Ruby and Rails have taught themselves, while sub-par and mediocre Java programmers are produced in their hundreds, fresh from their first programming experience in college.
Seems logical to me then that its going to be far easier to get experienced Ruby programmers than to get experienced Java programmers.
Most startups fail anyway, so devoting a single day more than needed on development is a waste of very valuable time and money. How many extra VPS' is a month of saved development time worth?
All skill being equal, choosing Java over Ruby for a new project is one of the worst cases of optimize early I can imagine.
That said, I have taken over development of a few legacy rails applications and never had a problem adapting to the idiosyncrasies of the old developer or team.