# bridging Published articles for bridging. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## ESP32 Bit Pirate: a multi-protocol workbench built on the ESP32-S3 DevFeed: [ESP32 Bit Pirate: a multi-protocol workbench built on the ESP32-S3]() Original publisher: [Read original article]() Author: John Lee Published: 2026-08-20T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32-S3](), [Embedded Software Dev](), [Hardware](), [Command-line interface](), [ESP32-C5](), [Scripting](), [Open Source](), [Python]() Tags: [2](), [ble](), [blog](), [bridging](), [cli](), [community-contribution](), [debugging](), [development-board](), [esp32](), [esp32-c5](), [esp32-s3](), [firmware](), [hardware](), [open-hardware](), [open-source](), [python](), [scripting](), [tooling](), [usb](), [wi-fi]() ### AI overview ESP32 Bit Pirate turns an ESP32-S3 into a scriptable multi-protocol workbench. The article describes its firmware, more than twenty wired and wireless modes, serial and web-based interfaces, Python scripting, and companion open-hardware projects including an ESP32-C5 radio adapter and a carrier dock. ### Source excerpt ESP32 Bit Pirate turns an ESP32-S3 into a scriptable multi-protocol workbench with more than twenty modes, a web and serial CLI, and dump and sniff tooling. This article walks through the firmware and the two open-hardware companions that extend it: a carrier dock with selectable 1.8 V, 3.3 V and 5 V level translation, and an ESP32-C5 adapter that adds a dual-band radio. ## Bridging Pub/Sub to Temporal with Standalone Activities DevFeed: [Bridging Pub/Sub to Temporal with Standalone Activities]() Original publisher: [Read original article]() Author: Houman Kargaran Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [execution](), [client](), [Latency](), [Cloud]() Tags: [bridging](), [client](), [cloud](), [community](), [execution](), [latency](), [worker](), [workflow]() ### AI overview This guest post explains how Temporal Standalone Activities can connect Pub/Sub message handling to durable execution without wrapping each activity in a Workflow. It describes how this approach can reduce application-side retry, state-tracking, reconciliation, and monitoring complexity, while offering lower latency for short-lived activity executions. ### Source excerpt How a Temporal Standalone Activity bridges Pub/Sub to Durable Execution, keeping your event handler thin. ## The CI/CD moment for data analytics DevFeed: [The CI/CD moment for data analytics]() Original publisher: [Read original article]() Author: Gaurav Nanda Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [data analytics](), [DataOps](), [real-time](), [data-engineering](), [CI/CD](), [Kafka](), [apache-flink]() Tags: [ai](), [analytics](), [apache-flink](), [architectures](), [bridging](), [cost](), [data-analytics](), [data-engineering](), [engineering](), [event](), [fraud](), [google](), [insights](), [kafka](), [latency](), [real-time](), [scale](), [streaming](), [systems](), [tools]() ### AI overview The article argues that data analytics is approaching a CI/CD-like transition toward continuous analytics. It describes how multi-step pipelines introduce latency, operational risk, and maintenance burden, and explains why real-time insight is becoming a baseline platform capability for applications such as personalization, fraud detection, reliability, and AI-driven features. ### Source excerpt How converging OLTP and OLAP architectures are driving 'Continuous Analytics', the CI/CD moment for data to deliver real-time, unified insights and operational simplicity. ## ARP with EVPN Asymmetric IRB DevFeed: [ARP with EVPN Asymmetric IRB]() Original publisher: [Read original article]() Published: 2026-05-14T05:45:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [evpn](), [VXLAN](), [networking](), [BGP]() Tags: [arp](), [bgp](), [bridging](), [evpn](), [netlab](), [vxlan]() ### AI overview This tutorial explains ARP behavior in EVPN asymmetric Integrated Routing and Bridging (IRB). It identifies prerequisites for forwarding between VLANs, including creating ARP entries from MAC+IP routes and having end hosts send an early ARP request for their first-hop gateway. It also describes how to verify the behavior with a netlab topology and EVPN route and ARP-table inspection. ### Source excerpt In a previous blog post, I described the ARP issues you'll encounter when using centralized routing (on a spine switch) between two EVPN MAC-VRF instances (a fancy name for a VLAN encapsulated in VXLAN or MPLS). That blog post established a baseline that will help us unravel the ARP behavior in a more realistic scenario: asymmetric Integrated Routing and Bridging (IRB). That's a mouthful, but it's really quite a simple concept; the following diagram explains the asymmetric forwarding behavior: Packet forwarding in an EVPN asymmetric IRB design Read more ... ## Lab: Integrated Routing and Bridging (IRB) with EVPN MAC-VRF Instances DevFeed: [Lab: Integrated Routing and Bridging (IRB) with EVPN MAC-VRF Instances]() Original publisher: [Read original article]() Published: 2026-04-17T06:13:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [evpn](), [networking](), [VXLAN](), [GitHub]() Tags: [apple](), [bridging](), [container](), [evpn](), [github](), [infrastructure](), [installation](), [mac](), [routing](), [vxlan]() ### AI overview A hands-on lab introduces Integrated Routing and Bridging with EVPN MAC-VRF instances by adding anycast gateway IP addresses to VLAN interfaces. The lab can run on netlab-enabled infrastructure, GitHub Codespaces, or an Apple-silicon Mac using an Arista cEOS container. ### Source excerpt Most EVPN documentation rushes into the complexities of symmetric IRB, type-5 EVPN routes, and EVPN IP-VRFs, but if you want to master a technology, it's better to take it slow and proceed with small steps. In today's lab exercise, we'll do just that: explore what happens when you add IP addresses (we'll use anycast gateways) to VLAN interfaces tied to EVPN MAC-VRF instances. Explore the lab exercise You can run the lab on your own netlab-enabled infrastructure (more details), but also within a free GitHub Codespace or even on your Apple-silicon Mac (installation, using Arista cEOS container, using VXLAN/EVPN labs). ## Bridging two JSX runtimes: How we solved Astro's React children problem DevFeed: [Bridging two JSX runtimes: How we solved Astro's React children problem]() Original publisher: [Read original article]() Author: Kyle Finken Published: 2026-03-10T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Astro](), [React](), [MDX](), [React Component](), [render]() Tags: [astro](), [bridging](), [component](), [components](), [engineering](), [mdx](), [react](), [render](), [solved]() ### AI overview Mintlify describes how its Astro integration addressed a JSX runtime mismatch that caused compound React components to lose their children during hydration in Astro's MDX pipeline. ### Source excerpt How Mintlify solved a fundamental JSX runtime mismatch to make compound React components work inside Astro's MDX pipeline. ## Lab: More Complex EVPN/VXLAN Bridging Scenario DevFeed: [Lab: More Complex EVPN/VXLAN Bridging Scenario]() Original publisher: [Read original article]() Published: 2026-02-27T08:13:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [evpn](), [VXLAN](), [GitHub]() Tags: [apple](), [bridging](), [container](), [evpn](), [github](), [infrastructure](), [installation](), [vxlan]() ### AI overview This tutorial presents a more complex EVPN/VXLAN bridging lab using several EVPN MAC-VRFs mapped to different VLAN segments on individual PE devices. The lab can run on netlab-enabled infrastructure, a free GitHub Codespace, or an Apple-silicon Mac. ### Source excerpt In the first EVPN/VXLAN lab, we added the EVPN control plane to bridging over VXLAN. Now, let's try out a more complex scenario: several EVPN MAC-VRFs mapped to different VLAN segments on individual PE-devices. Explore the lab exercise You can run the lab on your own netlab-enabled infrastructure (more details), but also within a free GitHub Codespace or even on your Apple-silicon Mac (installation, using Arista cEOS container, using VXLAN/EVPN labs). ## How to harness skills that AI can't automate DevFeed: [How to harness skills that AI can't automate]() Original publisher: [Read original article]() Author: Emma Webster Published: 2025-09-09T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Artificial Intelligence](), [ChatGPT](), [Claude]() Tags: [ai](), [ai-tools](), [bridging](), [chatgpt](), [claude](), [figma](), [generate](), [how-to](), [prototypes](), [scope](), [skills]() ### AI overview The article explains how human qualities such as curiosity, intuition, taste, and intention help teams guide AI tools toward higher-quality product outcomes. It describes using Figma Make to generate and evaluate prototypes, and using Claude or ChatGPT to compare campaign ideas, while emphasizing that AI cannot independently challenge scope or pursue unexpected directions. ### Source excerpt With more teams moving faster than ever, the real differentiator is craft--the curiosity, intuition, taste, and intention behind every detail. ## When Switches Flood LLDP Traffic DevFeed: [When Switches Flood LLDP Traffic]() Original publisher: [Read original article]() Published: 2025-08-25T07:13:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Cisco](), [datacenter](), [Server]() Tags: [bridging](), [cisco](), [data-center](), [ethernet](), [network](), [networking](), [servers](), [standards]() ### AI overview The article examines why Cisco switches in a data center network flood LLDP packets between servers, potentially causing DCBX parameters to be negotiated between servers and leading to NIC resets. It compares IEEE LLDP requirements with Cisco TAC's explanation for flooding on NCS equipment and discusses the role of MEF standards. ### Source excerpt A networking engineer (let's call him Joe1) sent me an interesting challenge: they built a data center network with Cisco switches, and the switches flood LLDP packets between servers. That would be interesting by itself (the whole network would appear as a single hub), but they're also using DCBX (which is riding in LLDP TLVs), and the DCBX parameters are negotiated between servers (not between servers and adjacent switches), sometimes resulting in NIC resets2. Read more ... ## Finding End-to-End Paths: Topology and Endpoints DevFeed: [Finding End-to-End Paths: Topology and Endpoints]() Original publisher: [Read original article]() Published: 2025-06-06T05:51:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Routing (disambiguation)](), [Network design]() Tags: [arp](), [bridging](), [dhcp](), [discovery](), [ipv4](), [ipv6](), [network](), [networking-fundamentals](), [router](), [routing]() ### AI overview This article explains how networks discover topology and endpoints, build forwarding tables, and adapt end-to-end paths when links or nodes fail. It contrasts complete topology views in link-state protocols with local-neighbor knowledge in distance-vector protocols, and describes learning mechanisms including bridging, ARP, DHCP, and ICMPv6 Neighbor Discovery. ### Source excerpt We know there are three main ways to move packets across a network. However, before we can start forwarding packets, someone has to populate the forwarding tables in the intermediate devices or build the sequence of nodes to traverse in source routing. Usually, whoever is responsible for the contents of the forwarding tables must first discover the network topology. Let's start there, using the following network diagram to illustrate the discussion. Read more ... ## Bridging the Gap between Business Stakeholders and Engineering Teams: A Business Analyst's Playbook... DevFeed: [Bridging the Gap between Business Stakeholders and Engineering Teams: A Business Analyst's Playbook...]() Original publisher: [Read original article]() Author: Shelby Boyle Published: 2025-05-30T06:49:43Z Content type: tutorial Language: en Sources: [GumGum]() Topics: [Support](), [Data Science](), [jira](), [dashboards](), [data]() Tags: [bridging](), [business-analytics](), [collaboration](), [communication](), [data-science](), [engineering](), [guide](), [practical](), [product-development](), [teams](), [ticketing]() ### AI overview A business analyst playbook explains how to translate stakeholder needs into product solutions. It covers clarifying problems and impacts, using JIRA to support engineering work, and applying data science models and dashboards to analyze variables, customer behavior, revenue, and conversions. ### Source excerpt Bridging the Gap between Business Stakeholders and Engineering Teams: A Business Analyst's Playbook to Creating Quality Product SolutionsDoes your bridge look like this?! Tsingy Bemaraha National Park, Madagascar (my own photo August 2024) In today's evolving technology world, communication and collaboration are vital between business and engineering teams to deliver functional, scalable solutions. The Business Analyst (BA) is the problem-solver who ensures that business needs are translated into practical products to fuel powerful strategic decisions. What does this process look like? This is a detailed playbook BAs can follow to guide from stakeholder need to fully materialized product. 1. Meet with Stakeholders on Problem and the Impact The first step in solving any business problem is understanding the problem itself. What is the problem? What would be the desired outcome? What is the business impact of the problem? What would be the business impact of a possible solution? Ask these questions of your stakeholders and encourage them to distill the problem to its core. Meeting with stakeholders guarantees no details are left out: not just what may be documented, but what may not be documented as the problem. Using an engineering ticketing system like JIRA can facilitate this initial step. The better scoped the problem is, the sooner you can start working on analytic solutions. These initial conversations set the foundation for all subsequent steps. It makes your work easier too! 2. Define the Problem and Impact After initial stakeholder conversations, the BA defines the core problem, the present consequences of not having a solution, and the impact of constructing a product solution. These are some examples of this step: We need to understand variable likeness e.g. finding types of words associated with a holiday event or grouping customers based on shopping behavior. Without knowing this, we cannot derive target strategies for success or resolve weakness. Cue the ## Forwarding Packets Across a Network DevFeed: [Forwarding Packets Across a Network]() Original publisher: [Read original article]() Published: 2025-05-08T06:20:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Networks](), [networking](), [Network](), [Routing (disambiguation)]() Tags: [bridging](), [networking-fundamentals](), [networks](), [routing](), [switching]() ### AI overview This article explains how packets move across networks after a single cable is divided by an intermediate network device. It introduces source routing and path-based forwarding, while contrasting bridging, routing, and switching terminology. ### Source excerpt After inspecting the confusing bridging/routing/switching terminology and a brief detour into the control/data plane details, let's talk about how packets actually move across a network. As always, things were simpler when networks were implemented with a single cable. In that setup, all nodes were directly reachable, and the only challenge was figuring out the destination node's address; it didn't matter whether it was a MAC address, an IP address, or a Fiber Channel address. On a single cable, you could just broadcast, like, "Who has this service?" and someone would reply, "I'm the printer you're looking for." That's how many early non-IP protocols operated. Read more ... ## The designer's handbook for developer handoff DevFeed: [The designer's handbook for developer handoff]() Original publisher: [Read original article]() Author: Jake Albaugh; Chad Bergman Published: 2025-04-01T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [data]() Tags: [bridging](), [collaboration](), [communication](), [complexity](), [design](), [developer](), [developers](), [engineering](), [figma](), [guide](), [handbook](), [scope](), [technical]() ### AI overview A practical handbook for collaboration between designers and developers during design handoff. It explains how to align on scope, understand technical constraints, involve developers early, use Figma or FigJam to ground feedback, and identify redundant work or opportunities with limited engineering effort. ### Source excerpt A tactical guide to collaborating with your developer counterparts, including common pitfalls, practical tips, and guidance on when to lean in. ## Matrix/IRC bridge is now self-hosted DevFeed: [Matrix/IRC bridge is now self-hosted]() Original publisher: [Read original article]() Published: 2025-03-31T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [IRC](), [Matrix](), [Self-hosted](), [The Lounge](), [Protocol (disambiguation)](), [maintenance](), [protocols](), [Network](), [Software]() Tags: [bridging](), [irc](), [maintenance](), [matrix](), [patches](), [postmarketos](), [protocol](), [self-hosted]() ### AI overview postmarketOS moved its Matrix-to-IRC bridge to self-hosting after evaluating whether to go Matrix-only or use a third-party service. The project chose matrix-appservice-irc because it supports full single puppeting, while also considering maintenance and available forks. ### Source excerpt The postmarketOS chat rooms are available on both the Matrix and IRC protocols (IRC on OFTC). Communicating from one protocol to the other is possible via matrix-appservice-irc. We have been using the instance hosted by the Matrix.org Foundation, which will probably get shutdown at the end of March 2025. This would be today, we haven't heard any further information whether it will actually happen or not and when. But as of today we are now self-hosting the bridge. Evaluation First we considered going Matrix-only since the majority of our uses are on that protocol. But via our Mastodon poll and direct feedback via chat it was apparent that a lot of people still want to be able to use IRC for talking in the postmarketOS channels so we investigated how to make this possible. Next we decided whether to self-host a bridge or using a 3rd party offering. Our conclusion was that for us since we already run a Synapse instance, the maintenance effort should be rather minimal after we do the initial setup of the bridge. So we are trying that first, and only if it turns out to be more work than expected we will switch to a bridge that is hosted by somebody else. We had to figure out which software to use for the bridge since the Matrix.org Foundation wrote regarding matrix-appservice-irc that they "will also mark the software behind those bridges as archived". The heisenbridge project had a very useful comparison table, through which we realized that we want to keep using a version of matrix-appservice-irc, as it seems to be the only one that can currently do the full single puppeting mode. All others would either show up as one user on IRC or on Matrix side. matrix-appservice-irc runs in full single puppeting mode where both IRC and Matrix users are puppeted both ways. The Matrix users identity is directly mapped to IRC and they are in full control. This method of bridging creates multiple IRC connections which makes is mostly transparent for both sides of the bridge. As the r ## IPv6 Router Advertisement Forwarding Disrupts netlab VRRPv3 Integration Tests DevFeed: [IPv6 Router Advertisement Forwarding Disrupts netlab VRRPv3 Integration Tests]() Original publisher: [Read original article]() Published: 2025-03-24T07:08:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Networks](), [Linux](), [Containers](), [Testing](), [Integration testing]() Tags: [bridging](), [cisco](), [container](), [integration-testing](), [ipv6](), [linux](), [netlab](), [networks]() ### AI overview This technical blog post investigates VRRPv3 IPv6 integration-test failures in netlab. It finds that an Arista cEOS container forwarded IPv6 router advertisements between two LAN segments because newly appearing interfaces were enabled in VLAN 1, causing some hosts to treat both prefixes as directly connected. A workaround was implemented in netlab 1.9.4. ### Source excerpt This blog post describes another "OMG, this cannot possibly be true" scenario discovered during the netlab VRRP integration testing. I wanted to test whether we got the nasty nuances of VRRPv3 IPv6 configuration right on all supported platforms and created a simple lab topology in which the device-under-test and an Arista cEOS container would be connected to two IPv6 networks (Arista EOS is a lovely device to use when testing a VRRP cluster because it produces JSON-formatted show vrrp printouts). Most platforms worked as expected, but Aruba CX, Cumulus Linux with NVUE, and Dell OS10 consistently failed the tests. We were stumped until Jeroen van Bemmel discovered that the Arista container forwards IPv6 router advertisements between the two LAN segments. Read more ... ## Stories from Bangkok: Devcon SEA Scholars Program DevFeed: [Stories from Bangkok: Devcon SEA Scholars Program]() Original publisher: [Read original article]() Author: Next Billion Published: 2025-02-18T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Learning]() Tags: [bridging](), [community](), [creators](), [devcon](), [learning](), [next-billion](), [stories]() ### AI overview The Devcon SEA Scholars Program brought 93 participants from 86 countries to Bangkok to explore how Ethereum connects with different disciplines and communities. The program included community organizers, law students and legal professionals, artists and science-fiction writers, and other builders, who later documented their experiences in Learning Artifacts. ### Source excerpt Across different disciplines and geographies, builders are exploring how Ethereum fits into their work and communities. The Devcon SEA Scholars Program brought together 93 of these individuals in Bangkok who are bridging Ethereum with other worlds and pushing Ethereum's boundaries. This community of builders, thinkers, and creators was selected... ## Why VLAN 1 Should Not Be Tagged in a Trunk DevFeed: [Why VLAN 1 Should Not Be Tagged in a Trunk]() Original publisher: [Read original article]() Published: 2025-02-11T07:05:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Ethernet](), [DHCP](), [Cisco]() Tags: [bridging](), [cisco](), [dhcp](), [ethernet](), [lan](), [netlab](), [network](), [security]() ### AI overview The article examines conflicting interpretations of VLAN 1 in trunks by Cumulus NVUE and Arista EOS. It recommends avoiding VLAN 1 in VLAN trunks and using it as the native VLAN when necessary, while explaining the historical and operational reasons behind this behavior. ### Source excerpt It all started with a netlab issue describing different interpretations of VLAN 1 in a trunk. While Cumulus NVUE (the way the netlab configuration template configures it) assumes that the VLAN 1 in a trunk is tagged, Arista EOS assumes it's the native VLAN. At that point, I should have said, "that's crazy, we shouldn't allow that" and enforce the "VLAN 1 has to be used as a native VLAN" rule. Alas, 20/20 hindsight never helped anyone. TL&DR: Do not use VLAN 1 in VLAN trunks; if you have to, use it as a native VLAN. Read more ... ## Repost: Why Are Layer-2 VPNs So Popular? DevFeed: [Repost: Why Are Layer-2 VPNs So Popular?]() Original publisher: [Read original article]() Published: 2024-09-03T06:35:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Virtual Private Network](), [Provisioning](), [Network]() Tags: [bridging](), [complexity](), [customers](), [lisp](), [mpls](), [network](), [providers](), [provisioning](), [vpn]() ### AI overview The article explains that Layer-2 VPNs are popular because they require less configuration coordination and are easier to provision and automate than Layer-3 VPNs. It also notes that L2VPNs can support Network-as-a-Service models, while requiring customers to install edge routers. ### Source excerpt Béla Várkonyi wrote a succinct comment explaining why so many customers prefer layer-2 VPNs over layer-3 VPNs: The reason of L2VPN is becoming more popular by service providers and customers is about provisioning complexity. Read more ... ## Streamline SSR app development with FirebaseServerApp DevFeed: [Streamline SSR app development with FirebaseServerApp]() Original publisher: [Read original article]() Author: David Della Bitta Published: 2024-05-24T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Server-side rendering](), [SDK](), [JavaScript](), [Node.js](), [Development]() Tags: [auth](), [authentication](), [bridging](), [browser](), [firebase](), [javascript](), [js-sdk](), [next-js](), [node-js](), [sdk](), [server](), [ssr](), [web]() ### AI overview The article introduces FirebaseServerApp, a Firebase Web SDK object that lets authenticated sessions created in the browser continue through server-side rendering in Node.js. It explains how Auth ID tokens are passed into SSR requests and discusses service-worker-based token handling and rendering-performance considerations. ### Source excerpt The Firebase Web SDK has introduced FirebaseServerApp ## Why Are We Using EVPN Instead of SPB or TRILL? DevFeed: [Why Are We Using EVPN Instead of SPB or TRILL?]() Original publisher: [Read original article]() Published: 2024-04-05T06:17:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [evpn](), [networking](), [VXLAN](), [IS-IS](), [Routing (disambiguation)](), [BGP]() Tags: [bgp](), [bridging](), [evpn](), [fabric](), [gre](), [is-is](), [mpls](), [network](), [routing](), [vxlan]() ### AI overview The article explains why EVPN, particularly with VXLAN encapsulation, became preferable to SPB and TRILL. It contrasts their encapsulation, control-plane, deployment, and transport requirements, and notes that VXLAN separates edge virtual networks from the physical transport core. ### Source excerpt Dan left an interesting comment on one of my previous blog posts: It strikes me that the entire industry lost out when we didn't do SPB or TRILL. Specifically, I like how Avaya did SPB. Oh, we did TRILL. Three vendors did it in different proprietary ways, but I'm digressing. Read more ... ## Can We Skip the Network Layer? DevFeed: [Can We Skip the Network Layer?]() Original publisher: [Read original article]() Published: 2024-02-12T09:52:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Ethernet](), [Protocol (disambiguation)](), [Terminal]() Tags: [boot](), [bridging](), [complexity](), [cycles](), [digital](), [ethernet](), [memory](), [network](), [networking-fundamentals](), [physics](), [protocol](), [run]() ### AI overview The article examines proposals to omit network-layer addressing from local solutions by using Ethernet data-link addresses with transport protocols directly above them. It recounts how DEC's LAT and MOP protocols placed local terminal services over Ethernet, and explains how requirements spanning multiple Ethernet segments exposed the approach's limitations and led to transparent bridging. ### Source excerpt I mentioned that you don't need node addresses when dealing with only two entities. Now and then, someone tries to extend this concept and suggests that the network layer addressing isn't needed if the solution is local. For instance, if we have a solution that is supposed to run only on a single Ethernet segment, we don't need network layer addressing because we already have data link layer addresses required for Ethernet to work (see also: ATAoE). Too often in the past, an overly ingenious engineer or programmer got the idea to simplify everyone's life and use the data link layer addresses as the ultimate addresses of individual nodes. They would then put the transport layer on top of that to get reliable packet transport. Finally, put whatever application on top of the transport layer. Problem solved. Read more ... ## The art and science of annotations in Dev Mode DevFeed: [The art and science of annotations in Dev Mode]() Original publisher: [Read original article]() Author: Oscar Nilsson Published: 2024-01-31T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [User interface design](), [Code]() Tags: [accessibility](), [bridging](), [collaboration](), [design](), [dev](), [developer](), [figma](), [product-development]() ### AI overview Figma Product Designer Oscar Nilsson explains annotations in Dev Mode, a feature intended to streamline designer-developer collaboration. Annotations keep design context, specifications, accessibility properties, and interactive behavior in one place while helping developers identify the relevant engineering work. ### Source excerpt Product Designer Oscar Nilsson explains how we're streamlining designer-developer collaboration with annotations in Dev mode. ## Ibis: Because SQL is everywhere and so is Python DevFeed: [Ibis: Because SQL is everywhere and so is Python]() Original publisher: [Read original article]() Author: Phillip Cloud, Cole Bowden Published: 2023-07-03T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [Python](), [SQL](), [Data analysis](), [data]() Tags: [analysis](), [bridge](), [bridging](), [data](), [performance](), [python](), [sql]() ### AI overview The article presents Ibis as a lightweight Python library that bridges Python data wrangling and SQL query engines. It converts Python code into SQL for multiple engines, including Trino, allowing users to combine Python's usability with Trino's performance for large-scale queries. ### Source excerpt The PyData stack has been described as "unreasonably effective," empowering its users to glean insights and analyze moderate amounts of data with a high level of flexibility and excellent visualization. The large-scale, production data stack using a query engine like Trino sits on the other side of the world, capable of handling petabytes and exabytes, but perhaps not integrating as seamlessly with the Python ecosystem as one would hope. SQL has been a means of bridging this gap, but we've now got an exciting solution to bridge it even better: Ibis. ## Making Figma better for developers with Dev Mode DevFeed: [Making Figma better for developers with Dev Mode]() Original publisher: [Read original article]() Author: Kris Rasmussen Published: 2023-06-21T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [dev-tools](), [Front end]() Tags: [bridging](), [dev-tools](), [developer](), [development](), [development-tools](), [figma]() ### AI overview Figma introduces Dev Mode, a dedicated workspace that helps developers inspect designs, access implementation details, export assets, and connect design concepts with code, icons, and tokens. It is intended to reduce friction between design and development workflows. ### Source excerpt How can a design tool work better for developers? It's a question we've been asking ourselves and our community. Today, we're excited to introduce Dev Mode, a new workspace in Figma that's designed to get developers what they need, when they need it, harnessing the tools they use every day. [Next page]()