Other article which isn't so sparse on detail (the NYT will probably improve the article linked in the OP later): https://www.cnbc.com/2018/06/21/intel-ceo-brian-krzanich-to-...
HN user
__aeneas
http://github.com/arekkas/
This should also show that append is really, really heavy when the slice is not pre-allocated and should be avoided whenever possible!
I can only agree. I wrote a CMS with Zend Framework 2 which is heavy on DI and tries to be like Spring + Hibernate (Doctrine). Apart from being very hard to understand for new devs in the project, it's also very, very slow.
The way PHP is evolving is definitely towards the Java world and I think it's the worst decision they could make.
Moved to Go 5 years ago, never looking back.
Nice, thank you for taking the time to explain this!
Yes, but a keel is also limited right? It's still possible to tip over and - if potentially submerged, not come back up?
But to be honest, I have very little knowledge on this topic, so maybe a keel is all it needs!
Saw the video yesterday on YouTube. I wonder what happens if they get into very strong winds or very strong swell - if they tip over, do they get up by themselves? What happens if they submerge?
Apparently they figured out how to do it, but my question is, how exactly are they doing it?