kelafoja

5 ms·

1.
by kelafoja 1y ago
You know that there are more friendly sounding ways to give this suggestion, right?
2.
by kelafoja 1y ago
> A procedual implementation will necessarily have the same essential complexity as the regex it replaces I don't think I fully agree with this, and I don't see a basis for why this should be true. If I have a very specific imp
3.
by kelafoja 1y ago
That is quite a generalization. The regex engine is tested, but my specific regular expression isn't. My ability to write correct regular expressions is weak, so there can be many bugs in the one line of regular expession.
4.
by kelafoja 1y ago
My problem is that regexes are write-only, unreadable once written (to me anyway). And sometimes they do more than you intended. You maybe tested on a few inputs and declared it fit for purpose, but there might be more inputs upon which it
5.
by kelafoja 1y ago
I agree, there are only superficial similarities. Like they're all 3 C-based. And Go and Rust both compile to machine code. I believe once one of the creators of Go mentioned that it felt to some users "like a faster Python".
6.
by kelafoja 1y ago
Thanks. I was starting to get pretty insecure about it. I don't actually know why in my brain it was tightly linked to only database access. It makes perfect sense to apply it to other types of data retrieval too. Thanks for the insigh
7.
by kelafoja 1y ago
Naturally, Repository is a pattern for data(base) access, so it should have nothing to do with objects that are not persisted. I used "entity" as meaning a persisted object. That was not very clear, sorry.
8.
by kelafoja 1y ago
Thanks, that makes a lot of sense. I don't have a whole bunch of experience with SQLAlchemy itself. In general, I prefer not to use ORMs but just write queries and map the results into value objects. That work I would put into a Reposi
9.
by kelafoja 1y ago
Thanks. In my mind, anything about complex structures of (abstract) classes and/or inheritance trees has nothing to do with a Repository pattern. As I understand it, Repository pattern is basically a generalization of the Data Access O
10.
by kelafoja 1y ago
Could you give me some insights what the possible alternative was that you would have rather seen? I am either now learning that the Repository pattern is something different than what I understand it to be, or there is misunderstanding her
11.
by kelafoja 1y ago
What is the alternative that you use, how do you provide data access in a clean, separated, maintainable way? I have seen it a lot in my career, and have used it a lot. I've never used it in any situation to switch out a database layer
12.
by kelafoja 1y ago
Could you explain how repository pattern is a "huge overkill that adds complexity with very little benefit"? I find it a very light-weight pattern and would recommend to always use it when database access is needed, to clearly sep
13.
by kelafoja 1y ago
I was so in love with Delphi 7 (didn't care much for Delphi 8, didn't try any version after). I don't think I've ever been more excited about a programming language/environment as when I was easily and quickly creat
14.
by kelafoja 1y ago
But the explicit goal of this project is not to evolve, but to rewrite 1:1. Also making progress bars and colors does not require Rust, it's equally possible in C, C++, Zig, Go, Swift, etc.
15.
by kelafoja 1y ago
Missing squeel (sql) and chason (json).
16.
by kelafoja 2y ago
Perhaps for those who would not like to buy cars from China.
17.
by kelafoja 2y ago
One of things I find challenging is understand the meaning of the word "scales". It is sometimes used differently in different contexts. Can it be performant in high load situations? Certainly. Can is elastically scale up and down