![](https://lemmy.world/pictrs/image/42de7b68-ee8b-40f5-96f6-6e8cc418441e.jpeg)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
Perl? Nah, in this country its vb6, C#, java, gupta/centura and javascript :')
Source: been working for multiple healthcare market leaders in this country for 5 years now
The real deal y0
Perl? Nah, in this country its vb6, C#, java, gupta/centura and javascript :')
Source: been working for multiple healthcare market leaders in this country for 5 years now
Writing raw byte binaries ftw!
(Jokes aside, all programming languages have their good and bad things. Some just have more bad than good. And i say that as a C/C#/typescript/asm developer :p
Modern php is not bad actually. Still kinda slow and dangerous, but A LOT better than it used to be :')
That said, i wouldnt build a web service with php still lol
Thats interresting, thanks! Stuff for me to look into!
I also think halfway through the conversation i might have given the impression i was talking about pointers, while it was not my intention to do so. That said, the readonly/mutable reference thing is very interresting!
Ill look into what rust does/has that is like the following psuedocode :
DataBaseUser variable1 = GetDataBaseUser(20);
userService.Users.Add(variable1);
variable1 = null; // or free?
[end of function scope here, reference to heap now in list ]
That sounds odd. That also means that a mapper, command, service,… can never return a class object or entity. Most of the programming world is based on oop o.O
Keep in mind im not talking about the usage of pointers, but reference typed variables.
Thanks for the response. Ive heard of rust’s compiler being very smart and checking a ton of stuff. Its good thing it does, but i feel like there are things that can cause this issues rust cant catch. Cant put my finger on it.
What would rust do if you have a class A create something on the heap, and it passes this variable ( by ref ? ) to class B, which saves the value into a private variable in class B. Class A gets out of scope, and would be cleaned up. What it put on the heap would be cleaned up, but class B still has a reference(?) to the value on the heap, no? How would rust handle such a case?
Serious question, how would using rust avoid this? Rust still has reference types in the background, right? Still has a way to put stuff on the heap too? Those are the only 2 requirements for reusing memory bugs
I assume this is because their communication is based on posture, look and pheromones?
I was wondering if ducks would understand each other, with them having confirmed to have accents based on region
My mistake, youre right. Its sauron that was on savage island
Figured, guy looks like stegron, which i assume is him
I swear to god this didnt used to be a problem few years ago. However im having that bug constantly now…
You can but compilers will optimise that away unless you tell it not to.
The problem with java is the language and how it works itself, and not the byte code idea.
I say that as a few things do that and .net, java and wasm are the first that jump to mind.
Hell, pure technically any programming language that is not asm does that :')
My problem is java itself, not its byte code. Wasm as advantage, imo, is that its not stuck to a single language like java is. .net blazor can build to wasm, but you could also use c++ to compile wasm applications :)
Hexagons are bestagons
~ !cgpgrey@toast.ooo
Jokes on me for saying github != git though
And wherever you go, its always a spread that technically isnt chocolate spread, as there is not enough cacao in there :p. Well, depending on the country’s law at least. I know here it isnt legal to call nutella a chocolate spread. Label can only say “hazelnut spread”
Came here looking for DX:HR. Its atmosphere, story and ending made me just sit there and think.
About humanity as a race, their dark urges, those in power, the complexity of the world we live in,…
It truely was an eye opener for me
Same haha. But i use a combination of commits ( but not pushed ), ammending, fixups and usually clean it up before making a PR or pushing ( and rebase/merge main branch while at it). Its how git should be used…