yxhuvud

6 ms·

121.
by yxhuvud 8mo ago
Ubuntu's perfectly fine if you avoid LTS versions.
122.
by yxhuvud 8mo ago
Essentially all the most important functions to interact with rings during runtime is static inline. The prep_* methods for sqes are so simple they are not problematic to reimplement, but all the other interactions necessary - submit, advan
123.
by yxhuvud 8mo ago
> likely because they do not want tons of slightly different functions No. They do it because it avoids the overhead of dynamic dispatch. Nothing else. So when I've seen these in reality in real library interfaces they have not been
124.
by yxhuvud 8mo ago
If the language provides nice features to libraries for C language users by sabotaging the library for use outside the language, then this is absolutely a problem on the language side.
125.
by yxhuvud 8mo ago
That is not an option - it may be layers on layers of them and force you to recreate half the library and force you to have to redo subsequent version updates in your code. Then a shim is the preferred solution. But anything that requires a
126.
by yxhuvud 8mo ago
> "static inline" neatly avoids needing to think about it. Sure, except when you do FFI bindings. Then those functions just don't exist and you get a linking error.
127.
by yxhuvud 8mo ago
What makes you think functions defined as `static inline` is not in the .h? These are very much not private functions. Example: https://github.com/axboe/liburing/blob/master/src/include/li...
128.
by yxhuvud 8mo ago
`static inline` is definitely not private. See https://github.com/axboe/liburing/blob/master/src/include/li... , for a practical example.
129.
by yxhuvud 8mo ago
Modern libraries consistently use `static inline`, to avoid the overhead of dynamic dispatch. Just take a look at liburing, and the client libraries for pipewire and wayland. All of them have `static inline` all over the place, for methods
130.
by yxhuvud 8mo ago
Doesn't help. The point is to avoid having to invoke a C compiler when working in X language. But it would certainly be nice if the distros enabled that.
131.
by yxhuvud 8mo ago
"static inline", the best way of getting people doing bindings in other languages to dislike your library (macros are just as bad, FWIW). I really wish someone on the C language/compiler/linker level took a real look at
132.
by yxhuvud 9mo ago
3 has a really nice feel when you manage to get the early timing attacks off against the neighbours, but the later half of the game is too solved - the game ends with infantry + artillery stacks being the only units you need, and with the 3
133.
by yxhuvud 9mo ago
Google is certainly looking better than stack overflow.
134.
by yxhuvud 9mo ago
Generally speaking I wouldn't support blocking their IP, but rather I'd block the ability of European companies to pay for ads on X unless they fixed their shit and paid any damages. That might of course lead X to block Europe vis
135.
by yxhuvud 9mo ago
Yes, if you don't follow EU laws prepare to not do business in Europe. Likewise, if you don't follow US laws I'd advise against trying to do business in USA.
136.
by yxhuvud 9mo ago
Given your username, do you have the same reaction to bundler?
137.
by yxhuvud 9mo ago
Was the link changed? Right now it points to the github page, and it doesn't really say why anyone would care about it.
138.
by yxhuvud 9mo ago
No, the system package managers is part of the fragmentation problem, as every app would have to support n different package managers. That is a nonstarter. Getting away from that is the main feature that drive adoption of language specific
139.
by yxhuvud 9mo ago
It is easy to see why the system package managers in that are in use are not sufficient. The distro packages are too bureaucratic and too opinionated about all the wrong things. I don't disagree that it would be nice if there was more
140.
by yxhuvud 9mo ago
Afaik bankid will actually run as long as you can install play store (IE the device don't need Google certificate), which isn't great but a little bit better than what it could have been.
141.
by yxhuvud 9mo ago
Honestly, that doesn't sound too bad if you have decent bandwidth.
142.
by yxhuvud 9mo ago
> phones are wireless, which is too slow to test things Eh, wifi7 go up to 1.7gbit or something like that. Should be plenty assuming the hardware supports it. Which is a pretty big assumption.
143.
by yxhuvud 9mo ago
The author also suggests simulating flood walls. That is also a very .. local suggestion.
144.
by yxhuvud 9mo ago
Depends on your jurisdiction I suppose. If you are in EU it's a question if you have PII or not - if you are a SaaS or not is totally irrelevant.
145.
by yxhuvud 9mo ago
Deleting data is also a very easy way to not get GDPR compliance issues. Data is a cost and a risk, and should be minimised to what is actually relevant. Storage is the least part of the cost.
146.
by yxhuvud 9mo ago
I disagree. I find accepting extra random bytes in places to be just as harmful. I prefer APIs that push back and tell me what I did wrong when I mess up.
147.
by yxhuvud 9mo ago
It is a reference to Torvalds making an appearance on the LTT youtube channel, intentionally getting the LTT meaning wrong.
148.
by yxhuvud 9mo ago
If nothing else, the history recap is absolutely brilliant.
149.
by yxhuvud 9mo ago
No, but both demand and space to grow stuff are very much limitations in that space. They are not even close to being that for programming.
150.
by yxhuvud 9mo ago
Right, what is needed is something trie-like, with the root being the most fine-grained call.

More ›