Most of the time yeah. But it depends as you can write c# with very little GC use if you avoid allocations.

Ahead of time compiling also gets things much closer. But then you lose runtime optimization.

Actually jit languages can outperform compiled languages by using runtime analysis to perform tiered compilation and profile guided optimisations.

C# has made some great strides in this regard.

All the normal optimisations are applied when it is compiled to byte code. Like loop unrolling etc.

Then once it detects the hot paths during execution it can apply even more based on how it is called. It can also do optimisations that aren’t possible at initial compile time.

Dynamic PGO it’s called. It’s a really interesting topic.

Indeed. But the pdf file itself isn’t the issue here. They very clearly don’t know what serialisation is.

And while there are risks with java serialisation it isn’t being deserialized here.

It’s literally just the format of the file here. If you skip the java serialisation header it’s a normal pdf file. I said nothing about the pdf file itself.

I did explain what it is. I just don’t know why certain programs encode it this way. It’s supported by multiple pdf readers so it must be semi common but I can’t find a reason for it to be encoded this way.

I’m trying to help you out there’s no need to be a dick.

The file is a serialised java array that contains a pdf file. I’ve seen a few things online about this. Some pdf readers accept it, some don’t.

And I’m not sure why an application would output a pdf this way. But there’s nothing harmful going on.

You’re kind of freaking out about nothing.

Ok boomer.

But seriously this is the sort of stuff our grandkids will roll their eyes and laugh at

In sane countries cases like this end up with lifting abortion bans.

America is so fucked up.

I’m fairly sure use after free isn’t possible unless you explicitly use unsafe code right?

It’s compiler enforced is the point.

That sounds like a comment written by somebody who has no idea what the article says

2.6% increase in thread ops when copying data from user space seems pretty significant.

I bet you plenty of people absolutely do want this.

Most people can barely use a computer and would love this if it worked well.

You forget a huge percentage of users can barely access their emails.

Lemmy is very techcentric and most users on here are far from the average consumer on technical literacy.

You just aren’t the target audience.

It’s amazingly good at moderating user content to flag for moderator review. Existing text analysis completely falls down beyond keyword filtering tbh.

It’s really good at sentiment analysis. Which is great for things like user reviews. The Amazon ai notes on products are actually brilliant at summarizing the pros and cons of a product. I work for a holiday let company and we experimented with using it to find customers we need to follow up with and the results were amazing.

It smashes other automated translating services as well.

I use it a lot as a programmer to very quickly learn new topics. Also as an interactive docs that you can ask follow up questions to. I can pick up a new language as I go much faster than with traditional resources.

It’s honestly a complete game changer.

I’m guessing they have limited resources for direct intervention so use this to flag up people who have the most risk factors.

It doesn’t sound like this is people asking for help but more trying to predict who might need it.

after an investigation by The Fuller Project and The Markup found the department’s algorithm prioritized White, male veterans. It also gave preference to veterans who are “divorced and male” and “widowed and male” but not to any group of female veterans.

It shouldn’t favour anyone. It should treat each person as an individual and figure out what they need based on their characteristics. If it’s been designed to only work well for white men it’s been designed poorly.

It has always had structs. They are often used for interop but can be used to avoid allocations and they are memory safe out the box, which nice.

Both languages are really great in my opinion. But very different use cases generally.

The reason is the vast majority of places use c# to avoid this stuff. So performance is often not the first priority

The complexity it adds takes away from the readability and maintainability. Which is often the priority.

But in a hot path where you need optimization these are a good send as previously you had to use raw pointers and completely side step all the safety of the language.

I would say 90% of c# developers will never touch these. It’s more for library and framework writers.

I believe most of these features are driven by what the Microsoft Devs need to write asp.net and EF.

It’s 100% not a borrow checker because c# doesn’t have borrowing. It’s just static analysis to ensure memory safety. But the author acknowledges that.

It’s just checking the scopes the variables are defined in in the first example.

As a type 1 diabetic with multiple attachments already this sounds great.

Honestly I would just commit your in progress work then on the other machine check it out and reset to the previous commit.

Then you have your in progress work on the new machine with no random commits.

You could set up an alias that does commit with message “switching machines” and pushes.

Similar have one that pulls and resets.