> You're getting confused between lifetimes (the static analysis that prevents use after free and similar errors) and lifecycles (more commonly discussed under the heading of ownership) which determines when objects (and thus memory) are allocated and deallocated.
Ownership is
That's a semantic distinction which does not matter in the point OP is making. And contrasting rust static approach to general GC.
I felt the same for a while after switching to jj. I think using the word "commit" in jj is creating a lot of confusing. The snapshotting is closer to auto-save in your favorite editor. In does not change your ability to version and save your work. It's just a savety net for quick undo
> This is meant to be mitigating? What is this thought process? Who in their right mind is like "okay, a group of people broke into your home at night but your state shouldn't have been so hard on them for what ensued because akshually it was part of a whole nationwide trend at the time."
You analogy doesn't not hold, and in manyways point at the root of the issue.
The point was to show that harsher punishment did not seems to result in meaningful effect on crime stats.
It's fine to want harsher sentencing for some kind of emotional fuffilement, let's just not pretend that is helping in any otherways.
> Whereas someone who has committed 30 petty thefts and then gets arrested, locked in a cage, and guarded by armed agents of the state, is extremely unlikely to commit another theft as long as he remains locked in the cage.
How does that help, if after incarceration that person become a much hardened criminal both because of the lack meaning pathway to integration, and you know spending years locked up with the worst of society.
> but we don't really have a good understanding of what specific people can and cannot be rehabilitated, or how to go about actually effectively doing the rehabilitation.
> Every year that a criminal is incarcerated is a year that they CANNOT kill an innocent citizen, rob a home or store, desecrate or vandalize the community, shoot up fentanyl in the streets, or do any number of things.
Why stop at criminal, this also true for non-criminal; Let's just jail everyone, then we will all be safer.
> I wish people would stop using the word “child” in an effort to minimize criminal behavior by young adults. A 16 or 17 year old isn’t a “child.” The Marquis de Lafayette and James Manor were just 18 when the revolutionary war started. Societies going back to ancient times ascribed significant responsibility to teenagers. And in modern times, there is a scientific basis for distinguishing between adolescents and children when it comes to brain development. Historically, adolescents were treated like adults.
Looking at the past for wisdom on how to treat young adult/people is very dangerous...
> People who start engaging in criminal conduct at an earlier age more likely to engage in criminal behavior as adults
this is not quite what the citation means. I am also very curious on how these study correct for cofactors .People who start a life of crime early are probably not comming from the best conditions in term of life circonstances. Which in it self is also a strong predictor.
> A more rational and less emotional sentencing system would be harsher on teenage offenders while reducing sentences overall.
No, that would be the fear based emotional response. The ration response would be to simply measure whether or not harsher sentencing have a better outcome. Instead of prehemtively jailing people based on dubious stats.
I think in many ways D was just too ahead of it's time; Packaging the same feature set and abstraction level of C++ in much cleaner and saner package wasn't really seen at valuable at that time.
I think that if D were to be "re-release today" with a lighter syntax, and some coporate backing a-la GO/swift/typescript/carbon; It would find quite a bit of success.
As compiler have become more sophisticated, and hardware architecture more complicated, there are been a growing sentiment that some of the code transformation done by modern compiler make the code hard to reason about and to predict.
A lot of software engineer are seeing this as compiler engineer only caring about performance as opposed to other aspect such as debuggability, safety, compile time and productivity etc... I think that's where the "sabotage" comes from. Basically the focus on performance at the detriment of other things.
My 2 cents : The core problem is programmers expecting invariant and properties not defined in the languange standard. The compiler only garanty things as defined in the standard, expecting anything else is problematic.
And most of the standard we have now starts with something similar to NIH. Vulkan itself is an offshoot of mantel from AMD.
There are valid reason to have a custom api. Especially in domain like game console with hardware with long release cycle, tight performance requirement and legacy (ps4) code to support.
Yes... but no...
From the article :
> At a 2015 office Christmas party with a Back to the Future theme, François allegedly told a member of staff that he liked her 1950s dress. He then allegedly stepped towards her to kiss her on the mouth as his colleagues restrained her by the arms and back. She shouted and broke free.
Every team and sub culture will have an "energy" and different attitude etc... sure
But this is much more than racy poster on the walls... This behavior was never acceptable.
I find it fascinating that we have to rediscover and relearn every generation why professional etiquette is so important. And what happens when. We blur the line between professional life and "familial" attitudes
Fsharp is such a nice languange. Such a shame that I never seem to get the light it deserves.
Between the alternative light syntax, type providers and first class "scripting" mode supported it really was a great middle point between fully scripting language and fast prototyping and full blow projects
That's a semantic distinction which does not matter in the point OP is making. And contrasting rust static approach to general GC.