kewin (kewin)

Ruby 程序员可以容易的转型安全

kewin — Thu, 03 Dec 2015 10:41:40 +0800

这两年在随着互联网 + 口号越来越响亮，移动互联风生水起，与此同时网络安全领域也异常火热。Ruby 程序员在专注 web 的同时是否考虑转型安全领域呢？

目前 Ruby 的自动化测试可以说做的很棒了，然而很少有人知道在安全领域的渗透测试框架metasploit-framework 也是 Ruby On Rails 的，目前这个框架主要是 Rapid7 的人在开发，Rapid7 目前还支持 SOHO 哦

另外 metasploit 在比较主流的渗透测试系统Kali Linux 上自带了

本周末 RubyConf 2015

kewin — Fri, 13 Nov 2015 11:15:44 +0800

本周末 15-17 号的 RubyConf 讲演 schedule http://rubyconf.org/schedule

大家可以关注下

一行 Ruby 代码把 Mac 坑了

kewin — Wed, 19 Aug 2015 15:51:46 +0800

今天看了下http://ruby-doc.org/stdlib-2.2.2/libdoc/benchmark/rdoc/Benchmark.html#method-c-bm 试着执行了下里面的示例

require 'benchmark'
puts Benchmark.measure { "a"*1_000_000_000 }

输出

irb(main):056:0> puts Benchmark.measure { "a"*1_000_000_000 }
  0.340000   0.340000   0.680000 (  0.693746)

我脑残的改了下参数，多加了 3 个 0

require 'benchmark'
puts Benchmark.measure { "a"*1_000_000_000_000 }

结果吧 Mac Pro 坑了

他跑了好久都没出来结果最后还强制退出了 irb , 过程中一直 top 命令看了下 ruby 进程内存消耗一直在 1G 上下结果内存的压缩值 CMPRS 快速的飙升至 56G

Flash 导致 Mac 死机

kewin — Mon, 01 Jun 2015 10:30:16 +0800

我默认是禁用 Flash 的，上午看一视频，就点击视频就启用了一次，结果 Mac 死机（键盘，touchpad 都无法执行任何操作）了这周遇到两三次，大家由遇到吗

Debugging memory leaks in Ruby

kewin — Wed, 01 Apr 2015 14:31:01 +0800

Discourse 的 co-founder 写的一篇关于 Ruby 内存泄露分析过程 http://samsaffron.com/archive/2015/03/31/debugging-memory-leaks-in-ruby

作者是一个 Ruby 程序员，个人站 http://samsaffron.com/ Discourse http://samsaffron.com/

Ruby 2.2 中实验性的采用 Vfork

kewin — Thu, 08 Jan 2015 10:53:38 +0800

在 Ruby 2.2 release notes 中提到，除了 Symbol GC 和 Incremental GC 外，还实验性的引入 vfork 这两天看到几篇文章

CoolShell 的陈浩写的 vfork 挂掉的一个问题
tanaka-san’s blog in Japanese

fork 和 vfork 的差别： fork 是创建一个子进程，并把父进程的内存数据 copy 到子进程中。 vfork 是创建一个子进程，并和父进程的内存数据 share 一起用。这两个的差别是，一个是 copy，一个是 share。（关于 fork，可以参看酷壳之前的《一道 fork 的面试题》）

你 man vfork 一下，你可以看到，vfork 是这样的工作的，

1）保证子进程先执行。 2）当子进程调用 exit() 或 exec() 后，父进程往下执行。

但是目前 vfork 还是存在一些风险

Airbnb 使用 Ruby 在国际化支付方面的 Blog

kewin — Sat, 03 Jan 2015 22:27:47 +0800

今天在逛 airbnb 的时候看到他们呢的工程博客 http://nerds.airbnb.com/ 上很多项目是使用 ruby 发现在国际化支付两篇好的文章：

http://nerds.airbnb.com/international-payments-platform/ http://nerds.airbnb.com/interning-airbnb-payments-team/

Shopify 的 Docker 使用经验

kewin — Wed, 03 Dec 2014 00:02:29 +0800

在 infoq 上看到 Shopify 使用 Docker 提供服务的文章 http://www.infoq.com/cn/news/2014/12/shopify-docker-experience

