| #!/usr/bin/env ruby | |
| def pop; $stack.pop || raise(StackUnderflow); end | |
| def push(expression); $stack << expression; end | |
| def unary; -> { push(yield pop) }; end | |
| def binary; -> { push(yield pop, pop) }; end | |
| def unary_boolean; -> { push(if yield pop then 1 else 0 end) }; end | |
| def binary_boolean; -> { push(if yield pop, pop then 1 else 0 end) }; end | |
| def swap; $stack[-2,2] = $stack[-2,2].reverse; end | |
| $stack = [] |
| # Example Usage: ruby froth.rb ": sq dup * ; 2 sq ." | |
| class Froth | |
| attr_reader :storage | |
| attr_accessor :trace | |
| WordDefinition = Struct.new(:name, :xt, :immediate) | |
| class WordDefinition | |
| def immediate? | |
| immediate |
| having problems with git with my node app on nodester (similar to heroku). | |
| I did a force push to nodester, and I believe it merged my | |
| server.js file with the starter server.js file, | |
| resulting in an error on the <<<<<HEAD line git adds. | |
| tried git push --force nodester master a few times, along with | |
| git pull nodester master, and git fetch nodester master | |
| What's more, when I do git fetch nodester master, I get: | |
| * branch master -> FETCH_HEAD |
Ok, I geeked out, and this is probably more information than you need. But it completely answers the question. Sorry. ☺
Locally, I'm at this commit:
$ git show
commit d6cd1e2bd19e03a81132a23b2025920577f84e37
Author: jnthn <jnthn@jnthn.net>
Date: Sun Apr 15 16:35:03 2012 +0200
When I added FIRST/NEXT/LAST, it was idiomatic but not quite so fast. This makes it faster. Another little bit of masak++'s program.
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
| /* Flatten das boostrap */ | |
| .well, .navbar-inner, .popover, .btn, .tooltip, input, select, textarea, pre, .progress, .modal, .add-on, .alert, .table-bordered, .nav>.active>a, .dropdown-menu, .tooltip-inner, .badge, .label, .img-polaroid { | |
| -moz-box-shadow: none !important; | |
| -webkit-box-shadow: none !important; | |
| box-shadow: none !important; | |
| -webkit-border-radius: 0px !important; | |
| -moz-border-radius: 0px !important; | |
| border-radius: 0px !important; | |
| border-collapse: collapse !important; | |
| background-image: none !important; |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
| Original text here: https://whydavewhy.com/2013/08/16/loyalty-and-layoffs/ |
| # .railsrc | |
| -B #Skip Bundle | |
| -T #Skip Test-Unit | |
| -d postgresql #Use postgres |
