Skip to content

Conversation

@sumitshinde-84
Copy link
Collaborator

Description

Related Issue(s)

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created (instructions)

@netlify
Copy link

netlify bot commented Jan 23, 2026

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit a9ef524
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/697374522450f9000858d919
😎 Deploy Preview https://deploy-preview-4436--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 83 (🟢 up 23 from production)
Accessibility: 80 (no change from production)
Best Practices: 100 (🟢 up 8 from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Jan 23, 2026

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit e50ccfc
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/697398e62bf8df0008b92b25
😎 Deploy Preview https://deploy-preview-4436--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 88 (🟢 up 31 from production)
Accessibility: 80 (no change from production)
Best Practices: 100 (🟢 up 8 from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

@andreguerra7 andreguerra7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sumitshinde-84 Approved, please check my first comment


<!--more-->

Yet in 2026, new equipment still ships with Modbus as the primary interface. Not tucked away for backwards compatibility: front and center as the deliberate first choice.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sumitshinde-84 suggestion Not tucked away for backward compatibility, but front and center as the deliberate first choice

---
title: "Why Modbus Refuses to Die"
subtitle: "Why your factory's newest equipment still speaks a 46-year-old language"
description: "Learn why Modbus, a 46-year-old protocol with zero security, still dominates industrial automation despite billions invested in modern alternatives"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sumitshinde-84 It should be 47-years-old (1979 - 2026)

- flowfuse
---

Modbus is 46 years old and has no built-in security. By every measure, it should have been obsolete a decade ago. OPC UA, EtherNet/IP, MQTT, Profinet: modern protocols with semantic modeling, encryption, and real-time capabilities arrived backed by billions in vendor investment and industry standardization efforts.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sumitshinde-84 Same as above, 47 years old

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants