Quekid5

43 ms·

601.
by Quekid5 6y ago
> elegant, easy-to-learn, easy-to-read language. Compared to C? Yes, obviously. Compared to languages we have now? Not so much.
602.
by Quekid5 6y ago
Did your programs in 1996 do anything close to as much as they do now? It's easy to feel a lot of nostalgia, but those truly were simpler times when we expected a lot less of our computers/programs.
603.
by Quekid5 6y ago
Basically same deal here, though using 'magit' and 'wip' instead of 'nt'. ('No text', one assumes?) Doesn't help with IDE settings and such, but that's such a niche situation that it doesn&#
604.
by Quekid5 6y ago
It's in the context menu for files/classes at least.
605.
by Quekid5 6y ago
> So even with exceptions off one pays the price either in the form of non-standard library or accepting non-optimal performance. Holy moving goalposts, batman! The "don't pay..." thing has only ever applied to runtime, th
606.
by Quekid5 6y ago
I'd appreciate some elaboration on that too. It sounds vaguely similar to SFINAE in C++, but I don't know enough about Zig's compilation model to know for sure. (I'm vaguely familar with Zig from a talk by the creator ab
607.
by Quekid5 6y ago
"A witty saying proves nothing". - Voltaire (or Einstein)
608.
by Quekid5 6y ago
True, and you can even turn data journaling on. The problem is... what is an "atomic write" from the perspective of an application? There is no POSIX interface for that. Of course making a single 'write()' syscall atomic
609.
by Quekid5 6y ago
I don't disagree, necessarily, but ACID[0] is/was quite expensive for (usually) marginal gain. These days, I'm sure it could be done a lot more efficiently (with SSDs and such), but the fact is that there's no real way t
610.
by Quekid5 6y ago
On this particular issue I find it hard to fault them for using a (perhaps overly) safe default. Summarily killing processes with a SIGKILL should really be a last resort because it can very easily corrupt data. If you have processes which
611.
by Quekid5 6y ago
> > [errno] > I can believe that there are other issues I fail to consider, but again it works for everybody else, what makes Go so special here? errno being thread-local doesn't really help all that much with a M:N threading
612.
by Quekid5 6y ago
I'm 99% certain that KDE has it's own full compositor implementation for Wayland.
613.
by Quekid5 6y ago
> "fundamentals" You're right to call this out. It means absolutely nothing. These massive hedge funds (etc.) throw around billions of dollars on a whim and suddenly they're worried about "fundamentals"? C&#
614.
by Quekid5 6y ago
> This is one of the reasons why it takes so long for projects to migrate from Java 8 to Java 9 and beyond. EDIT: Oh, just realized... it's probably a misunderstanding on my part. "Java 8 to (Java 9 and beyond)" is the int
615.
by Quekid5 6y ago
Ah, but now you're discretizing! :D ... also, it Technically depends on your throughput (something something queue theory).
616.
by Quekid5 6y ago
Oh dear god. I suppose it can be counter-intuitive, but people really need to learn about timer precision... and, more importantly, statistics (basics, at least!). I absolutely hate the 'combinatorics' part of statistics, but dist
617.
by Quekid5 6y ago
> Still think generics are static typists admitting the shortcomings of a type system, without actually doing so, though. Wait, what? Any static type person will readily say that type systems have shortcomings (though I'd probably p
618.
by Quekid5 6y ago
Hah! Touche! Weird to think that game programming is (weirdly) kind of a niche thing at this point. Compared to programming boring CRUD apps, that is. :)
619.
by Quekid5 6y ago
1) Most of (micro-)benchmarking in computing. Of course you want a tiny bit more analysis in that case. 2) Slightly more real-world: Measuring things when you only have approximate rulers, have difficult things to measure (odd surfaces, e
620.
by Quekid5 6y ago
Ah! Might be helpful to specify that up front. Even so: Interval math could be quite helpful for lots of things that ... aren't using it.
621.
by Quekid5 6y ago
What programmer never uses math? I mean, most of us aren't going use linear algebra, but still...
622.
by Quekid5 6y ago
I guess it wasn't Durable.
623.
by Quekid5 6y ago
Interesting perspective, thanks! Not sure whether I agree or disagree, actually... AFAICT Linearilazable is about the best we can expect in reality (at least for a distributed system), but as you point out: Very few people actually check th
624.
by Quekid5 6y ago
Oh, I know about them. In fact, I'm trying to introduce ZIO in my Scala-mostly company. The problem is that a stray UUID.randomUUID() can destroy any and all guarantees. (We're already using Monix.) That truly is the singular re
625.
by Quekid5 6y ago
Not OP, but if I could ask further... How much consistency can you tolerate on your reads? From the use case you mention I imagine... quite a lot, but you could risk locking yourself out of networks/systems if you get it wrong? EDIT: N
626.
by Quekid5 6y ago
As long as you're guaranteeing correctness[0], it's hard to disagree with the "simple" approach. As long as you don't over-promise or under-deliver, there's no problem, AFAICS. [0] Via mutex in your case. Have
627.
by Quekid5 6y ago
For history buffs: https://en.wikipedia.org/wiki/Hindley%E2%80%93Milner_type_sy... was invented in 1969 (and rediscovered my Milner in 1978). AFAIK, that was the basis of type inference in many of the non-mainstream la
628.
by Quekid5 6y ago
Overselling the salami? (I hope that's an actual euphemism. I love these sort of weirdling phrases.)
629.
by Quekid5 6y ago
Yup, sounds about right. That was an excellent insight from him.
630.
by Quekid5 6y ago
I may have overreacted to the title of the blog post and carried that over to the post I replied to :). That's my bad.

More ›