I completely agree. For basic things, it is very good. But for productivity, it leaves a lot to be desired, because they (the developers) simply cannot accept that different people work in different ways and they refuse to accommodate that.. I prefer environments that can be adapted to my workflows - I don't want an environment that forces me to adapt to it. And it doesn't help that extensions tend to break on upgrades.

  • source
  • parent
  • context
  • Interesting, I was not aware of libdecor. Sorry to hear that it degraded your experience - it really sucks when things like that happen. For what it's worth, I have seen some interesting themes which could be a reasonable solution to that problem - basically, they made the titlebar very thin or completely missing, except in the area where the window buttons were located, which were enlarged. Not sure which window manager they were made for though - I think it was either xfwm or openbox.

    But in any case, this is the problem with CSD - it doesn't really have a complete, holistic vision. It's great that they're trying to be innovative, but then they very quickly run into problems like the one described by the Factorio developer above. So now they're in a very awkward position that simply cannot meet everyone's needs.

    And yet, we never had this problem before they went on their quixotic CSD journey - that's why many people think it was a really bad idea.

  • source
  • parent
  • context
  • [–] 8 points 1 year ago* (6 children)

    I don't understand what change has to do with it. The problem is, lots of people have used it, tried it, criticized it, and been ignored. It has nothing to do with change.

    Change is fine, as long as the new version is better than the old one. Look at how KDE evolved. Sure, there were a lot of people that didn't like the 3 -> 4 transition (not me personally, I loved KDE4), but very few people lament what KDE has become today and it certainly is very different from what it was during the 3.x days.

    Personally, yes, I and a lot of other users have read why GNOME does not implement SSDs, and frankly their reasoning is not very convincing, but I don't think it matters that much. The fact is, users don't care why it's not implemented - if they don't like it, they're just going to criticize the project and that's just why GNOME is so widely hated.

    Trust me, I don't want to hate GNOME - I wish I could just make my life easy and use it as a sane default. But if it's not good, then I can't do that - and by "good", I mean how I define a good desktop, not whatever creative definition they dreamed up.

  • source
  • parent
  • context
  • The funny thing is, before Google existed, people had no idea if their marketing attempts were working. Maybe they had some ways of knowing or guessing, but there was no way to know how accurate their metrics were. Internet-based advertising, and tracking-based advertising in particular was supposed to change that.

    And now that we sit here with a duopoly of advertising giants, we're back to the stage where marketers just have to trust that their provider is giving them good helpful information. And how are they supposed to know whether they really can believe it or not? They can't of course! So we've come right back to where we've started.

    But considering they still spent tons of money before Google and Facebook gave them these "analytics", it looks like they probably don't even care that much.

  • source
  • [–] 2 points 1 year ago (1 child)

    I would love to try making a game. Even games that I love to play still have a few minor things here and there that I wish were different. If I made the game myself, I could just change it myself and make it as close to perfect as I'm humanly able. Engines like Godot and similar make it so easy to do these days.

    But the competition is extremely fierce. There are so many games on Steam that the chances of "making it" and being the next Hades or similar are just not that good. I'm clearly not the only one with a dream like this. That and the fact that making a game is a ton of work. Graphics, audio, gameplay, balancing, marketing, social media🤮, etc.

    If I'm in the position someday where I don't need to turn a profit from it, then I may do it anyway, but I really feel bad for all the people who are trying to pursue their dream and yet may never make it there. We're in a golden age for the players, but for the creators, it's very difficult, to say the least.

  • source
  • One principle I try to apply (when possible) comes from when I learned Haskell. Try to keep the low-level logical computations of your program pure, stateless functions. If their inputs are the same, they should always yield the same result. Then pass the results up to the higher level and perform your stateful transformations there.

    An example would be: do I/O at the high level (file, network, database I/O), and only do very simple data transformations at these levels (avoid it altogether if possible). Then do the majority of the computational logic in lower level, modular components that have no external side effects. Also, pass all the data around using read-only records (example: Python dataclasses with frozen=True) so you know that nothing is being mutated between these modules.

    This boundary generally makes it easier to test computational logic separately from stateful logic. It doesn't work all the time, but it's very helpful in making it easier to understand programs when you can structure programs this way.

  • source
  • [–] [S] 2 points 1 year ago

    Interesting, I had never heard of ccache before, though yes, all good build systems (CMake, Ninja, etc.) should cache intermediate object files.

    But the projects I was working on were so large that even binary and unit test executables were so large that even they would take ~20 seconds to link. You can't use caching to alleviate that buildtime cost unfortunately.

  • source
  • parent
  • context
  • [–] [S] 0 points 1 year ago (2 children)

    I think it’s just because it is always recommended as an “easy” language that’s good for beginners.

    The only other thing it has going for it is that it has a REPL (and even that was shit until very recently), which I think is why it became popular for research.

    If that's the case, then why didn't Javascript take its place instead? It's arguably even better at Python in both of those areas....

  • source
  • parent
  • context
  • [–] [S] 2 points 1 year ago

    Agreed. I have seen a lot of Python code that was really painful to massage back into a more structured object hierarchy. Java certainly does a bit better in that respect, and as a language, it does a much better job of encouraging better practices, but I think it's also largely due to the kinds of people that use those languages as well.

  • source
  • parent
  • context
  • view more: ‹ prev next ›