• 0 Posts
  • 17 Comments
Joined 2 months ago
cake
Cake day: August 20th, 2026

help-circle
  • Yeah, I reflected on your comment for a bit and I can see what you’re saying. All software uses dependencies, but how they are shipped is different for a lot of languages. If we take an extreme example, Go has a lot of the same microdependencies that Python, JS, etc. have, (probably a lot more than Python even), but since programs are usually compiled into a standalone binary, you never think about them as a user. Interpreted languages on the other hand tend to not do this because they’re not compiled, and when you’re installing a dependency, you’re often installing the source code itself, rather than a shared library or .jar like you would in C++ or Java.

    A lot of people do complain about virtual environments though, and while I don’t personally have a problem with them, I do wonder why nobody uses bundlers in Python. It seems that something like this already exists, but it doesn’t seem to be widely adopted or used for all the complaints I hear about virtual environments and such.


  • It’s not a question of what other browsers would offer, that doesn’t really matter all that much. From Mozilla’s perspective, it has more to do with the fact that Firefox has to keep up with a behemoth that has several times the amount of money and resources that they have.

    But for you and me, it’s something completely different, and much more ominous than whatever Mozilla’s issues are.

    The truth is that, now that Chrome has monopolistic control over the web, they can make it into whatever they want it to be. And I frankly don’t want to find out what that is. Maybe it’s the return of AMP, maybe it’s more invasive DRM, maybe it’s forcing you to put your ID into the browser so they know who you are and can blacklist you from the web if they have a vendetta against you. Maybe it’s the fact that they won’t let you browse the web on a computer if it doesn’t have a locked bootloader and rootless access to the OS the same way Android does.

    These may sound like crazy ideas today, but bear in mind that the hell we’re living today is the long term realization of the crazy ideas of a few decades ago. Why should we want to see what that’s like? Why shouldn’t we be trying whatever we can do to prevent it?


  • Google has done more for web standards than the open source community ever could

    Google was a great company when they were an upstart that needed to create standards so they could compete with the likes of Microsoft and Apple. They pushed for standards, adopted them, and promoted others to do the same.

    Today, they have weaponized standards to entrench their monopolistic positions. They pushed so many standards in CSS, Javascript, and other technologies that it’s impossible for a competing browser to emerge outside of Chrome, which they own, and Firefox, which… they also own in any way that matters. And they also leveraged their search monopoly to favor websites that adopted the standards they were trying to push in order to force the web to adopt the standards they wrote, and therefore, their own browser.

    They helped create the open web. Then they claimed it as their own.

    It’s a great example of how a group starts out being your friend, but then amasses all the power for itself and gets corrupted by it. They have not been our friends for over a decade now, and we can all see how bad it gets.





  • Sure, it’s slow. Google’s landing page is 4 MB for a small graphic, a text form, and some buttons. But what are you going to do? Not use it? They won. They don’t have to fix shit.

    This neglects to include the massive amount of additional front-end code Google (and other large tech companies) toss on their webpages for things that are purely for their own benefit while being of zero or negative value to the users. Mouse tracking, analytics, fingerprinting, and all kinds of other harmful content that tech companies put out go a long way towards reaching that 4MB figure.


  • It’s not so much “But that’s not how you build stable software.” It’s more like “But that’s not how you build software [at all today].” Modern software is powered by loads of shared packages, that’s just how all modern languages work. This is equally true for Rust and Python.

    You’re not wrong - all libraries with automated dependency packaging do have this problem. But you’re downplaying the scale by a lot. Javascript dependency graphs are absolutely massive. Python has a decent standard library that reduces the number of shared packages by quite a bit. There are definitely downsides to having a large standard library like Python has, but it does significantly reduce the probability of a supply chain attack compared to Javascript.

    I can’t comment on Rust personally, since I don’t have much experience with the ecosystem.



  • The magic damage meta is so much more interesting that right-click damage. Every fight, you’re on the edge of your seat wondering if they’re going to be able to burst down the main hero, or are they going to run out of mana/spells/cooldowns. Teams have to coordinate their spells and abilities which just makes for much more interesting analysis. It’s just much cooler than watching HP bars steadily tick down from right clicks.

    You’re definitely right about all the saves in the game making heroes like Jugg unviable. The game has evolved a lot over the years with a lot more itemization, and the game continues to get better and better, but it’s also made many of the original heroes feel pretty unloved. A lot of the new mechanics in the game haven’t been backported to them. Look at Muerta for example - a viable carry because her ultimate goes through ghost scepter (right?) and she has a better built-in farming mechanic too. So yeah, Jugg does need a little more in his kit, but you could probably say the same about a lot of the old heroes too (especially carry ones).


  • Maybe. The thing about nullifier is that any of the other 4 heroes on your team can build it too. And even if you fix that issue, there’s still the fact that there’s still too much of a change that you jump away to different targets.

    The problem with omnislash is that it’s just too RNG to be useful in pro matches. You don’t know who you’re going to hit, and you don’t know where you’re going to be when it’s over. That’s fine for pubs, but can’t work in pro matches. And then there’s the balance issue - buff it too much and Jugg becomes a smurf hero, or first phase ban in pro matches. Bounty hunter is another great example of this - it’s either in the dumpster or first phase-banned.

    It’s hard to make a hero that works both at 1k MMR and in the pro scene, and at all MMR levels in between too. So we end up seeing a lot of bland heroes in tournaments because it’s really easy to balance the game around all the heroes’ HP pools. The tanky strength core meta (like carry DK that felt like it was meta for 3 years) was really what killed my interest in watching the pro scene.

    Well, that was a bit rambly, but with all of that said, this year was a lot better I have to say - really refreshing to see all the magic-based linueups. Seeing teams trying to burst through heroes with just enough mana/abilities/damage amp was really what made all the fights fun to watch.