[-] FizzyOrange@programming.dev 2 points 6 months ago

What kind of vectors?

Without further information, right-open is usually the best choice.

[-] FizzyOrange@programming.dev 2 points 8 months ago

For benchmarking commands you can't beat hyperfine. But if you are really talking microbenchmarks you have to do that in-program so it'll depend on what language you're using.

E.g. for Rust Criterion is the go-to option.

[-] FizzyOrange@programming.dev 2 points 9 months ago

Why? MATLAB is pretty dense normally, and most MATLAB code is hacky scripts that wouldn't bother with "boilerplate" anyway.

[-] FizzyOrange@programming.dev 2 points 1 year ago

I think you will be disappointed by battery life. It is almost always worst on Linux than Windows. Sometimes much worse. Mine get 90-120 minutes. Yeah in 2025. Apple just released a MacBook with 24 hours of battery life.

Doesn't matter too much to me because I almost always have it plugged in, but yeah.

[-] FizzyOrange@programming.dev 2 points 2 years ago* (last edited 2 years ago)

WPRS uses the term rootless like this. I didn't come up with it. But I agree it is not a great term. If you can think of a better one I will happily use it. Parallels calls it "coherence mode", which also isn't great.

Actually Xprs uses "seamless mode" which is probably better.

[-] FizzyOrange@programming.dev 2 points 2 years ago

Yeah true. It definitely has downsides. But so does begging corporations for money...

[-] FizzyOrange@programming.dev 2 points 2 years ago

but there are literally dozens of strategies you probably don’t know about

Oh please tell me, wise old man! You can't be talking about garbage collection, reference counting, smart pointers, never-free, arenas, defer, or god forbid, the "I am perfect and can do it manually and never make mistakes" method. Because I know about all of those methods.

What are these other dozens of methods that I don't know about that mean Rust is unnecessary? 🙄

[-] FizzyOrange@programming.dev 2 points 2 years ago

Yeah i know, they are simply corrupt

They aren't stupid or corrupt. They have different priorities. Perfect privacy isn't a fundamental right. It's perfectly reasonable for some people think it is worth giving up in return for making it easier to catch criminals.

And yes it does make it easier to catch criminals. They aren't all tech masterminds with perfect opsec who think "oh, no E2E encryption in WhatsApp; I'd better use Signal instead".

I still think we should be allowed to have proper encryption. But I totally understand why some people don't, and it isn't because they are corrupt or stupid.

[-] FizzyOrange@programming.dev 2 points 2 years ago

Why would you use the is operator like that?

Why would you add two arrays like that?

Do you not use containers when you deploy

No because I am not using Python to make a web app. That's not the only thing people write you know...

JavaScript is so bad you’ve resorted to using a whole other language: Typescript

Well yeah. Typescript isn't really a new language. It's just type annotations for JavaScript (except for enums; long story). But yes JavaScript is pretty bad without Typescript.

But Typescript isn't a cop-out like Docker is.

But the language it’s built on top of it is extremely warty. Maybe we agree on that.

Yeah definitely. You need to ban the warts but Typescript & ESLint do a pretty good job of that.

I mean I would still much rather write Dart or Rust but if I had to pick between Typescript and Python there's absolutely no way I'd pick Python (unless it was for AI).

[-] FizzyOrange@programming.dev 2 points 2 years ago

Honestly I would take a look through a good standard library that provides a lot of algorithms (e.g. C++ or Rust). That has the basics, especially for data structures.

Also have a go at some hacker rank tests. Especially if you want to learn dynamic programming (abysmal name), they absolutely love that.

[-] FizzyOrange@programming.dev 2 points 2 years ago

Lol no. Please show me where he says that.

[-] FizzyOrange@programming.dev 2 points 2 years ago

Yeah I agree but in my experience developers seem to struggle with "keep important things in history; squash unimportant things". An open "merges allowed" policy leads to people unthinkingly merging branches with 50 "typo", "fix" commits for a 100 line change.

Dunno what the answer is there.

view more: ‹ prev next ›

FizzyOrange

0 post score
0 comment score
joined 3 years ago