Epic lost on 9 counts out of 10 in the original lawsuit. The one they won is being appealed and in the process Fortnight was ordered to be reinstated in the US. I wouldn't bet that this arrangement will survive appeals.
Good point. That makes them a combined platform and payment processor. So it seems to me the logical question would be, shouldn't they just break the platform part out then? But isn't that exactly what their percentage fee amounts to? So Apple should be entitled to 30% of their (IIRC) 5%, right?
Really they ought to further split that out into "processing fee" and "platform services fee" and Apple would then be entitled to 30% of the latter.
And yet despite his alleged criminal activities Russian prosecutors have failed to present an evidence-backed case that would warrant the notice to Interpol. That is why it was cleared.
It's the second time today when I see that the higher number of LoC is served as something positive. I would put it strictly in "Ugly" category. I understand the business logic that says that as long as you can vibe code away from any problems, what's the point of even looking at the code.
> Remember, there used to be a time programmers productivity was measured in LoC per hour.
Do you remember such a time or company? I have been developing professionally since the early 1990's (and hobbyist before then), and this "truth" has been a meme even back then.
I'm sure it happened, but I'm not sure it was ever as widespread as this legend would make it sound.
But, there were decades of programmers programming before I started, so maybe it just predated even me.
I do, besides the sibling comment, there is hacker lore about these kind of issues,
> They devised a form that each engineer was required to submit every Friday, which included a field for the number of lines of code that were written that week.
IBM had such a culture back in the day, where they feted 1 kloc/day programmers. That was what Bill Gates sneered at with the "Measuring software productivity by lines of code is like measuring progress on an airplane by how much it weighs" quote.
Yes, as we all know, when evaluating which programming language to use, you should get a line count of the compiler's repo. More lines = more capabilities.
Why would I ever want a language with less capabilities?
Yes, but it's not recommended - it does not have inter-frame compression, so it is significantly less efficient than just having a regular video file and slapping 'gif' on it.
That's not strictly correct, it's rather that the current encoder does no inter-frame compression. Patches (and the frame system in general) does give tools to do some inter-frame compression (not as many as in video, but still quite expressive), just nobody stepped up to implement compression using them for animations yet.
Progressive decoding isn't a very useful video feature because you need to decode the whole frame before you decode the next frame for inter-frame coding methods anyway.
It is, however, a very useful image format feature, giving you most information from the spinner/sticker/emoji/sprite, and refinig the already playing loop as it loads. That's why animated jxl is a bad video format — it's not a video format, it is a separate kind of seemingly weird thing.
What, isn't this the cue for someone to explain that it's ironic webp is really a video format which is a bad image format, and now we have symmetry that JpegXL is a good image format which is bad video format? :-D
(I don't know if any of this is true, but it sounds funny...)
> We wouldn't tolerate secrecy in the calculations used to keep our buildings upright, and we shouldn't tolerate opacity in the software that keeps our tractors, hearing aids, ventilators, pacemakers, trains, games consoles, phones, CCTVs, door locks, and government ministries working.
Construction industry if full of privately owned technologies and closed source software, from architectural drawing board up to the last glass panel in a window.
Building are staying upright not because of openness, but because of the enforced standards for construction. Same can be applied to software orders.
Want to prevent a government office suite to be bricked remotely? Put forth requirements for autonomous work, self hosting, multiyear coverage for critical patches and ability to export the data at any moment in the format of your preference. Whoever provides this will get the contract.
This seems to me far more realistic aim than trying to enforce global legal straight jacket to be universally applied to all software and hardware products available for purchase in your country
For the major part BYD sales performance is dependent on government subsidies in the country where they sell three quarters of all the cars they produce. That is a high risk factor investors don't like.
