> While JinjaSQL can handle insert/update statements, you are better off using your ORM to handle such statements. JinjaSQL is mostly meant for dynamic select statements that an ORM cannot handle as well.
This is a fantastic anecodote and after the year we've had I'm finding the challenges people are having from entering Linux are becoming less and less.
Earlier today I marvelled at running a game through Steam whilst listening to streaming music through Spotify whilst being able to switch window into bash.
I recently bought a new laptop and dual boot Windows 8 and Ubuntu 13.04. It took me 3 hours to get all the drivers working in Windows whilst the only issue I had with Ubuntu was the fact my video card drivers (ofcourse, Nvidia) were going to be proprietary.
Locks and Alarms are the lowest common denominator of security - it stops people from walking in but more than anything just gives an illusion of security.
I think there is more to it than a buzzword though, the HTML5 way of doing web ie, paving the cow paths is radically different to the methodologies of XHTML, such that the range of technologies to be born/adopted out of that paradigm shift could be thought of as HTML5 era technologies.
As an Australian, I welcome this wholeheartedly. It has been extremely frustrating watching the payment revolution in the states, whilst at home there is next to no alternative to getting a merchants facility through a bank up until now. It will also be nice dealing with an API that isn't stuck in the 90s.
I remember early on in my web development career to make sure you are selling a service not a product. You aern't building a website - you are providing a marketing service, requiring expert advice and a component of that service is building a website. As people have said, websites are easy - Wordpress + theme + hour of time and you are done.
Sell your knowledge of digital marketing - SEO, Adwords, etc in order to drive sales for your client, which is ultimately the reason they want a website in the first place.
If you place rate limiting on email accounts by default and then for the lower percent of users that need a higher rate do it on a case-by-case basis. In my experience most users that fall victim to these types of phishing attacks do not need to send high volumes of emails.
What exactly makes it impractical to do powerful things? You may have disdain for certain language features but I don't understand how that makes it impractical.
Most of the tech demo's we're seeing coming out of the JS crowd are from people who have only just started using the WebGL API (which is still experimental). I'm extremely excited to see the things that experienced OpenGL developers will be able to do as the API becomes more mainstream.
I would consider that a contradictory statement. In order to provide the best range of browser support it is usually necessary to not code to web standards to support older browsers (that do not support latest web standards) or to support newer features (vendor specific CSS, etc).
We're not necessarily talking about "experienced" developers. I know plenty of people who have set up their own self-hosted WordPress instances for their personal blogs who don't know how to how to self-manage a VPS.
Keep in mind not everyone who uses or even installs software is an "experienced developer".
If HATEOAS implementation was more widespread the biggest advantage would be the ability to create standard libraries for API calls rather than thin wrappers for every language. Your API would also be more or less self-documented, hopefully making it easier to navigate for humans and machines alike.
I am curious as to why this can't be handled at a HTTP level with OPTIONS? Could I not OPTIONS query a URI, and receive a list of supported HTTP methods (GET, POST, PUT, etc) that are available on this resource?
Chris Coyier has a great blog entry [1] on using and creating custom fonts but Font Squirrel [2] is my tool of choice for generating cross-browser font files and the markup to embed them.
Whilst using CSS pseudo elements to generate shapes is useful, I believe it's ill suited to iconography when the better solution is to use a custom web font. We've had a lot of success here recently, being able to create cross-platform, vector icons with minimal problems with maintainability.
I think you've misunderstood the post. There are jobs available to work on "big things" and there are jobs to work on "small things". Job advertising provides a really nice set of domain specific data to work out why people are more likely to work on the "small things" then the "big things". Jason's concluded that from the data they have available that they can see that people find geography to be more important to the job they choose then the satisfaction from working on the "big things".
As a Windows to Linux convert for the past 5 years I actually enjoyed this parody due to some of the points he brought up that make me facepalm every time I use Windows. I don't know how many times I've cursed Microsoft over not recognising alternative file systems, then to realise I can't even get straight back into Linux because my boot loaders been replaced!
I converted from Windows to Ubuntu bout 4 years ago and haven't looked back. The Unity UI in my mind is just as visually appealing to a consumer as OSX's (which might be a slightly controversial opinion!)
In terms of IDE, I think it really depends on what you are using it for. I've been using Cloud9, a web-based IDE, quite extensively recently for Javascript work but you still have your standard Eclipse and NetBeans, which are both fairly extensible. You might also consider taking a jump into Vim.
The great thing about Ubuntu is the ability to create a USB Live Distro. Road test it before committing if you are worried. But I don't think you'll be looking back :)
[1] https://github.com/hashedin/jinjasql#when-to-use-jinjasql