6,767 karma · joined January 2, 2016
take an existing budget line item
do not try and combine line items
do not cross operational boundaries in the customer
Imagine a current era designer trying to design Photoshop without just copying an existing system. It would be useless.
Ethernet has so, so many gotchas. Maybe if it was a layer 3 only network it would work. Maybe.
Not everyone likes squashed/rebase workflows and it's frustrating to have to police people. A lot of groups use a workflow where all commits to branches of global interest are strictly pull requests.
For those who are in this situation, consider that what you can do is test _only_ merge commits - that is, put something like this into a script:
if git log -1 --pretty=%B | grep -q 'Merge pull request'; then
# tests here
exec the_actual_test.sh
else
exit 125
fi
... then "git bisect run script.sh". This skips the intermediates and only tests merge waypoints.Edit: someone below notes --first-parent option, which basically accomplishes the same thing.
https://www.npr.org/2016/06/13/481845003/a-childhood-of-tran...
There are plenty of online resources about the cult aspects of TM if you actually look.
They were as dead as SGI in the same timeframe.
Those things aren’t even true in a 500 person company let alone an economy.
Because while there is a place for some hands on developers at such a place that is not most of the staff? The Manhattan project hired a lot of engineers but none of them were the design leads.
Most of the time it’s easier to just add another few dozen fibers when laying cables.
Network hops are notoriously slow. In the datacenter the best I have ever seen is 200ns or so per packet which is very rare, most in DC hops are closer to 3-9 usec (especially modular chassis); then you hit the routers. With moderate congestion your routing hops are going to be twice that or more ignoring queuing, and you are likely six hops at least between two points in each direction.
The hollow core stuff mostly will jot help since it gains with distance, but distance means more hops on average, so we are talking about an application where low latency is required but distances are high (where the improvement applies) but the minimum latency achievable is still tens of ms.
It is interesting technology but I think it’s more interesting for hypothetical materials savings than for latency improvement.
This is part of how they avoided the ROI catastrophe (researchers with enough cred could argue that there was a long term potential) and the publish or perish issues.