veilleinfo

dev front-end, back-end, code, ebook, IT

[veilleinfo]

My Heroic and Lazy Stand Against IFTTT (Pinboard Blog)

http://ift.tt/22IIKSL Because many of you rely on IFTTT, and because this email makes it sound like I'm the asshole, I feel I should explain myself. In a nutshell: - IFTTT wants me to do their job for them for free - They have really squirrely terms of service via IFTTT

[veilleinfo]

d’Oh My Zsh - How I unexpectedly built a monster of an open source project

http://ift.tt/1UO0OWM This wouldn’t be my first foray into open source software; nor my last. It was the summer of 2009. I found myself helping a coworker debug something in their terminal. As I attempted to type in a few command lines, I noticed that the prompt wasn’t responding to the shortcuts that my brain had grown accustomed to. Frustrated, I exclaimed, “when are you finally going to switch over to Zsh?!” via IFTTT

[veilleinfo]

Project: Raspberry Pi + Alexa Voice Service

http://ift.tt/1MAP6XD This project demonstrates how to access and test the Alexa Voice Service using a Java client (running on a Raspberry Pi), and a Node.js server. You will be using the Node.js server to get a Login with Amazon authorization code by visiting a website using your computer's (Raspberry Pi in this case) web browser. via IFTTT

[veilleinfo]

Pub et presse en ligne

http://ift.tt/1VMxOhJ Depuis une semaine environ, de nombreux éditeurs de contenus français ont conjointement lancé une campagne anti-bloqueurs-de-pub. Après observation de ses méthodes et de ses effets de bords, je crois pouvoir affirmer que c'est absolument catastrophique. Autour de moi, ceux qui n'utilisaient pas encore un bloqueur de pubs sont en train d'en chercher un ; ceux qui en utilisaient un sont souvent suffisamment avancés pour contourner facilement et rapidement les blocages. Mais revenons un peu sur les sites en question via IFTTT

[veilleinfo]

Micropackages and Open Source Trust Scaling

http://ift.tt/1T7DlP5 What frustrated me personally about this conversation that took place over the internets about the last few days however has nothing to do with npm, the guy who deleted his packages, any potential trademark disputes or the supposed inability of the JavaScript community to write functions to pad strings. It has more to do with how the ecosystem evolving around npm has created the most dangerous and irresponsible environment which in many ways leaves me scared. via IFTTT

[veilleinfo]

require-from-twitter

http://ift.tt/1LIuH80 Since Twitter doesn't have an edit button, it's a suitable host for JavaScript modules. via IFTTT

[veilleinfo]

Foundation for Emails 2 is Here

http://ift.tt/1VF2Xnc It's time. Foundation for Emails 2, the successor to Ink, has landed ashore! When Ink first launched in 2013, it made HTML email development suck less by giving developers a full responsive grid and set of components that worked right in any email client - even Outlook. Ink was the first product to take email best practices and create a framework out of them. Since then, companies of all shapes and sizes - Airbnb, Vice, Express, the Golden State Warriors - have been using Ink to easily produce great email campaigns. Now, with Foundation for Emails 2, we're streamlining email development workflow even more. via IFTTT

[veilleinfo]

kik, left-pad, and npm

http://ift.tt/1LIgzff Earlier this week, many npm users suffered a disruption when a package that many projects depend on — directly or indirectly — was unpublished by its author, as part of a dispute over a package name. The event generated a lot of attention and raised many concerns, because of the scale of disruption, the circumstances that led to this dispute, and the actions npm, Inc. took in response. Here’s an explanation of what happened. via IFTTT

[veilleinfo]

Dirty Tricks From The Dark Corners Of Front-End

http://ift.tt/1pvk1z9 In this talk, Vitaly Friedman, editor-in-chief of Smashing Magazine, will present dirty practical techniques and clever ideas developed in actual real-life projects, and use many examples to illustrate how we can solve problems smarter and faster. Please take the techniques with a grain of salt. Beware: you will not be able to unlearn what you’ll learn in the session! via IFTTT

[veilleinfo]

The web on my phone

http://ift.tt/1S6CzwV I’d like to be able to use Chrome, Firefox, or Opera on my iPhone—real Chrome, real Firefox, or real Opera; not a skinned version of Safari. Right now the only way for me to switch browsers is to switch phones. Switching phones is a pain in the ass, but I’m genuinely considering it. via IFTTT

[veilleinfo]

Should you have defaults styles for `table`?

http://ift.tt/1KNn2F6 We front-end devs decided this is best because it means we can easily style custom tables without having to override any default styling. This includes having to override media queries that reduce padding on smaller screens, which would be annoying. We also think it would be important to have a selector on these content tables in case we need to implement JavaScript solutions like responsive table plugins. via IFTTT

[veilleinfo]

Microsoft Has Just Blackmailed Linux Twice in One Single Week and the Media Didn’t Notice or Just Ignored It Because of Microsoft’s Charm Offensives

http://ift.tt/1RClwTh Microsoft loves Linux enough to strangle it to death with patents while the media isn’t paying attention and instead telling us that Microsoft is now a buddy or “pal” of GNU/Linux via IFTTT

[veilleinfo]

The complete guide to transforming your desk into a peaceful, productive place to work

http://ift.tt/1pQTmxl Unless you’re already a creative genius, having a helter-skelter work space is likely to hinder you from feeling productive, happy, or inspired. But working at a desk that’s too impersonally tidy can be just as fruitless. Luckily, Quartz is here to help get things in order and set you off on a path of organizational triumph. via IFTTT

[veilleinfo]

PX, EM or REM Media Queries?

http://ift.tt/1Ve4uQO Have you wondered if you should use px, em or rem for media queries? I had the same question too, and I never figured it out, not till now. via IFTTT

[veilleinfo]

The copy & paste guide to your first Service Worker

http://ift.tt/1XKHOXd There are a lot of tutorials on the web for Service Workers (many of which are very good), but there's a lot of reading too. So, this is me throwing my hat in with the fast and loose: copy & paste guide. via IFTTT

[veilleinfo]

watching your projects

http://ift.tt/1RwXzw9 I'm a big fan of having an "automated build step" as part of the development workflow for a project. Figured I'd share what I'm currently doing with my Node.js projects. What is an "automated build step"? For me, this mean some "shell" code that gets run when I save files while developing. It may not actually be "building" anything - often I'm just running tests. But the idea is that as I save files in my editor, things are run against the code that I just saved. via IFTTT

[veilleinfo]

UI components for Elasticsearch - Searchkit

http://ift.tt/1Rd3bQg Searchkit is an open source project developed and maintained by Ten Eleven and released under Apache v2 licence. Searchkit is a suite of React components that communicate directly with your Elasticsearch cluster. Each component is built in React and is fully customisable to your needs. via IFTTT