1,265 karma · joined December 6, 2011
Wouldn't that just be any culture that has a significantly offset male-female ratio?
From what I've seen of D8 it is going to be so different that it will almost certainly be cheaper to rewrite it in a simpler way (something like laravel for instance) than attempt the migration. For all but the most trivial sites, that is.
*edit: Oh, and are you aware of backdropcms? it is a fork of drupal 6 that is maintained.
unfortunately my early 2013 macbook pro can't drive it at 60hz, since that was only added in late 2013. Guess it's a good time to upgrade anyway.
I dove in because i try to get a balanced view of things before I make up my mind about things, and there was some stuff in there that I really liked. I tried building something with it, and it didn't really work out.
But even worse was the way that they interacted with their open source community.
It was completely cathedral-style, for a long time. And just as they became more bazaar-like everything dries up from them. Nobody was on irc, nothing on the issue queues. The only thing we heard was more promises for x integration, and y integration.
Eventually the community got fed up and called them out on it, to which they finally admitted that they had started a complete rewrite behind closed doors to use 'mixed mode' css3d and webgl rendering. 6 months later, they released their new 'engine' rewrite, and an additional 'framework' on top of it, which really did not seem fully baked.
They subsequently made a really big deal of helping found the jquery foundation, and organized a jquerySF conference that had them on stage promising to replace major jquery widgets with drop-in famo.us ones.
And then nothing. Commits stopped, feedback stopped, slack channel was closed. News started filtering out of devs working there leaving one after the other.
The entire thing did teach me some important life lessons, though =) At least there's a few mistakes i won't make again.
It didn't quite end up working out that way. Also, there's a community-run "fork": infamous[3]
[1] http://famous.org/ [2] http://venturebeat.com/2014/08/13/famo-us-raises-25m-to-doub... [3] http://infamous.io/
I am quite glad I didn't go into delphi more when I started out. I decided to stick to open source solutions, and I was proven right when the whole Kylix thing failed to happen.
How is lazarus these days?
the subtasks usually become apparent very soon.
> Uncaught ReferenceError: extesion is not defined(anonymous function) @ build.js:3
I was looking for a real world example to give people a reality check.
With Require.js you make changes to your code to be able to drive it, to avoid having a build step.
Browserify you had to have a build step, but it operates on your code 'from the outside', to avoid having to modify it.
Webpack does both of those.
it has a build step, but it works by extending the require() format to be able to specify the transforms inside the code itself.
The webpack configuration format is mostly just a way to replace require calls at runtime with a regular expression.
I find that this is a lot more straight forward, powerful and explicit than the [1] filename extension checks that happen in most browserify transforms. https://github.com/jnordberg/coffeeify/blob/master/index.js#...
I made a presentation about webpack, if you want to see :
Anything extra was very easily managed by some simple Makefiles.
Although, LocalStorage is the best way i've seen to handle the situation in a single page app, where you log out on one of the open tabs, and the other ones still think they are still logged in.
In general, there's a lot of really "fun" edge cases when it comes to modern web apps and multiple open instances ...
It's truly a gem.
by working longer hours, i was reducing the value of my time. I was also reducing the value I provided in those hours.
So it ended up giving me more balance than working a salary job.