Open Source

Open source thrives when people come together. Not just to write code, but to solve problems, share knowledge, and build software that benefits everyone. Scattered across the globe, contributors bring wildly different priorities, personality, and communication styles to the table. While conflict is inevitable, how a community handles that conflict is what separates the oens that thrive from the ones that implode.

Be Helpful by Default

A drama-free community isn’t one without debate, but it’s one where the core principles of: be helpful, be human and be honest create the conditions for successful collaboration.

In today's digitally competitive world, startups want to move fast with controlled costs. The technology stack, commonly known as Tech stack, is the key to balancing speed, scalability, and running costs. There are many web development frameworks out there, but React is the one favored by most startups and for good reasons. 

This blog will discuss how React is a cost-effective solution for startups, including the benefits of React and why they must opt for it to build their applications.

The third feature release of Drupal 9 recently became available. New features and improvements in Drupal 9.3.0 include:

This is old news but I thought still worth mentioning. Last month Drupal 8 reached its end-of-life. This means that all versions of Drupal 8 core and Drupal contributed project releases that are compatible with only Drupal 8 have been marked unsupported and are no longer supported by the Drupal security team.

Drupal 8.0.0 was first released on November 9, 2015. The last version was released on November 17, 2021. With the end of life approaching, I also updated my two websites from Drupal 8 to Drupal 9.

Back in February I wrote an article saying how I believed Google AMP has been imposed on the web by Google as a ‘standard’ for developing fast webpages, and my dismay about that. Google apparently developed this as an internal project without any open collaboration, and avoiding the W3C standardization processes. Google made implementation of Google AMP a requirement to show at the top of the search results for common news searches.

To many of us open web folk, Google’s AMP violated the widely held principle of search engines not putting bias into search results, and/or the principle of web standards (take your pick – it would not be bias if it was a standardized approach that the wider web community had agreed upon).

Appropriately, for the wildly popular CMS, it all started with a blog post. Way back in January 2003, Matt Mullenweg, the co-creator of WordPress, wrote a short blog on his website, lamenting the lack of updates from his preferred blogging software, b2/cafelog.

Despite becoming increasingly popular since its release in 2001, b2/cafelog’s developer stopped maintaining the software in 2002, seemingly disappearing completely from all community forums.

Like others in the IT community, I have become increasingly concerned with Google's behavior with their AMP technology.

For those who aren't really aware what AMP is, it's Google's proprietary solution for speeding up mobile pages. Webmasters implement AMP, which is a kind of Google-sanctified and Google-code-driven version of your webpage. It works very well and solves an important problem. Often when you search Google on a mobile device it will show AMP articles at the top of the results, so you get access to fast content first, which is reasonable in and of itself.