So, it’s still not here :P

Ringworld :)

You know how they say there is a difference between what people need and what they want? This is one of those cases. We gave up privacy in exchange for convenience. E.g. Cloud storage is convenient. For files, for documents, for code. It’s so convenient that apart from acting in outrage when we discover that companies are scanning our data to train AIs, among other things, we are willing to do absolute nothing. And I think that’s because we fear to lose that convenience if we force a change (not that we could even if we wanted). In other words, we are getting what we pay for (which makes sense because often all those cloud services are “free”).

There is also another problem: some personal data is irrelevant to us, but it makes companies money when the data is all aggregate together. So, it’s easy to let it pass (apart from some outrage) when you are informed that there is a leak and everyone can know how many hours you spend using a service. We don’t feel it’s very relevant. But having this kind of data about everyone can help companies to tailor their service to tske advantage of our habits, bringing THEM a lot of money. Most data they have is irrelevant for you but very relevant for companies that try to sell services.

Ideally I’d like to get paid. I’ll allow you to track me, but I get 1$ every time records on the database with my data are returned by a query. See if they like it…

The things he asks to do are the reasons why I find no joy anymore working in coding. Hammering my thumbs seems to be more interesting than doing most of these actions. I swear, I got so bored I couldn’t finish the read. Specifically “if you find yourself commenting on every line of code” the right thing to do is to setup a meeting with te hiring department.

I’d say it suggests it’s “legally” the wrong thing to do.

Code review can’t fix incompence though. I lost count of how many times my boss told me “review that PR well because X is not very good”. Also my point is that they are overrated, not that they are useless.

Probably unpopular opinion, but peer reviews are overrated. If coders are good AND know the project, the only thing you can do in a PR is nitpicking. They are more useful for open source collaborators because you want to double-check their code fits with the current architecture. But people here are reacting as if peer reviews could actually spot bugs that tests can’t catch. That happens rarely unless the contributor is junion/not good.

I would fire you for incompetence and sabotage. Problem solved.

Lol I feel so old reading these replies… I learnt copying BASIC games from magazines and typing them manually on the computer.

But jokes apart, when it comes to learning, I think the best thing is to tinker with weather language you choose and don’t worry about making the “right choices” since the start. Forget about writing “pythonic” code and don’t worry about being “idiomatic”: just build something. Building good software is not just constructs, but also knowning which subsystem to improve and when. That’s what makes experience.

When it comes to improving, you can dig deep into the language.

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

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.

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.

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.