In the case of scikit-learn, the code implementing some components does so much crazy dynamic shit that it might not even be feasible to provide a well-engineered serde mechanism without a major rewrite. Or at least, that's roughly what the project's maintainers say whenever they close tickets requesting such a thing.
I'd think the CPU will drop proportionally to the TPS, they just want to show how high it can go here.
(1) In general, 'c' is always 'c' at the command line, regardless of the platform.
(2) yes, there are options and build tools, but cc my_program.c -o my_program works fine. I have a very hard time figuring out how to compile/run java.
(3) hard to see how this has anything to do with 'C', vs any other compiled language.
(4) so?? I would think I would be more concerned about how to use 'c' for my problem, without worrying about how to use 'c' to solve some other problem. It is hard for me to understand why a language that can do many things is more problematic than a language that only does a few things.
My sense is that reading this article makes things harder, not easier. Most people do not care whether an int is 32 or 64 bits.
I won't argue that copying things (that are not ints or floats) needs to be understood, but many popular languages (specifically python) have the same problem. Understanding the difference between a reference and a value is important for most languages.
There are different schools of thought -- those that can imagine lots of issues after reading the documentation, vs those that simply try writing code and start exploring edge cases when something breaks. I learn faster by trying things, and rarely encounter the edge-case issues.
* install java (includes compiler/runtime): `sudo apt install default-jre`
* compile: `javac MyProgram.java`
* run: `java MyProgram`I’ve noticed this with many more shows recently and personally don’t subscribe to it. I very much dislike how more shows include distracting visuals, sophomoric humor, and sexual innuendo as if it’s normal for younger kids. It’s not. Rewatching what I watched as a kid at these ages(Barney, Sesame Street, Gullah Gullah island) with my kids definitely shines a light on that.
Personally I think having a strong type system with an IDE that instantly tells you if the data is the right shape is very valuable when interacting with network interfaces.
In Python you either send the request at runtime and see what the server responds with, or you read the docs, both of which are at least 10x slower than an IDE telling you nearly instantly.
Rust's type system can represent null and polymorphic types quite well, both of which are quite common in JSON-like network interfaces.
Macros work well for code generation that is often used to convert a network api spec into code.
Of course you can do types and macros in Python, but neither are primary features of the language so are not as well supported.