renox

Bah, each time someone say this they "forgot" that one side effect of 'every frame is perfect' is that it can increase latency.. Perfection or latency? That should be the user's choice not the developer's..

1) the name is a discoverability issue for non-german people.

2) In the examples, the placement of & is incoherent: sometimes it's 'i64&', sometimes it is 'i64 &', pick one (I prefer the first).

3) constexpr is a long name for a 'base' concept. comp/<a special letter> would be better. Also conversion_constructor is huge.

4) In D, their static_if doesn't introduce a scope, Alexei Alexandrescu has made a very insteresting pitch about this.

5) zero_init is nice.

6) I don't like "hidden" overloaded operators, how about #+ for the overloaded variant of +?

7) you support i128 natively but integer literals are limited to 2*64-1?

8) I'm slowly reading "reference checking" ( https://panzerschrek.github.io/U-00DC-Sprache-site/docs/en/r... ) which seems to be an important part of the language, and I still don't know what's the integer overflow behaviour which is quite important..

I advocate Zig's behaviour: signed and unsigned have undefined behaviour in case of overflow for optimised build, trap in debug build and there are modulo operators.

Bah, I think that these kind of vulnerabilities exist in any "packaging ecosystem" where the base language offer "ambient authorities"(any library can access your filesystem) which is .. all of them! AFAIK only research languages do not provide these ambient authorities :-(

> In fact I think atheists should make more effort to learn about the vast diversity of other faiths. It's very narrow to be atheist only about the Abrahamic deity.

Your sentence doesn't really make sense, and there is a lot of deities..

> You end up incorporating a lot of Christian thought without realizing because it's so deeply ingrained that it seems like the only option.

Depends on the country, some Northen european countries have a very high proportion of atheists, so it happens probably less there.

Is there an OS whose primary FS is a taggedFS? It'd be interesting to hear from the users if this is nice to use or not..

Yes and being 'opposed' to QM contributed to expose the 'spooky action at distance' that QM implies, which is very important.. It's a pity that experimentators were able to demonstrate it only a long time after Einstein's death, what would have been his reaction??

> - Tabs.

Tabs aren't really new: look at BeOS which could "tab" windows..

That said I agree with you that tab are really nice, especially the way VSCode manage them with the vertical list of opened files (I switched from vim to VSCode due to this feature).

Well, it dépends: there are a lot of places where the locals goes because they are cheap not because they are good.

But yes, ask the locals.

Note that in Zig, unsigned integer have the sqle semantic qs integers on overflow (trap or wrap or UB). You also have operators providing wrapping. That is the correct solution.

And the Chrome capsicum hallucination got me..

It may gives them less headache but if the part about the antivirus flagging the exécutable as suspicious it may give the users headaches..

I still find weird that they didn't make A,B... just after the digits, that would make binary to hexadecimal conversion more efficient..

I worked (a long time ago) on a C project where every int was wrapped in a struct. And a friend told me about a C++ project where every index is a uint8, uint16, and they have to manage many different type of objects leading to lots of bugs.. So it isn't really linked to the language.

I've seen some issue with this approach is that management will want to sell the prototype, bypassing the "rewrite from the lesson learned" step, and then every shortcut took into the prototype will bite you, a lot..

And things like "race conditions"/lack of scalability due to improper threading architecture aren't especially easy to fix(!)..

It's a minor detail but list starting at 1, with -1 being the last élément and 0 being 'none' is weird.. Why did you make this choice instead of 0 for the first élément, -1 for the last one? It would avoid the 0 'trap'.

> Eventually both Windows and Linux programs moved to a model where the OS just gave you the window as a drawing surface, and you were supposed to fill it.

If you follow this model, how do you solve the accessibility issue?

>signed integer overflow being UB would count for C/C++

Then, I raise you to Zig which has unsigned integer overflow being UB.

> Java everything is boxed anyway

Not true, there's int and Integer.

> I noticed during my three week summer vacation that it took me a good week to unwind and slow down.

It depends a lot on what you do on your holiday. I think it's best to start with something "mind focussing": you're not going to think about your job while skydiving, scuba-diving etc.

For && and || I disagree: they are 'shortcircuiting' operators and as such they deserve a différent name than just 'and', 'or'. That said &| should have been named and,or which would have freed &| to use for the shortcircuit operators.

> The cost of dead people is a lot higher than the cost of developer time.

So you're using proof on every line of code you produce?

Once Claude found a bug in my code but I had to explain the structure of the data. Then and only then it found the bug.

Of 'yourself', if a text field contain embedded/nested text you need to escape the delimiter.

Error safe, the : or :: I kind of doubt it, I think that finding a typing mistake (two : instead of 1) won't be easy..

Your point is funny but if you're not anal-retentive about the syntax you get monstrosity such as the CSV-escape rule instead of the passwd-escape rule..

> Dual use means extra ceremony with escaping

It depends, if you allow nesting you also need escaping.

I wonder if it wouldn't be better to have two fans: one at a high position and one at a low position.

No, it doesn't. But I'm not sure that this matter, a sufficiently "smart" compiler understand that this is the same thing.

> you can't have practical automobiles without inventing the windshield wiper

Sure, but remember that some wipers were "hand activated".

D (as always) is clever: the operator is ~ So no confusion between addition and concatenation and you can keep | for or.