5,164 karma · joined March 18, 2010
Downvoted for expressing contempt for the English language and common decency, but then failing to add in the obvious "irregardless."
Pension plans are currently not allowed under federal law to fully fund themselves because that would be so expensive it would disrupt federal taxation. Instead we are constantly building up future pension crises that will have to be paid in higher taxes and economic chaos later.
It works, but it's no good for daily driving. You can get out of town in a car with some patience, but you're going to take the train in town.
If you can accept that, you can have it all. But no American city has made that choice.
Copying the immigration policy of Hungary, Japan, Korea, and Poland is easy if you want all the people of your nation to prosper. If your elite is more interested in keeping the people down so they can stay up, you get a different policy.
Yes.
Japan, Mexico, Chile, Poland, Hungary, Korea, Thailand.
Well, j and k are fine if you're not moving far. A lot of slow scrolling up and down should be { and } or C-d and C-u or <count>[jk]. Even better: Use / and ?. It's bad to be repeatedly tapping j and k or waiting for the keys to repeat.
But h and l are the EMACS approach. You should be moving in a line with w, e, b, f, F, t, T, ^, $, I, A, 0, and the like. Vi provides lots of tools for efficient line editing and h and l are not good.
Beginners should try
:noremap h <nop>
:noremap l <nop>
to keep them from the temptation of the nefarious h and l keys.Lately I use
:no h ^
:no l $
which is even better because ^ and $ require moving your hands off the home row even though they're much better than h and l for you.Next time, get out on foot and see the city. You can't see anything from a car. [0]
[0] https://www.youtube.com/watch?v=6r83MF9BRZA&feature=youtu.be
You can just look at neighboring Mexico with 1/6th the per capita income and correspondingly lower public budgets where transportation, urban maintenance, and quality of city life are routinely better. And not just relatively better: Mexican cities (outside the shady border region) are nicer than American cities to live in. If you could put a typical neighborhood from Puebla or Guadalajara or León or Mexico City into Dallas or Los Angeles or San Jose or Atlanta, it would be the best, nicest neighborhood in the city.
And that's not even bringing up the great cities of Europe at all. Because that would be completely unfair.
It's like the health care system: Even a great country does some things horribly wrong and suffers for it.
Alas, President Young had long since exhausted his outrageously lavish budget of divine providence just getting to Utah.
If you're looking at $105k in SLC, you should be asking for $225k+ in SF by my experience.
--
We did the calculation between $125k in SF and $45k in SLC a decade ago and SLC came out well ahead for a family of four.
(Also: quaternions)
:ino kj <Esc>
:ino <Esc> <Nop>
Try it for a week; you'll love it.But some regex engines accept non-regular expressions. [0] The usual notation for it is an escaped number: \1 or \2 or so on. They're used to refer back to capturing groups earlier in the expression, usually marked by parentheses.
Regular expressions don't have backreferences but various enhanced expressions add them. If you use those extensions, you are in danger of exponential execution time unless you are careful and know what you're doing. In particular you should know not to use regular expressions as your principal tool to build a parser.
Well, Trump could withdraw support for DACA as he promised, but he's now signed off on thousands of new DACAs, so he's in no hurry to change the program.
[0] https://github.com/WildUtah/secret-personal-dotfiles/blob/ma...
What you really want is just to run
lein repl
in your repository and then fire up another terminal and edit code with Vim. Then you should send whole top-level forms to the repl with :Eval from Vim and it should just work. You can then test them in the repl. (I alias C-c C-c to :Eval (:no <C-c><C-c> :Eval<cr>) because I'm used to the old vim-slime)And it should all work automatically. With the new versions of vim-fireplace it does just work automatically.
I'll write a 'process-data function in Vim, send it with :Eval, and then test it in the repl with (process-data {:some "data", :more "other data"}) and it all just works. There's a little reading up on namespaces necessary once your projects get complicated, but it works on a bare repl right out of the box, too.
People remember that kind of thing and millions edit themselves in a general low-level miasma of fear they might get targeted.
But the Neovim port is great. Installation requires a little patience, but it works well.
In any case, one should read the Clojure style guide on GitHub [0] and get used to writing code in normal editing modes first. Then move on to Parinfer or Paredit once you feel the shape of the code and sense why it's like that.
The defining characteristic of a garbage collected system is an active outside process with priority and control over my code that chooses when to inject bugs (to wit: arbitrary pauses) into my program outside my control.
This is the plan with Swift and what makes it zippy.
bone of contention with sweeping collectors is constantly walking
The real problem is that you cannot determine when the program will pause. It makes interactive and soft realtime impossible with gc. (Hard realtime should not run a generic allocator at all.) You can't write anything but servers and unpleasantly unresponsive apps.
Android developers have to carefully jump through hoops to avoid allocating any RAM at all if they don't want to bug their users. For years when the chips were slow, ref counting was a major competitive advantage for iPhone. A hundred-billion dollar win.
And then there's system software. You can't afford a live, unpredictable runtime messing with you in systems code so anything that touches low level code can't use gc. There's a disincentive to really invest in a language that simply can't ever do a full stack, even if you're unlikely to need to write a device driver anytime soon. That's why no major browsers, performant ACID databases, or fast app servers depend on RAM gc.