@Hazarth I still like it a lot too. It's easy to debug and often feels a bit like a scripting language and comes with all the tools you need by default. Super low maintenance. Sometimes they do take the simplicity part a few steps too far though.

Yeah there are no enums. Go has plenty of quirks but it's highly effective.
Rust has a really nice enums implementation but you will be fighting a lot of the language at the beginning.

I know about performance but really can't be bothered by big O notation.
So far I'm the one fixing all the issues. Most of the issues are race condition or database representation related.
All my coworkers seem to know about big O, but none of them can seem to grasp the rules of synchronization. Understanding the implication of things is far more important than anything any school has to offer.

It for sure had a place but for most things I find go and C more useful. Quite some C++ use cases where Go just isn't good enough Rust makes sense. That is why I do think that an application like a browser makes sense to write in Rust.

The cult/hype peak may come to an end. Go had the same over hype bs. Now I see it used too little where it makes sense. Paru for example should never have existed for example Yay could benefit from the extra development that went into Paru, Rust adds nothing here. Network and pacman are the limiting factor.

@Lensflare Actually it is not when done right.
SuperDuperAbstractFactorySingleton
is harder to read and distinguish from SuperDuperAbstractFacilitatorSingleton.
Contains way more crap you read before you get to the unique descriptive part than say Facilitator.

The closer the variable is to it's usage the more context you have and the shorter you can get. This translates to his deeper the code and the smaller the function the shorter variable and function/method names can be.
The opposite is also true the further away and more exposed the more verbose you need to be. This is because you don't have the context and in need of some descriptive naming. Still just enough so you can dirive context without making it a chore for your brain to process.

@donkulator you like to dance around a campfire?

@CoreFusionX the EU is vastly more reasonable. A lot of liability waiving is in violation of the law here.

I think that the claim has to do with the actual usage, even in US but can't be sure.
Because laws in the US are stupid they will try to get damages on Disney if their kids jump off a building and try to spin it that they did it because Disney showed them a super hero that can fly.

If there is no persistent state a restart should fix it. Don't think there is a way shutdown gracefully

The lowering salary is very weird. 10% is no rule at all. Switching companies is one of the best ways to get a higher raise that can go 20% with ease.

No it's not. You can say you do not want to disclose it if you think that will help in the negotiations. It's a very stupid way to shoot yourself in the foot to lie about it.

When your current salary is indeed quite high the recruiter might think that they can't go above your current salary to warrant a change. Or they notice something is off especially if they know your current company well. Indians so this all the time and our company always terminates the procedure when they do. Americans like to inflate their resume, same thing.

Some companies require proof of your current salary during the finalisation process of the contract. Here they can legally dissolve the deal if you wilfully lied during the process.

At work we have a central logging server but also always log to stdout.
As our team actively removes noise this works nicely without impact. Did have an instance where sending the logs was sore l so slow (network issue) that there was internal resource usage buildup and it killed the service anyway. At least that was visible.

Ah yes, what happened to the good old days when the answer to that question was "dunno copied from stack overflow".

Edit: see I was late to the party...

Ouch at least they know for real you work there 😅

As I mainly use Go and haven't touched PHP in a long time people are always surprised that I'm positive about PHP.
It's far from perfect and still holds some API inconsistencies that can be traced back to the early days or POSIX equivalents. However since 5.6 it's matured a bit and with 7 you got enforced type hinting making it a very nice tool to get things done.
You can even work with sockets without any extra lib. Workerman demonstrates that it can be bloody performant too if you know what you are doing.
I know I can write faster PHP than my coworkers can do in JVM based stuff.

@SidTheITGuy can you describe in one or two sentences what your videos convey and what your goal in putting them out there is?

@SidTheITGuy of course not, there is no reason for me to do so. Even if you have awesome tutorials or what not then I'm never the audience. Managers and absolute beginners are.

The right medium for the job seems to be lost on a whole generation. Being able to reference text, copy/paste it, or simply skim to the relevant part that I'm looking for is infinitely more important than the "extra context" a talking head can give me.

@CoreFusionX don't be blinded by a single incident. Go ahead and ask the affected banks if they would rather have their endpoint security system shut down their systems or leave them running insecure.
Running insecure means that (financial) customer data is leaked or cash machines handing out free money.

Anyone that thinks they are an influencer is not worth my time or attention.

There are people that exert influence as part of their real job. Influencers aren't, they are just a live yapping billboard for someone else's agenda.

@CoreFusionX
I hope you do understand that this can happen with any kernel level driver update and not snap user land crap. Although I agree with you that ideally one can do a controlled, tested rollout I do think the risk of delaying and potentially missing critical security system updates is higher than what just happened.

What I would like to see is canary roleout tests to be done by the updater. That would reduce risks dramatically. And even then there are situations where you rather have it broken than insecure.

@lorentz again on the array of was a bad example to begin with. As stated from the very first line it's a the original issue is a non issue because on practice it's not done in TS (what I mostly use professionally) it's even less likely.
There are still some cases where not set at all needs to be handled differently from explicitly entity empty list resulting in nullable array in TS.

@lorentz that is exactly what I mean!

@lorentz crashes on null/undefined. This is why I do both checks as indeed it is far better to be explicit about what you want here.

I always do explicit checks unless it really needs to be more flexible but that is almost never. Was just trying to provide an example while still using an array.

Hate the whole null and undefined difference by the way. It's not a big enough of a dream to warrant two different types in my opinion.

@Lensflare I'm actually more in the JS hate camp, actively avoid it as much as possible. htmx is the best framework that came out for me.

Dynamic typed languages often use loosely typed checks to be able to be used dynamically in the code as well. So I consider it a feature of the dynamic type system even though a strong typed language like python proves that it does not need to be the case.

@mostr4am just came here to say that. Stupid comparison to begin with.

Not understanding the very basic characteristics of the tool you use makes any of these complaints shit posts to me.
It's like blaming the screwdriver for painting falling off the wall when not using plugs in plaster.

In any dynamic typed language you need to use strict comparison operator when you care about the type or non empty-like checks.
It's a nice convenience that you can do
If (myList) {
// Yay have an actual non empty list/value
}
If zero or "" is also valid you need to specify that because guess what you want something explicit.

SRE is still all the rage be prepared to answer something about that.

@Lensflare sad just sad

@jestdotty Yeah just came here to say:
github != git

In fact it's build to be decentralised. If you have a file share or even just some place with ssh (sftp) you are good to go for pushing.

Chemical industry is way more toxic...

Sounds like I'm joking but I'm actively combating other use of the word "toxic" because it's largely a meaningless blanked statement that avoids naming the real problems. And that is harmful in itself by prohibiting change.

There are some cultural issues in general that stem from male dominance. But the actual level of social/political issues are highly specific to the company and often the team you are in.

The biggest problem here is that what you are trying to do is either not suited for object storage or your software is not designed for the cloud.

You can always use cloud building blocks to build your own Ceph server as this seems to be more like what you want. It's a bit like what you would need to do in your own rack but with cloud scalability with EKS (as that seems to add value to you).

I found GKE with filestore to be much simpler for this by the way. Had a similar issue with a scalable EC2 setup (and traditional CMS needing a real file system). Moving that to GKE was nicer.

@SidTheITGuy don't know your circumstances but generally if you have job you should be able to either request a home setup from work or save up rather quickly. Decent monitors aren't that expensive anymore.

I wanted higher than 60 refresh and usbc power delivery (already had a cheaper dell with usbc power but all so 60hz max). That was a bit harder to find but is also becoming more common. Still that set me back more than the average €200 - €300. Worth it though.