bborud

44 ms·

391.
by bborud 2y ago
Agreed. But knowing a bit about how a language (and runtime) actually works can make a huge difference when you design stuff. For instance, I've seen lots of examples of people implementing LRU caches in Java, and then scratching their
392.
by bborud 2y ago
That's an odd assumption. That you either have to choose between rabbit holes or development speed. Usually languages with lots of rabbit holes tend to require a lot more work. Take C++ vs Go for instance. C++ is an endless series of
393.
by bborud 2y ago
I think JS is a degenerate case. The reason I stay as far away from JS/TS as possible is that everything seems sloppy and therefore people try to "fix" things by replacing them every N months. Indeed, when you see so many com
394.
by bborud 2y ago
I disagree. ChatGPT is like pair programming with someone who is on drugs and tends to lie a lot. Co-Pilot is even worse as it constantly bombards you with poor suggestions and interrupts your flow when you should be left alone to think a
395.
by bborud 2y ago
The way to become good at something is to do it for a long time and to be willing to think about what you are doing and continually improve. There's much more to learning a language properly than just learning the language spec itself.
396.
by bborud 2y ago
I've been doing Go for a long time now and I still occasionally come across snippets of code that I don't understand or understand the purpose of. So I think "never" is too strong a word. I'd say "rarely&quot
397.
by bborud 2y ago
You are mixing two things. Learning a language and learning a codebase. Those are not the same thing. Besides, you are also just talking about what happens during the first N months. Most companies I've worked for allow for time to l
398.
by bborud 2y ago
Perhaps. Most people I work with do servers/backends, distributed systems and embedded systems. I think it may have more to do with the kind of people I work with.
399.
by bborud 2y ago
> Go and Node have some significant overlap, but Go and Rust are > barely even competitors. Among the people I know Go and Rust seem to be at the top of their list. Almost all people I know who program Rust also know Go. Not as many
400.
by bborud 2y ago
I wasn't aware of that project. This looks pretty new, but after clicking around a bit in the documentation looks very interesting. I get the impression that it isn't as verbose as a lot of other frameworks I've seen.
401.
by bborud 2y ago
I think the hype has already peaked for Go. When we switched to Go 8-9 years ago I already felt the hype had died down. We were late to the party. And I saw that as a good thing. To me it suggested Go was going to stick around. And now, a
402.
by bborud 2y ago
People always under-estimate the cost of properly learning a language. At any given time I tend to have a "main go-to language". I typically spend 2-4 years getting to the point where I can say I "know" a language. Th
403.
by bborud 2y ago
Can you give me an example of a decent UI framework? Or frameworks? (I'm not a GUI programmer, but I've been dabbling a bit using Fyne. I figured that in the C++/C# sphere UI frameworks especially on Windows were sorted out
404.
by bborud 2y ago
You can view the question as a proxy for "how do you provide value for money?". If you build something that then gets replaced a few years later, maybe you did something wrong. Ideally you make something that evolves, or even bett
405.
by bborud 2y ago
I have been following the advice of others more knowledgeable than me when buying AI-S lenses off of eBay, and I have to say that even on the D850, all of them have performed surprisingly well. However, I'd really like more "arty&
406.
by bborud 2y ago
Do you know of any manufacturers that still make (or have) interesting lenses for F-mount?
407.
by bborud 2y ago
You said it better than me. As for lack of autofocus, I’ve actually done action shots with a Petzval and various vintage manual focus lenses. Yes, it is tricky and you will miss a lot, but when you nail focus the result is glorious.
408.
by bborud 2y ago
Well, when it comes to lenses there is actually some old equipment that is still desirable. You can get lenses that are optically decent for very little money if you can live with manual focus or lack of modern coatings etc. I have several
409.
by bborud 2y ago
The good thing about lenses is that if you buy good lenses, they usually retain a lot of value, so you can sell them. And it isn't like you have to use them all the time. For instance, I rarely use my macro lens. And that's okay
410.
by bborud 2y ago
You forgot synthesizers. And I'm not even a good player :-)
411.
by bborud 2y ago
The problem is that it usually takes me a while to realize that something is good. Not least because I like durable things and ... well, it takes time to determine if something is durable. I bought my favorite jacket 12 years ago in Tokyo.
412.
by bborud 2y ago
It is tempting to look at the election in the US and ask what will determine the outcome - who has the policies that will make peoples lives better or who can come up with the most effecive derogatory nickname for the opponent and stoke the
413.
by bborud 2y ago
I thought the mission was to replace C++ for a many things at Google . You can't really lose to someone you are not competing with. The choice of managed memory is a pretty obvious hint that Go isn't a general direct competito
414.
by bborud 2y ago
We live in exciting times :-)
415.
by bborud 2y ago
I usually take it one step further: embed services that are typically external by default so that your application can run stand alone in a useful minimal, zero configuration configuration. It is a huge timesaver during development not havi
416.
by bborud 2y ago
Sure, but we're often making sparing use of what make has to offer, like the pattern rules. I think that's okay, but it is also a reminder that perhaps there is room for a similar tool that can support patterns and built-in mecha
417.
by bborud 2y ago
I use Makefiles to build Go applications for two reasons: it is available on the systems we develop on, and it provides a real alternative to writing bash scripts. Build scripts are bad. They tend to lead to complexity over time. It is ver
418.
by bborud 2y ago
I think one should aspire to not have to make use of a container to get to where you can build a project. I don't think it is productive to start off by telling people that it is okay to make a mess of projects and then try to hide t
419.
by bborud 2y ago
I guess it depends on how much of a departure from the current language it would be and if that introduces complicating factors. It would make sense to seriously consider adding matching (like in Rust) but then you might want to consider m
420.
by bborud 2y ago
Enums in Go are not good. Code generation just makes it worse. Both because code generation has a bad smell and because nobody can agree on how to do enums in Go so we just end up with lots of diverging solutions. Go 2 needs to have more u

More ›