2,220 karma · joined October 30, 2018
Probably true of absolutely everything in the end.
But Dirt Rally on the other hand... That is a different story. VR is great when realism is the goal. Games in zero g environments are cool too.
optional int32 result_per_page = 3 [default = 10];
If the default value is not specified for an optional element, a type-specific default value is used instead: for strings, the default value is the empty string. For bytes, the default value is the empty byte string. For bools, the default value is false. For numeric types, the default value is zero. For enums, the default value is the first value listed in the enum's type definition. This means care must be taken when adding a value to the beginning of an enum value list. See the Updating A Message Type section for guidelines on how to safely change definitions."
Well according to the docs on protocol buffers at least my understanding is as I have read elsewhere.
I don't know what your problem is guy.
I watched a talk about F# on YouTube recently and the guy said they used F# for domain logic and C# for plumbing code and he showed them working together...
I came from the Java ecosystem to .NET and even they are different. The .NET ecosystem was held back a little by the lack of embracing open source at the beginning and being super commercially focused. So things like finding a good library for easily working with PDF will set you back $400 rather than just using the defacto library that everyone has used forever and is free. I've encountered that with PDF libraries, rules engines, workflow engines, job scheduling libraries.
It's still a decent ecosystem, it just is different because of its roots.
VS Code doesn't come close.
I use VS Code when doing front end stuff with Vue/TypeScript and I love it for that, but .NET Core was painful on VS Code compared to Rider.
It just feels very clunky in comparison. I have to remember so many things, which I invariably can't so I have to look them up.
I find EF Core pretty straightforward.
I was under the impression that you can't specify fields as null. Instead they just get assigned whatever the default value is for that type.
That seems like a significant drawback for me if it is indeed the case. Especially in the case of a public facing API.
I like the idea of a lot of client libraries able to generate easily, I'm just not sure on this one point how to deal with it nicely...
I think you missed my point. Because you state:
>Basically there are ways how to fix it
My point is it's not actually broken. It's working. It's working very well.
Although it doesn't tend to, opportunity _could_ arise anywhere. So, potential geniuses are peppered everywhere such that if opportunity were to arise there there are people who can take advantage of it.
The assumption that it should work the other way around is ridiculous.
Opportunity isn't for geniuses. Geniuses are for opportunity.
So, in certain respects it's an enabler. Context always matters.
"Oh no! Think about all the potential geniuses we are missing out on! We must be doing something wrong!"
Ok, thought about it.
My conclusion is:
"Wow, the rate of genius production has never been higher, we must really be doing something right."
Could it be better? Sure. Is it getting better? According to Factfulness: sure.
I just don't understand the ridiculous in-built assumption that we are somehow wronging society and the potential geniuses themselves by them not being in a time and a place that makes use of the quality of the substrate of those particular individuals.
Well, sorry but nature doesn't optimize for the individual, it optimizes for the whole.
You may as well get equally mad at something silly like "why doesn't everyone always roll a 6?"
Think about it more like MyBatis meets Spring Data JPA. Define that entity in XML the run a code gen which gives you the CrudRepository class but also generates a controller that exposes an API with pretty good good ability to specify adhoc queries. Plus view models.
I think it worked because it both reasonably well designed and hyper opinionated.
It sounds like a workflow engine. I'm picturing one table that is very generic that tracks "this job id, this workflow type, this stage in workflow, this entity, this state of the entity" and a single job has multiple of those entries over the lifetime of that job execution and the JSON blob is the current state of things, so that you don't have to go and recompute that.
Yeah, it seems like a reasonable choice.
What sticks out to me in a scenario like that is a good CQRS implementation. The write side of it pumps in the history of the job execution, then denormalizers run to project that into a shape amenable to being read by the application.
It had a canonical XML format that entities were defined in and code generation for data access layers, domain models, view models etc.
It actually worked better than I've seen the abuse I've seen developers put EF through. I found it nicer and simpler than times I've worked with Hibernate.
I'm not going to say it was perfect, but every time I think back on it it makes me want to revisit the idea of leveraging a bit of code generation or metaprogramming to be able to have a canonical definition of an entity transformed into concerns that deal with the given entity at different points in the application.
That part of it just really hit the sweet spot for me.
Its difficult for me to picture how Dapper even comes into play when you're doing this trick with the JSON blob.
Why not use NoSQL?
Also 1000+ properties on an object? I know some domains sometimes surface these kind of extreme cases, but is there not an alternative to having 1000 properties in one object?
I'm kind of curious about what data the select limit 1 queries were returning that the ORM couldn't get in a single query and had to go back per record. Can you shed any light on this?
ORMs have a degree of flexibility. It's possible to write n+1 queries accidentally, especially for developers who are new to the ORM. It's also often possible to address those issues. Sometimes trivially, sometimes not.
The other thing that comes to mind here is that maybe the query was hitting a non-covering index and that was triggering the lookups? In that case a covering index would have fixed the issue?
Curious about this one...
Use an appropriate combination of ORMs and raw SQL.