The OFFICIAL programming thread

Lob12

@Kilemall said in The OFFICIAL programming thread:

@Lob12 said in The OFFICIAL programming thread:

I speed read everything Jam posts and it’s been serving me well so far!

I actually read them because it’s same speed comprehension for me. He makes points that are valid but more complex then USA Today level writing, but a LOT of you are missing it.

You can start talking shit after you watch the Tucker interview, poser!

Pakoon

@Hog said in The OFFICIAL programming thread:

@Jam said in The OFFICIAL programming thread:

@Hog said in The OFFICIAL programming thread:

I fucking tech marketing.

When one is filled with hate, sometimes words go missing.

I bet that I can read your mind though! ;-)

I had to re-read the line you quoted 3 times before I saw the problem.

I drop/miss words way too often in my writing. I read a how-to book on speed reading in my early teens and I think it permanently broke me because unfortunately I seem to write the same way I read - leaving out chunks that can be inferred from the surrounding words.

I have the same problem.

Gators1

There’s a new job opening at Google if anyone is looking…

No Tech For Apartheid on Twitter

https://time.com/6964364/exclusive-no-tech-for-apartheid-google-workers-protest-project-nimbus-1-2-billion-contract-with-israel/

Gators1

The birth of the relational database and SEEEEEQEL!!!

The Birth of SQL & the Relational Database

Jam

So . . . .

SQL was initially developed at IBM by Donald Chamberlin and Raymond Boyce. It was initially called “Structured English Query Language” (SEQUEL) and pronounced “sequel”, though it later had to have it’s name shortened to “Structured Query Language” (SQL) due to trademark issues. It was created to supplant the then popular QUEL database language, and the name “sequel” was meant as a pun (it was the sequel to QUEL). However, this leads to the big question – was language still called “sequel” after the name change?

Answer here:

Pronouncing SQL: S-Q-L or Sequel?

So, it turns out that My Ess-Cue-Elle is the more official way to pronounce MySQL. We work with the Oracle MySQL team a couple times a year and that is how they say it.

Tazz

@Jam said in The OFFICIAL programming thread:

So . . . .

SQL was initially developed at IBM by Donald Chamberlin and Raymond Boyce. It was initially called “Structured English Query Language” (SEQUEL) and pronounced “sequel”, though it later had to have it’s name shortened to “Structured Query Language” (SQL) due to trademark issues. It was created to supplant the then popular QUEL database language, and the name “sequel” was meant as a pun (it was the sequel to QUEL). However, this leads to the big question – was language still called “sequel” after the name change?

Answer here:

Pronouncing SQL: S-Q-L or Sequel?

So, it turns out that My Ess-Cue-Elle is the more official way to pronounce MySQL. We work with the Oracle MySQL team a couple times a year and that is how they say it.

Depends on its pronoun

Jam

I suppose in a way that is true.

It can be My Ess Q El, but it can be your My Sequel, or vice-versa, lol,

Kilemall

It’s used interchangeably in my department.

Tazz

@Kilemall I’m sure this news is making its rounds in the medical field. How is this even possible?

https://www.seattletimes.com/seattle-news/health/houston-hospital-halts-liver-and-kidney-transplants-after-learning-a-doctor-manipulated-some-records/

Gators1

Kilemall

@Tazz said in The OFFICIAL programming thread:

@Kilemall I’m sure this news is making its rounds in the medical field. How is this even possible?

https://www.seattletimes.com/seattle-news/health/houston-hospital-halts-liver-and-kidney-transplants-after-learning-a-doctor-manipulated-some-records/

Doctors are to the medical field as fighter pilots to air forces. They are watched like hawks though by hospitals for things like this, note they saw higher failure rates so probably a QA oversight software trigger caught him. Usually it’s going to be a problem like physicians prescribing themselves drugs that causes lower outcomes, this twist was probably a surprise.

From a software security perspective, if he was running the transplant program he would have legit access to make changes.

So the combo of fighter pilot carte Blanche, a trusted physician with access, and time for the outcomes to trigger review explains it to me.

Pakoon

@Gators1 said in The OFFICIAL programming thread:

The My part is pronounced Myy. It’s a Swedish girl’s name.

One of the Moomin characters is My

Little My - Wikipedia

Gators1

Should you trust the government though?

US Government declares the safest programming language

It’s not a very ergonomic language despite their efforts to make it so but I got a lot out of learning Rust. The first weeks / months where you are fighting with the compiler as it teaches you Rust is the hardest but eventually it clicks and you stop trying to do things the “wrong” way. It’s worth it for how it opens your eyes to the pitfalls in other system languages because every time you get a compiler error you tend to think, “what’s the danger with that?” You usually figure it out and after a while you start feeling a growing horror at how potentially unsafe a lot of non-Rust code is.

Gators1

@Hog said in The OFFICIAL programming thread:

you start feeling a growing horror at how potentially unsafe a lot of non-Rust code is

That’s exactly what the government wants you to think! Meanwhile Rust was made by the NSA with all kinds of backdoors!!!

Kilemall

@Hog said in The OFFICIAL programming thread:

It’s not a very ergonomic language despite their efforts to make it so but I got a lot out of learning Rust. The first weeks / months where you are fighting with the compiler as it teaches you Rust is the hardest but eventually it clicks and you stop trying to do things the “wrong” way. It’s worth it for how it opens your eyes to the pitfalls in other system languages because every time you get a compiler error you tend to think, “what’s the danger with that?” You usually figure it out and after a while you start feeling a growing horror at how potentially unsafe a lot of non-Rust code is.

Mainframes win again- the OS locks the average peasant out of the dangerous instruction sets through APF authorization.

https://www.quora.com/Is-the-average-IBM-mainframe-application-inherently-more-secure-than-the-average-cloud-application-or-is-it-simply-security-through-obscurity

@Kilemall What Rust really addresses is a more a whole host of failure and attack vectors around memory. Not so much gatekeeping what a legit program can do.

This is 2019 data but it’s the type of thing Rust was designed to address:

Microsoft: 70 percent of all security bugs are memory safety issues

You can code safely in C and C++ but it takes both a lot of experience and immense amount of discipline and I’d be surprised if even the above-average developer had completely memory safe code in any large code base.

Pakoon

Is Baldwin behind this?

Kilemall

@Hog said in The OFFICIAL programming thread:

@Kilemall What Rust really addresses is a more a whole host of failure and attack vectors around memory. Not so much gatekeeping what a legit program can do.

This is 2019 data but it’s the type of thing Rust was designed to address:

Microsoft: 70 percent of all security bugs are memory safety issues

You can code safely in C and C++ but it takes both a lot of experience and immense amount of discipline and I’d be surprised if even the above-average developer had completely memory safe code in any large code base.

A better explanation of APF authorization…

What is the authorized program facility?

Because this security kicks in BEFORE the OS loads, if you screw up the libraries or the LPA you can literally lock the system up to where you cannot bring the system up. This is why you ALWAYS define a rescue LPAR that also has access to the same disks so you can fix the problems and come up without epic IBM assistance.

Gators1

@Kilemall what kind of FPS does your mainframe get though? Can it play Skyrim?