Legally it's probably fine, but as the Belgian American Radio Company has been around since the 1930s, the title of the article did confuse me: my first guess was something about how Barco was using Linux containers in their products.
Guilty as charged. Based on design validation testing, I ended up making the design choice to partially rely on a software offset, a strong fan blowing into the sensor not being a supported scenario.
But the placement / air flow / multiple openings definitely took us more design iterations than we had planned for.
There's AntennaHouse and PrinceXML, but both are pretty
pricey ($3-5K / server), and both of these do now support CSS as well.
Apache FOP / Batik is okay for generating nice looking PDFs, but its SVG rasterization is much worse than that of Chrome's PDF renderer (Skia).
As I didn't get the memo about XML being dead, I'm still using Docbook and XSLT/XInclude to structure and filter content written in markdown/rst.
But I will be switching over from XSL-FO to CSS paged media for layout as soon as Chrome supports bookmarks in PDF output, or either WeasyPrint or wkhtmltopdf improve their CSS3 column support.
"Consumers plug-and-play hotspots in their homes and businesses. Labor cost is $0".
But in doing so, these customers most likely would break the contract with their ISP, or they'd have to upgrade to a contract that does allow them to "redistribute" Internet access.