bnolsen

5 ms·

31.
by bnolsen 10mo ago
Unfortunately it makes the libraries difficult (or at least very tedious) to read. I find zig's standard library a very good reference for figuring out to do things in application space, from what I've seen it's been very cle
32.
by bnolsen 10mo ago
I don't think manual memory management is c's problem. a very large number of errors i see in 'c' programs comes from the null terminated string paradigm and also mistakes from raw pointer manipulation (slices/fat p
33.
by bnolsen 10mo ago
"wrong practice" i always get the impression that rust is an authoratian language that thinks it knows how programming should be done.
34.
by bnolsen 10mo ago
I don't think D brought enough new to the table. I had already been coding in c++ for a while and was getting tired of all the little things wrong with c++. While D cleaned up a few things it was already too complex for my taste. And
35.
by bnolsen 10mo ago
Issues now are mostly with the standard library itself which is still in flux.
36.
by bnolsen 11mo ago
C++ explored a lot of ideas that some modern languages borrowed. C++ just had to haul along all the cruft it inherited and built up.
37.
by bnolsen 11mo ago
I don't think zig is that much more complex than golang, with a (currently) crappier standard library. The bonus being you leave no performance on the table. I wonder if it would work with devops, where both c++ and rust fails.
38.
by bnolsen 11mo ago
Zig is simple, clever and clean. certainly not perfect but it addresses much of what I disliked about c++. I wanted to like D and rust but they seem just as complex as c++. Yes, better in some ways but still full of complexity.
39.
by bnolsen 11mo ago
Custom allocators in c++ was never enjoyable nor easy. It introduces more template slop everywhere. That's one thing I really liked about eastl, it did allocators much better. But it wasn't maintained.
40.
by bnolsen 1y ago
Which version of zig compiler does this use?
41.
by bnolsen 1y ago
Both go and rust had substantial dedicated corp support and dollars behind them. Zig not so much. With that in view its advancement is pretty remarkable.
42.
by bnolsen 1y ago
The language itself won't change much. The standard library is what is still in flux.
43.
by bnolsen 1y ago
Go doesn't belong in this discussion.its a better java, c#, python and not much more. It doesn't work for 24/7 or for performance sensitive applications.
44.
by bnolsen 1y ago
People seem to underestimate this. One of the first reasons I noticed about c++ was trying to figure out what functions were being called in an overly complex inheritance hierarchy. The next was from hidden behavior from seemingly benign l
45.
by bnolsen 1y ago
The anti rust sentiment in large part is dissatisfaction with rust itself. Ziglang.org lists 3 principles of zig: no hidden control flow, no hidden memory allocations, no macros. This is not anti rust for the sake of being anti rust, this
46.
by bnolsen 1y ago
Hidden control flow violates the zig manifesto.
47.
by bnolsen 1y ago
The answer there was to always write small standalone executable unit test sets and simulation for day to day coding. Avoiding template heavy pigs like QT or boost helps too.
48.
by bnolsen 1y ago
Compilation speed makes go nice. Zig should end up being king here depending on comptime use (ie: lack of operators can be overcome by using comptime to parse formulae strings for things like geometric algebra).
49.
by bnolsen 1y ago
You could almost swap systemd and sysvinit out here. the biggest difference is that X and Wayland is a true dichotomy here.
50.
by bnolsen 1y ago
We can always dream about the unicorn language. In my opinion zig is the closest I've seen. Simple and orthogonal yet brilliantly extensible with its comptime. But it's not without its warts. And it doesn't annoy me like Ru
51.
by bnolsen 1y ago
That might violate the no implied behavior rule that zig has.
52.
by bnolsen 1y ago
Rust is super heavy handed in how it does it.
53.
by bnolsen 1y ago
Odin just hasn't been in the same league performance wise as rust, c, c++, zig. For these types of languages it's important.
54.
by bnolsen 1y ago
Tariffs are bad if you are the United States and tariffs are good if you are any other nation.
55.
by bnolsen 1y ago
I had a 3060 12g in my daughters computer. It would freeze every couple of weeks for who knows what reason. Swapped out her mobo/CPU/ram with mine and it still froze. Put in an rx5709xt and it's all good now. The 3060 is n
56.
by bnolsen 1y ago
The opposite is true. He uses vim therefore I trust him.
57.
by bnolsen 1y ago
My experience is the opposite. Epgot a hold of a bunch of floppies in 1991. Dual booted so I could play Diablo. Some time around '98/99 got tired of dual booting. Steam getting proton was a godsend, all those years of games becam
58.
by bnolsen 1y ago
Having coffee almost 30 years in c++ I really good tired of the complexity of it. Some of the newer complexity being workarounds for (in retrospect) poor decisions made decades ago. Build system situation never helped, and I still despise c
59.
by bnolsen 1y ago
Regarding ruby and python I thought the 2 were in the same league, esp compared to perl. Over 20 years ago I evaluated both and went ruby because of the more consistent api and of course pythons forced whitespace is an easy tie breaker agai
60.
by bnolsen 1y ago
Run your own locally but beware of copyright violations. My company uses some form of copilot that supposedly is guaranteed to be copyright safe. Personally i think it's very bad policy to make your skills dependent on something propri

More ›