View SConcatBenchmark.java
package org.osgl.util;
import org.osgl.$;
import org.osgl.util.S;
public class SConcatBenchmark {
public static void main(String[] args) {
final int WARMUP = 1000000;
final int LOOP = 100000000;
View logback.xml
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<statusListener class="ch.qos.logback.core.status.NopStatusListener" />
<!-- Send debug messages to System.out -->
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<!-- By default, encoders are assigned the type ch.qos.logback.classic.encoder.PatternLayoutEncoder -->
<withJansi>true</withJansi>
<encoder>
View act-project-logback.xml
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<statusListener class="ch.qos.logback.core.status.NopStatusListener" />
<!-- Send debug messages to System.out -->
<appender name="OUTPUT" class="ch.qos.logback.core.ConsoleAppender">
<withJansi>true</withJansi>
<encoder>
<pattern>%date %highlight(%-5level) %cyan(%logger{5}@[%-4.30thread]) - %msg%n</pattern>
View apt-issue-mint-18.1.txt
 root  ~  apt install skype
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
View gulp-sonar.js
var git = require('gulp-git');
var replace = require('gulp-replace');
var sonar = require('gulp-sonar');
var util = require('util');
/*
SONAR
*/
View table_test.md
Tables Are Cool
col 1 is l $1600
col 2 is c $12
col 3 is a $1
View resp_my_idea_framework.md
  1. More RoRish framework (APIwise)

    If you are talking about expressiveness and developer friendly, I think ActFramework is really hitting this point!

  2. So that on scalability issue or JVM migration, people can easily switch to this framework. This will be a big selling point. (Migration script will be a bigggg selling point!)

    Comparing to Play, Act is using standard maven project layout, using maven to manage the dependencies, using google guice to manage the depedency injection. It's more easier for developer to move from place like SpringFramework. Actually I specifically designed Act so that it get the greatest part from Play but without those very special requirements on project layout/static method in controller etc in play.

  3. More RoRish in terms of convention over configuration

View introduce to ActFramework.md
View sample-act-app-pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycom</groupId>
<artifactId>myapp</artifactId>
<version>1.0.0-SNAPSHOT</version>
<packaging>jar</packaging>
<name>My Act Application</name>
<properties>
View font.config
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<!--
Documented at
http://linux.die.net/man/5/fonts-conf
To check font mapping run the command at terminal
$ fc-match 'helvetica Neue'