this has been years in the making, and converted from a golang version into rust only very recently not to deny your statement though lol

Interviewer: How are your programming skills? Not Me: A little rusty... Interviewer: Hired!

@@karpfenboy it only proves that rust is future and all other languages are merely the past

Seconded! While the 100 seconds videos are always a joy to watch, I _sometimes_ get an impression that's quite different from the actual experience with the actual tool. This is like the 101 that gives a look and feel of the thing in practice.

^This

Definitely agree. Being able to write intuitive and easy-to-maintain code is also very important, especially if you only have a very limited number of concurrently active users.

Not sure I would agree here. It's a database - not scaling is not an option. I would store my data somewhere else if fast & synchronised access is not needed.

@@EdubSi again, it depends on the project,

True, I most likely don't need the best performing stuff, just need something to get it working , instead of spending precious time developing more complex and hard to maintain tech stacks.

I suppose if you're sure you'll never need to scale it, but most projects worth working on do have some scaling goals at some point. Not sure I'd want to invest in this technology then have to re-write it all in the future.

It seems like it's built where you can pick the tradeoffs you are willing to live with. Some want "all teh speed" while others just want enough speed to be reasonable, but relatable code.

You can also enforce schema too

that's like saying that spoons make soup so easy to eat that one might burn oneself, so better stick with forks.

It's also like saying that exposed wiring makes it so easy to do electrical repairs, but that one might accidentally shock themselves if they aren't careful. Making it hard to foot-gun yourself isn't a bad thing in itself. It's at which cost we should argue about. Some will prefer the freedom of schemaless. Others will prefer the structured nature of a schema. I lean towards the latter.

@@pjarnfelt in your analogy choosing to use a fork instead of a spoon suggests it will take longer to program with a schema based db , however being burned represents your query’s being so in performant many fail and users are left waiting multiple seconds for anything to load on top of their own internets speed, and or crashes start happening from lack of ram to support the quantity of requests for how long each ones taking. And although as the developer you might not care about a little burn, programming is more like being a chef. Are you gonna serve your soup while it’s still boiling, or make sure it’s just hot? Cause you won’t have many users returning if their experience is being burned by a painstaking slow website or application because of non thought through database scheme or just lack of one

@@fluffio2976 If your application could kill someone (i.e. you're in critical systems) then you should be using an enforced schema and other safety checks. 99% of our applications are _not_ critical systems, yet our DB tools are designed as if they are. How many decades did it take for someone to design something intuitive like this?

Very relatable

Yassss

Same

Same

@A english is sometimes weird… but then, so is the internet… 🥶

Same dude. Except I'm not an architect - I mainly sit around in my underpants watching KZfaq videos, but this makes me consider giving all that up...

Think twice before jumping in development. Companies are laying off and the next decade might not be as bright as the last one. Cheers if you guys still make the switch :)

My man talks about changing his life around. I mean rn he sits in his underpants doin nothing and he thinks about developing, you tell him to think twice??? What did companies/colleague did to you man WTF?

@@huydh This has always happened. Recruiting and laying off is just a cycle when it comes to IT and does not mean that things will get harder for future developers. This is like clamining that "AI will steal our jobs". It just won't.

@JT wanna swap? Been a software engineer for 10+ years and writing code for 20. Wish I’d studied architecture and as building tangible things in the real world. Agree, SurrealDB looks Sick! 😍

Modern DBs are what they are for a reason. Have fun diagnosing your performance issues on a production database after a dozen of developers have crafted the most obtuse and convoluted queries possible. The syntax might be simple on the surface but the generated queries under the hood are going to explode quickly

I love ArangoDB which is much further into development (mature) but this looks more intuitive! I'll definitely be following this project...it has that new, shiny vibe! LOL

Because some pain in the ass must build up to make improvement worthwhile. 😃

Chances are knowledge of this database has reached more people than knowledge of this guys KZfaq channel. And there’s documentation so why would you need a course? That’s the give me the answers I don’t want to put in the effort type mindset

@@dabbopabblo nearly every piece of software out there that has a course for, is also documented. That point doesn't hold. It doesn't matter if other people know more than Jeff because some people really like the way that Jeff teaches and would rather have him doing the course, which is also a way to support a creator they like. Regarding your last sentence, why is that any of your business? It's not your time, nor your money. Why do you feel like this comment could be useful at all? Do you even know what are this person's intentions with knowing this tech? You know way too little to be placing judgment

@@YuriG03042 And what do you know about me to be judging my opinion? Its almost as if anyone can share any opinion they want and judging someone for being judgy is just hypocritical. Like your one to talk about not posting a comment because its "not useful" when you define criticizing an opinion as non useful, yet post a comment about your opinion on the matter. But my rebuttal to your counter argument in regards to my original point is; Sure general information tutorials and courses can be useful for understanding the fundamentals, however without digging into the documentation you will never know more about the subject than the person who made the course you took (assuming you only learn from that course and others) when the person who wrote or taught that had to learn from somewhere, and even if that was another course its not a chicken or the egg type question. The courses simply would not exist without the prior knowledge being available through documentation. Even in the case when none is provided because any project that lacks the industry standard of being properly documented will fail to be picked up by the mainstream and not be worthy of spending time making courses on. Point is if something has the potential to have a course made about it(disregarding general concepts of course), the information was already readily available and the people who actually take their work, hobby, or mere interest in programming seriously enough will already have the resources available to fulfill their desire to learn more about the product or library or framework in question with no course as crutches necessary. If a course is available as an appetizer into the content by all means necessary watching it can be refreshing before reading through potentially boring documentation. That's the only reason I watched this video as I haven't even touched this database yet and want a better idea of what its capable of before dissecting the documentation and refactoring my production code to use it. But in the end I truly believe requesting a course for something you have the means of learning yourself is a "I don’t want to put in the effort" type mindset.

@Batman Well if you ever find yourself using react maybe you should just reevaluate your choices and learn an actual programming language instead of syntactical abstractions on top of one, like all these kids who've been stumbling through KZfaq having the audacity to refer to themselves as developers because they watched a few react tutorials have been doing

@Batman cause "react" developers are the kind of people on stack overflow admitting they avoided working with promises because they are "too" complicated

But it could be solved with a single SQL table. What was the problem?

gogogo benchmark