Shopify 是一个电子商务平台，提供专业的网上店面。目前的客户超过 12 万，包括 GE、特斯拉汽车、GitHub 等。作为首家市值超过 10 亿美元的加拿大网络公司，Shopify 在欧美市场的影响力也与日俱增。Shopify 是一个大型的 Ruby on Rails 应用，其产品服务器能通过给 1700 个处理核心和 6TB RAM 分配任务来完成每秒处理 8000 多个请求。Shpify 为了更加便捷、跨平台跨版本地进行分包任务，采用了时下炙手可热的 Docker 封装技术。近日，Shopify 在其博客上分享了自己的 Docker 技术使用经验。

官网上介绍的文章在 http://www.shopify.com/technology/15934308-docker-at-shopify-how-we-built-containers-that-power-over-100-000-online-shops

Terminal 视频录制与在线查看

kewin — Sat, 22 Nov 2014 15:22:24 +0800

在微博上看到有人推荐使用 Aaciinema https://asciinema.org/docs/getting-started 安装只需要使用 sudo pip install --upgrade asciinema Console 下操作录制只需要执行asciinema rec 当录制的视频操作结束时只需要 exit 即可将你的视频发布到 asciinema 上即可在线查看，很方便在线协作和在线教学录制 Record and share your terminal sessions, the right way.

Udemy 上的课程促销全部是 $10 截止到 11.28

kewin — Tue, 18 Nov 2014 14:47:48 +0800

YotaPhone is coming next season

kewin — Wed, 12 Nov 2014 10:04:30 +0800

Yotaphone 2 在 2015 年第一季度进入中国市场，YotaDevices 是俄罗斯的小米，将进入中国这一市场 YotaPhone

YotaRuby --- Route

《Pro Git》已发布 2014 版本了

kewin — Tue, 28 Oct 2014 22:20:05 +0800

git 官网今天 10.28 已发布最新的 pro git http://git-scm.com/book/en/v2 https://progit2.s3.amazonaws.com/en/2014-10-28-d7e0b/progit-en.56.pdf

Web Development Trends For 2015 And Beyond

kewin — Wed, 03 Sep 2014 12:01:29 +0800

Web Development Trends For 2015 And Beyond In this post, I will take a look at web development trends happening now and I would like to share my thoughts, observations and predictions for year 2015 and beyond. I have been working on Web technologies since early 2000, but last few years, I have been mainly involving with Cloud solution architectures. As a Web developer, I have worked on .Net, Node.js and Go technology stacks for developing Web apps and Web services. Recently, I have just looked on the Web technology and development trends as a whole, and I would like to share my thoughts and observations.

First, let me share some of the current trends I have observed on both usability and architecture.

Trends in Usability

Now days, user experience is getting more importance than ever before, and Responsive Web Design (RWD) is becoming a must have feature for web sites. RWD lets the end users browse web sites from multiple form factors, including mobile and tablet browsers. RWD can be replaced for some mobile web sites where we don’t have to develop separate web site for mobile users. This will work for some scenarios especially for developing web sites mainly focusses on presenting contents. But if you are building Web apps instead of Web sites, which is having lot UI workflows, RWD will not help you. Please keep in mind that Web apps and Web sites are different. Twitter Bootstrap and Zurb Foundation are the most popular RWD frameworks at this moment. If you are building apps that targeting mobile users, I highly recommend for using light-weight frameworks such as Yahoo Pure CSS.

Trends in Application Architecture A mobile-first strategy in the enterprises, impacted a lot in Web development architecture as well. When organizations are developing Web apps and Web services, they are aligning this with their mobile strategy. Now days, Web APIs are becoming central point of Web apps and Mobile apps, where developers are building RESTful services on the server-side and building the front-end apps for both Web apps and Mobile apps based on the RESTful services.

The Rise of API Driven Development

In the era of Mobile, APIs, oftenly RESTful APIs are becoming a key component of Web apps, and server-side implementations are becoming a thin layer with an API for data and security. These RESTful APIs are not only restricted to Web apps, but can also be used for Mobile apps. So that modern Web developers are writing their server-side code for both Mobile apps and Web apps, which has given more opportunity to Web developers. Another trend in this regard, is the rise of Mobile Backend as a Services (MBaaS) solutions on the Cloud platforms such as Parse and Azure Mobile Services. These MBaaS platforms are providing automatic REST APIs aginst the data models along with many mobile specific back-end services. We can use the MBaaS services for Web apps since these services are providing RESTful APIs and and also providing JavaScript SDKs for HTML5 clients along with native Mobile SDKs. In future, I strongly believe that MBaaS services will be widely used for both Web apps and Mobile apps.

