metaltyphoon

14 ms·

91.
by metaltyphoon 10mo ago
Unless someone is vetting code, nothing.
92.
by metaltyphoon 10mo ago
> and similar package ecosystems altogether Realistically, this is impossible.
93.
by metaltyphoon 10mo ago
I truly despise the damage those books did to the SWE as a whole.
94.
by metaltyphoon 10mo ago
It’s this simple in .NET ArrayPool<T>
95.
by metaltyphoon 10mo ago
> many devs keep ignoring And thats why Zig don’t offer much. Devs will just ignore it.
96.
by metaltyphoon 10mo ago
What are you trying to imply?
97.
by metaltyphoon 10mo ago
I don't consider C# a very large language. Most of what has been added removed boilerplate code. Swift, a much younger language, is way more complicated IMO
98.
by metaltyphoon 10mo ago
> Those two aren’t natively compiled Idk how up to date ou are in .NET but so you can have an idea how trivial it is in C#: echo ‘Console.WriteLine(“hello world”);’ >> app.cs dotnet publish app.cs That’s it. By default
99.
by metaltyphoon 11mo ago
> Minecraft Typo?
100.
by metaltyphoon 11mo ago
Out of all those only Java and Kotlin captured significant market like OP mentioned
101.
by metaltyphoon 11mo ago
‘static
102.
by metaltyphoon 11mo ago
> I am almost certain that the zig project will somehow manage to survive anyway without you following them. It took longer than expected for this comment to show up.
103.
by metaltyphoon 11mo ago
C#?
104.
by metaltyphoon 11mo ago
>zero actual dependencies on Linux only with CGO_ENABLED=0 and good luck using some non web related 3rd party module which can be used with CGO disabled.
105.
by metaltyphoon 11mo ago
This is exactly the problem, thread safety. The function being supplied with std.Io needs to understand what implementation is being used to take precautions with thread safety, in case a std.Io.Threaded is used. What if this function was d
106.
by metaltyphoon 11mo ago
Why? Asynchrony has nothing to do with multiple threads. In fact you can have async with only a single thread!
107.
by metaltyphoon 11mo ago
Except that now your library code lost context on how it runs. If you meant it to be sync and the caller gives you an multi threaded IO your code can fail in unexpected ways.
108.
by metaltyphoon 11mo ago
In C# that Task is ALWAYS hot, aka scheduled to run.
109.
by metaltyphoon 11mo ago
Attribute, lambda and turbofish?
110.
by metaltyphoon 11mo ago
Thats not the point OP was mentioning as in “battle tested” doesn’t mean free of bugs.
111.
by metaltyphoon 11mo ago
This is a reason why so many enterprises use C#. Most of the time you just use Microsoft made libraries and rarely brings in 3rd party.
112.
by metaltyphoon 11mo ago
Yes it's meant to be used in test code. If you're sure it can't fail do then use .expect() that way it shows you made a choice and it wasn't just a dev oversight.
113.
by metaltyphoon 11mo ago
> Well Rust won't save you from the usual programming mistake This is not a Rust problem. Someone consciously chose to NOT handle an error, possibly thinking "this will never happen". Then someone else conconciouly reviewe
114.
by metaltyphoon 11mo ago
Rust isn’t that complicated if you have some background in non GC languages.
115.
by metaltyphoon 11mo ago
> As a small example wrt Rust: resetting an arraylist/vector while reusing its memory is a weirdly complicated trick https://lobste.rs/s/emvkea/why_we_didn_t_rewrite_our_feed_ha ... Nitpicking? Let’s show a
116.
by metaltyphoon 11mo ago
> It's interesting how much Rust has slowed down Rust has a SDK from the 3 big cloud providers, Rust IS mainstream.
117.
by metaltyphoon 11mo ago
It is Java as C# disallow this
118.
by metaltyphoon 11mo ago
Read that and what part of that can’t be done in Rust in 2025?
119.
by metaltyphoon 11mo ago
> managing lifetimes If you are not using a GC language, you WILL be managing lifetimes. Rust just makes it explicit, when the compiler can’t prove it’s safe, which Zig, C don't really care.
120.
by metaltyphoon 11mo ago
> I know that Zig doesn't allow attaching data to error for good reasons. If error data contains interior pointer then it causes memory safety problem IMO this is not a good reason at all.

More ›