Git does allow multiple contributors on each commit. Of course people can lie, but it's a matter of policy in the end. Make it a crime to not add all contributors to a diff.
Not Brazillian, and I didn't know about the 2-turn system, but I definitely became a fan. It's simple to understand and to implement. Ranked voting is too complex to implement and for everyone to understand. Run-off lets you vote for you preferred party first, and for the realistic contender second. Sadly, almost no one did that in Brazil - >90% voted for the finalists in the first turn.
I really strongly believe in approval/disapproval with a runoff.
You can vote for or against as many candidates as you want. Take the top 2 score getters and do a runoff. This means in the first round you can have as many candidates as you want. Those with no name recognition get no support. Also it prevents the situation so many find themselves in where both candidates are deeply unpopular but we feel we have no other choices. If the most well known candidates are deeply divisive then they won't get through.
The runoff gives people time to research the 2 candidates.
LLMs still struggle with deciding what parts of a document or concept are more important. So documentation often trashes wildly around specificity, like "In this driving game the car moves forward and the glove compartment can be used to save the game". I think it's a big part of why reading unredacted and unedited LLM slop feel so much more tiring than reading human-written text.
It's not. Brazil has a good elections system with the 2 turns. But still on the first turn more than 90% voted for these 2 parties. The only party on "the left" is a Unionist president and a right wing vice president. There's no serious politics on the left, and people vote like they are cheering for football teams. Voting for Lula was the evident lesser evil (as in, proven track record, and no concrete evidence of corruption like his opponent), but half the country disagrees...
Really? I couldn't tell. In the last debate alone, the main TV network conceded to Flavio's request to not use live fact checking systems on TV. Turns out 75% of his statements were not true. He's facing no consequences for that, nor is the network for hosting and broadcasting his fake facts.
Fact checking systems often lack context and self-correction mechanisms, suffer from selection bias and numerous other problems that doesn't elevate them above other forms of media. Especially media that doesn't claim to be an authoritative source.
You probably could have constructed a fact checker that would have said that 75% is true, the completely other way around. For most truths or facts that is entirely possible without any contradiction if you change perspective. This basic media literacy isn't optional and it cannot be outsourced.
That's true, and indeed the fact checking they posted online sometimes lacked nuance. But they actually tried to tackle that exact problem by labeling several statements as "not quite right", and all facts had a description, it was not black and white. I also understand that in live TV that nuance would be lost. But some statements were 100% straight out lies. Those could be even flagged by the debate moderator.
Such laws always work better for one side than the other, it's always selective about which facts get checked and which false news get suppressed. I don't know about how trusted that media network is in Brazil, but from all we've seen from other countries, authoritative fact checking from old information monopolies just fan the flames. It wouldn't surprise me if conceding to the request was the best they could do in the situation.
CSS isn't useless eyecandy. Everything we currently do in javascript that can be offloaded to CSS is a performance gain. Sadly datepickers are out of scope for CSS. Expecting this group to solve datepickers is the same as expecting them to work on solving world hunger (and almost as difficult :)
Off topic: But contrary to popular belief world hunger is technically solved (as in solved on a technical level). We do produce enough food so nobody needs to be hungry, and we know how to distribute that food to anyone who needs it (outside of a handful of warzones, but even there the right organizations have a good plan that will probably work if given the funding and the political backing).
World hunger is now fully a political problem and needs to be solved politically. It may sound hard, but in this case it is only a matter of money. The right organizations just need more funding, again that might sound hard, how do you pick the right one, but in this case the right organization is almost always the UN World Food Programme. They need exactly $13B to solve world hunger. And that is not a lot of money.
well, no, the WFP's current yearly budget is 13B, which is nowhere near enough to solve world hunger, considering world hunger still exists. They actually say they need 93B/yr until at least 2030 to solve it.
I stand corrected. Regardless it is still an easy thing to solve. 93B/y is still not a lot of money for solving world hunger. Well worth it if you ask me.
Perhaps WHATWG just needs more money and then they will solve the date-picker.
Jokes aside, I never has had any major problem with ``. Yes there are some annoyances when translating between local time and an absolute timezone aware timestamp. Yes it is annoying that `.valueAsDate()` doesn’t work out of the box. But those are very easy to overcome with a three line utility function.
I've been away from CSS for a few years and this looks alien to me. I don't know any of this syntax except for the div declaration, and I used to think I was good at CSS with less and sass. I don't want to deal with molecules, or atoms, this is just too much.
reply