At work our internet connection is painfully slow for the moment while we sort something better out and I ran into a rather interesting quirk whilst using Composer and timeouts.
I was trying to install Laravel and because of the sheer number of components it got part of the way through and then would display some error message about exceeding the timeout limit of 300 seconds (5 minutes).
The reason for this appears to be due to the fact my Internet connection is mega slow and some components being largish in size. When calling composer update or composer install you just need to specify a higher timeout value.
Currently Bootstrap is still the preferred choice for prototyping web applications and rapidly getting a MVP out the door. As great and undeniably helpful it is, Bootstrap is far too opinionated to be a viable front-end CSS solution for a lot of people. It throws the kitchen sink at you and its default style.
There are numerous themes for Bootstrap and means of creating your own styles, but as someone who’s now worked with Bootstrap quite extensively, it feels like you’re constantly overriding base styles (even using Bootstrap Sass won’t help you).
Newcomers to Node.js will have run into this issue a couple of times. You get your setup working, you’ve built a little application and on your server you start your Node app, but then you close the terminal window and your application stops.
When I first started using Node.js, this is the first thing I Googled, “How do I keep a Node.js app running after I close the terminal console?”
Chances are you are living in the past or working on a project that was built in the past that is still marking up content using DIV tags instead of semantic tags like article and section.
Don’t get me wrong, there is nothing wrong with using DIV tags and there will always be a use for them, some pieces of content should be marked up using tags with semantic meaning. They’re not only cleaner, but also help bolster your chances of ranking better on the likes of Google.
Everyone wants to build the next Facebook, the next Google, the next Instagram and the next big thing. The harsh reality is that only a handful of people every so often actually make it. For every Mark Zuckerberg there are probably tens of thousands of entrepreneurs toiling away in cafes, the early hours of the morning and weekends who end up not “making it” presumably because only a very small percentage of entrepreneurs actually do.
If you’re like a lot of developers out there, you start your projects off with the best of intentions. No developer ever says, “I am going to make this project a fucking mess, a cluster-fuck of spaghetti code that even I’ll struggle to read in 2 weeks, let alone any other developer”
We’re living in the golden-age of front-end development. We have tools, we have awesome methodologies like BEM and CSS pre-processors like Sass. And for all that automation without a proper structure, our CSS always ends up being unorganised and messy.
For some time now there has been a slowly growing movement amongst particular designers and developers against WordPress. We’ve seen light CMS’s, decoupled PHP frameworks, open source alternatives and the big one: static site generators, but no matter the alternative, it seems it’s for the wrong intentions.
What WordPress Is Firstly, WordPress is a content management system that started out as a blogging platform. I’d actually argue WordPress is a framework of sorts in that it provides you with; user authentication, plugins sytem, themes system, helper classes and a loose structure which it expects you to follow (but isn’t overly strict on).
For some weird reason, this very blog has started getting a lot of traffic the last few days, from Google. I wonder if Google have recently tweaked their search algorithm again?
I have been trying to update the blog on a more regular basis, I’ve been posting two, sometimes three posts a day and I have been focusing on making the quality of them as decent as I can.
Perhaps I am experiencing the effects of a previous search engine algorithm change, and my recent updates have put me into the upper-echelon of Google’s almighty preference circle.
Firefox has supported CSS variables since version 29 and at present, no other browser supports them. In version 31 of Firefox, Mozilla are once again first to implement the latest working draft from the W3C for CSS variables. You can read the post about the addition to Firefox here.
All I have to say is, who the hell over at W3C came up with the syntax? I am very disappointed that the syntax doesn’t follow that of another language like, I don’t know, Javascript or perhaps you know, implemented similar syntax to that of Sass or Less.
First things first, I am not a Ruby on Rails veteran. I am fairly new to the framework, but have dabbled with Ruby before and understand it. Take this post with a grain of salt, this isn’t a debate or article putting down X language or X framework.
I see Ruby on Rails and Node.js compared so much and this question being repeatedly asked in every crevice of the Internet I thought I would take a stab at clearing up any confusion about making a choice.