@jestdotty I think Pulsar was the successor to Atom, though I never tried it.

I think I'll give it a shot, and maybe try lapce again. Even though it'll be difficult to get either of these on the corporate pc.

@ViRaS just... basic things not working anymore

I open the settings menu, it's blank. Not even buttons visible.

I open the extensions tab, it takes about 3 minutes to actually show the extensions that are installed.

The extensions that need 3 more minutes to install, if it works at all.

And I think all of these problems don't exist in a "normal" environment. But I'm using the remote development on a machine that doesn't have internet access, and for some reason that just seems to break things...

Lapce can't hit 1.0 soon enough for me

Any USB WiFi nic will work okay
An actual WiFi PCI card would be better but honestly a complete waste. If you want a good connection you go wired not wireless.

I never set one up and I've only barely used one and yeah it feels just... off

Its like team speak 3, the ui is of a certain era and just didn't age that well.

I am cringe but I am free.

@IHateForALiving it wasn't that bad... it was more like

param.randomLimitLower = 0;

param.randomLimitUpper = 360;

param.randomEnabled = true;

...

...

...

EXPECT_GT(result[0], 0);

like, we could've seen this coming to be fair

@Lensflare oh those are also fun

we tend to test the snychronous components on their own. Multithreaded stuff get dedicated, very complex tests. Everything that isn't strictly part of the multithreaded functionality is done through dependency injection, so that in unit tests we can test the actual threading and so on.

In one test, one of the dependecies I injected had a mutex in there so that I could lock that mutex from the test to "pause" my worker. Using an atomic counter around that I could check to wait until the worker was exactly where I wanted it to be.

Oh the algorithm had random input from 0..360

But the rest checked if the output was >0 at given points

Well this was simple, I feared for the worst (undefined behavior)

most people in management don't either, yet they will parade it around

Pray that one of the mods awaken from their slumber and yeet these bots off of the platform

Can you do us all a favor and jump off a sky scraper? Thanks in advance

@chaosesqueteam kys

Be the change you want to see in the world

@chaosesqueteam who the fuck even are you

@black-kite nope... A windows domain controller and small lab network I have the honor of maintaining

Reminds me of this
I feel like some people have completely twisted priorities in code reviews

https://morling.dev/blog/...

I'm absolutely used to the layout so I don't really see any problems with it (and I write mostly C++)

Though I do know some German devs who use other layouts mainly because of programming. One of em even uses Dvorak but I feel like that's a different rabbit hole...

wait that is actually a useful feature why did I never know about this?!

@retoor do you mean that specifically for that library?

@b2plane I would expect to have an async version of that send function, so you could make your sendSocketIOMessage async as well.

But I don't know that library, I just expect IO to be asynchronous in general.

from what I understand you want to send read acknowledgements to all other clients?

Either way, if you wanna send something to every client, you're gonna have to loop over all of them in some way or another.

What I think could improve this performance wise is making this async. I suspect all of this is network based so most of the runtime of sendEvent will be spent waiting on IO.

I guess you could also process let's say 8 or so of these async operations at the same time.

But I don't know if that would make any better, I would suggest to do some measurements.

I've explained what REST actually is numerous times but some people still manage to think that REST = that openapi code generator
And since it uses yaml files their 3 brain cells go YAML = REST

@AlmondSauce I kinda get what you mean

I'm kind of tired of one certain project at my workplace that has like almost a gigabyte of compiled binaries of some proprietary library that we need to use in the repo.

Of course it's in there once, the repo wants to be cross platform so there's different builds for different platforms...

lfs feels like a big after thought in git.

I don't think it's a great solution, but definetly better than having your .git grow into gigabytes in a handful of commits

@electrineer funny that that the EU manages to regulate devices that are mostly made elsewhere but right to repair in cars and vehicles is still a major shit show

I mean I'm not complaining about them regulating phones.
But I wish they'd make it mandatory for car manufacturers to hand out service manuals for their shit. And ideally blueprints, assembly instructions and firmware for parts they dont produce anymore.

Good fucking lord what is this

Not sure if you can ever demangle this mess
Word of advice though, try to do ff-only, even if the others in the project dont.
Merge commits lead to pretty painful situations

@devRancid from my own experience Rust+Cargo will be a much better building experience than I had with C++ & CMake.

Your build file is just a small Rust file, not an entirely new scripting language, it actually gives you meaningful error messages instead of unreadable gibberish, it is reasonable fast WITHOUT you going out and "optimizing your build time" by forward declaring everything because we're still stuck with a pre processor from the stone ages.

Granted, C++ 20 modules kind of fixes a lot of the pain you get in that ecosystem, but Rust is just so nice to use.

Rust's syntax is definetly hard to get around

Although I felt the exact same way about C++ when I started to learn that coming from C#.

>And I feel like the sadistic rust cult members actually enjoy making it hard to read so that they can jump on any occasion to shout at you : you still lacking rustlang skills

These kinds of people are genuienly a problem. I've seen a lot in C++ and also some in Rust. Don't listen to 'em.

A good tool/language/ecosystem will actively try to make the user experience a good experience. Especially for newcomers.

I find that Rust generally does this well. The documentation I've worked with was always clear and concise.

@aviophile I do agree with that paragraph though I dunno what you're trying to say with this