fhunt

Do you anything about data science or deep learning? If this is not about scientific methods then what else?

And even if not? Why not question existing methodology, people just follow some news outlets believing one and only thing.

Problem is that most people don't listen and turned off their brain. Look at this thread. They rather believe some random experts and news outlets calling some random dudes with random degrees experts because they have themselves no clue, never lead always followed others. What do we expect?

False claims. There're as many who do and do you know what it does not matter for this discussion because data science and deep learning is a science independently of what some people do or not. This was the point.

Haha sure, read some papers about Bert and its successors. Come back and summarize what you have learned. But your comments shows so clearly that your opinion is set and politely you should check out data science and deep learning before you again write such shallow dismissals (which is against the guidelines btw).

Yeah, but just picking one of many requirements in game dev and advocating why lang x can do this better than y ignores all the other checkboxes. Yeah, C++ is nerve-wrecking but Rust can be even more. IIRC there was a thread about Zig vs Rust and why Rust is just the wrong tool (for OPs use case in that case). IDK but there is a reason why C++ dominates game dev and a reason why Rust still struggles with mainstream adoption compared to same agers like Go or TS.

Then take data science or deep learning which is a science as sophisticated, same there.

We trust experts from other industries so much that we do not tolerate any other view without having a clue what is going on ourselves. The reason is simple, we have our views, they are political and we refer to "experts" to make our views scientific. Just my opinion and I bet that a huge number will disagree again with this comment. But—could I be right? Why not admit that I might be right? Because it's a political topic and your opinion is set.

My question is probably off because I lack the knowledge but how do the commercial games/game engines do this then if this is such a rocket science? Something like Fortnite or an aged GTA do what you've described (downloading assets on demand without any fps-drop) for quite some time now.

Ofc I'm aware of this and this is what I did, I just want a nice form factor.

OT: Imagine "experts" from our industry explain the mainstream our world: e.g. what's the right programming language, or database technology, why types matter, or not?

Why do we trust "experts" from other industries?

Few weeks ago I was looking for something like this. If there was anything similar, it was always sold out or did never launch, I don't expect better availability with item. And if they ask for $100 which is way too high and would give me better boards, pls provide two M2 slots.

> but I wouldn't advocate completely doing away with them.

didn't say this

> Carefully written tests allow you to confidently edit the code without worrying that you might have broken something in the process.

yes true but again you get this with typed code without any tests for 80% of the code as well, look, it's about the quantity and what you are going to test. with types you need way less unit tests (some like ben awad say none!) but still integration tests. still doing tests like crazy and like it's 2010 defocusses your devs and makes refactoring much more tedious, change a small thing and rewrite twenty unnecessary tests from a too ambitious test warrior who didn't understand types. this creates a notion where codebases get stale and untouched for years. nobody likes to refactor test code bc it's an unattached piece of code which complicates things more than it helps, it rarely feels like a true spec but rather like some random code and the next one wonders why his predecessor wrote this test at all. this is so the past idk why people are worshipping this.

Write tests where types don't help anymore (integration tests!) and things are crucial, otherwise focus on the core logic. I have rather devs who write excellent typed code with just very few integration tests than somebody who drives nuts and goes down the full rabbit hole writing 10x more test code nobody asked for than actual code paired with such blog posts like from OP on top, they've missed the boat.

TS has by far the most advanced compile-time type system followed by Rust.

TS has the best and most responsive editor support (tsserver). I know that Rust's is much slower but IDK much more than that.

Re ecosystem and build system: TS' build system is not trivial but it's very flexible and has a bigger ecosystem.

> I'm not sure how they're mutually exclusive.

Where did I say that? I just meant, and my apologies for not being clear, focus should be types, ofc you still need tests. But not as many as a decade ago and more important, people must drop this dogma that tests are the key to everything. There are not and the more tests a codebase has the worse its quality and maintainability.

> I still practiced TDD

You can do this ofc but my experience differs: Once you have an excellent type system, both in terms of language features and tool chain eg editor, you can literally code for days without running even the compiler once. This is pure flow and very much the opposite of TDD. But the entry barrier of is much higher than TDD. Don't get me wrong, you still need tests but TDD?? IDK, this feels like trial-and-error-coding from 2010. I mean if we still used all Ruby, yes tests and TDD everywhere but the environment has changed.

