vrotaru

8 ms·

1.
by vrotaru 6d ago
This has strong vibes of "Do this and you will get rid of back pain" followed by the video of some crazy acrobatic stunt. Congrats, BTW.
2.
by vrotaru 11mo ago
Here is my experience. Claude did generated a rather good template for what I needed. It did not compile at first but I copy-pasted the errors and it fixed them. Not all was good, though. It used literal bullets instead of `-` required for
3.
by vrotaru 1y ago
Sorry for harping on it, but I think this clearly reflects the difference between 2 approaches to storing knowledge, lossy but humongous, and lossless but limited. LLMs - Lossy highly compressed knowledge which when prompted "hallucina
4.
by vrotaru 1y ago
There is a podman-compose which works almost as drop-in replacement. Almost because most common commands work, but I have not check all. And almost, because for some docker-compose.yaml which you downloaded/LLM generated you may need t
5.
by vrotaru 1y ago
That is a good questions and I guess we have good progress since Plato whose definition was - A man is a featherless biped. But I think we still do not know.
6.
by vrotaru 1y ago
To some degree *all* LLM's answers are made up facts. For stuff that is abundantly present in training data those are almost always correct. For topics which are not common knowledge (allow for a great variability) you should always ch
7.
by vrotaru 1y ago
Well, not exactly convince. I was curious what will happen. If you are curious it was a question about the behavior of Kafka producer interceptors when an exception is thrown. But I agree that it is hard to resist the temptation to treat LL
8.
by vrotaru 1y ago
You should always check. I've seen LLM's being wrong (and obstinate) on topics which are one step separated from common knowledge. I had to post the source code to win the dispute, so to speak.
9.
by vrotaru 1y ago
So what is your pick? * AI is the next electric screwdriver * AI is THE steam engine. My pick is that the AI is not THE steam engine.
10.
by vrotaru 1y ago
> Oberon also doesn't seem to be actively developed anymore That's pretty much it, for maybe 10+ years now. There was a successor project BlueBottle with some promise, but it did not deliver. Later it was renamed to A2. Surpris
11.
by vrotaru 2y ago
It happens. It shows you the right suggestion, and if you keep typing it assumes that you meant something else and displays other suggestion. Good for slow typers, not so much for quick ones.
12.
by vrotaru 2y ago
Maybe web.skype.com will be better? Just a guess. Anyway, that's how I use Skype when I still have to use it. Which is about once a month.
13.
by vrotaru 2y ago
The are LLVM Caleidoscope (toy compiler) in both Haskell and OCaml https://github.com/sdiehl/kaleidoscope https://github.com/arbipher/llvm-ocaml-tutorial The Haskell one is a nice one. Can say not
14.
by vrotaru 2y ago
I guess Modula-3 was doing it as well. Records were structurally typed. But you can "braid"(?) a record and that will make it nominal type.
15.
by vrotaru 2y ago
You know what else is self-cleaning? /dev/shm The advantage being that it does not even touch the disk.
16.
by vrotaru 2y ago
Just an example. Should teachers be judged on how a pleasant life they live, or how good they teach?
17.
by vrotaru 2y ago
Stop optimizing for consumers, start optimizing for producers. Maybe, you want to rethink that.
18.
by vrotaru 2y ago
lsattr - for reading attributes chattr - for setting them You need the `i` attribute. But this is filesystem dependent. Anyway protecting the `sudo` binary from package managers is a so-so idea.
19.
by vrotaru 2y ago
So, in order to write a new browser you first have to write (as a training exercise) a new OS. Not the fastest way, but it seems to work. Best wishes to Andreas.
20.
by vrotaru 2y ago
Guess so. Unfamiliar with Zig. The point is that not a "all or nothing" strategy for a compilation unit. Debugger writers may not be happy, but maybe lldb supports all conventions supported by llvm.
21.
by vrotaru 2y ago
There was an interesting aproach to this, in an experimental language some time ago fn f1 (x, y) #-> // Use C calling conventions fn f2 (x, y) -> // use fast calling conventions The first one was mostly
22.
Writing a Fast Compiler(tibleiz.net)
3 points by vrotaru 3y ago|0 comments
23.
by vrotaru 3y ago
Well, I guess, that are islands of superconductivity and normal conductivity in the same sample. This gives a low resistance and diamagnetism which is used as proxy to real superconductivity. I may be wrong though.
24.
by vrotaru 3y ago
That's just a sequence of commands echo s .. # sync echo u .. # unmount echo b .. # reboot Just a guess though
25.
by vrotaru 3y ago
My beef is mostly with GTK3 and how it was introduced. GTK4 seems to be better and at least it can be fast
26.
by vrotaru 3y ago
There was no real reason to rush the transition to GTK3, but it was done anyway. GTK3 with its half-assed support of CSS for theming is just just bad, and slow (especially on Macs) And they continued to change GTK3 API after 3.0, which did
27.
by vrotaru 3y ago
Linux desktop will probably have more applications if there would have been less GTK versions.
28.
by vrotaru 4y ago
Probably, but this is not enough. You also need to to have low expectations.
29.
by vrotaru 4y ago
The web based reader will refuse to display some books, unfortunately. In my case this was the sort of book than can be only realistically read on a big screen tablet, not on a Kindle. Well, I've shrugged and downloaded the pdf from li
30.
by vrotaru 4y ago
`fst` and `snd` possess a symmetry which `first` / `second` lack Personally I've got used to them like in no time

More ›