I traded a Prusa MK3S for a secondhand Bambu P1S and it was night and day. I believe the prusa could have gotten to a place where it printed well and consistently, but the P1S *just works*. It printed better out of the gate with 0 tinkering than the Prusa did after I had spent hours calibrating, testing, and re-calibrating it.
I wanted the Prusa to be just as good, which is why I started with it. I wanted to support the open ecosystem, but not at the expense of not getting to do what I actually set out to (print things nicely). It's a shame! Maybe I was holding it wrong (but again, with the Bambu, I didn't have to worry about it).
Interesting; I’ve had an mk3s for years now (which i bought specifically to avoid the tinkering necessary with other brands at the time) and apart from dealing with a couple of blockages (probably due to a cheap roll of filament) it’s been totally reliable and hassle-free. I think I’ve had it recalibrate itself maybe three times amongst hundreds of prints. I wish it had automatic print head adjustment to deal with flexible filaments, but that’s about it.
I have a p2s (and x2c) but the main difference in can instantly tell here is that I haven't had any clogs with any enclosed Bambu so far and whatever material I throw at it it just works. It's maybe not a lot difference but it's the thinker free experience I was hoping for.
Interesting you chose to link to 2 hit peaces interpreting his political views from their perspective instead of his posts detailing those views directly.
But you do. You're a tech lead at Stripe and your CEO is a founding contributor to this foundation. This is what you fund with your labor.
And if you weren't afraid of people coming to their own conclusion about DHH you could just link to his blog[1] rather than some literal marxist's opinions about his blog. Why not be intellectually honest and curious enough to state what someone says and point out what you disagree with directly rather than mimetically echo someone else's outrage?
I'm with you. And beyond his political views, I've never been particularly impressed by anything he's built, from Basecamp to HEY. I can at least understand why some people admire Elon Musk because of what he's accomplished, even if I don't share that admiration. But the almost cult-like devotion some people have for DHH is a complete mystery to me.
I love these release notes but I really wish they would add syntax highlighting to the Go blog. I'm always a little bit surprised/disappointed whenever I land on a go.dev link since I know the code will be just a little harder to visually parse than it needs to be.
There's a reason for this. Rob Pike was asked about it and said that syntax highlighting reminds him of the bright colors of children's toys and he personally disables it so that he can focus on the text.
I don't know why it's still like that but that's the original reasoning.
> Syntax highlighting is juvenile. When I was a child, I was taught
arithmetic using colored rods
(http://en.wikipedia.org/wiki/Cuisenaire_rods). I grew up and today I
use monochromatic numerals.
The reason traffic lights are colored is because they are showing distinct states of the same thing and the color is the means of differentiating.
Same for transit maps: different routes are colored to distinguish them from other routes, which is especially useful if they overlap.
But that’s not what syntax highlighting does.
The equivalent of your examples would be to not highlight the syntax at all, but only use color coding to distinguish variables.
The equivalent of how syntax highlighting currently works for your examples would be if the light fixture was one color, and the light pole was another, but then all the actual lights were the same color.
I actually think highlighting only the variables with distinct colors could be extremely valuable. Would certainly help avoid mistakes with nested i/j loop counters.
Edit to add: come to think of it, it would have been even more valuable in Go, until recently anyway. The variable color coding would expose the common loop variable instance bugs, because a programmer would be instantly puzzled by the unexpected coloring.
That does exist, it's called semantic highlighting.
In any case, my analogy was not perfect, but neither was Russ's! The point is it's totally normal and not "childish" to use colours to help distinguish things. Traffic lights do not technically need colours (you can use the position of the lights - I assume that's what badly colourblind people do). Nor do transit maps technically need colours - you could just label the lines, or use patterns.
Your comment makes me think of LabVIEW - if you're not familiar with it, it uses a visual programming language ("G") in which data flows down wires. The color of the wire indicates the wire's data type (blue for ints, orange for floats, green for bools, pink for strings) and the width of the wire indicates the dimensionality of the data (thin line = scalar, thick line = 1D array, double-thick = 2D array). The color is more than decorative or even assistive - it's essential to understanding the program.
I still wonder why every open-source visual programming language is either a toy for teaching or straight up awful, often not implementing but even loops, when LabVIEW has been doing it right for decades.
Despite its huge size and it installing several services that constantly run in the background, it's still one of my favorite "languages" of all time. It's the only one I've ever seen people going from never having programmed before to making simple but meaningful contributions in within a single day.
There are a bunch of identical things on my screen called lines. They contain a bunch of mostly identical things called tokens. Syntax highlighting uses different colors to identify the different purposes of all of these
tokens blasted onto my screen.
> Gofmt was written to reduce the number of pointless discussions about code formatting. It succeeded admirably. I'm sad to say it had no effect whatsoever on the number of pointless discussions about syntax highlighting, or as I prefer to call it, spitzensparken blinkelichtzen.
> When I was a child, I used to speak like a child, think like a child, reason like a child; when I became a man, I did away with childish things.
I sincerely hope Rob Pike was being sarcastic/ironic, because otherwise, he sounds insufferable
He sounds insufferable because he's calling syntax highlighting childish. Not simply politely saying it's not his thing. It's like he can't understand why anyone else would use it, or isn't bothering to. Maybe there's more nuance to what he said, but it's not obvious from the quote.
"Everyone who uses syntax highlighting is a child"
I mean, maybe he was genuinely trying to make a joke, but I'm well past the point of assuming random strangers are joking when they're being offensively dumb.
Unlike formatting preferences, the colours I use in my editor don't effect others. That said I might not mind living in a world where everyone used the same highlighting scheme, as long as it was reasonable ;)
That makes sense as a personal preference for him, but it's odd for that to still be the company/project stance. Like, surely he knows he's the minority for not wanting highlighting?
Apart from the fact that your comment is against the rules: please don't trivialize that quote. It has a profound meaning, and is completely out of place here.
There is a thread linked where we literally see gophers express the belief that they do not like syntax highlighting, and mock those who do - because Great Leader - born in 1956 - does not like syntax highlighting. Its called double think.
that's an extremely odd explanation and it makes me think that he has some hidden PTSD. it's also insane that one person's preference trumps the rest of the world's.
I understand and respect this position. I think syntax highlighting
is a highly subjective matter, bordering on personal preference with regard to shell interactions, editor configurations, bindings, shortcuts, snippets, and the like. It's also... insignificant somehow, like quibbles over formatting rules that Go settled once and for all with `go fmt`.
I often prefer not to enable syntax highlighting just for color. Occasionally I'd choose some minimal theme that only highlights string literals and keywords. So it has two or three colors. But some of the color schemes I see are a festival of lights where every special element of syntax has its own color.
I don't understand how that is supposed to help me parse anything and why the rules are complex. The `range` keyword needs to be purple, and `chan` must be navy blue. Why exactly? And every site has a different color scheme? There is no consensus, and there shouldn't be.
For a serious community-driven project like Go, dealing with the question of syntax highlighting is strange. The creators deliberately avoided the questions of IDEs and editors for Go, leaving them to the community. I think the same principle applies here.
> The creators deliberately avoided the questions of IDEs and editors for Go, leaving them to the community. I think the same principle applies here.
Exactly. This is fundamentally about accessibility (in the broadest sense). Do people have opinionated screenreader settings they like to force on others too?
I get the why, kind of - if you need colors to make sense of code, maybe the code isn't clear enough. If you send blobs of code through email and other systems that don't necessarily have syntax highlighting, it also makes sense. But on a website, whyever not?
Personally I can't say when I was last actually aware of syntax highlighting. The only time I'm actively engaged with it is to change the default low contrast comment color that a lot of themes have (for some reason, as if comments are unimportant / noise) to something better. For Go, I don't really notice when it has or doesn't have syntax highlighting, at least not on e.g. go's website.
When I started learning Go I went all in including using the recommended editor (acme editor) which has no syntax highlighting, no autocomplete and a very different way of writing code. My production went down a lot but the quality of the code went up a lot.
I think the lack of syntax highlighting was one reason for that. It makes you think more about the code you write and how it should compose, while a fully fledged IDE encourages you to just throw more code at the problem.
I think the ACME way should be used for love of code and ideally when you want to create libraries that stand the test of time.
When you just want to get things done fast bring the full IDE and now some LLM vibes and it’s done.
I go through intervals of turning autocomplete on and off. I think autocomplete is useful for boilerplate (similarly LLMs are useful for boilerplate), but I prefer not to use either when writing code where correctness is particularly important. This is because it’s easier for me to internalize what something is doing by typing it out. It’s actually more effort for me to understand code by reading it rather than writing it.
I experience something similar with system design, where the act of creating a diagram helps me to understand much faster than trying to read someone else’s diagram. It’s not because only I can create good diagrams (I cannot) but again because the act of creating one helps me internalize the design.
I think there's a lot of value to be gained from turning all modern day features off for once and just code "raw", no syntax highlighting, just typing out all the code. Doesn't even need to be your own code, manually transfering code over can also help a lot with your basic coding skills.
I think a lot of people lose this over time because it's easier to use templates, autocomplete and LLMs, work from a higher level. But it's nice to go back to basics. Consider also firing up Pico-8 and writing some really really bad code. It's got a very rudimentary editor, 40 columns of code, no syntax highlighting, and you're limited in how much total code you can write. It also helps with leetcode since a lot of leetcode uses game coding tricks like modulo operators, min/max/clamp, etc (that's as far as I got, don't judge).
The Go language is by itself more than enough to get a trademark. They only additional thing you can do with a font is get a design patent... for the font.
It's more likely that they don't feel the need to use the font they gave you (for your code editor) on code samples on their own web pages. As it's a custom font, the text would be susceptible to pop-in, or would visibly switch from one font to another, both of which are ugly.
So they have no specific font preference for code samples, they only show their Go-specific font on the blog post about it. They prefer fast loading and no jank over custom font.
EDIT: just force reload https://go.dev/blog/go-fonts and look at the first hyperlink, "golang.org/x/exp/shiny". Watch it visibly switch from generic monospace font to Go Mono as the page loads. Janky! They probably don't want that for all their code samples ever.
There's also different building pressures. Before, companies would want to build / power / maintain the smallest amount of data center hardware they could while still serving their needs. Overprovisioning just meant worse opex number.
Now, because supply is so constrained relative to demand, there's no limit. More is always better, which leads to a crazy amount of construction (as its negative effects).
Maybe we are using different tools (or we've set it up wrong) but I'm consistently surprised at how slow Go's linting is (using golangci-lint). Takes nearly 5 minutes on our codebase after any change (which means I just don't run it locally or in-editor). It's remarkable how poor the experience is after using tools like Python's Ruff (instant) or Rust's Clippy. I'd have expected a fast, default setup that I could tune.
Event JS's Eslint, which runs in actual JS, takes 21 seconds for a full sweep (which I don't normally run, since the in-editor hints are so fast)
It's surprising, because so many of Go's dev tools are so well thought out!
Bummer. Airtable's a killer product and I've been using and evangelizing it for nearly 10 years at this point. Built whole side projects around it (and its API), plus organized a ton of personal information. I've made some custom integrations too which have just kept working without maintenance for years. I've got fairly regular backups of all my data, but still. Hurts my heart a little.
Best case scenario it keeps working without totally jacking up the prices. But also starting to think about long-term alternatives. BaseRow seems reasonable, as does spinning all of my many bases into a single big Django monolith (something I've had in the back of my head for while anyway). But it's been nice not having to micro manage this service. Pretty good mobile app, too. Enjoyed it while it lasted, I guess!
Why not simply rebuild what you need with Claude? Airtable seems to me as a prototyping product. Once you know what you want, formulate it as product objectives and ask Claude how it could be implemented from scratch. Dont even give it any ideas about Django. Just ask it what technologies are sensible for what you need, read and verify its answers, lock in a stack, plan your features and implement them.
You will be surprised how many things you could not fix in Airtable or where awkward workarounds can be solved much more elegantly if you (or Claude) consider them straight in the design phase. Just make sure to start with your objectives and _maaaybe_ desired workflows to avoid biasing Claude too much and that you end up rebuilding Airtable.
> Why not simply rebuild what you need with Claude?
Claude isn't some magic genie that can give you whatever you ask for. If you need a spreadsheet, it is much easier at this point to start Excel than to ask Claude to write you an Excel.
Stripe | Hybrid (50% of time in Toronto office) | Senior Go developer
We're looking for a senior-level Go developer who can design and ship idiomatic code our users love to work with. We can all write Go that compiles, but don't always know what best practices for 3rd party code are (in the Go ecosystem specifically). Ideal candidates are a part of the Go community / ecosystem and know what the current best practices are. They also probably have TypeScript experience (most of our tooling is TS) and in a perfect world, Ruby/PHP ecosystem knowledge (the other languages we're currently seeking expertise in). But, if we get a Go expert who's willing to learn a bunch of TypeScript, that probably works!
This sounds up my alley - Go (10+ YoE), TS (10+ YoE), PHP (25+ YoE) and I'm very interested but my wife and I both have elderly parents to support so relocating isn't really an option. (Minnesota)
> People will claim real harms but the connections are spotty at best.
This is a wild claim because it's trivially provable. There's been tons of reporting around the effect they have on the immediate vicinity, and that's without even getting into the unknown long-term effects.
Is every single mad person doing investigative reporting and / or living next to a data center? No. But something doesn't have to personally affect me to know it's harmful.
Is it not trivially provable. That video you linked to is sensationalized. You can do the same to almost any topic.
At the start of the video they claim data centers are being built in growing neighborhoods as though it's a conspiracy. Everything is being built in growing neighborhoods, that's the defintion of a growning neighborhood. Speaking "Coffee shops are growing in XYZ city" in ominous tones doesn't make it actually ominous.
They when go on to say there are 4x the data centers since 2010. Streaming TV went from 10% to 98% between 2010 and 2025. And there are plenty of other similar things (spotify, youtube, tiktok) that need data centers. In other words, consumer demand. Don't want the data centers, stop using them. I'm sure HN traffic also grew
The entire video is just digging up random stuff and trying to make it sensational. Oh, you can hear birds near data centers if you filter out the noise? That's true of basically everything, freeways, roads, bread factories, veg canners, etc... They're sensationalizing random common facts to make a ragebait video.
There's a sign next to a bridge that says "Weight Limit: 10 tons". Calvin asks how they know the limit and his dad says they build the bridge, then drive progressively heavier trucks across it until it falls down. Then they rebuild it exactly how it was and put up the sign for the how heavy the last truck was.
I wanted the Prusa to be just as good, which is why I started with it. I wanted to support the open ecosystem, but not at the expense of not getting to do what I actually set out to (print things nicely). It's a shame! Maybe I was holding it wrong (but again, with the Bambu, I didn't have to worry about it).