It's great to hear you've already tried X twice. But have you tried reading our FAQ section on X? Also, try using this setting that doesn't exist or this dialog that was removed in 2022
Depends. If it takes an assembly programmer 8 hours to implement <X>, can an equally proficient Python programmer spending 8 hours to implement <X> create a faster program?
Let's say they only need 2 hours to get the <X> to work, and can use the remaining 6 hours for optimizing. Can 6 hours of optimizing a Python program make it faster than the assembly program?
The answer isn't obvious, and certainly depends on the specific <X>. I can imagine various <X> where even unlimited time spent optimizing Python code won't produce faster results than the assembly code, unless you drop into C/C++/Zig/Rust/D and write a native Python extension (and of course, at that point you're not comparing against Python, but that native language).
If LLMs were like compilers, you could put src/ into .gitignore and only upload the prompt.
Even the earliest compilers didn't work by the programmer writing code, copying the assembly output into their source tree, and throwing away the code.
This is not a value judgement, they simply aren't the same thing at all.
You are much more likely to be repressed/harrassed/arrested by your local government than a foreign government. So a local government knowing your behavior is more likely to lead to bad consequences than a foreign government knowing.
Of course, that might change in the future. Hypothetical example, the US government bans you from using any US cloud services because of what you did in private.
Though that's not exactly exclusive to governments either, Google banning you from GMail and Google Docs because of your YouTube uploads is already a thing.
That's definitely true. Can't have generics / compile time evaluation across languages. Need to design your code around that restriction ahead of time. SQLite being dynamically typed luckily doesn't have any problems with that.
I've actually run into a similar problem with a C library before, because it heavily used macros as part of its API. Glad most developers don't do that.
Although MS themselves apparently don't realize that, considering how they push the web version which doesn't support them?
reply