2,691 karma · joined July 15, 2016
Where 3D printing has been revolutionary for Battletech though has been terrain. Battletech's played on a hex grid, and ever hex has an elevation printed on it to form hills, buildings, and rivers. There's one company (Thunderhead Studios) that makes STLs of the elevation of the official maps that's very popular. Popular enough that they've actually started mass manufacturing them and selling prepainted terrain retail. That shows up in every event I've been to, even official events where 3D minis are banned. But it's a decidedly ancillary part of the experience for Battletech.
[0] Catalyst Game Labs and Iron Wind Metals
The reverse playbook then is that Apple is trying to make every option other than staying in the Apple ecosystem a bad choice, while Valve is trying to make Steam the best option in every scenario. The difference in base philosophy is the important part.
(Of course as a profit-seeking corporation there's no guarantee they'll stay this way, particularly after gaben leaves, but I'll appreciate it while it's here at least.)
tl;dr NVGs are sensitive to near IR so you want lights that are dim in those wavelengths (but not completely out since you still want to see them with NVGs) while still being bright in visible light. There's a neat picture of the flying controll tower on one of the UK's Queen Elizabeth-class aircraft carriers that shows two rooms with similar illumination levels in visible light, but under NVGs one room which isn't NVG compatible is massively brighter than the other. In the NVG-compatible room there were still a handful of panel indicator lights that were not compatible and lit up the whole space
[0] the original source of the haiku: https://www.reddit.com/r/sysadmin/comments/4oj7pv/network_so...
> ...
> Apple’s attention to detail is what has propelled it to be the most valuable company on earth. Whether it’s the click of a physical button or the math behind inertial scrolling, Apple employees work really hard to make products that are deceptively simple and just feel right. The virtual knobs found in Garageband are no exception and I hope others enjoyed learning about them as much as I have.
I think these two statements are contradictory. Personally, I've noticed a pattern when people post about Apple UX that seems to go "yes this thing may be unintuitive but actually it's a sign of really good design!" that I can't quite seem to wrap my head around
The solution to this isn't fact checking, banning disinformation, or forcing unbiased media, because that creates an impossible standard that nobody will be able to reach all the time (which will cause the standard to degrade as exceptions are passed over). Instead, it's to cultivate media literacy: who's reporting this, why are they reporting this, why are they choosing these facts to highlight, why do they deemphasize facts reported by other sources, what's their long term bias and affiliation, and what are they trying to get you to believe. You need to apply those questions to every source and trust none of them implicitly, at least because nobody's perfect.
Now the packet is in the ISP's network. Logically this will be a big pile of switches with some servers attached, such as CDNs and the like, and connected at points to other ISPs/backbone providers at IXes. Physically it's a bunch of neighborhood racks feeding to ISP datacenters scattered around the country and interconnected wither by the ISP's own cables or backbone providers. Your packet will traverse this network in a number of ways depending on the specifics. Maybe the ISP's switch recognizes that 64.233.177.100 is a CDN on a server in the ISP's datacenter, so it forwards it there. Maybe the address is outside of the ISP's network. The switch that your modem is plugged into will pass the packet along to a router of some sort which will have a routing table (which is distributed and updated by internal routing protocols like OSPF or IS-IS) which will tell it where to sent the packet. If the address is outside of the ISP's network, then the router will direct it to one of the IXes based on its routing information.
Now we're at the IX. Your packet has gone from your laptop, to your AP/switch/router, to your modem, to the ISP's switch, to the ISP's router, to several other ISP switches and routers, and is now at the ISP's router in the IX. The physical configuration of an IX is like any other datacenter: just a bunch of racks, this time with routers in them. There'll be Comcast's routers in one rack, Cox's in another, Lumen (a backbone provider) in another. Then each router will be cabled to each other router, just like you plug your desktop into your router at home. The routers will exchange routing information with BGP, and that information will include who has address 64.233.177.100 connected directly to their network, or if nobody has it then who has a connection to the network it's directly connected to, or if nobody has that then who has a connection to a network that's connected to the network that 64.233.177.100 is connected to, etc. Like your ISP's network, each other network is a logical mass of switches and routers, and a physical connection of datacenters, neighborhood routing racks, and IXes.
Maybe in this case 64.233.177.100 is in a datacenter connected to another ISP at the IX; in that case the packet will go to that ISP and through its internal network to the datacenter. Or maybe nobody connected to this IX has 64.233.177.100. In that case the packet will probably travel through one of the backbone providers' internal network to the IX where the ISP that does have 64.233.177.100 connected to it is connected.
Since physically an IX is just a bunch of routers in a rack, you can have things plugged into them other than other routers, although this is generally frowned upon. Many IXes have locked racks to prevent that