Making software development greener | Computer Weekly
Summary
“When I was writing websites – this was before .Net came along, and in classic ASP [active server pages] – you had to write all your own objects.” When people used to visit websites via a low-bandwidth, dial-up modem connection, he says: “You had to be conscious about the size of the image, stylesheets and page sizes; you had to be conscious about how much data you were sending down the pipe because load time was important.” For Powell, from an application development perspective, this meant that developers considered code efficiency. This has led to code bloat, where developers no longer focus on writing software that runs as efficiently as possible and uses the smallest footprint of storage, memory and processing power. Mav Turner, chief product and strategy officer at Tricentis, points out that code bloat typically stems from several sources, such as overly verbose syntax, redundant or unused features, and lack of optimisation during development. Speaking at KubeCon + CloudNativeCon in Paris in March, Gualter Barbas Baptista, lead consultant for platform enablement and strategy at Deutsche Bahn, discussed the rail operator’s ongoing efforts to monitor and minimise the ecological impact of its cloud-based applications. In a panel discussion at the KubeCon + CloudNativeCon event, Chuck Dubuque, head of direct product marketing for OpenShift at RedHat, warned that artificial intelligence (AI) is driving Kubernetes to somewhere it has not been before.