Re:Writing secure Go code
by blibble on Monday November 04, 2024 @03:17PM
(#42045608)
if you don't pull in 50 jars to replace the "new" keyword (aka spring DI), then this ceases to be a problem
[ Parent
| on HN ]
Re:Writing secure Go code
by oftenwrong on Tuesday November 05, 2024 @12:18PM
(#42053401)
This Spring hater (me) thinks that's a fair summary. It also eliminates much of the safety the compiler can give you for free. You will only find out during Spring init, or even later, that your program is broken.