OT but it this decade not more about types than tests?

Edit: Since this seems to be an unpopular opinion why stop here, haha: The more one stresses tests the more he/she signals that he must have missed years of advancements in software engineering. If you do this with peers, ok, but publicly? Even Ruby added types, not the kind of types we hoped for but still, it's a strong signal. If your lang has a mature type system you don't need half of your tests anymore and might not be into such write-ups. Praising and writing gazillions of tests don't make you look smarter, very much the opposite.

i haven't used the original ctrl keys for a decade, nowadays everyone puts control on caps, even on a mac haha. then your left pinky is closer to ctrl + faster than your left thumb to command and if you want you beloved spotlight just install ms powertoys which has powerrun, it's the same, bind to alt-space

do you think this always praised evil-mode feels natural to a vimmer or feels like something close but yeah, not great like all vim emulations in all other editos?

then you might have missed coc.vim (vscode's full LSP for vim)

me too, plus some oddities like c-d and c-u are not remapped to d and u like on vimium, while not standard compliant it's a must because it is overridden by a browser bind. otherwise it's fast but there was more stuff which was not great/

There are not as far apart as I thought https://trends.google.com/trends/explore?date=all&geo=US&q=v...

Moved to Win after a decade on a Mac, this doesn't make sense, most Mac keys are not much better and you are just used to it, rather install AHK, something which no other platform has, and remap keys in a sane way.

IDK I am totally fine with i, I and A haha and the brain is also faster when processing chords from the fingers only. If you blend feet or even just thumb strokes in you significantly slow down.

edit: just thinking of piano players, maybe I am wrong but this thing feels odd

Thought how great, for a split-second. But key for being 24/7 in front my computer with zero issues for decades is among other things—I move all the time, hence I need a keyboard which moves all the way with me and you can imagine that my feet are also moving their location and nobody wants to arrange all the foot paddles every time you move. And in these times in your home office it's great to put your feet up here and then.

Depends on the schema changes. If you (1) change/remove existing keys from existing types, you need as well a migration which runs before the app starts. If you (2) add new keys to existing types or add new types you don't need migrations. That's the beauty of NoSql or in particular Mongo which most forget, you just write to the db and Mongo creates key, collections and dbs on the fly if not there yet. But again, only do this if you have validations before in place. Otherwise you end up will all these people complaining without having a full understanding of type safety and where to deal with it.

Case 1 should be always prepared well or better avoided if possible. It doesn't matter if you have sql or nosql, they're just more complex and with a big production database some longer downtime is to be expected if the changes/migrations affect large parts.

Me neither, try Tachyons which is what Tailwind wants to be, minimalistic, atomic, great UX.

While Hasura is nice, it's too much blackbox, too much all-in, too much risk, we decided against it.

2021 is great because of TypeScript, types and decorators (just put here any other typed lang with decoraters if you do not like TS). If your db is your leading system for your schema, everything else is derived and "code-generated" with all the restrictions SQL has. Which is not great if you want to decorate and enhance. Yes, you could use interfaces but it's not the same, you can't decorate code-generated type definitions but your architecture wouldn't stay DRY either.

If you think TS' types as the leading schema you do not need a type checked db like Postgres anymore, anything which can store data works just fine you have all schema definitions at one place which is not the DB. Good examples enabling such an architecture are TypeORM and TypeGraphQL. However most stick to SQL and 'my schema must be in my DB, there is no other way to enforce a schema' (but there is!) you just need a good architecture (types and decorators!) and not another mainstream-from-the-shelf-solution.

> our data was an inconsistent

Because you didn't put strict validation before data entered Mongo and I guess you didn't use a typed lang which makes such a validation like a no-brainer and quite natural.

SQL gives you type checking for free, Mongo does not. However, if you have a typed lang and have a proper validation in place you just have to define those at one place and not in the database and in your app (DRY).

@dang, I found this in the guidelines: Please don't post shallow dismissals, especially of other people's work.

I see good critical comments here but also many shallow dismissals from people who just sneer at the work of all software engineers who created MongoDB. Why is such behavior tolerated in any Mongo thread and why do these people never face any consequences?