I was shocked years ago that the mac, famous for its early network peer discovery and zeroconf and all, couldn't present a list of SMB servers and shares despite that kind of function being around forever on every other platform in existence.
Must have been a lot of years ago since Samba was introduced in Jaguar (2002), and SMB replaced AFP as the default for file sharing as of Mavericks (2013).
8051! I love it. Its like running web stacks on these ESP8266's without the crypto acceleration.
But at the same time, we have to stop pretending that 1Gbit Ethernet isn't utterly obsolete in the same way that RS-232 is. Useful maybe for low power, longish reach, but its slower than a good number of internet connections now, and the wifi on the other end too.
Ex: My house, turns out the 1Gbit uplink from the ISP provided hardware to my firewall was causing me to lose 300MB because it was actually provisioned at 1.3Gbit, and when I switched it to 5Gbit, my Wifi got faster.. Ex, I can get in excess of 1Gbit in about 2/3rds of my house now to sites on the internet.
1GbaseT is 27 year old technology this year, 10GbaseT is 20 this year, and by any other computing metric should be obsolete too since there has been a 25GbaseT spec for 10 years that no one has bothered to manufacture. And here in 2026, double or more should be easy with modern phy technology, and with proper line quality could easily be all of dynamic power, dynamic length and dynamic speeds over a range of cable types and length, both running at lower power and higher performance.
I believe this to be a utility issue. In the average home network, having greater than a gig networking provides little value for the center of the bell curve of users.
Maybe its different outside of America but most people in America have less than 1gbps internet connections, and have little need to transfer data in-house from one location to another that the time saved by having a 5, 10, or 25gbps connection would benefit them in any measurable way.
Even for those people who run NAS systems for extra storage will only saturate gigabit connections occasionally, and being able to save a few hours a year waiting for transfers to complete is likely not worth the initial setup effort and costs for them.
I'm a bit of a techie, and my house is wired for 10gbps internally, but no isp in my area offers more than 1gbps, and I live in a well-to-do and densely populated area near to many tech companies.
So, in short, 1gbps is not obsolete. It probably should be, but it still meets the needs of the great majority of people that use it.
I think about 80-90% of the UK can order >1G broadband, fairly similar in most of europe, though some countries do lag behind. Realistically the number of homes with more than 20metres of cat5 structured cabling is very very low (much less than 1%). Typical new builds might give you a CAT5 from the utility cupboard to the TV and study if you're lucky. As such for now it's fine as 10G is 'OK' and even in the case the cabling doesn't support 10G, it should at least do 5Gbase-T.
Most providers are topping out at 2.5Gbps and big part of that is that you can't actually use even that much over Wi-Fi and anything >2.5Gbe consumer side is comparatively expensive/rare and no hard wired cabling in most houses anyway. So as such most ISP routers are 2.5Gbe LAN with only a few exceptions (https://www.choose.co.uk/broadband/sky/reviews/sky-gigafast-...).
At home, I have 10G only between machines that actually do transfer between each other. The rest is either 1G or Wi-Fi 7 (which in my use case is faster than 1G and cheaper than 10G)
As an American who recently moved and can now get 1/2/5Gbit XGS-PON, in a location which is borderline rural/suburban and was originally platted out 50 years ago, at the same price I was paying for shitty 400/20... I don't think our failures to invest a single cent in infrastructure or regulation over the past few decades should define the Ethernet working group's priorities.
I dunno, I'd like to see faster options taking off but last time I checked they were just starting to get cost-effective. I'm not paying a factor more for 10GbaseT when I don't actually need that kind of speed.
1 Gbps is perfectly adequate for things such as Apple TV's, smart home controllers/gateways (heck even 10 Mbps is fine for them), networked printers, UPSes (also would be fine with as low as 10 Mbps), KVMs, etc etc etc
I think the larger point is that dumping baseband and going with OFDM/etc over wider spectrum allows those cat5e runs that are rolling off at 600Mhz (or whatever) and the super clean cat8/whatever to coexist with bad cables, bad termination, etc. The spec could easily be built for say 50Gbit, and fall back to 2.5Gbit/etc on 200M chicken wire runs.
Then the argument about "but we have to pull more cable to guarantee those speeds" or "It consumes to much power" all go away, and instead the analog side gets a bit more complex, but given the $100+ phy's in 10GbaseT the argument that it drives cost is bogus when triband Wifi7 USB nic's are $30.
POE and existing wiring, and terminating copper on the lower end is dead simple for the kinds of people who wire houses, being able to run on cat3 phone cable would be even more of a bonus. There is a market for attaching APs, security cameras, and a load of other stuff on copper.
I'm a bit irked that there aren't more, less expensive 10gb 10baseT ethernet switches available. I have one that I have as my main connection in the wiring closet (need to get my NAS back in there), and a few 2.5gb switches off of that (one in my office)... mostly because I just didn't want to shell out the dramatically more expensive option.
Its more than that, its that x86 vendors know how to maintain hardware backwards compatibility, they don't throw out the entire USB subsystem every time a new phy/whatever shows up because there is a standardized mailbox interface sitting in front of the actual HW. Same with the core platform, which works out of the box using 25+ year old firmware standards that are flexible enough to support simple sensors and behaviors, like lid close notification on a laptop for example across multiple OS's. Even something as simple as the firmware interface for handing off a frame buffer to the OS isn't universally support on arm platforms because a significant fraction don't support uefi. Apple was an early uefi adopter, but whatever internal politics they have, means they tossed even that on the latest mac's.
I don't even think that is the problem. It seems more an engineering cultural one, that has sadly infected most of the software industry at this point. Instead of incremental improvement it seems the old ATI drivers (and seemingly much of the recent history) are just rewrites rather than having a replaceable low level core and a reasonable amount of legacy that just gets forward ported to newer HW architectures. So, they release the hardware and its basically obsolete before the driver stack ever stabilizes sufficiently that any single driver can run a wide range of games well.
I just wish they would make another pass at cleaning up the stack. It should be easy to `git clone --recurse-submodules rocm` followed by a configure/make that both prints out missing dependencies and configures without them, along with choices for 'build the world' vs just build some lower level opencl/HIP/SPIRV tooling without all the libraries/etc on top in a clear way.
Right now the entire source base is literally throw a bunch of crap into the rocm brand and hope it builds together vs some overarching architecture. Presumably the entire spend it also tied to "whatever big Co's evaluation needs this week" when it comes to developing with it.
I recently dumped opnsense because they took a stand against a few things I was trying to do (ex, webUI on wan port IIRC) which make sense at a high level. But I _HATE_ devices that think they know better than me. I was trying to configure it on a _LAN_ such that the identified WAN side was actually my local lan, and I spent an hour hacking it to work and was like "you know if they can't get this shit right i'm out". There are a lot of places in the technology world where someone who thinks they understand my use case makes a decision based on some narrow world view because they can't understand that not everyone trying to use their product is some idiot home user using it for their home network.
I've been a fan of opnSense for a few years now - I'm actually using it as the WAN device for our office, as well as a VPN concentrator in other contexts.
Some recent changes are driving me up the wall though - their new UIs for configuring VPNs (IPSEC and OpenVPN) are far less intuitive than what they've termed the 'legacy' UI and I note that recent versions have introduced a firewall rule migration feature that I'm not touching with a 9-ft barge pole.
These changes are making me wary about using opnSense in future, which is a pity because other than pfSense there isn't really a fully-featured, open-source firewall OS that comes close to matching it (and pfSense has its own issues). Linux is great and all - and I do use it for routing/firewall/VPN in places on our network - but there doesn't seem to be a dedicated network appliance distro that bundles in a comprehensive Web UI. Apart from OpenWRT and its ilk, but I'm not convinced that that's suitable for enterprise deployment.
I've got one of those N100+10Gbit router devices with a handful of ports. It seems a pretty reasonable device with one of the router distros running on it, but it doesn't seem nearly as efficient as my ucg-fiber/route10 devices, and that wouldn't bother me except that I suspect the packet latency is significantly higher too. Those devices AFAIK have hardware programmable router chips, which means the forwarding is done 100% without the interaction of the main CPU, so there isn't any interrupt/polling/etc delays when a packet arrives, the header gets rewritten, the checksum verified and off it goes.
Anyone actually measured this? I see a lot of bandwidth/etc style tests but few that can show the actual impact of enabling disabling deep packet inspection and a few of the other metrics that I actually care about. Serve the home seems to have gotten some fancy test HW but they don't seem to be running these kinds of tests yet.
From what I can tell you're pretty much right. A linux bridge cannot possibly be as efficient or speedy as a dedicated switch asic. OpenWRT has support for a few different hardware switch kernel APIs, but you can't exactly buy one of those on a PCIe card and I've never seen one of those N100-class boards with one instead of a set of i226 ethernet controllers taking most of the PCIe lanes.
Mikrotik sells the CCR2004-1G-2XS-PCIe, which is a fascinating device:
It is a full Mikrotik router stripped down to just a board and hung off a PCIe interface. Iirc by default it exposes a virtual gigabit interface to the host and otherwise acts exactly like a CCR2004 running RouterOS.
Doesn't really buy you anything vs a RB5009 unless you can use the pair of 25Gbps ports, but it sure is neat.
The hardware-based routers have low latency. Fortigate advertises under 5 usec forwarding latency for its routers. Linux kernel forwarding is on the order of 10s of usec. However, under 100 usec of latency is negligible over a WAN link, where you're talking ~5 msec latency even on a fast fiber link. The downside of hardware routing is the lack of flexibility and some performance cliffs. On the consumer grade hardware routers in particular, connection setup is handled by a low-power ARM CPU. You have limits on the number of flows you can accelerate in hardware at a time, etc.
I've got a 10G fiber connection, and I swapped out a Fortigate 100F for a server running VyOS. I had performance problems, because the 10G to 1G transition caused dropped packets at the switch. I was able to solve it by shaping the traffic to the 1G devices to handle queuing in the router, which is something this particular Fortigate can't do. (High end routers have algorithms like WRED designed to get TCP to behave nicely on 10G to 1G drops, but I don't want the noise of a Cisco in my basement.)
His early stuff contains some real masterworks. Hyperion is still to this day, going to show up at the top of my scifi recommended reading list, most of his horror novels were also great in their own ways.
PS: I thought Fall of Hyperion should have been the end, it was just too final. There was plenty of space for some prequels but while the sequels contained some interesting ideas, they just never got to the level I felt justified reversing the finality of Fall. And Olympus/etc was pretty forgettable, but I don't regret the time I spent reading pretty much everything he wrote, sometimes more than once. So again, RIP.
Its not against the law in any US state (a quick search seems to back this up) to pass on the right. With one huge gotcha, it must be "safe" defined in various ways.
OTOH, most states have a stay right except to pass, slower traffic keep right laws.
Which means, that unless the person to your right is weaving through traffic, driving on the shoulder, or a few other bits of unsafe behavior, if someone passes you on the right your likely the one violating the law by not moving right when your not actively overtaking/passing someone.
In Austin too, and probably just caused a driver to think the same thing. They were in the left lane on a frontage road which was suddenly turning left even though there was an entire lane opposite the intersection blocked off by those plastic things that seem popular to randomly place in the road these days. I saw them hesitate and figured they wanted to merge right, so i decelerated a bit to add another car length or or so, at maybe 10-15mph. They had plenty of space, flipped on their blinker, and instead of just merging started slowing down, to which I decided I wasn't going to brake more to allow them to block myself and everyone else from rolling through the intersection. They basically stopped in their lane, and beeped as I rolled by, to which someone behind them beeped at them for blocking the lane.
In Austin if you want to merge, decide if you can, blink and then merge.
Don't expect people to stomp on their brakes and stop to let you in, especially if your already traveling slower than the lane you are trying to get into and decide to further slow yourself.
And if you can't merge, deal with it, exit, or miss your exit and go around. Next time you will be more prepared or you will learn how to properly merge.
I was shocked years ago that the mac, famous for its early network peer discovery and zeroconf and all, couldn't present a list of SMB servers and shares despite that kind of function being around forever on every other platform in existence.