jeddy3's comments

I can name one. At my job we do the kind of embedded programming were encoders inside machines send data to each other. Like reading optical sensors and sending bits indicating state to other controllers.

We absolutely do not "need" to know about Unicode, outside of interest about other realms.

Thank you for an exhaustive answer!

> The difference is pretty important. Getting this certification does not require that the abstract concept of the Rust language is being specified in any specific way.

Sorry, I was being vague. I meant the outcome for "us", the users, creating certified software relying on Ferrocene.

Totally on board with that there is a huge difference for certifying Ferrocene itself.

> The opposite, this means you can use Rust in these places. Even though this work does not specify Rust.

Nice, that's what I was hoping for. We are currently in a project creating safety certified software (in C, as are our other code) and are curiously looking at Rust, partly because of this effort.

> Essentially, the ISO 26262 certification mostly verifies that the compiler release process conforms to a certain standard. It does not create an ISO standard for rust, not does it aim to.

Sorry for a stupid question, but what does this mean?

Is it only that Rust itself (the language) is no use in a certification, but rather a specific compiler version? I.e. basically leading to the same outcome in the end.

Or does this mean to not get the hopes up (right now) for using Rust in a ISO26262 certified project?

Sure, but many cities in the world are not in the US.

Assuming no other transportation alternative, and single person per car as well I guess?

Not assuming that, it's not that obvious how big parking needs to be.

> all of our computing resources are based on a 100+ year old concept of a file cabinet with folders and files.

While they are based on the same concept, putting things inside of things (in hierarchies) is a pretty solid way of sorting stuff.

There are other ways as well, such as labels/tags. But regardless of technology I feel like folders (in one way or another) is one of the tools you would reach for.

IMHO both exceptions and error handling in Rust (and others) have their upsides and downsides.

Personally, I much prefer Rusts solution, being both more up front and at the same time more terse.

The metaphor is kinda stupid though, the "cavemen" in our scenario knows very well that exceptions exist.

To be fair, they said particular location from the equator.

Does not have to mean close to the equator.

I can absolutely see that piracy could fit under (a).

"to deprive the owner of it" it being copyright

They have the right over copies, and to make money from it if they choose.

Are you hung up on that it has to be some physical object?

Edit: to be clear, in this reasoning, the thing deprived from someone is not your copy of the movie, but rather the right of copying.

I haven't read mastering emacs, but reading about it gives me impression that it is more for using emacs?

Emacs is very much on the radar otherwise, and I have actually skimmed documentation for information about its architecture.

how?

First of all, "one out of a thousand" is grossly wrong.

And yeah, of course nobody wants that, but you can't take away a healthy part of growing up because of that.

Yes there is a huge difference.

I'm not sure what OP had in mind when asking the question, but at least for me it can be rephrased as:

"I LOVE Software Development/Engineering but HATE the industry. Can anyone relate?"

I really like the challenge of everything regarding SWE...users, specifications, documentation, planning, working with teams, testing, et.c.

But in most projects I have worked in something else has crept in:

  - No access to customers/product owners to discuss solutions
  - Everything being treated as manufacturing line
  - Fixed long term plans even though conditions have changes
  - Developers taking blame for changed conditions/wrong features

I feel like you are talking about something more like roadmap.

Of course long term plans/road maps have their place when everybody agrees on that it is an "idea of what's coming"

However most long term plans I have encountered at my last two companies have absolutely been treated as commitments to detailed plans two years ahead of time, before we have no idea what we really want.

This is causing project members constantly stressing/hurting about not meeting plan still years after everyone knows that the plan does reflect real life anymore.

> Somehow these language communities decided that panicking and giving up on the spot is a smart behaviour.

Oh, come on, that's a straw man.

Just because panic! exists as a "abort-program-with-a-message", does not mean it's somehow encouraged above using idiomatic error handling.

Just as you can do the same thing in languages with exceptions. Sometimes exiting the program is the right thing to do.

This is one of the best "side-effects" of testing, with the reasoning is that testable code is good code (as in modular, cohesive, etc...)

Fair enough.

And live in a neighborhood were everybody else is "nerdy" about the noise?

There are no clippings in the way they mean.

The robomover cuts the lawn so often so there is just a fine mulch that disappears below the lawn (and fertilizes it).

I have heard stories about your rabid HOA, but they can't have a problem with that?

Yeah, thats what he is saying as well, the long parenthesis makes it kinda hard to parse, but you are saying the same thing.