I feel like all the points you raise could be replied by : if you do not like it, no one is forcing you into doing it.

It is my understanding that people do this for fun - to take the occasion to get into a new language and/or exercise their problem resolution skills.

Personally, although I love coding (it is a passion), after a whole day of coding I do not feel the energy to partake in a coding event. And during holidays I am busy doing other stuff. So I do not participate in the Advent of Code. But I am still glad that the event exists for people who enjoy it and have the time for it

For a first time don’t try to get the strongest character possible. It’s a time sink to do that. Usually the main campaign of games are beatable even if you screw up something. The worst that can happen is you backtracking a bit and spending time to level up before doing the next quest.

When you played the game once and got used to the mechanics you can make a 2nd char and plan it more deeply ahead if you wish. You know what mechanics you like so the prospect of finding what to invest in what is worth etc… becomes more streamlined. But you don’t have to. You can just be happy to have finished the game and call it a day.

That’s what I did for Diablo 4. After the main campaign I did not feel like venturing more into the game or making another character so I started playing another game. If you really want to 100% a game it does require a ton of time and planning but you don’t have to

On the world’s roads last year, there were over 20 million electric vehicles and 1.3 million commercial EVs such as buses, delivery vans, and trucks.

But these numbers of four or more wheel vehicles are wholly eclipsed by two- and three-wheelers. There were over 280 million electric mopeds, scooters, motorcycles, and three-wheelers on the road last year

There are about 20x more e-bikes than electric cars. Of course its going to demand more oil.

The real question is what is best in terms of oil demand between electric cars and e-bikes

Agreed that some people can find it easier with explicit names - however some people find it easier with short meaningless names as it makes them focus on the abstraction rather than the naming. There is no right or wrong here. It all depends on the reader.

A specialized architecture will always be better than a general purpose processor no matter how advanced the tech gets.

So you will always need a GPU as a GPU is quite literally a Graphical Programming Unit, that is a specialised architecture for Graphical computations

A friend of mine got asked if she had a boyfriend. She asked back “why that question”. It was to know whether she would be likely to get pregnant and miss work.

What a horrifying mentality some companies have

Hot take: Git is hard for people who do not know how to read a documentation.

The Git book is very easy to read and only takes a couple of hours to read the most significant chapters. That’s how I learnt it myself.

Git is meant for developers, i.e. people who are supposed to be good at looking up online how stuff works.

There are techniques like abstract interpretation that can deduce lower and upper bounds that a value can take. I know there is an analysis in LLVM called ValueAnalysis that does that too - the compiler can use it to help dead code elimination (deducing that a given branch will never be taken because the value will never satisfy the condition so you can get rid of the branch).

But I think these techniques do not work in all use cases. Although you could theoretically invent some syntax to say “I would like this value to be in that range”, the compiler would not be able to tell in all cases whether it’s satisfied.

If you are interested in a language that has subrange checks at runtime, Ada language can do that. But it does come at a performance cost - if your program is compute bound it can be a problem

Why would you have to choose between tests and compiler checks? You can have both. The more you have the less chance of finding bugs.

I would also add that tests cannot possibly be exhaustive. I am thinking in particular of concurrency problems - even with fuzzing you can still come across special cases where it goes wrong because you forgot a mutex somewhere. Extra static checks are complementary to tests.

I think you can write “unsafe” code in Rust that bypass most of the extra checks so you do have the flexibility if you really need it.

When I first got daily access to internet (back in 2009), I got curious about how programs are built. Like, if I wanted to make my own application, what should I do?

I googled something along that direction and it linked me to a famous french website for learning programming (site du zéro) where I learnt C language.

After the course I made a 2D Snake game with SDL2. How naive was I to think I could write it in one go without testing anything in between! I scrapped the 1st attempt because it was a disaster and randomly inserting/removing * was not helping.

I started again from scratch, testing in smaller steps, and I really liked it. After a couple of weeks I had my Snake game working! I was so proud of it that I showed it to my mom. I do not have the source files anymore but I still have the binary somewhere

Afterwards I sticked with it and continued programming - I was back in school without much access to internet so I programmed on my TI-83+ instead. Eventually I pursued computer science studies then a PhD… It got me hooked real good.

Looks cool! This reminds me of Freespace, another beautiful space fighter game

Yes, getting into a new project is hard. Even when you do know the languages and frameworks it’s still hard because you have to get into the mini ecosystem that the developers of that project built. In companies there is usually an expected amount of time (days? weeks? Months? Varies on the project) where a new developer is not really expected to do anything major, just getting used to the project.

I do not know if you are professional or hobbyist. But coding takes a lot of time, a lot of it is spent on just figuring out how you will code this or that feature ; then another bunch of time is spent debugging ; and finally, yet another bunch of time is spent integrating your new feature. That’s why it’s a whole job, and that’s also why you need a ton of free time to do this as a hobbyist.

But the good news is that once you spent that upfront time to get into the project, you can code more efficiently (that is, get right to the features you want to make) and you will also spend a little bit less time getting into other projects because although projects are different, there is always some level of organization that remains similar. The more advanced you become, the quicker you can get into a “production” state where you can code right away thanks to spending less time figuring out how things work.

This is such a basic functionality. It does not deserve advertisements, it should have been there from the start.

and it’s not locked behind a paywall

Are we supposed to cheer?

The Christian Bible’s Matthew 24 had a prophecy that is about to become historical-fact, in the coming decade.

Here’s a decent version of it:

https://www.biblegateway.com/passage/?search=matt+24&version=AMPC

That bit around verses 15-20 is the pertinent area.

Simply wait 1 decade, and see: if Israel still exists, as a country, in 2033, I’ll eat a hat.

The nice thing about prophecies is that they can never be proven to be false. Indeed, one would have to examine the future to prove it wrong. Which is either impossible or unrealistic.

Me too I can make a ton of prophecies and claim they will be eventually right. I will never be wrong.

Let’s see. Let me prophesize that:

• The US will cease to exist
• We will encounter aliens
• See where you are living right now? Eventually, it will be filled with lava.
• See where you are living right now? Eventually, it will be flooded with water.
• A giant comet populated with nyan cats will crash on Earth

However, you can be sure that in 2033 I will come back in this thread and have you eat a hat. Marking the date and the link in my calendar. If lemmy is still alive, that is

They are not making them more efficient. They are studying how to make them more efficient. It’s a really big difference because I am not yet ready to place my life in the hands of a CNN-based AI

Yeah exactly. Here follows some spoiler for those who have never played Dark Souls

The bottom line is that I think you need to have someone telling you where not to go to really enjoy Dark souls. Because its not obvious whether you die because of your incompetence or just because you were not supposed to be there right now. I wouldn’t say its bad design though - but it’s not for everyone for sure

I used to dislike dark souls. Recently I tried it again - I struggled but I finally got the hang of it!

I think the hardest is to know what to do. I figured out I was struggling because I kept going in zones I was not expected to go yet.

Also it’s such a big shift compared to what I was used to. You have to wait for the right opportunity to attack rather than going in there and relying on reflexes.

I doubt Elon Musk does programming

I see. You want to offload AI-specific computations to the Nvidia AI cores. Not a bad idea, although it does mean that hardware that do not have them will have more CPU load so perhaps the AI will have to be tuned down based on the hardware they run on…

You could imagine training one AI for each game AI problem like pathfinding but what is see the benefit over just using classical algorithms?

Can DLSS and XeSS be used for something else than upscaling?