Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)B
Posts
6
Comments
40
Joined
3 yr. ago

  • Yeah, this is also useful when learning a new programming language, even when you are an experienced coder, already.

  • Sometimes I wonder if this pure search for being "idiomatic" is worth the effort. On paper yes, more idiomatic code is almost always a good thing, it feels more natural to create code in a way the language was designed to be used. But it practice, you don't get any points for being more idiomatic and your code isn't necessarily going to be safer either (smart pointers are often "good enough"). I'm fine using references to pass parameters to function and I love the idea to "force" the programmer to organize objects in a tree way (funny enough I was already doing that in C++), but I'll take a Rc rather than a lifetimed reference as a field in a structure any day. That shit becomes unreadable fast!

    EDIT: but I love cargo clippy! It tells me what to change to get more idiomatic points. Who knows why an if/then/else is better than a match for two values, but clippy says so, and who am I to question the idiomatic gods?

  • Ofc I knew! Yeah, (neo)vim takes time to adjust. Personally I only use a bunch of commands, never bothered with the advanced stuff.

  • Personally, I mostly use neovim, both at home and at work. My reasons are:

    1. I hate any kind of screen cluttering. The minimap comes straight from hell.
    2. it's very responsive. I don't even bother using language servers as they occasionally introduce micro delays that I hate.
    3. it helps me in organizing the code better. No minimap means I keep the file size manageable, not seeing the definition of the function straight away means I keep the static complexity of the code in check (tend to reduce the number of delegates). It doesn't help when I have to read cose from legacy codebase, but I don't care too much about that.
  • I can't not upvote someone who brings Clipper to the table :)

  • "intuitive" is extremely subjective, and based on your past experiences. I've coded in C++ for years, and some Python, too and was able to grasp many Rust concepts very quickly, while for others I struggled (and still am). I'd say that if you are looking for "intuitive", Rust ain't it. It's a system language, so it requires planning, it's definitely not the ideal language to slap a prototype quickly together, expecially as a beginner.

  • It competes with C, so in 2023 this basically means embedded systems. It offers executable size of few KB and out-of-the-box cross-platform compilation. It's a modern C, basically, and it claims to be even faster than C as some language rules allow more optimizations

  • My understanding is that this is possible: you should be able to take a C project, add a build.zig file and under the hood the system is calling clang to compile the C project. HOWEVER, you can now add a .zig source file, compile that in zig and link together with the output of the C compiler into an executable. If this is actually true, I can definitely see the attractiveness of the language.

  • I salute the author of this for drawing a CRT monitor.

  • I wouldn't say it's a new LinkedIn, but it's definitely a defacto monopolio. It pains be that Cargo (the official rust packaging system) is so integrated with it. My own personal hobby projects are self-hosted on a gittea instance right now, but I still have a github account to contribute to a friend of mine's project which is, sadly, hosted there.

  • I'll remember to celebrate that :D

  • Well I guess the point is that you shouldn't need all these method calls to achieve simple goals. Most of those "getF" are calls to some SystemFactory to get a GenericObjectFactory and so on and so forth.

  • I'm going to be the devil advocate here (so please, don't take anything I write personally) but sometimes I wonder if people live in the real world or the Little Pony one. Your expectations on how the real companies work are imho completely off the mark. Now, I'm sure that ethics is not dead and you might find something that has the checks in the right spots, but ultimately the IT world is a shark tank where you either are hunting or are the prey. At BEST the work you do is to steal business from your company 's competitor to affirm itself in the market (thus causing the other company to potentially go out of business and layoff employees). At worst, you actively damaging some group of people somewhere. Hell, even the fact we keep datacenters close to deserts, increasing the amount of air conditioning needed so that we can share memes quicker is unethical, and yet here we are. So, on one hand I say "what were you thinking!". On the other, I want to say that I admire you for your search. I hope you can find solace somewhere. Personally, I'm content with not causing direct damage to anyone (AFAIK, at least...)

  • Follow up of: "Mmm... should I put lifecycle annotation in these 10 structs or just use and Rc and call it a day?". Rc and Box FTW.

  • I second this game. The cat can also find a mate abd have kittens

  • I've been hearing "This is the year of Linux on desktop" since at least 2002...

  • I used to love IDEs with immediate feedback on the code, and a modern VSCode setup can really shine in this regards. But these days I'm going for a minimalistic approach where I don't want to see anything in my screen but the code. I use Neovim and while I use plugins for formatting code on save, my screen is absolutely code only. No linting hints, no function definition appearing when I hover thr mouse, nothing at all. It's far less distracting and you also feel much less constrained, even if I unconsciously already write the code in a way that the linter doesn't complain (too much) later. I haven't noticed any drop in my productivity in the last year I've been doing this.

  • I love cargo, but cargo.io could REALLY make good use of namespaces. It's insane when clear library names are taken by highschoolers at their first project and there is nothing to be done about it. I'd also like some kind of curating on the packages.

  • Oh man, I hate code reviews with the strength of a thousand suns. In the enterprise world, there are so many constraints and conventions that reading other people code is even more boring than it should be. It's even worse when you LGTM it and your colleagues "accuse" you of not having read it with attention because "I can't believe you don't have any comment on my code".