3,349 karma · joined November 1, 2014
As to your "not a complex system" remark, when a system is built for 60 years, piling up new rules to implement new legislation and needs over time, you tend to end up with a tangled mess of services all interdependent that are very difficult to replace piece-wise with a new shiny architecturally pure one. This is closer to a distributed monolith than a microservices architecture. In my experience you can't rebuild such a thing "in 3 months". People who believe that are those that don't realize the complexity and the extraordinary amount of specifics, special cases, that are baked into the system, and any attempt to just rebuild from scratch in a few months hits that wall and ends up taking years.
I played a bit however after 2 minutes or so some enemy ships get stuck going in a square pattern across the edge of the screen where they are impossible to hit and the game stops progressing. I refreshed once and got the same issue after a few minutes (Firefox).
https://www.clarionsolicitors.com/articles/reselling-used-so...
It might be difficult in practice though, with platforms like Steam providing no means to actually resell a game to someone else.
String? id(String! arg) { return arg; }
String s = null;
Object! o1 = s; // NPE
Object o2 = id(s); // NPE
Object o3 = (String!) s; // NPE
Surely at least the two first cases should yield a compiler error. The last case you're explicit so it's borderline but I'd rather see something like : String s = ...
if (s != null) {
# Here the compiler knows that the effective type is String!
String! ss = s; # OK
}
Like this no possibility of error.Mathematically, if votes are random, with 10,058,774 voters you have 10,058,774^2 ~= 1e14 possibilities of different results for 3 candidates (Maduro, Gonzalez and "Other"). On the other hand, the number of possible results that land exactly on the closest integer to be a round 0.1 percentage point is 1000^2 = 1e6. So the probability of the actual votes landing on a round 0.1 percentage point purely by chance is 1000^2/10,058,774^2 ~= 1 in 100 million.
Of course the votes are not entirely random, but they have a random element, so it gives a rough idea of the reality.
So `zig cc` will have to go as well ? I was under the impression Zig as a drop-in C (cross-)compiler was one of its main selling points.
> This is not the first controversial change I have made to the Zig project, and it won't be the last. I have a vision, and I know how to execute it. People are often surprised by what Zig has accomplished, and they wonder why other projects have not done what Zig does. Well, you are seeing the magic right now. I ignore the peanut gallery and do what I know is right, while taking care of my users' needs at the same time. If you don't understand now, you will understand once this plan unfolds. By that time it will seem obvious in hindsight.
He's probably brillant and all but this ... feels like hubris.
I prefer the more classic treemap view, my personal favorite being the classic version of SpaceMonger but it's Windows only and very slow.
Evolutionary traits usually come with a tradeoff, and if a predator evolved to be able to catch sloths more easily it might make them less able to catch the juiciest prey, so overall it might be more worthwhile to focus on the other animals and leave sloths off the table, so to speak.
It's pretty much mandatory if you intend to serve multiple domains with different certificates from the same host/proxy, which seems like a very very common use case, and there is no alternative to this right now.
You mean, copies of ourselves. Our current selves would remain right where they were before, and wither and die, while our copies would lead on merry and adventurous if disembodied lives. Provided they practice good backup hygiene of course. I find that quite depressing to think about.
I don't think that argument has a lot of weight. By the same logic a zip file of a book doesn't resemble the original work if you look at the raw bytes but you can extract it and get it back. It would be hard to argue that the copyright violation happens only when you extract the zip, and not, say, if you distribute the archive.