It is so readable that you missed the fact it doesn’t have the FROM clause
It is so readable that you missed the fact it doesn’t have the FROM clause
I know XML is very last century but if they could coexist in one file, a file that treats each config section as an object, so we can create a Project Object Model, call it pom for simplicity, and then if you are old store it in xml and the you could have only one file and call it pom.xml and then maybe one day someone can make this very useful file a bit more modern and turn it into json or yaml but for now a single pom.xml could save us from that config hell others speak of /s
USB-C and usb 2/3 are not the same thing. You can have a standards compliant USB-C port shape that delivers USB2 speeds which is what the non-pro has and a USB-C port that implements USB3 which is what the pro has. What arstechnica says is that in bot cases for the Pro and non-pro Apple delivered a standard usb implementation with no additional proprietary requirements
it makes you a Windows engineer which is worse
And then we both lie to the client
Just wait until you have to work as part of a team on a big project. The lack of types will murder the team’s productivity
In the world of C and pointer arithmetic this makes perfect sense /s
Tell me you are a Java dev without telling me you are a a Java dev 😂
Just create a al Inter rule that rejects Any types and a pre-commit hook that refuses the commit if the linter fails. Sometimes the brute force approach is the best way to teach
Before 3.9 the lack of type hints made it a nightmare for large projects. Strong typing is, among other benefits, a way of self documentation and helps IDEs with auto-complete. If I use Python I always use type hints and if I have to use JS sigo with Typescript instead
I’m sorry but stackoverflow will give you a tardigrade and swear to you that it was a frog when they tried it on their PC
If they move to Python they can just have pain without constant 😜