Emergence of Single Page Applications (SPA)

When server-side implementations are limited with RESTful APIs, Web front-end development is moved to client-side with desktop like UIs on the browser where developers are rendering the UI on the client-side instead of server-side rendering. In SPA apps, our front-end will be simply using the RESTful API for the data and build the entire UI on the client-side. In this context, JavaScript becomes a key technology for building web apps. One advantage of SPA apps are we can easily package these apps as Mobile apps to multiple mobile platforms using a hybrid mobile container such as Phonegap and Trigger.IO. This is okay for small-size to mid-size Mobile apps where UIs are based on data forms. So we can use a single code base for building Web apps and Mobile apps.

In SPA based Web development, JavaScript is becoming a key technology, and JavaScript skill is more important than ever before. I have developed few SPA apps using different frameworks, and observed some challenges with this model. Here’s the challenges I have observed with SPA apps:

When we develop large-scale SPA apps, it would be very difficult to maintain the app comparing to everything we do with server-side. I feel that building larger JavaScript apps is really a challenge from the maintainability preservative. It would be very difficult to implement complex security models on the client-side, with different kind of authorization roles which is having different levels of access restrictions on the UI. My Observations on the SPA Frameworks Currently, AngularJS, EmberJS and Backbone are the most popular SPA frameworks used for building real-world apps. I have evaluated these three frameworks and developed apps with it. Based on my experience, AngularJS is more productive framework which is filled with enough features for building larger SPA apps. IMHO, using a MV* framework for front-end development is not a good idea and MVC doesn't scale at larger front-end apps. Now, we are using MVC for both server-side and client-side that I don’t think it as a good practice.

ReactJS — An Awesome Front-End Framework

When most of the SPA frameworks are living with traditional MVC paradigm, ReactJS provides a different approach for building UI on the client-side. React is a JavaScript library developed by Facebook and Instagram team, for building user interfaces. The entire front-end of Instagram web site and some parts of the Facebook web site was built with ReactJS. Interestingly, you can use ReactJS with other front-end frameworks such as AngularJS and EmberJS. You can use ReactJS as the view layer along with an MVC framework. But, in practice, I don’t recommend to use ReactJS with traditional MVC frameworks. ReactJS introduces Virtual DOM, which is awesome part of the ReactJS library and it enables high performance for the rendering the UI. ReactJS provides better performance for the UI rendering than MVC frameworks such as AngularJS and EmberJS. You can build re-usable UI components with the Virtual DOM abstraction and later we can compose these components on the actual DOM. Virtual DOM lets you use React for building UIs outside the browser. For an example, React team at Facebook, building a Objective C bridge for building UIs on iOS apps. For scaling front-end apps, we can use Flux architecture with React, which is basically set of architecture practices, that provides data flows in a single direction. I have evaluated BackboneJS, EmberJS, AngularJS and React and I highly recommend React for building user interfaces.

Trends in Server-Side Web Technology Stack in 2014

Few years back, dynamic type languages such as Ruby and Python had been attracted lot of start-up companies. Ruby on Rails was really a revolution in Web development until few years back. Many start-up companies had developed innovative products in RoR and Python Web frameworks. Now days, the interesting thing is that, these apps are re-engineering to other Web technology stacks due to performance and scalability challenges. Using a dynamic type language for larger apps, is like having a drink with too much sugar. Initially, the sugary feeling would be attractive, but for long period, it can be harmful to the health of apps. This year, we have seen lot of Node.js adoption in the enterprises especially for building for back-end services for high profile Mobile apps. Larger enterprises such as LinkedIn and Walmart, are using Node.js for powering their Mobile back-end services. As a new technology, Node.js is really a winner in the adoption market of the year 2014. Node.js is a preferred technology stack for building Mobile Backend as a Services (MBaaS) solutions on the Cloud. And this year, we saw lot of Node.js based CLI tools used for front-end development. The rise of Node.js and the fall of Ruby stack are the most notable trends in this year.

Here’s the some of the observations on the server-side Web stack:

