IIRC, go cannot run arbitrary code at build time, so that should not make it vulnerable
HN user
saturn_vk
The package might not ever be executed on the user's machine. Depending on your setup, it might only be ran on a server, where the data that can be exfiltrated is completely different.
Is there an example of this?
Are you claiming that this does not show the speed difference between socket vs in process communication?
Great. I must be living on the moon then. I guess gnome work great there since it manages this part
On the other hand, it should be very obvious for anyone that has experience with concurrency, that changing a field on an object like the author showed can never be safe in a concurrency setting. In any language.
completely unusable
You forgot „for me“
Why does the display server have to restore window positions?
Do you have a source for that statistic?
It might be better budget wise, especially in volatile times
There are dozens of you. Dozens!
Wayland is still years away from usable state
… for you, surely. I’m sure there are some wayland users.
autotype keepassxc passwords
What is that?
remote desktop sessions
IIRC, gnome comes with an ootb RDP solution that, last I tried, worked as advertised. I’m not a big remote user though.
The company is VC backed. Why would the software disappear though? It’s open source, so it can survive even if the company doesn’t
I found nothing. Could you share the links you found, or are you lying
Imho calling this engineering would be an insult to advertise engineers.
Curiously, I too prefer Gnome 3, but with at least one extension - hot edge to make moving to the bottom edge of the screen show the overview, and thus the launcher.
It's just make polution to be produced in another location.
So you prefer to have locally sourced pollution then?
The Bulgarian currency has been pegged to the Deutsche Mark for more than twenty years now. This means that we’ve pretty much been using the euro since its inception, and any opposition is just a populist manoeuvring
I remember twirp being quite nice, too. Especially since it would also handle json from the same proto file.
this is irrelevant
I think OP mentions this due to your mention of meteor impacts
What about the tens of thousands of axe heads found all concentrated in one spot?
According to Wikipedia, Stone Age axes. It seems reasonable to believe that the site provided easy access for material
Do you have recommendations for embedding models?
Because it's so easy that you'd have a lot more time for gardening?
You can use records for the data structures. The only little annoyance is that you need to write the functions as static methods. So an argument for easy translation would lead to C#. Also, C# has advantages over Go, e.g. null safety.
Wouldn't these things be useful if you are making an actual compiler, that would run TS? Since in this case, the runtime is JS, I don't think any of these things would get any usage, unless they are used in the existing transpiler.
Calling the US the free world might be one of the reasons we’re in this mess in the first place
Also DI, which is arguably not necessary at all in Go given how elegantly interfaces work.
DI is necessary in every language that doesn't rely solely on global singletons. Passing dependencies as arguments to a function is DI.
What may not be necessary, are IOC containers automatically create objects and satisfy their dependencies.
Maybe stash a slog logger in there, but that’s about it.
Please don't do this either. Read the stuff you want to log as additional attributes in your slog handler from the context, which you ultimately pass to `slog.*Context`
Kitty honestly looks pretty bad, at least on gnome. I’ve tried tweaking its settings, but I could never get it to look even remotely as good as ghostty out of the box. And the latter looks like a proper gnome app
No immigrant who turns up at the US border has paid any taxes or contributed anything to US society. It's ridiculous to suggest otherwise.
Are you trying to tell me that until someone becomes a citizen in the US, they pay no taxes whatsoever? I find that hard to believe.
This is a dumb statement. Immigrants pay taxes as well
Even if you don't have any help from an LSP, I don't really see how this change adds any meaningful complexity.
With `for x, y := range m.Range`, you know you are iterating over something, and you are getting an `x` and a `y`. For the purposes of understanding the range block and what it does, it doesn't really matter what `m.Range` is, only that it allows iteration. Just like you don't care in <=1.22 land whether `m.Range` is a slice, map, or channel, because for the purposes of understanding the code, that doesn't matter.