• 0 Posts
  • 669 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle

  • Hmm, I don’t know anything about Whoogle, but from other privacy-conscious search engines, I would expect it to work when you use that URL in your bookmark.

    Three things I can imagine:

    • Something in your hosting stack strips the URL parameters, like maybe your reverse proxy, if you use one. You might be able to see in the Whoogle or web server logs, which URLs actually reach it. Might need to set it to debug/trace logging.
    • Maybe there’s a flag in the Whoogle configuration you need to enable to accept these preference URLs.
    • It’s a bug in that Whoogle version.



  • What I don’t like about the genre, is that I’m bad at it. 🙃

    More seriously, I do find it kind of frustrating at times. Restarting ten times in a roguelike, no problem, because it’s always a new challenge.
    But if I miss the same jump ten times, or have to retry the same platforming passage ten times, you’ll see me getting impatient, which means I’ll fail the next ten attempts, too…








  • Not sure, if I stopped listening to mainstream music around that time, but uh, both of my examples are from 2011, apparently:

    • Kind of a classic response to this question, is “Pumped Up Kicks” from Foster The People. It’s got that upbeat melody, and the lyrics are this:

    All the other kids with the pumped up kicks
    You’d better run, better run, outrun my gun
    All the other kids with the pumped up kicks
    You’d better run, better run, faster than my bullet.

    • And my other example is “The A Team”, apparently originally from Ed Sheeran, and apparently also with an upbeat melody. I think, I only ever listened to a cover version. But yeah, it’s about drug use and sex work, and how those kind of necessitate each other…

  • Personally, I’ve found Poetry somewhat painful for developing medium-sized or larger applications (which I guess Python really isn’t made for to begin with, but yeah).

    Big problem is that its dependency resolution is probably a magnitude slower than it should be. Anytime we changed something about the dependencies, you’d wait for more than a minute on its verdict. Which is particularly painful, when you have to resolve version conflicts.

    Other big pain point is that it doesn’t support workspaces or multi-project builds or whatever you want to call them, so where you can have multiple related applications or libraries in the same repo and directly depending on each other, without needing to publish a version of the libraries each time you make a change.

    When we started our last big Python project, none of the Python tooling supported workspaces out of the box. Now, there’s Rye, which does so. But yeah, I don’t have experience yet, with how well it works.



  • We’ve got a WebAssembly web-UI at $DAYJOB. Implementation language is Rust, we use the Leptos framework (although other mature frameworks are available for Rust).

    Pros:

    • Same language and similar tooling as in the backend. Most libraries work the same way (obviously excluding libraries that read from the filesystem, for example). This is especially good, if you’ve got lots of “full stack” devs.
    • Same model classes as in the backend. If you change a field, the compiler will force you to fix it on both sides. It is compile-time guaranteed that backend and frontend are compatible.
    • Rust is a nicer language than JS/TS. I find especially Rust’s error handling via Result and Option types + pattern-matching works really well for UI stuff. You just hand the Result value over to your rendering stack and that displays either the value or the error. No unset/null variables, no separate error variable, no ternaries.
    • Having a strict compiler makes it less bad when you’re lax on testing, and frontend code is a pain to test.

    Cons:

    • If you’ve got pure frontend folks, or people who are deep into React or Angular or whatever, those are not going to be as productive.
    • The JS ecosystem is massive, you just won’t find as many component libraries for Rust, which can definitely also reduce productivity.

    With me being in a team with few frontend folks, I would definitely opt for it again.