cztomsik

13 ms·

151.
by cztomsik 4y ago
> This just reinforces my feeling that a major driver behind VSCode's popularity is that people just don't know better I am very happy that VSCode is mostly just editor.
152.
by cztomsik 4y ago
I think the most important thing is "wanting to be faster/10x" (from the author's personal blog BTW) https://www.scattered-thoughts.net/writing/moving-faster/ Also, it's good if language d
153.
by cztomsik 4y ago
rust has absolutely nothing to do with prevention of side-channel attacks
154.
by cztomsik 4y ago
only SMIs are passed by value (because they are actually encoded in the reference data type) It might be a bit outdated but here's more https://github.com/thlorenz/v8-perf Also the https://v8.dev/
155.
by cztomsik 4y ago
In the meantime I was trying to install new fedora kde plasma and it got frozen during the install. You were lucky. I was not.
156.
Automatic Node.js Bindings for Zig(github.com)
2 points by cztomsik 4y ago|0 comments
157.
by cztomsik 4y ago
you are right about cxx, I made this comment with C FFI in mind. and for that, Zig couldn't have better integration. AFAIK there is no simple way to interface with C++ from Zig, you either have C headers or you write a bit of C++ to ex
158.
by cztomsik 4y ago
I admit it's a long time since I've been using neon so things might have changed but at the time I had a feeling that the whole thing is very fragile and not really safer than if I was using pointers directly. Especially, if you c
159.
by cztomsik 4y ago
I understand why is that needed. I am saying that prototyping (for me) is much easier in Zig. Some people like to define all the types (and traits) first, if it works for them then it's ok. I like to get feedback on something working a
160.
by cztomsik 4y ago
for me, - easy interfacing to C libs (glfw) - very easy and readable metaprogramming (compile time inline for over all enum variants, duck-typed and strong-typed anytype at the same time, @compileError for advanced compile checks so you can
161.
by cztomsik 4y ago
had the same problem, if you're just prototyping, it's easy to silence that with _ = someVar you get used to it after some time - much better than for example rust, where you have to figure out all the lifetimes, muts and generic
162.
by cztomsik 4y ago
for native addons for GC'd languages you probably don't want to introduce another GC, rust is not well-suited for interfacing with FFI, C++ is a bit heavyweight but okish I guess and C is totally unsafe, Zig is just right.
163.
by cztomsik 4y ago
try to do ReadOnly<T> yourself, and then put Cell into it, or RwLock, or Mutex, or Atomic, or crossbeam channel, ... it LOOKS like it's possible but it can be broken easily. again, because rust is not really about (i)mutability,
164.
by cztomsik 4y ago
wrong, rust is about exclusive ptr access, nothing more. you cannot do ReadOnly<T> in rust.
165.
by cztomsik 4y ago
not actually disagreeing, just my opinion: .env would be nice but I personally do not miss .yaml/.toml at all so there's likely some subjectivity in these feature-requests and keeping it in user-space has a value too (simple, rock
166.
by cztomsik 4y ago
It is very good comparison, I've recently switched to Zig from rust so I can answer some questions if you're curious. Regarding comptime, it's not just that you basically have proc-macros available everywhere and you just nee
167.
by cztomsik 4y ago
after 5ys of (hobby but frequent) rust I'm pretty confident most people cannot tell what their code will compile to and what its runtime profile is going to be (aka you can't reason about performance -> so there is a lot of mag
168.
by cztomsik 4y ago
then take my upvote, I agree 100%, I'm saying exactly this to many people and they just roll their eyes (to be fair I don't use PHP anymore but I certainly don't share the despect which others have) fun thing I also wanted to
169.
by cztomsik 4y ago
you don't need node.js/V8 for plugins there is quickjs and some others, some of them are rust-based and all of them can run in wasm host EDIT: to be honest, I clearly see where you are going with this and I agree :)
170.
by cztomsik 5y ago
Oh, sorry for my misunderstanding then, I thought you were OP. 1. that's... not a problem for me 2. fair but you have tests & pipelines, so not a problem... for me :) 3. this is kind of fair, yeah 4. I absolutely agree about unnece
171.
by cztomsik 5y ago
Yes but unfortunately I don't see how it invalidates my point. a) you either replace DIC with custom hard-wired functions (composed using any-order custom helpers) and then it's still hard-wired at one place b) you reinvent DI wit
172.
by cztomsik 5y ago
except the container can do whatever mumbo-jumbo you may want/need, like declarative transactions, declarative permission checks, logging, publishing events to external systems, etc. and then you have async constructed dependencies, fo
173.
by cztomsik 5y ago
haha, I know the book but the first one which came to my mind was this :-D http://wiki.squeak.org/squeak/64
174.
by cztomsik 5y ago
Ah, ok, having cycles is another problem, also hard, but my point was about multiple mutable references which is not a safety problem if you have GC. You only get race conditions. And I think it could/should work also with Rc<> b
175.
by cztomsik 5y ago
yeah I mean rust Rc<>, I don't have experience with lobster, does it allow mutation from multiple places or does it panic just like rust?
176.
by cztomsik 5y ago
Is that the one where you need to derive() for every struct you want to use and which is, in general, not compatible with the rest of rust ecosystem?
177.
by cztomsik 5y ago
The problem is that Rc<> is not replacement for GC, in GC language you just don't care about having multiple mutable references at all because it's mem-safe (so you don't need to panic). The only thing you can get is co
178.
by cztomsik 5y ago
I think one interesting solution is to store energy in "gravity", just pull something really heavy up and then when you need energy, let it fall and go through generator. https://gravitricity.com/
179.
by cztomsik 5y ago
I believe it was meant to be ironic comment, pointing at systemd
180.
by cztomsik 5y ago
I think currently, the only closest thing is bevy-reflect. Which is nice, but IMHO it should be in the language because nobody supports it ATM and to get there, it will take at least the same time it took for serde to get supported. https:

More ›