nasretdinov

3 ms·

1.
by nasretdinov 1mo ago
I must say I find my colleagues who use AI instead of answering the damn question equally frustrating, and unfortunately they're in another country so I can't throw them into the ocean
2.
by nasretdinov 1mo ago
The risk with any cloud is that while your data might be physically intact, you can still lose access to it for a variety of reasons (e.g. being born in a wrong country)
3.
by nasretdinov 1mo ago
With that modern LLMs are capable of I'n seriously considering investing in at least M-DISC storage or similar to store stuff I don't want to lose :). It's unlikely that both iCloud and Synology get hacked at the same time, b
4.
by nasretdinov 1mo ago
Interestingly enough, the question "do we want to support it" has been the main one (not "can we write it") in any sufficiently large and mature project for as long as I remember. Now, becoming large is now a solved prob
5.
by nasretdinov 1mo ago
That's an interesting technique! I'd also like to point out that there's something odd with the page itself too, my phone got really hot while I was reading the page, and drained a significant amount of battery charge as well
6.
by nasretdinov 1mo ago
That's one of the things that surprised me (in a positive way) about Mac OS X when I first got to use it -- it actually does indeed do lots of things in an _understandable_ and genuinely simple way. It's also clear how much work w
7.
by nasretdinov 1mo ago
Go was born into 64-bit era, I remember seeing many more bugs that only occur on 32-bit systems. I'm pretty certain the observation in the article is correct that no one at Google tests Go on anything apart from 64-bit ARM/x86 Lin
8.
by nasretdinov 1mo ago
Yeah that's quite odd that people somehow now think you can't reject a PR because you can't understand it -- but initially that was one of the reasons to have code review in the first place.
9.
by nasretdinov 1mo ago
I believe what's being described in the article is the same reason why some shells like fish also use posix_spawn() on macOS instead of fork/exec. Not only is it much faster, but it's also effectively problem-free for multi-t
10.
by nasretdinov 1mo ago
Yes -- the bigger the difference between languages the worse they perform. However I'm not really expecting e.g. Claude to be able to port sync.Map from Go to Rust, because sync.Map relies on GC to do the hard work of cleaning up refer
11.
by nasretdinov 1mo ago
IMO that's precisely why software engineering is going to become even harder than it is right now -- all the "easy" stuff is semi-automated, so now you have to spend even more time and energy "drawing the rest of an owl&
12.
by nasretdinov 1mo ago
LLMs are scarily good at translation, whether between natural or between programming languages. Also very good at re-implementing the stuff that has been provably done before. And, arguably, 90-95% of writing code is exactly that.
13.
by nasretdinov 1mo ago
TBH Apple never should've been the one who makes the best CPUs -- that's not really their area of expertise historically speaking either. It just appears that everyone else did such a terrible job for so long that they caught up
14.
by nasretdinov 1mo ago
Yeah, Odin's auto-SoA looks nice indeed
15.
by nasretdinov 1mo ago
Hard to say tbh, but there are some high-profile examples, e.g. from Discord: https://discord.com/blog/why-discord-is-switching-from-go-to...
16.
by nasretdinov 1mo ago
I think the fact that package names are URLs is simultaneously genuis and horrifying.
17.
by nasretdinov 1mo ago
I still believe that SIMD support is one of the most underrated new features in Go. It's relatively straightforward to read and to write code using Go's SIMD package (the caveat being that you have to convert your data to SoA manu
18.
by nasretdinov 2mo ago
As someone who tried doing things like condition pushdown, transpiling from one language to another, etc, this is really impressive. Correctly pushing subqueries while preserving the semantics of the original database is something I can&#x2
19.
by nasretdinov 2mo ago
Correct concurrent code is mind-bogglingly hard even for seasoned veteran humans (and don't get me started on distributed programming...), so it's hardly surprising that LLMs with their limited context windows into the code have a
20.
by nasretdinov 2mo ago
You know, clouds in general let you run arbitrary code and that's not really considered an exploit :)
21.
by nasretdinov 2mo ago
I've once made a disk image backup of the running system (and it warn that it might be a good idea) and then wiped the laptop clean and installed a new macOS. The disk image (predictably) failed to mount and there wasn't much I co
22.
by nasretdinov 2mo ago
Now I have full understanding
23.
by nasretdinov 2mo ago
Why isn't it a good fit? The design prioritises readability of code that uses generics vs writing generic code (which is in line with the overall language philosophy). It also does it in a way that doesn't impact compilation speed
24.
by nasretdinov 2mo ago
Also having stuff like a concurrency limiter (instead of doing weird var limiter chan struct{} and using it as `limiter <- struct{}{}` and `defer <-limiter`) as a library function in `sync` package would be great too.
25.
by nasretdinov 2mo ago
Well, better late than never. Stuff like sets or a typed heap is long overdue. Maybe they'll even add iterator API for database/sql results this decade too (something like my pull request for sqlx https://github.com&#x2
26.
by nasretdinov 2mo ago
> the main issue is that they’re completely undebbugable now Well, that means the quality actually dropped then :). Looking impressive isn't equal to quality, understandability and reliability is
27.
by nasretdinov 2mo ago
Well, no, I don't think you should be doing that :)
28.
by nasretdinov 2mo ago
Yes, but on the other hand what I'm implying is that you might not actually need it :)
29.
by nasretdinov 2mo ago
Sorry can you please clarify what you mean by having two databases? You can share the same SQLite between applications if you really want
30.
by nasretdinov 2mo ago
Well if you already have Postgres then yes, sounds fine. I don't really agree that SQLite needs tons of tweaking -- setting journal_mode to WAL/WAL2 is the only real thing worth doing, everything else I would consider optional. Ve

More ›