DVI-D uses TMDS, which is a serial protocol. So if you want to be really pedantic you could call it a serial port even though it’s not RS232.
DVI-A also transmits metadata over a serial connection, but the video signal is parallel analog.
DVI-D uses TMDS, which is a serial protocol. So if you want to be really pedantic you could call it a serial port even though it’s not RS232.
DVI-A also transmits metadata over a serial connection, but the video signal is parallel analog.
Are you speaking from experience?
Not sure why you’re getting downvoted, since you gave clear instructions that anyone can follow to verify what you said.
In this case, we’re talking about the OPs example of someone implementing a complex message passing architecture in Java instead of using an off the shelf solution. There are devs with 20+ years at the same company who don’t know the basics of networking/cloud, because they haven’t improved their technical skills much in those 20 years and instead focused on corporate politics. Those are the people who tend to gets asked for advice from upper management.
These kinds of issues are common on any large software project.
That because you’re an engineer (I assume). The people signing off on these kinds of projects don’t know enough themselves, so they go to someone they trust (the old timers) to help them make the decision. The old timers don’t keep up with new tech, so we keep reinventing the wheel.
A colleague still codes in emacs and its code is dirty af.
PEBKAC - don’t blame emacs (not sure why anyone would use it when vim exists, though)
You’re probably right, but I can think of a couple other 3d printing projects that have the same issue.
We’re pretty much at the point where 2.5" SSDs are old…