valenterry

9 ms·

91.
by valenterry 1y ago
Indeed, it's the opposite of what I thought. Confusing! Thanks for the clarification. So in fact, unix seconds can be longer than intuitively expected. Which also means two timestamps of e.g. UTC with different seconds can map to the s
92.
by valenterry 1y ago
Really? Now I'm confused
93.
by valenterry 1y ago
Yeah that's fair, but that's purely a UI/display problem and there is and cannot be any solution that works without context. Ultimately, if you don't like it, tell your calendar to show it differently. > It's a 4
94.
by valenterry 1y ago
But it's correct. It's "a" count. Just not the count that you might always expect. And the "second" in this definition means what people usually understand as a second, as in the duration is always the same. Th
95.
by valenterry 1y ago
That's easy though. An event of such type is about an absolute point in time, so your calendar stores it like that and then displays it in your current timezone (or whatever one you specify). When you change locations and you have yo
96.
by valenterry 1y ago
Well, what I meant is that there is some language feature missing. So either the language gets "better" in the sense that this feature is being added, or a different language is chosen, that is already "better" in that
97.
by valenterry 1y ago
Right, that makes sense. But if it's an evil bug that triggers e.g. over a year-change only, then that might not help. So I suppose theoretically also AWS can go down all together, even if less likely.
98.
by valenterry 1y ago
Exactly. Look how we are getting downvoted for the truth.
99.
by valenterry 1y ago
Happy to see I'm not alone.
100.
by valenterry 1y ago
> Go's simplifications often introduce complexities elsewhere Exactly this. Basically: have a complex compression algorithm? Yes, it's complex, but the resulting filesize (= program complexity) will be low. If you use a very ba
101.
by valenterry 1y ago
I understand your feeling. There are many magical frameworks like e.g. Spring that do these things and it's super hard to figure out what's going on. The solution is usually to have an even better language. One, where the typesy
102.
by valenterry 1y ago
How does AWS do that though? Do the re-implement all the code in every region? Because even the slightest re-use of code could trigger a synchronous (possibly delayed) downtime of all regions.
103.
by valenterry 1y ago
No, Apple should have three options Yes, No, Never ask again. Like every other software with good UX.
104.
by valenterry 1y ago
This is spot on. And it's a general misunderstanding of security in practice. Availability is often missed/ignored (but it is part of security) and attention is an important currency that needs to be treated carefully - or you a
105.
by valenterry 1y ago
Fair enough. > Since then you are allowed to write it either way Okay, my interpretation is that it doesn't really make sense within the language rules, so they changed it but allowed to use the old style to make the transition easi
106.
by valenterry 1y ago
"Du" and "du" are generally 100% equivalent. Regular casing-rules apply, e.g. in the beginning of a sentence it's "Du" but inside it's "du". "Kannst du mir helfen?". "Du kanns
107.
by valenterry 1y ago
For a single developer? What do you mean?
108.
by valenterry 1y ago
> lets say it can process a request normally in 20us. Then what if the OS/thread hangs? Or maybe a hardware issue even. Seems a bit weird to have critical path be blocked by a single mutex. That's a recipe for problems or am I
109.
by valenterry 1y ago
I personally use that style in Scala with ZIO. Because the same problem exists in basically every language. I think more and more languages capture something like that and more under the term "capabilities". In a sense, the Rust b
110.
by valenterry 1y ago
Exactly. This is basically confirming that markets are, at least temporarily and sometimes for a very long time, irrational and hence not perfectly efficient.
111.
by valenterry 1y ago
> you no longer know when code is executed - it's magic Kind of. That is what makes react a framework and not a library in my opinion. That being said, it's still learnable and managable (in pure react). > state can be manag
112.
by valenterry 1y ago
"Markets can remain irrational longer than you can remain solvent"
113.
by valenterry 1y ago
Did you, by chance, find here because I posted a link to spacetimedb? :)
114.
by valenterry 1y ago
Very interesting! Have you also thought about using an invitation system (like the one on lobste.rs - https://lobste.rs/about#invitations )? Would you mind to tell a bit more about the exact logic and algorithms you use for
115.
by valenterry 1y ago
What you are saying isn't all that wrong. But it's besides the point that I'm making. Because it's not required to use ALL (or even more than one) of the tools or things (such as an http API) that I listed.
116.
by valenterry 1y ago
I disagree. First and foremost, what if there is not "the" database? What if you have multiple places that store data? For example, a postgres for ACID stuff, something like Kafka/RabbitMQ or similar to easily communicate wit
117.
by valenterry 1y ago
> Should you start with a domain model from the get-go? Maybe, but it's risky because you may end up with domain objects that don't actually do a better job of representing the domain than whatever you have in your SQL tables.
118.
by valenterry 1y ago
This is cool. It could be generalized into arbitrary ranking (not just photos). Questions: how do you plan to deal with people that will randomly rank other's pictures to get credits quickly (or even build a script to do so)?
119.
by valenterry 1y ago
You have a point. When using MD5 (128bit) then when AWS S3 would apply this technique, it would only get a handful of collisions. Using 256bit would drive that down to a level where any collision is very unlikely. This would be worth it if
120.
by valenterry 1y ago
For small amounts of data yeah. With growing data, the chance of a collision grows more than proportional. So in the context of working on storage systems (like s3 or so) that won't work unless customers actually accept the risk of a c

More ›