metaltyphoon

Since go 1.25 you can declare the what is the “root” of a go module, which is a good thing. Not everyone wants the top level directory filled with go files specially in a multi language repo. So this idea that /src is not good go directory will soon be outdated.

Look at the issue tracker and its history too.

> Learn your basic UNIX/POSIX utilities first, please, before you start preaching because of Rust. :D

Maybe, jus maybe the defaults for UNIX/POSIX was just not good and thats why they Rust based one?

> Yup I have no doubt that there's a Rust 'evangelist' group somewhere aiming for inorganic growth of the language.

So anything using Rust now must be the ‘evangelists’ work right?

And it’s still a choice you can make regardless of Git moving to Rust or not, so what’s the problem?

> Rusty rust and C++-y C++ are both often slower than hand-rolled C for a given function

This makes no sense whatsoever and very far from the truth.

> Like a modern C with lessons learned.

Yet no string types. So lessons not so well learned. Zig does remove many warts in C.

That looks so bad :D

Maybe it’s a way to attract contributors?

Or you can just install ripgrep on windows too and have it check much faster ;)

> worst case you're getting that struct with all the fields set to zero, and you just have to handle the zero values

In the field I work, zero values are valid and doing it in Go would be a nightmare

> Would be nice if google released a self hosted server

These mofos are too greedy to do this.

Because it wouldn’t be a sport

This is one thing Rust did it right and I hope more languages adopt this.

It's a niche use case to have software that load plugins and it just so happens those plugins are written in Go? No it's not a niche case. If all programing you do in Go is web servers than sure you won't see this.

> Go’s design caused a production issue

A simple one, if you create two separate library in Go and try to link with an application, you will have a terrible time.

I've ran into this same issue: https://github.com/golang/go/issues/65050

https://www.youtube.com/watch?v=xuv9A7CJF54&t=440s

> Now if only Go was consistent about methods vs functions

Generics can only be on function and not methods because of it's type system. So don't hold your breath and modifying this would be a breaking change.

Traits, generics, ownership, RAII shows up in many languages, so what other concept outside of lifetimes does Rust introduces?

Nah not really. If you are in C/C++ land you know exactly what problem Rust solves. If you only even known GC languages then yeah it will be a up battle hill.

How is Sublime faster?

was de but named fy and no one planted anything :D

fy_pool_day

You just get to fight now at runtime!

Anyone that started computing using DOS is very aware of terminals.

> I find it uncommon to see anyone who chooses to use a terminal regularly using the MacOS default terminal

If you are going to say that about windows the same could be said about macOS. In fact, I only know of one mac user within my circle that has used the non default terminal.

Anecdotally, at day job, every terminal I see on windows is riced out. The Windows terminal app video from MS probably helped with that lol.

This is a wild take.

100% agreed

Yep. I've migrate to it as I need a terminal that is truly cross platform.

Not saying you are wrong, but this is akin to “this is the year of the Linux Desktop”.

You probably don’t have this telemetry but have you thought about how having window support helps Zig adoption?

Anecdotal, at day job, we started to use Zig build system to target Windows because that’s where the customers are.

“Ghostty is cross platform…” but not on windows :D

“App XYZ is mobile ready…” but not on Android.

Same vibe

This is to be said for any addiction