start new:
tmux
start new with session name:
tmux new -s myname
So, you want to send a motherfucking XMLHttpRequest (XHR, or commonly and falsly known as AJAX.) Too bad, just ran out of motherfucking XMLHttpRequests; but I still have one regular. XHR is not magic. It does not autofuckinmagically send things the way you want them do be sent. It does not do the thinking for you. It just sends an Http Request.
You get a hold on such a prime beast like this:
#define HTTP_STATUS_100 "100 Continue" | |
#define HTTP_STATUS_101 "101 Switching Protocols" | |
#define HTTP_STATUS_102 "102 Processing" | |
#define HTTP_STATUS_200 "200 OK" | |
#define HTTP_STATUS_201 "201 Created" | |
#define HTTP_STATUS_202 "202 Accepted" | |
#define HTTP_STATUS_203 "203 Non-Authoritative Information" | |
#define HTTP_STATUS_204 "204 No Content" | |
#define HTTP_STATUS_205 "205 Reset Content" | |
#define HTTP_STATUS_206 "206 Partial Content" |
// Copyright Joyent, Inc. and other Node contributors. | |
// | |
// Permission is hereby granted, free of charge, to any person obtaining a | |
// copy of this software and associated documentation files (the | |
// "Software"), to deal in the Software without restriction, including | |
// without limitation the rights to use, copy, modify, merge, publish, | |
// distribute, sublicense, and/or sell copies of the Software, and to permit | |
// persons to whom the Software is furnished to do so, subject to the | |
// following conditions: | |
// |
http://www.thoughtworks.com/radar/#/languages-and-frameworks/683 - ThoughtWorks Technology Radar - January 2014
We continue to see teams run into trouble using JSF -- JavaServer Faces -- and are recommending you avoid this technology. Teams seem to choose JSF because it is a J2EE standard without really evaluating whether the programming model suits them. We think JSF is flawed because it tries to abstract away HTML, CSS and HTTP, exactly the reverse of what modern web frameworks do. JSF, like ASP.NET webforms, attempts to create statefulness on top of the stateless protocol HTTP and ends up causing a whole host of problems involving shared server-side state. We are aware of the improvements in JSF 2.0, but think the model is fundamentally broken. We recommend teams use simple frameworks and embrace and understand web technologies including HTTP, HTML and CSS.
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
/* This has been added to CSS Protips https://github.com/AllThingsSmitty/css-protips */ | |
/* The type font size in a responsive layout should be able to adjust with each viewport. | |
You can calculate the font size based on the viewport height and width using :root */ | |
:root { | |
font-size: calc(1vw + 1vh + .5vmin); | |
} | |
/* Now you can utilize the root em unit based on the value calculated by :root */ | |
body { |
[Unit] | |
Description=RClone Mount (crypt) | |
AssertPathIsDirectory=/mnt/decrypt | |
After=plexdrive.service | |
Requires=plexdrive.service | |
PartOf=plexdrive.service | |
[Service] | |
Type=simple | |
User=username |
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset="utf-8"> | |
<title>esptool.js</title> | |
<script src="https://cdnjs.cloudflare.com/ajax/libs/xterm/2.9.2/xterm.min.js" integrity="sha256-8rsVcpCnO6HdeJL84i0VdubjM42fjSmO8aONghdq3gc=" crossorigin="anonymous"></script> | |
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/xterm/2.9.2/xterm.min.css" integrity="sha256-w69o8Y6P5VZjfYFmn2KlqMU7TUi2I+oWObi8FLlVZZg=" crossorigin="anonymous" /> | |
</head> |