bchen | 8 years ago | on: Angular 5.1 and More Now Available
bchen's comments
bchen | 9 years ago | on: The end of the clearfix hack?
bchen | 11 years ago | on: Google Maps Pacman
bchen | 11 years ago | on: Microsoft takes .NET open source and cross-platform
bchen | 12 years ago | on: Open-Source Static Site Generators
So far, what I can tell is that Middleman provides a more efficient workflow than the database-driven CMSes I have used in the past.
bchen | 13 years ago | on: Sass Style Guide
> List "Regular" Styles Next
> List @include(s) Next
Depends on what the @include gives you, I would either treat @include the same as @extend and put @include after @extend, or just treat @include as regular styles and mix them together. The reason for this is that I generally organize my styles by listing block styles first and then the text styles. It would mess up this organization if all @includes that set only 1 property are listed the last.
bchen | 13 years ago | on: Play an accordion recording by resizing your browser window
bchen | 13 years ago | on: John Resig's ‘Secrets of the JavaScript Ninja’ has been released
bchen | 13 years ago | on: GitLab 4.0 Released
For my company, however, Gitlab makes a lot of sense. We have a large number of small and close source client projects to manage. We don’t want to pay for file hosting, e.g. $50 a month for 50 repos, when each repo is tiny and we can easily and cheaply host them. GitHub Enterprise is also out of question, as it is not very affordable by a small company.
Cost factor aside, Gitlab does have advantages over GitHub. Legal requirement is one, and the ability to integrate with other tools in the company is also quite nice. Although this feature has not been implemented yet, I look forward to the ability for Gitlab to integrate with Jenkins and display build status.
I will continue to use GitHub for personal and open source projects. For client work, Gitlab will be the one I use.
bchen | 13 years ago | on: Gitlab
- I used RVM to install Ruby 1.9.3. This should be fairly straightforward.
- adduser command has a different interface on RHEL, but it shouldn’t be hard to figure out.
- I used Apache ProxyPass instead of Nginx. unicorn.rb needed to be updated to listen on a tcp port instead of a socket file.
- Supplied init.d script did not work out of box. Some modifications were required.
- Redis server was installed from REMI.
Let me know where you’re stuck and I can try to help you.
I agree that Gitlab is not very easy to install, as there are many complicated steps. The benefits of having a free private GitHub, though, were totally worth it.
bchen | 13 years ago | on: JetBrains Doomsday Sale - 75% off for 24 hours only
bchen | 13 years ago | on: How Lanyrd moved from AWS to SoftLayer and MySQL to PostgreSQL with no downtime
bchen | 13 years ago | on: Embrace the Static Web with Punch
- you can source control your blog content
- update your blog without ever leaving command line terminal or having to use less productive web interface
- use markdown, textile, html or whatever suits you
- easy to host and easy to scale
- no need to feel obligated to apply security patches
For me these are great reasons to migrate away from WordPress, Drupal and so on.
bchen | 13 years ago | on: Named Parameters in Java
> o.doSomething1("Alfred E. Neumann", "http://blog.schauderhaft.de, 42, "c:\\temp\\x.txt", 23);
As other commenters have pointed out, I think the builder pattern is one of the two solutions I would use. The other solution is to simply create an object that represents the values to be passed in to the method. Consider:
User user = new User("Alfred E. Neumann");
user.setLink("http://blog.schauderhaft.de);
user.setUltimateAnswer(42);
user.setTempFile("c:\\temp\\x.txt");
user.setZip(23);
o.doSomething(user);
Even with named parameters, I would say the latter approach is still superior than having a long parameter list.bchen | 13 years ago | on: Mountain Lion seems to have addressed the memory management issues in OS X
bchen | 14 years ago | on: Daring Fireball: iPad (3)
Regarding repurchasing apps, it may be a good thing. There are plenty of good iPad apps, which fully take advantage of the tablet form factor. Although I have not used many Android tablet apps to prove it, Tim Cook should have good reasons to criticize about tablet apps on Android.
bchen | 14 years ago | on: Wikipedia blackout page
There are certainly some issues with Angular. For example, starting Webpack Dev Server is really slow (a minute or longer). Running a lot of tests with Kharma can be slow. If you know what the issues are and can either live with or work around them, then it is not that bad.