Other accounts (verify ownership):

  • @moseschrute@lemmy.ml
  • @moseschrute@lemmy.zip

aspe:keyoxide.org:JOVNV7OHSJCZMPZCCWS5TZI34A

  • 10 Posts
  • 274 Comments
Joined 1 year ago
cake
Cake day: October 6th, 2024

help-circle


  • I think what’s happening is the app is refreshing in the background, and it’s not smart enough to tell the difference between initial launch and background refresh. I would either have to think of a solution to tell the difference, or have a toggle to disable automatic refresh entirely, so you always have to pull to refresh. But even I solved the refresh issue, I think it will still throw you to the top of the feed :/






  • Blorp dev here. Comment are virtualized. That means anything that isn’t currently in view can get unmounted to keep the comments page super snappy. For small posts, this is definitely overkill, but it means we can smoothly render posts with thousands of comments.

    I’ve kinda been waiting for someone to complain about this for me to fix it. What I’ll likely do is implement a custom search box that is compatible with the virtualized comments. I have a lot on my plate rn, but I’ll get this fixed as soon as I have time. Sorry for the inconvenience.








  • That’s funny because I - having not written much C++ - have an irrational hate of the language. But I like JavaScript. I think I need to look at C++ through the same lens I look at JS through.

    Imo you can write pretty performant websites in JS. I guess it depends what you’re doing, but e.g. if you pay attention to you’re rerenders in React, you’re gonna have a much better time.

    But I also totally understand as soon as you wanna do some compex stuff, JavaScript is not a good time. I don’t think webassembly has worked as smoothly as promised, but in theory, that should let you bring some C++ into the browser.





  • You’re not wrong, but newer version of the language have steered devs away from these quirks. The quirks remain because the JavaScript language is 100% backwards compatible. It’s fun to laugh at these quirks, but I’ve been a full time JavaScript developer for 4 years and part time since 2015, and I’ve never seen any of these quirks come up in the real world. If you tell your developers to use === instead of == in code review, you eliminate most of the problems imo.

    JavaScript tooling deserves more hate imo. The ecosystem is kinda a disaster, but Vite is making a lot of progress in fixing that. If you ignore React Native and metro bundler, I think the state of web is looking pretty optimistic right now. At least from a technology perspective. From a business/AI/enshitification perspective we’re cooked lol