Here is a true time scaled solar-system, which means that every objects have a time relative to an Earth year.
A Pen by Malik Dellidj on CodePen.
Here is a true time scaled solar-system, which means that every objects have a time relative to an Earth year.
A Pen by Malik Dellidj on CodePen.
import java.io.IOException; | |
import java.net.URLClassLoader; | |
import java.nio.file.Files; | |
import java.nio.file.Paths; | |
import java.nio.file.Path; | |
/** | |
* Example demonstrating a ClassLoader leak. | |
* | |
* <p>To see it in action, copy this file to a temp directory somewhere, |
Inspiration: Deis Commit Style Guide
I often quote Deis in sections below.
It makes going back and reading commits easier. It also allows you to spend less time thinking about what your commit message should be.
private String getKillStreak(int score) { | |
switch(score){ | |
case 2: return "Double"; | |
case 3: return "Triple"; | |
case 4: return "Quadruple"; | |
case 5: return "Penta"; | |
case 6: return "Hexa"; | |
case 7: return "Hepta"; | |
case 8: return "Octo"; | |
case 9: return "Ennea"; |
When hosting a project on GitHub, it's likely you'll want to use GitHub Pages to host a public web site with examples, instructions, etc. If you're not using a continuous integration service like Travis, keeping your gh-pages site up to date requires continuous wrangling.
The steps below outline how to use Travis CI with GitHub Releases and GitHub Pages to create a "1-button" deployment workflow. After testing and running a release build, Travis will upload your release assets to GitHub. It will also push a new version of your public facing site to GitHub Pages.
Let's assume you are hosting a JavaScript project that will offer a single JavaScript file as a release asset. It's likely you'll organize your files like this.
package self.vpalepu.stackoverflow; | |
import java.io.File; | |
import java.io.FileInputStream; | |
import java.io.IOException; | |
import org.objectweb.asm.ClassReader; | |
import org.objectweb.asm.ClassVisitor; | |
import org.objectweb.asm.ClassWriter; | |
import org.objectweb.asm.MethodVisitor; |
Continuous Integration (CI) is an important practice every team should adopt in order to detect defects and errors early and solve integration problems easily. Roughly speaking we may say that CI is a practice that allows the growth of solid software by giving greater confidence to the developers and better products to the final customers.
The concept behind CI is fairly simple: the codebase is owned by several developers that continuously integrate their changes to a common version control system. For each integration the system runs a predefined set of tasks automatically; these tasks may vary from running all the tests to building all the components.
public void countdown(final Player player){ //A method | |
new BukkitRunnable(){ //BukkitRunnable, not Runnable | |
int countdown = 10; //Instance variable in our anonymous class to easily hold the countdown value | |
@Override | |
public void run(){ | |
if(countdown <= 0 || !player.isOnline()){ //countdown is over or player left the server, just two example reasons to exit |
puts 'Hello World' |
extern mod sync; | |
// str op trait | |
use std::str::StrSlice; | |
// for tcp listen | |
use std::io::{TcpListener, TcpStream}; | |
use std::io::net::ip::SocketAddr; | |
// for trait | |
use std::io::{Listener, Writer, Acceptor, Buffer}; | |
// for spawn |