[dead]
Sorry to hear that - are there any particular tweaks you think would work to reduce the impact? Is it i.e. the blue used by code snippets? Or because there's also the diff syntax which has green/reds?
Go 1.24's go tool is one of the best additions to the ecosystem in years
11–20 of 207 posts
Re: Go 1.24's go tool is one of the best additions to the ecosystem in years
#12[dead]
[deleted]
Re: Go 1.24's go tool is one of the best additions to the ecosystem in years
#13[dead]
I came to the comment section for this comment.
Dark background, too many colors, inconsistent spacing, inconsistent font-size and/or family, some links appear fully pink with pink underline, some links aren't pink and only have the underline, inline I had to stop reading unfortunately. is blue, but large code blocks are the same color as regular text – on black background, etc.
Re: Go 1.24's go tool is one of the best additions to the ecosystem in years
#14As someone who’s been using Go since 2013 at commpanies like Apple, Microsoft, and Uber, this all seems quite unnecessary. That said, if it helps people do “their thing” in what they believe is an easier (more straightforward) way, then I welcome the new changes.
I am both strongly of the opinion that this was already done much better in Bazel, and that the go-native version seems clean, clear, and simple and should probably be adopted by pure go shops.
The digraph problem of build tooling is hardly new, though the ability to checksum all of your build tools and executables and mid-outputs to assure consistency is relatively new to feasibility. Bazel is a heavy instrument and making it work as well as it does was a hard problem even for Google. I don't know anyone making the same investment, and doubt it makes the slightest hint of sense for anyone outside the fortune 500.
Re: Go 1.24's go tool is one of the best additions to the ecosystem in years
#15[dead]
Sorry to hear that - are there any particular tweaks you think would work to reduce the impact? Is it i.e. the blue used by code snippets? Or because there's also the diff syntax which has green/reds?
> are there any particular tweaks you think would work to reduce the impact?
Yeah, remove all CSS.
I clicked on View -> Page Style -> No Style in Firefox and suddenly I could read it. Reader mode in Safari also worked. Reading mode in Chrome didn't work properly.
Re: Go 1.24's go tool is one of the best additions to the ecosystem in years
#16[dead]
Sorry to hear that - are there any particular tweaks you think would work to reduce the impact? Is it i.e. the blue used by code snippets? Or because there's also the diff syntax which has green/reds?
Choosing colors is like making music. This color scheme feels discordant, like a jumble of loud notes. Maybe try looking at color palette creators online?
Re: Go 1.24's go tool is one of the best additions to the ecosystem in years
#17[dead]
Sorry to hear that - are there any particular tweaks you think would work to reduce the impact? Is it i.e. the blue used by code snippets? Or because there's also the diff syntax which has green/reds?
(not OP) some ideas: make the
's not go all the way to out the edge of the window. Make the diff colors and code colors less dramatically different from its surroundings. Increase the contrast of the default text. Use blue for links. Drop the orange
Re: Go 1.24's go tool is one of the best additions to the ecosystem in years
#18Earlier quoted context omitted.
Sorry to hear that - are there any particular tweaks you think would work to reduce the impact? Is it i.e. the blue used by code snippets? Or because there's also the diff syntax which has green/reds?
Choosing colors is like making music. This color scheme feels discordant, like a jumble of loud notes. Maybe try looking at color palette creators online?
My first thought was Monokai (the default theme in Sublime Text 3 and earlier)
Re: Go 1.24's go tool is one of the best additions to the ecosystem in years
#19Earlier quoted context omitted.
Sorry to hear that - are there any particular tweaks you think would work to reduce the impact? Is it i.e. the blue used by code snippets? Or because there's also the diff syntax which has green/reds?
Choosing colors is like making music. This color scheme feels discordant, like a jumble of loud notes. Maybe try looking at color palette creators online?
Thanks - this is based on the Srcery theme (https://srcery.sh/) but maybe needs some tweaks, as per some suggestions in the thread
Re: Go 1.24's go tool is one of the best additions to the ecosystem in years
#20I always think it's a shame that these features end up getting built into ecosystem-specific build tools. Why do we need separate build systems for every language? It seems entirely possible to have build system that can do all this stuff for every language at once.
From my experience at Google I _know_ this is possible in a Megamonorepo. I have briefly fiddled with Bazel and it seems there's quite a barrier to entry, I dunno if that's just lack of experience but it didn't quite seem ready for small projects.
Maybe Nix is the solution but that has barrier to entry more at the human level - it just seems like a Way of Life that you have to dive all the way into.
Nonetheless, maybe I should try diving into one or both of those tools at some point.