Is COBOL subject to buffer overflows and use-after-free bugs? I honestly don’t know.
I don’t recall the COBOL code I’ve read using pointers.
Is COBOL subject to buffer overflows and use-after-free bugs? I honestly don’t know.
I don’t recall the COBOL code I’ve read using pointers.
lol, right, this is terrorism!
If 10 people are sitting at a table…
When Russian citizens understand there are direct consequences to them, Russian citizens stop supporting Putin’s actions.
Personally I’m glad the sanctions have some bite. You can’t expect to just keep living your life as you wish when your country is obliterating its neighbors and disrupting stability worldwide.
Usenet or Fidonet would be a more apt comparison
Yeah maybe that’s true. I thought the recent work eliminated it but it looks like ZGC2 has a bounded and usually microseconds-range pause time.
FYI the JVM’s GC is concurrent and doesn’t freeze.
Try Scala. It has all the functional goodness, all the OOP goodness, all the imperative goodness, clean syntax like python or like typescript, really well thought out libraries like ZIO, Akka, Tapir, Caliban and access to all Java libraries. Very mature runtime with best-in-class high performance concurrent GC and a green thread implementation that can handle 10s of millions of concurrent operations.
Yeah let’s not forget the Common Lisp Object System (CLOS) which was more full-featured of an object-oriented language than most “current” languages.
The dynamism allowed both Smalltalk and CLOS to avoid a dark corner that will confound your typical OOP’er today - the circle/ellipse modeling problem; they allow an object to “become” a different type on its own accord. Take that, Java!
RAM is easily damaged by static discharge. Were you wearing a ground strap and took care not to let the memory module touch any ungrounded surfaces while you were handling it?
Static damage can often appear as marginal or intermittent failures, probably more often than complete failure.
That remote is the worst. Tiny, slippery device with no edges to grip. Super sensitive buttons so you can barely pick up without interrupting playback. Truly “design” fucking up usability if I have ever seen it.
yeah, I went ahead and bought a Kagi subscription
They are kind of like two hands making a handshake - they just twist/slide into each other and each is then looped around the back of the other. Very simple and effective
Have you seen these knife connectors used in aviation? They are genderless and lock together. Of course your crimp better be solid - meaning proper connector for the wire size and proper crimping tool die.
Could be a crypto key, or a randomly distributed 64-bit database row ID, or a memory offset in a stack dump of a 64 bit program
And then JSON doesn’t restrict numbers to any range or precision; and at least when I deal with JSON values, I feel the need to represent them as a BigDecimal or similar arbitrary precision type to ensure I am not losing information.
That’s because the nearest representable float to 0.99999999999999 is 1.0 - not because Python is handling rationals correctly.
This is a float imprecision issue that just happens to work out in this case.
It’s worth wondering why, if Python is OK with “/“ producing a result of a different type than its arguments, don’t they implement a ratio type. e.g. https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node18.html#SECTION00612000000000000000
How would you implement this in code?
And O-circumflex “ô” in French indicates an elided “s”. hô = hos