Ruby stack in generally and RoR in specifically is losing its momentum and larger Rails apps are re-engineering to other stack. The trend of using a dynamic language (Ruby and Python) for Web development is gradually losing its attention. Node.js is getting lot of adoption for building back-end RESTful services especially for Mobile space. Emergence of Node.js based CLI tools for front-end development. Microsoft .NET Web stack is going to a big paradigm shift with open specification OWIN – Practically, it is best of both ASP.NET and Node.js.

Emergence of real-time web apps.

Predictions for 2015 and Beyond

Which technology will dominate in the year 2015? Which technology will lost its momentum? I strongly feel that the era of using dynamic languages for Web development, is going to end. Then, will Node.js continue its momentum in the new technology adoption market? I don’t think so. Since 2011, I have been mostly writing code in Node.js and had planned for writing a book on the same, but dropped that plan later. Recently, I left from Node.js platform for the following reasons:

Node.js is always highlighted as a technology for building high performance apps, but it’s take on Performance over usability and maintainability is the biggest challenge for building larger apps and I predict that many larger Node.js apps will fail with maintainability problem in near future, and the era of hype over Node.js is going to end. The callback hell. I know that generators and promises are good solutions for solving the callback hell. Framework such as Koa.js provides some kind of solution for the same at the cost performance impact. But for me, it is hard to solve many of my problem.

The JavaScript language is also a problem for me. JavaScript is not a good language for building large-scale apps. Node.js is a minimalist platform. For me, it is good for building JSON based REST APIs and real-time systems. I want to develop variety of apps using a single technology stack. The point is that Node.js fails when CPU crunching logic is executes.

Some of my problems with Node.js will be the problem of some people and it is having many pragmatic problems with error handling, debugging and usability. I believe that maintainability will be the big challenge of larger Node.js apps. If you are building RESTful services on the Node.js, I highly recommend for using Hapi.js framework, developed by Walmart, which is really a good framework. I greatly appreciate Eran Hammer, who was the creator of Hapi.js.

On 2015, I bet on Go programming language, not just for Web development, but as a technology ecosystem for building distributed apps. For me, Go was far better choice than Node.js. On 2015, I predict that many Ruby and Node.js developers will move to Go.

Here’s my few predictions for year 2015 and beyond:

Re-engineering of Rails apps to other stack will reach at peak level for performance-critical web apps. The era of using dynamic languages for Web is going to end at least for performance critical apps. Many Node.js apps will suck with maintainability problems. Performance over usability and maintainability might fail for Node.js. Go will emerge as a general purpose programming language which will also attract web developer community. Go is a good replacement for both Java and Dynamic language and also for Node.js community. Go can become the next big language on enterprises after Cobol and Java, but it will take some time. Go is a language of the Cloud era. Java and .Net stack will continue its momentum on mid-size to larger enterprise apps, but it will gradually fall on web development. Go : Technology of 2015 and Beyond Recently lot of good apps are being developed with Go, which including Docker and Packer.IO. I predict that Go will get lot of attraction from different developer communities including Java, Ruby, Python and Node.js. Go is a static type language while providing the flexibility of dynamic type language’s productivity. In Go, con-currency is a first class citizen in the core programming language. Like C and C++, Go compiles to native machine code and unlike Java and .Net, it don’t need any JIT compilation. I fall in love with Go’s simplicity and it’s pragmatic design and the package systems are really good. It may not be good idea to use Go for building traditional Web apps, but it is good for building HTTP servers for providing RESTful services. In future, you might be able to use Go for building Android apps. The advantage of Go is that it is a general purpose programming language, which can be used for any possible scenario — including systems programming and for larger distributed business apps. I strongly feel that Go is the language of distributed, con-current and parallel computing in the era of Cloud. Go can become the next Java in the enterprises.

link referer https://medium.com/@shijuvar/web-development-trends-for-2015-and-beyond-c2d3c1ef5718

DigitalOcean 开始大促销

kewin — Mon, 01 Sep 2014 14:30:21 +0800

一年一度的 DigitalOcean https://www.digitalocean.com/?refcode=01fdfc195565 开始了大促销高性能的 SSD 的磁盘和无限的带宽，全球多个机房，距离中国最近速度比较快的的有新加坡机房

Easily deploy an SSD cloud server on @DigitalOcean in 55 seconds. Sign up using my link and receive $10 in credit: https://www.digitalocean.com/?refcode=01fdfc195565