Nerd02

Interesting. Like I said in another comment in Italian it means exactly what I said. From the first line on the topic on Italian wikipedia:

A vasistas (also written wasistas) is a type of window that is also opeaneable on the inside […]. The system allows the door to rotate down and the opening is delimited by special stops, called opening delimiters.

But apparently, after reading the French wikipedia page they use that word for something else. So it appears that we did steal the word from them, but used it to describe something different.

Oh really? My bad then. We call those windows from the pic “vasistas” in Italian, and I was always told we copied that word from the French. I just checked whether such a word existed in French, saw that it did, and didn’t ask any further questions.

In Italian and French they are caled “Vasistas”, from the German “Was ist das?” (What’s that?), it’s said they called it that way because the first German tourists who saw those windows in France were confused and kept asking for clarifications on how they worked.

Axios for requests - easier than working with the Fetch API in some cases

May I ask what cases? I used to use Axios on Node, before they implemented the fetch API over there but I haven’t touched it since. And defintiely never used it on the client. Could you make an example of some case where it’d be easier to work with Axios than with fetch?

Interesting idea. I’m currently working on a Lemmy-ui fork for my instance and including a feature of this kind in the frontend would be kinda nice.

I’ll bookmark this and come back if I ever get to it.

Oof. Yeah maybe. I did play Skyrim on release, on a bloody PS3 no less. Pure pain.

Hopefully it doesn’t take them that long.

It might be, although I’ve read of some freezes happening even on the fastest SSD in the world so… idk, I think they might have fucked up somewhere. I also suspect there might be some memory leaks, although this comes solely from my experience, I have no data to show.

Tom’s Hardware article on the freezes

Yes, all very cool, but when are they going to fix the actual issues? Like, I don’t know, the constant freezes?

I’m loving this game so far, I’m playing it every night, but it feels like a constant test of my patience.

You do it if you want to, it’s a game :)

You can make decent money off it, but first and foremost it should be something you enjoy. Personally I think that’s a very chill way of breaking the monotony, after having spent too much time flying around or walking through cities to complete quests. Exploring planets has got the nice plus of not having to deal with loading screens, unless you want to get back to your ship and move to a different biome.

Then I guess this is what you get for talking about something without knowing what it is lol.

As another user pointed out, TypeScript is a different language (.ts extension) that extends JavaScript, meaning JS code is valid TS code, but TS adds various language features for type checking. Your editor is then able to interpret your code according to these type structures and warn you if you are making any stupid type errors like this one:

The problem many people have with TS (such as the “big projects” mentioned by Fireship) is that sometimes you end up having code that works but still have to do some weird type gymnastics to please the TS compiler and have it remove any errors and warnings.

That being said, frameworks that “create really weird undecipherable minified JS” do have their place, as they allow you to seamlessy do things that would be either very inelegant and verbose or significantly more complex in vanilla JS, but I won’t bore you with an excessively long wall of text.

PS: I love your Czech flag website. Had me jump on my chair when the music started blasting through my headphones.

How is that related to TS? Aside from the fact that your comment might have just started a civil war (no, vanilla JS is not “good enough”, they created libraries for a reason) this isn’t about using libraries / frameworks. It’s about needing some system to handle type annotations to avoid falling in the bottomless pit of:

Uncaught TypeError: Cannot read property of undefined

There’s no real alternatives to JS “for websites” (meaning on the frontend, the part of your code that gets executed on your client’s browser). That’s what JS was invented for and what it does best.

I say “no real alternative” because technically we also have WebAssembly, which is a tool that allows you to run code written with any language on the web, but if you indeed are a beginner approaching to web development you should just forget about this for now and stick to JS as you learn.

Of course this doesn’t mean that you can’t use Python on your backend, your server.

I think there’s a positive coming from this competition, though. Apparently this infighting has re-lit the want for type annotations to be embedded in vanilla JS (ECMAScript proposal). I feel like this would be the ideal scenario: things working right out of the box without needing a compile step or additional tooling.

You can get as close as it gets to this experience by using alternative runtimes such as Deno or Bun, which have native TS support (meaning you can just execute a .ts file without having to transpile it), but of course as soon as you have to write code for a browser you are back in the middle ages.

The backend is quite alright. The Rust backend makes it indimidating to approach, but I know it has many advantages.

The frontend could use LOTS of changes. I don’t like Inferno, it’s messy and confusing to work with. Instead, I would have opted for a Svelte+Tailwind stack for the UI.

I was under the impression that the Go compiler was written in C/C++, though don’t quote me on this one. My browser however is Firefox, so touché on that one.

Hot take:
Fuck TS, marry Go, kill Rust.