Hello Monday | |
Awwwards Agency of the year for the second time. | |
Word Map | |
Combination between Google-translate and Wikipedia for visual links between words in world languages. |
CSS Reference | |
An extensive CSS reference with all the important properties and info to learn CSS from the basics. | |
Transformicons | |
Animated icons, symbols and buttons using SVG and CSS. | |
SVGOMG | |
SVGO's Missing GUI (tool for SVG optimization). | |
Sublime Productivity | |
(book) all about being more productive with sublime text 3 (writing in progress). | |
Services Engineering Reading List | |
A reading list for services engineering, with a focus on cloud infrastructure services. | |
DebOps | |
A collection of Ansible playbooks for Debian, scalable from one container to an entire data center. |
RubyDNS | |
Intercept and modify DNS requests, provides most typical DNS server functionality. | |
Trello-ems | |
Use Trello to generate your email newsletters, inspired by TheChangelog workflow. | |
Frontend.md | |
A command line tool which generates documentation for your existing frontend code. | |
SANE stack | |
Sails and ember with docker and cli tools. | |
is.js | |
Check types, regexps, presence, time and more. | |
Taucharts | |
Free open source D3.js-based library for charts. Yeah there is always space for more of those. | |
Vivaldi | |
From the makers of Opera this is a new web browser. |
What’s New in systemd, 2015 Edition | feb 1 |
Note from the talk of Lennart Poettering at Fosdem. | |
Transitioning to SCSS at Scale | feb 2 |
How Etsy migrated from simple CSS to SCSS. | |
New Methods in Ruby 2.2 | feb 2 |
GC upgrades are not the only niceness in the new ruby 2.2. | |
Incremental Garbage Collection in Ruby 2.2 | feb 4 |
RincGC achieves short GC pause times compared to Ruby 2.1. | |
Ruby Concurrency and Parallelism: A Practical Primer | feb 4 |
various techniques and approaches that are available for concurrency and parallelism in Ruby. | |
Announcing the Interest Graph API | feb 4 |
Prismatic opens a public API to query their interest graph. | |
Authentication and API’s in the SANE Stack | feb 4 |
For single page application, oauth2 can be confusing. | |
Display Time Relatively in Angular | feb 4 |
Use momentjs lib for nicer date displays. | |
YouTube API, Version 3 on Rails | feb 6 |
Ruby client that works with v3 of the youtube api. | |
Getting Started with Less | feb 6 |
CSS pre-processors are not that hard, just dive in. | |
Spriting with | feb 6 |
Sprites aren't limited to background-image, with the object-fit and object-position properties. | |
Tree Structures in your Rails models | feb 7 |
Tree structures are needed any time you want to insert a hierarchy into your data. | |
Do It All With Ruby | feb 7 |
A glimpse into the broad spectrum of what Ruby is capable of. |
React.js Conf 2015 - Hype! (31m) | feb 2 |
Interesting use-cases of usage of react.js. | |
GoRails 41 (16m) | feb 5 |
Soft Delete with Paranoia. |
Web Platform Podcast #28 (58m) | jan 28 |
Securing our Web Applications. | |
Web Platform Podcast #29 (1h06) | jan 28 |
Reactive Extensions. | |
Giant Robots 132 (38m) | feb 1 |
Story Tellers (Adarsh Pandit, Kyle Fiedler). | |
Fullstack Radio 8 (58m) | feb 2 |
Ember and API First with Sean Devine. | |
Developer tea 13 (10m) | feb 2 |
Flexibility. | |
Ruby5 #525 (6m) | feb 3 |
Loaf, New RSpec Signing Certificate, Replace coffeescript with ES6, RSpec new site, Require only what you require, Rikki - the robot, Pry-remote and Vagrant. | |
Ruby5 #526 (6m) | feb 3 |
Ruby Concurrency, Sitemap with Rails, Ember.js with Rails, New Methods in Ruby 2.2, Robot, You Have One Job. | |
Developer tea 14 (16m) | feb 4 |
Daniel Kao - Self Control: Cutting Sugar for a Year, and Starting a Career in Something You Have No Experience in, On Purpose. | |
RubyRogues 193 (1h13) | feb 4 |
The Volt Framework with Ryan Stout. | |
Javascript Jabber 145 (1h06) | feb 4 |
Meteor.js with Matt DeBergalis. | |
Ruby on Rails podcast 183 (1h02) | feb 4 |
Sean Devine Interview on Full Stack Radio about API-First Development. | |
CodePen 34 (49m) | feb 4 |
Questions and answers. | |
The ship show 53 (55m) | feb 5 |
Developing CareerOps. | |
The Cloudcast - ByteSized - 1 (4 bytesized) | feb 5 |
Git & GitHub, Config Management, CI/CD, Containers. | |
Adventure in angular #28 (37m) | feb 5 |
Isomorphic JavaScript with AngularJS with Jeff Whelpley. | |
Developer tea 15 (8m) | feb 6 |
Code Kata - A Practice Arena for Becoming a Better Programmer. | |
The Changelog 140 (1h11) | feb 6 |
Aurelia, Durandal, and leaving AngularJS with Rob Eisenberg. |
Last week Green Ruby was sent with a delay. For some obscure reason my publication was blocked by Omnivore the automated fraud detection system from Mailchimp. My account was instantly blocked and it was pending a human review. Of course the human review made it clear that the publication was clean but it took 2 days and I still don't know why this omnivore beast went mad at me.
They declare it's getting smarter everyday, but really, we are still safe. The reign of the intelligent computer over the human species is not close yet.
Dynamic websites are great. But that's a long time I wonder about the trade-off. If you update your blog every day, and have 500 visits, your dynamic setup is useful when you edit, and it's a cost for each visitor. There are so many web applications that could be more clever about it. Especially that now the computation is going more and more client side.
Static pages have a really unbeatable response time, their security is really reliable, they are low dependencies and easy to deploy with a rsync.
When I get to think about making a new website, I always ask myself if it's an application or a website. For sure some kind of applications are computation intensive. Making it all dynamic could make sense. But frankly, if it's a website, it can have some fancy dynamic features without a huge dynamic setup.
I have seen so many websites made with php, mysql, 5 tables and 20 entries in each. Such site should have pre-generated content, data available as static json files, as a bit of js to make the magic happen. If there is a lot of data, fine, an API server makes sense.
So next time you gotta prepare a website, ask yourself how easy it could be to generate it and use tools like Jekyll or Middleman. Or you can even handle things with custom rake tasks (like I do for Green Ruby website), that's not that hard. It's a matter of cyberspace ecology.