100% this. When I reached the end of that page I felt pranked because the obvious question was never answered. How are these cases resolved? Is it possible to fix some inputs and only update others? What if I sometimes want to change input A, and other times I want to update input B? All this should be explained as early as possible.
You can do it and it is explained, actually. Use # as a prefix to indicate a constant, e.g.: #50 will be a constant and not a variable.
In the future I'd like to support more user input constraints, in particular domain constraints for variables. So you could tell the solver that this cell must remain in some interval, and it would respect that interval instead of assigning any real value.
Yes. Hyprland has burnt bridges with many of the classic/pre-existing Linux dev communities. Amongst other things, the main developer was banned from freedesktop.
But they have a very, very large user base, which means lots of contributors - especially young, first-time-FOSS/Linux contributors. In a way, Hyprland has partially done what Linus was hoping to do by adding Rust to the kernel (attract the next-generation of young developers). And they have an active BDFL - no "led by committee" issues.
i don’t care, hyprland is great software and much better than whatever the ‘non-toxic as labeled by drew devault’ communities have come up with for WMs
Drew Devault is a left wing nutjob. He's done nothing but cause drama and attack people for years now.
Vaxry is an immature ~20 year old Polish dude. That means a bit of angst, Eastern European humour, more conservative opinions than most US tech workers.
Yeah, Vaxry is considered abrasive to some of the ultra-privileged leftwing US tech sphere. Most people don't care, just as people don't care about DD's views when using Sway, Miguel de Icaza's views when using Gnome, etc...
The linux developer community has quite a diverse set of opinions so it would be unfair to say that they despise hyprland. At most it's just a small number of developers who hold such an extreme position.
I don't think despised is correct. Drew made an argument for more mature and responsible behavior and leadership but some people just want to write code and not manage a community. I think that can be a lot to expect from some young programer thrown into the public eye, Hyprland is a well regarded implementation amongst tiling wms but the category always has and in my opinion always will have limited appeal for good reason.
Your link itself admits the 0.05 makes it a different formula. Both Y and L* go to zero for hard black which is a very common color (the most common for me) and would be infinite with black in there. I disagree this is all "not real".
The 2x2 table in that contrast experiments link I sent enumerates some differences along the edge cases { even with just |diff|s. }. Just empirically if you change that 0.05 to 0.02 or 0.10 things change "a lot" in terms of all the edge cases. You can try fiddling with running that Python script yourself and see.
Also, I believe the project of an actual "contrast measurement" - not merely threshold checking - is a worthy goal. I think it would be good to be able to say how bad, and for that the specific monotonic transformation absolutely matters, and again, I expect the color space designer people have opinions on this very worth listening to. I think they are targeting differences in the numbers being the most meaningful thing.
All that said, I did like your George Box quote. :-) I just don't think dismissing the problem is a great solution here. I'm not sure there is a great solution. But you & anyone are always free to find any problem uninteresting. I mean, you could also find all the color space distinctions of TFA similarly "no real difference".
> Hundreds of thousands of cars physically move along roads and have to break, accelerate and change lanes in traffic to safely get to their destination. Future work: Other modes of transport (pedestrians, light & heavy rail, airports, etc.). Multi-modal pathfinding (combining walking, public transport, taxis and driving to reach destinations).
Eh. What they really show is a tech demo. It has simple houses and stores instead of a single apartment building with both in them because it needs to test the path finding and traffic simulation. It also needs to test the agent simulation, where each agent goes somewhere that satisfies a need. If everything were in a single building then there would be no way to find bugs in those systems.
I hated all the heavy traffic in SimCity, so I created the Church of PacMania, which worships PacBot: a gargantuan yellow road following car devouring PacMan.
The Church of PacMania generates a mobile traffic-seeking PacBot agent, plus a whole lot of traffic, the point of which is to attract the PacBot to the church, to sacrificially feed its followers to god, in contrast to the Catholic tradition of worshipers devouring the flesh and blood their god.
Kind of like an automotive version of PKD's "Rautavaara’s Case":
DonHopkins on April 12, 2020 | parent | context | favorite | on: Enemy AI: chasing a player without Navigation2D or...
In Micropolis, the open source version of SimCity, I scripted a "PacBot" agent in Python: a giant PacMan who follows the roads around, looking for traffic to eat, always turning in the direction of the most traffic.
The PacBot only has a limited local view down the roads a few cells, and can't see around corners.
Even though they're extremely simple and stupid and short-sighted, they still have interesting emergent behavior when multiple PacBots are competing for the same traffic, like how PacBot will give up and turn around when its competitors eat the cars it was wok-a-wok-a-ing towards.
There is a good example of lots of competing PacBots around 0:55:
>Now you have some good, uuh, there's some traffic here. There's this thing called a PacBot. It's this PacMan that follows the road around looking for traffic. And then he eats it. So that's good for your city. And you can have a lot of different PacMans on the thing, and you know, just editing the road gives the PacMan somewhere to go. So their score is how many cars they've eaten. So it's an "agent", and it woks all around, and he follows roads. And you can put a lot of them on the map to keep the traffic low.
MicropolisRobot.scanRoads looks down the road in a given direction for a given distance, and counts the number of cars (in the traffic density layer), attenuated by distance (further away cars don't count as much).
As it turns out, the PacBot is actually the God of the Church of PacMania (each Polytheistic PacMania Church spawns up to four PacBot God Agents, if it's connected to a road), and the church zone itself generates a LOT of traffic, in the hopes of attracting the PacBots. The emergent behavior is that followers of the Church of PacMania happily drive back and forth between church, home, work, and shopping, again and again, in the hopes of sacrificing themselves to their God, PacBot. And the PacBot Gods hang out around the Church of PacMania, eating their followers, and raising their scores -- everybody's happy!
reply