Greduan

Just ftr I believe in the holocaust and wouldn't want it repeated. But aren't there modern tragedies that could also receive more attention, and might be more impactful?

Sounds exactly like it yeah.

Other languages remove lifetime tracking by making you track it in very limited spots. Instead of "for each individual object", you track it for "this particular kind of object in this part of my application".

I.e. don't need to keep track of the memory for each allocation in my HTTP request and make sure I clean it up before closing the connection, I can just allocate some memory _per request_, put stuff in it, and at the end it gets cleaned up, whether I used the memory or not.

Some languages have the idea of "memory allocators" as a native construct, so that you can actually start thinking about managing memory in more sensible terms than "everything individually", e.g. Odin lang.

Was a pleasure to watch. It's unclear to me why AWS wouldn't post a real RCA, since that would also be more useful to themselves internally as well. Perhaps they have a sneaky "internal RCA".

Text editors in a thousand flavours has indeed already been programmed though. I don't think you understood what op meant.

Curious, does it perform at the limit of the hardware? Was it programmed in a tools language (like C++, Rust, C, etc.) or in a web tech?

> Software folks are obsessed with copying what has been shown to work to the point that any advance quickly becomes a cargo cult

Seems more accurate to say they are obsessed with copying "what sounds good". Software industry doesn't seem to copy what works, rather what sounds like it'd work, or what sounds cool.

If they copied what works software would just be faster by default, because very often big established tools are replaced by something that offers similar featurage, but offers it at a higher FPS.

Well imagine somebody was talking about "bass" the fish, in a context of "bass" the instrument. If they pronounced it like the fish, certainly for a moment your language processing would stop, figure it out, fill in the gap, and continue.

Every time the wrong pitch accent is used, a similar process takes place. Especially in highly complex conversations, where a lot of processing power is going towards the semantics itself, and hopefully the person shouldn't have to worry about figuring out which word the other person is saying.

It's unclear if you yourself have native-level (or close to) pitch accent yourself. But if you don't, how can you know whether it's actually important or not?

Oh if only you watched the presentation, where he quotes Bjarne Stroustrup and Alan Kay xD

I'm the author of the post. Want to bring attention to the post, but also want to have a discussion about this.

Ain't nobody got time for that! At least not those that did do this.

The original concept will be modified in the future, reading it back I can make some changes that will make it clearer.

It is meant to replace Markdown and yes, I have grabbed some inspiration from Markdown itself and Textile.

All I'm doing is basically combining both of these and making it more powerful with less and clearer markup.

Of course it's going to be developed to output the most recent HTML5.