Panzerschrek

6 ms·

31.
by Panzerschrek 2mo ago
Sandboxing for build scripts can't work properly. If you sandbox too much, some necessary stuff can't be done. If you sandbox too little, it has no practical value.
32.
by Panzerschrek 2mo ago
> In the end it is your decision to use unaudited or refuse unaudited crates. It should be the default behavior of the package manager to allow downloading only audited/trusted packages. Forcing end-users of the language to be respo
33.
by Panzerschrek 2mo ago
Languages like Rust have sources of income to be able to finance such audit. You don't need to audit all the crap is being uploaded right now. Only really necessary and widely-used packages should be managed in a centralized way, so, a
34.
by Panzerschrek 2mo ago
Why this still happens? Why after many previous supply-chain attacks maintainers of package repositories still allow anyone uploading packages and pushing updates without security audit?
35.
by Panzerschrek 2mo ago
John Carmack promised that Quake II will use MMX, but this wasn't done. That's why software rendering in Quake II is so boring, it doesn't even support colored lighting. In the other hand Unreal did use MMX, which allowed it
36.
by Panzerschrek 2mo ago
It seems for me fundamentally wrong to use C# to write some scripting language, since C# itself is pretty high-level and is used widely for scripting (like in Unity).
37.
by Panzerschrek 2mo ago
> Typically very long latency and poor throughput. Recently I have been investigating what operations modern compilers for modern CPUs can optimize. I fond, that for floating-point types there are vector division instructions (which comp
38.
by Panzerschrek 2mo ago
Extern "fil-C" can't be compatible with Rust code or something similar. It requires a metadata block attached to each allocation. So, if a memory block has been allocated in Rust and a pointer to it is passed to a fil-C funct
39.
by Panzerschrek 2mo ago
The root cause of all C ABI problems are shared libraries. They give so much trouble with little to no benefits. Ideally no application should use them. All dependencies should be compiled from sources with the same compiler and standard li
40.
by Panzerschrek 2mo ago
> // Proposed: Transparent Aliases > _Alias g = f; I think defining a constant function pointer should work. As long the compiler doesn't store this pointer in the result executable and optimizes-out all calls via it in
41.
by Panzerschrek 2mo ago
Google Earth is likely not profitable to keep it alive. This probably happened with many other services killed previously.
42.
by Panzerschrek 2mo ago
> mcpp.toml ← project manifest It's a fatal flaw. A declarative language isn't powerful enough to be able to describe complexity of typical C++ project. That's why cmake language (Turing-complete) exists.
43.
by Panzerschrek 2mo ago
Is it memory safe? Can I cause a memory-related bug writing normal (safe) code in this language? > The one rule is that once you use a resource, you cannot use it again What about data structures which need to be shared? Can I use some s
44.
by Panzerschrek 2mo ago
> You're inside a virtual machine. It's wrong. I have Hyper-V and VirtualBox installed on my machine, maybe it has some effect? > You use Microsoft Office No, I don't. It was installed previously, but my license expired
45.
by Panzerschrek 2mo ago
> The stack of each coroutine is fixed to a constant value. > #define COROUTINE_STACK_BYTESIZE 4096 That's the whole point of Go coroutines to have no such limitation on stack size. Go is able to grow stack if necessary. Implemen
46.
by Panzerschrek 2mo ago
> You have 12 marbles and a balance scale. I hate such interview questions. They have nothing to do with think one really needs to do in practice. It seems for me to be just a way for interviewers to show their intellectual superiority.
47.
by Panzerschrek 2mo ago
Can I write a game using OpenGL in this language? Does its functional purity allow this?
48.
by Panzerschrek 2mo ago
https://sr.wikipedia.org/wiki/%D0%94%D0%B0%D1%82%D0%BE%D1%82... https://de.wikipedia.org/wiki/Datei:Embassy_of_Russia_in_Hav...
49.
by Panzerschrek 2mo ago
Is it hand-written?
50.
by Panzerschrek 2mo ago
> influenced by Brutalism Actual brutalism is actually pretty. But what is today called modern architecture, is not brutalism, but a consequence of construction cost cuts.
51.
by Panzerschrek 2mo ago
> C++ is just fine No it isn't. Using undefined behavior for things which can be implementation-defined behavior instead is harmful. It creates more space for bugs and security vulnerabilities.
52.
by Panzerschrek 2mo ago
A good example of C++ bizarre design decisions. The exact handing of float<->int conversions should use implementation-defined behavior instead, defining some cases to be UB just adds more traps with little to no performance benefits.
53.
by Panzerschrek 3mo ago
They are widespread, but not among "normies", but professional programmers. That's what I call a failure, since they were initially designed to be used by non-programmers.
54.
by Panzerschrek 3mo ago
Yet another attempt to fix the problem with 14 competing standards by introducing one more standard. Now a C++ developer can face a problem, when he needs some thirdparty dependency and it requires Zig to be built.
55.
by Panzerschrek 3mo ago
I generally don't think it's a good idea to develop a language for non-developers. It was tried before multiple times and the end goal has not been achieved. Sooner or later one realizes, that professional developers are still nec
56.
by Panzerschrek 3mo ago
> GCC Isn't needed if we rewriting anything in Rust anyway. > GNOME, KDE They aren't that huge. Huge is the overall codebase of applications using them. It's relatively easy to create a native Rust GUI framework and rew
57.
by Panzerschrek 3mo ago
> we have to care about not using ages as shoe sizes and indexes with the wrong arrays. "Memory safe" languages usually don't help In languages even slightly better than C one can create a wrapper type for int/float
58.
by Panzerschrek 3mo ago
> but it's still possible to use memory incorrectly Only by misusing unsafe . Using it in regular programs actually isn't that necessary. In languages like C you have unsafe code almost in every line. > My understanding is
59.
by Panzerschrek 3mo ago
In case of such projects like LLVM C++ usage can be tolerated. But for new code or smaller codebases a better alternative should be considered. Also Fil-C can't be used for LLVM anyway, since performance and memory consumption overhead
60.
by Panzerschrek 3mo ago
The main problem of Fil-C or similar solutions is not that they provide absolute safety with no escape hatch (unlike languages with unsafe keyword). The problem is that they provide an excuse to keep using terrible programming languages l

More ›