Dev
- Python versus Go versus Rust: A subjective, primarily developer-ergonomics-based comparison – Python developer Nicolas Hahn shares his experiences writing a program in the three languages. He found Python lean, Go less fun, and Rust more complex—but ultimately concludes, “In the end, this comparison is a bit silly, because though the use cases of these languages overlap, they occupy very different niches.”
- Python vs Node.Js: Which Programming Language to Choose? – Every project has its specifications and demands. And when you’re building an application, it’s most important to choose the right technology to code it. In this article, we’ll look at Python vs. Node.js to learn about their benefits, downsides, and use cases so you can make an educated decision about which one is best suited to your project.
- The cost of JavaScript in 2019 – The last few years have seen a big improvement in how fast browsers can parse and compile script. Today, the dominant costs of processing scripts are now download and CPU execution time. Addy Osmani explains.
- My reflections on Golang – Do I like Go? Yes. Would I use it for every use case I have? Definitely not.
- Smaller objects = more memory – Python consumes a lot of memory. Here’s how to reduce the amount of RAM needed by reducing the size of objects.
Ops
- Serverless is not just “functions as a service” – Although serverless is becoming increasingly popular, there are still misconceptions about what it is and what it’s good for. If you’re new to this technology, this post covers serverless fundamentals—along with tips and resources to get you on your way.
- Powerlisp: A Common Lisp tool for automating tasks for Unix power users – Why Lisp, you ask? “Well, because [creator Lucas Vieira] could, and also to prove a point. Most tools nowadays are written in JavaScript or Python, two languages which can be much slower than Common Lisp at times. However, Common Lisp is a perfectly functional and powerful language, albeit a little old.”
- The case for making the transition from sysadmin to DevOps engineer – “The path you must follow to get to DevOps is paved with many twists and turns as you learn the new technologies and tools needed to support the ever-changing environments the new DevOps way. So what is it like, or how can one transition from the system administrator mentality and world to the way of DevOps?” asks Taz Brown. “Not surprisingly, this process begins with your thinking. It is not easy to change the way you have been doing things the last 10 or 20 years, but it’s mandatory.”
tail -f /dev/misc