In terms of shell, I moved to the fish shell 5 years ago.
Things are so much easier. No need to a massive amount of plugins and configs, mostly works out of the box.
254 karma · joined August 22, 2009
Things are so much easier. No need to a massive amount of plugins and configs, mostly works out of the box.
1. Promises are handled in micro-tasks. 2. `element.click()` causes the event to dispatch synchronously. Even on parent elements.
But, often times I have jumped around many times, or only scrolled. It doesn't work in these situations. Whereas `undo` `redo` reliably brings me back to the place of last input.
You could too, couldn’t you?
The TimeMachine datasets are backed up offsite.
Losing this pool would be a PITA, but not critical.
My primary goal with ZFS is some data redundancy. At a good cost. And quick remote backup for a fraction of the pool. Not performance.
At one point, 2 disks died within 2 days. While there was some panic involved, the data on the server could be reproduced with some time.
There isn’t a best solution, that fits all needs. If there was, ZFS wouldn‘t offer all the options it does.
Here are my thoughts: https://codepen.io/shvi/pen/poyqxWL
Did you ever consider adding a Markdown to HTML email option?
This is especially helpful when sending formatted code around!
As a consequence, I had to learn to touch-type.
As of now, I am slower than before, but there is hope ;)
C.f. https://accessibility.oit.ncsu.edu/it-accessibility-at-nc-st...
Here is what they could have done:
Right hand side: a regular power button that doubles as finger-print.
Left hand side: a regular esc key.
Replace F keys with a touch oled screen.
I could actually live with that.
It feels kind of wrong that a company that integrates video into web bug trackers needs to host their own video on a 3rd party video hoster.
I went ahead and made a pull request. https://github.com/zynga/scroller/pull/1
First learn about MVC and the first project they writer ends up being somewhat maintainable. It relies on state of the art paradigms, is modular and should be relatively safe.
With time, the framework will not provide all the needed functionality. This is when the young programers start to modify or write simple plugins. So they learn about the Framework API.
Even later, they need to modify some parts of the framework to make it possible to hook into it with a plugin. So they learn about the core Framework.
At every step, the programer is confronted with code written by more experienced programers… To me, this is the best way to learn programing.
But I like it!
What alternatives would you suggest?
http://files.pierrespring.com/techzinglive_bootstrap.rss
I have also added instructions on how to add an RSS feed to iTunes on my blog, if you don't know how to do that:
http://pierrespring.com/2010/11/19/techzing-compilation-boot...
Enjoy and let me know if you like it ;)
By reputation, PHP is a bit like JavaScript. JavaScript was this language nobody liked. It wasn't even considered a real language by most programmers. Some of it's design errors made it a language with low barrier to entry. Hence a lot of mediocre programmers made it unpopular with code that does not deserved to be called code.
This changed with people like Crockford and his 'JavaScript the good parts'...
It's pretty much the same with PHP. It gets the job done very easily... And once you know what you do, you can rely on it for large projects too. Especially with the changes that were introduced in the latest release: Namespaces, Closures, ...
1) Why would you go through the process of switching the language. There are perfectly suitable frameworks in PHP, e.g. Symfony, that have the exact same approaches than Django and ROR. MVC, ORM and configuration over Convention over Configuration. Once you have a team that is good at a Language, you'll loose a lot in switching... and this leads me to the second question:
2) How can it take 22 month to rewrite this kind of application? A bit of CRUD and workflow should not take so much time.
WDYT?