When will these guys learn/catchup....
94 karma · joined October 25, 2015
When will these guys learn/catchup....
I have started falling in love with coding/CS again with Go.
Our philosophy is to keep things close to the metal and not use layers as much as possible. Go enables you to follow with approach with the standard libraries that come with the language.
Problem with layers/frameworks is that while they seem to solve immediate problem quickly, layers will rear their ugly head down the road , making you feel helpless during debugging
We use standard libraries
database/sql for database html/template for UI
Only external package used so far is gin-gonic/gin for middleware&routing
Try using ARM based server and you quickly realize the pain.
Besides, other Hyperscalers won't use Amazon's Chips. So no economy of scale.
Do you remember Amazon Phone ?
Binary compatibility, of millions of third party libraries out there, is the biggest hurdle.
How many years did it take to switch from Python 2.7 to Python 3 ?
AWS lockin is a bigger threat.
I prefer to keep my binaries cloud agnostic and X86 and X64 compatible rather than AWS only code or even ARM binary.
By the way what happened to Amazon phones ?
Problem#2: "Liability Issues" doesn't make sense. Geico, Allstate and other insurance companies can easily provide coverage. In fact the insurance gets easier with self-driving cars. Premium might go up or down based on the technology used. But coverage is very much doable.
Driving is so monotonous,that it is a perfect "killer app" for computer vision and cognitive computing.