snsvrno is trying ...

Its a fine line between refined tastes and being a luddite

Reminds me of the HHGTTG quote: "Many were increasingly of the opinion that they'd all made a big mistake in coming down from the trees in the first place. And some said that even the trees had been a bad move, and that no one should ever have left the oceans."

I feel like I'm regressing to the 80s in terms of most computer things, like all this IDE, gui, complex and complicated languages ... no thanks. Give me a term + git + gdb + odin + make and I'm happy.

I agree zero risk is unattainable and we have to live with and manage it, but it feels like there is only high risk and no benefit to the package manage dependency model the way it's currently implemented.

I'm worried the same will happen when Rust becomes a key part of software (like the linux kernel). Someone compromises a dependence for a dependence for something in the kernel and it gets updated without checking and now all linux devices have an exploit.

The NPM ecosystem is the wild west and has vulnerabilities all the time. The package manager makes updating lib versions too seamless that a dependence's dependence's dependence could be compromised and no one would notice. Crates is trending that way. The package manager adds unneeded risk.

I opted for Mullvad. Really wish there was a viable non-chrome / non-firefox based browser out there.

Ment rust as bad as JS..

This makes javascript just a bad as rust IMO, any language benifits are null. I use arch and build most of my utilities / apps, but actively avoid rust and js on my system. I trust the app dev but I have no trust for any deps. Package manager malware / unwanted injection is very prevalent these days

Was tweaking the palette on my temp sprites .. then decided to make the palette automatically update on build .. then need to add metadata to the sprite file to know what palette to use .. then decided to build an aseprite extension to make editing data easier, ... then what am I doing here again ..

+1. Not as far as you, but feeling a little meh about the puzzles. I'm enjoying the process but it feels like my rewards are either cryptic vague story clues or another puzzle. Getting worried I will fizzle out before really unravelling anything satisfying.

beaux-he-meth?

I think thats a way...

Yeah! I've used in with an older Onyx Boox and 100% would recommend.

Still need to manually get the books on the phone somuhow, but then MoonReader does the rest.

I use Moonreader+ and it uses google drive in the app to sync whatever you want (reading history, page count, and ebooks too!!). Easy to setup and just works if the ebook reader has wifi. No need to have syncthing or extra syncing thing.

Giving me the same vibe I get from most google products: stabled together frankenstein with way too many cooks in the kitchen. Wanna learn how to make an android app in 2024, well here is 10 years of mistakes you're going to have to weave around oh and tons of compiler macros as "fixes".

Almost done shitting on them, promise ...

Now wanted to create a fresh project and port my work over because it was acting funny (was thinking some configuration ghosts somewhere in the mess of project files) but now an empty new project will not build because of dependence mismatches!!

So was fighting with error in the IDE for 2 hours, and turned out a beta version of the core #kotlin plugin was crashing so a ton of things that an LSP usually covers just were missing. Went back to the non-beta plugin but now highlighting only works half the time...

And on the opposite site, been switching to #odinlang for gamedev and that is so simple to get working ... wish there were more options for mobile app development..

Been trying to make an android app with #kotlin and #android-studio and having SOO MANY problems.

Turns out #kotlin is a cursed complicated mess for someone new, compiler plugins, macros, language extensions, defining dependencies in multiple places ... no wonder everyone says you need the IDE ...