spartanatreyu

joined 2 years ago

It wasn't the profits or ads that got in the way.

It was the security that got in the way. (remember the whole TPM module thing?)

Iterating the version number was just a convenient excuse to throw more ads, and tracking in.

It's not bad, the word you're looking for is hammy.

It's done like that on purpose, it's completely aware that it's going out of its way to make fun of the 80s.

Dr. Becky's videos are always great

Good news, X is now down.

[–] spartanatreyu@programming.dev 8 points 2 years ago (1 children)

GUIs are much more complicated than they seem at first.

My recommendation is to learn and get familiar with a specific framework first, before branching out to other frameworks and learning how they feel. Then and only then would I start learning about the concepts behind those frameworks.

About the web stuff:

When it comes to GUIs, web is a crazy constrained chaos.

It runs everywhere, is backwards compatible by necessity, and yet is so fast paced that it experiments with new ways of doing things, makes mistakes, and tries to find ways around those mistakes.

It's fast pace leads to it creating things that other GUIs end up looking to for hard lessons and inspiration.

Web is easy to click, but only if you learn it properly. It has decades of old features that you shouldn't be looking at as a beginner.

Beginners should only be looking at learning (and only moving to each new step once they fully understand the previous steps):

  • selectors
  • block model
  • display modes (block, inline, inline-block)
  • position
  • flex-box

You can make any site you want with those basic concepts.

The other stuff:

If you're really really set on learning some of the concepts behind GUIs, you can have a look at the rust space which has a whole bunch of incomplete GUI libraries trying to solve problems. Creating a proper GUI framework for Rust isn't as simple as other languages. Rust's borrow checker means that devs can't just reuse existing linked lists and graph based solutions. Raph Linus is one of those devs who is involved in that space, and they're all experimenting and looking at each other trying to figure out which approaches will work best for them. You can see some of those notes here:

Modern PHP shits all over the PHP v3, v4, v5 days of yore.

Anyone making new projects from scratch is living in a land of bliss while those working in projects/frameworks that started in the days of yore are having experiences across the whole spectrum of, "Wow, I sure am glad we migrated to modern php" to "please kill me, I'm in so much pain".

[–] spartanatreyu@programming.dev 20 points 2 years ago

And yet people will blindly trust AI ~~hallucinated~~ generated results...

The free bots that were helpful (like remindmebot) will probably all die, whereas advertisers will pay for artificial chatgpt users to boost their own content.

[–] spartanatreyu@programming.dev 6 points 2 years ago* (last edited 2 years ago) (9 children)

No competitor?

What about VRChat?

Yes it has a tenth the users, but it's also designed around an expensive peripheral you strap to your face which prices out a lot of users.

[–] spartanatreyu@programming.dev 26 points 2 years ago (3 children)

It's not rebase vs merge, it's rebase AND merge.

Commit your changes into logical commits as you go.

Then just before submitting a pull request, review your own code. That includes reviewing your own commits too, not just the code diff.

Use rebase to:

  • Swap commits so that related changes are together
  • Edit your commit messages if you find a mistake or now have a better idea of what to put in your messages
  • Drop any useless commits that you just end up reverting later
  • Squash any two commits together where the first was the meat of desired change and the second was the one thing that you forgot to add to that commit so you immediately followed it up with another commit for that one missing thing.

Then, and only then, after you have reviewed your own code and used rebase to make the git history easier to read (and thus make it easier to review), then you can submit a pull request.

[–] spartanatreyu@programming.dev 1 points 2 years ago (1 children)

Yeah it looks like it, I wonder if the authors there had some sort of professional relationship with my link's host

That was the one I couldn't remember, I got GPG and PGP confused but I remember it involved email encryption.

This guy was the reason that every security dev had those personal public keys clearly posted next to their email address on every announcement and blog post they ever released.

view more: ‹ prev next ›