Barges into a lemmy thread
Gives a strong, but quite abstract opinion criticizing abstractions
Refuses to elaborate further
verstra
joined 2 years ago
I have a convention to correlate the size of variable scope with its name length.
If a variable is used all over the program, it will be named "response". If it is <15 lines, then it can be "res". If it is less than 3 lines, it can be only "r".
This makes reading code a bit simpler, because it makes unimportant, local vars short and unnoticeable.
That's a valid point.
That's cool, but if I'm used to tmux already, what's the benefit of learning how to use zellij?
US states
United states states?
Aren't java packages strong modules? You can create circular dependencies between packages just fine.
No biggie, it a nice entry barrier to have, because nowadays, there just too much new frameworks and languages and crypto currencies.
Ah so the library is just made for problems like this. Who would have thought :)
What's the solution in Julia?
Because when you divide by zero and get a runtime error, the error will point you to location in SQL, not PRQL.
It's like if an error in a C++ program would point you to an offset in a binary and not the location in the source. This has a slight tone of sarcasm, because that's how compiled languages used to work. But after the years, they patched all leaks of their abstraction and now you are dealing just with the new language.
That's because the tooling is not there quite yet. For what you describe, that would have to be implemented by the compiler bindings for your language. And it's not that hard - basically one function. But yeah, not there yet.
You, my friend, should try EdgeDB. A database and an ORM in one.
When you change the data model, you can get to 100%, which you say is impossible for ORMs