Re: if you are a small, text-based forum,
That's eminently sensible. It will just take a while for those things to emerge. Software could ship with it.
3462 publicly visible posts • joined 23 May 2011
I didn't down vote, but the assertion low level code has to be written in C is false. I've written the kind of code described in ASM, Forth and C++. I presume you can write it in "unsafe" Rust. So C is not the only game in town.
And how does JSON or XML get transferred to the host? Is it an "unsafe" DMA or PIO? (Yes, I've written PIO code.) Whereas port based IO just looks like a function that takes or returns a value so that is intrinsically safe.
I'd've also thought a DMA could be made to appear safe - if we trust a kernel function which does the low level stuff so the device driver just makes a DMA() call in, presumably, the same way memory-mapped IO is made appear to be safe. But I don't know enough about modern IO or Rust to be sure on either case.
"Why wouldn't we write those programs in safe Rust and just skip the writing-in-C part?"
Because you have an existing code base represent $hours work and you want to convert it rather than scratch build it.
But that's the wrong question. The right question is what does Rust bring to the party when you already have code that, as I follow it, is mathematically validated and is written to such a narrow standard that it can go through this with few alterations? You want Rustification to reveal bugs and make it less likely those bugs re-occur in the future. But that means ordinary code, which means pointer-arithmetic and type-punning and all those other "unsafe" things ordinary C will do.
The way relativity works, all FTL machines are de facto time machines. It's easy to see it the other way round: with a time machine I could travel to wherever at subluminal speeds and then travels backwards in time to make it appear I had travelled faster than light.
The faster they can get everybody using it, the less of a problem this becomes. 1) Because there are probably cross licensing opportunities - you're using company X's IP but they're using yours.
But 2) because nobody is going to let the economy collapse under an epic sue ball (and the courts couldn't cope with all the cases). So if (1) doesn't cover it, rules will be changed and a accommodation arrived at. (Think about music sharing. How many individuals were unlucky enough to got threatened, let alone prosecuted, compared to those who shared?)
But that all hinges on getting lots of people using it quickly.
"You can always get it enabled, or if it bugs you that much, you can move to another WordPress hosting company that does have it on by default."
I think the choice argument is a red herring. e.g. "If you don't like Chrome, use another browser." "If you don't like gmail.com, use another email provider." etc... These are true at the most pedantic level. But once a product becomes ginormous it gets to shape the market and set the terms of engagement. The number of people who are prepared to go to the effort of using a different product/host and put up with a degraded experience are a rounding error. (Admittedly, most of them are rounded up on El Reg.) I bet many of us carry the IE6 scars because it couldn't be ignored.
So if you are willing to say the law matters to open source (and I think it does) then you also have to concede that market forces and the network effect matter, too. So this is a battle about who gets to shape that market and be the driving force behind Wordpress. WP Engine is large enough to be a threat to Automattic. However altruistic (or otherwise) you think the participants' motives are, I think we can all acknowledge this is a dick swinging contest for the future of Wordpress.
If, like me, you're uncertain of what a hyperparameter is then the paper gives a much more straightforward definition than Wikipedia:
In a typical neural network, the hyperparameters refer to the model depth, layer type, number of nodes, activation function, strides, padding, number of filters, kernel size, and pool size.
So its the structure of the network.
You missed the historical precedent in my subject line. Enigma was cracked by the British Government and we kept quiet about it and encouraged poorer nations to use reconditioned machines.
And by doing nothing you are betting the farm on it being impossible to crack when we have quantum-proof algorithms we could start using now.
The sudden wave of LLMs should remind you of the "slowly then suddenly" rule. LLMs were nowhere near usable and then overnight they were usable enough to excite the mass market.
For quantum it's worse because if a government cracks it, they will keep it secret and use it to their advantage. So you may not find out Quantum has been successfully cracking crypto till years later.
"The drones in question were the size of a car."
You have no way to estimate it's size. Once something is above the trees there is nothing to compare it with. Worse, consistency of scaling breaks down at these distances. So, for example, your brain should tell you the moon is about the size of a football soccer ball or a dinner plate. If you see a plane in the sky (as I regularly do living under a flight path) you are relying on knowing how big that plane ought to be to understand its size. But absent an accurate measurement of it's distance, the size of these things is pure speculation; all you know is the angle it subtends.
Who'd be a CEO? You do all the hard work. Get fired. And somebody else comes along and claims all the credit for your work.
No wait, I've seen the salary. I'd put up with it. In fact, it's pretty much what happens now but for far less money. Mine's the coat with the golden parachute in the pocket, thanks.
I believe the academic name for the enshitification of a business is "Leveraged Buyout".
(The killer line in that Feb 2021 report is "But interest rates are currently extremely low, which will made Asda's debt burden affordable." They didn't bank on Liz Truss, did they?)
I don't get it. I provide a summary to an AI which turns it into a post. And an AI at the other end turns back into a summary. Can't we just send the summary? i.e. why do I get pulled up for writing in my "terse" and "detailed-focus" style in the first place? You've just shown that what I write is, actually, what you want.
"Google made $237.86 billion from its Chrome-driven advertising"
I followed the link. It said Alphabet made $237.86 billion advertising sales. I see no evidence that such revenue is directly derived from the Chrome browser. It's driven by Goolge's search page, and all the advertising brokers they own that show adverts all over the web. I can't see that their earnings would be much reduced if all that happened was Chrome was cut off.
Ad blocking enabled by default in Chrome would really impact; but no new owner is going to do that because they would almost certainly have their fingers in the ad pie and so it would hit their revenues, too. And, as you point out, Chrome is already largely open source (Chrome is Chromium plus autoupdate, crash reporting, DRM and codecs) and such a huge cost that Google shares the burden with Microsoft and others. How does factoring out those few proprietary features of Chrome hurt Google? Would Google be banned from contributing to Chromium? The whole idea left you going "What?! Why?!"
Anyway, we can all agree it's not going to happen.
I have sympathy with this. But, equally, this is being used a staging post to spew malware. That has a cost for everybody else - one which the owner is not paying and which, in total, may outweigh the costs to the owner's business.
The way we decide these problems is via the courts. If a judge can be persuaded that a device is being used to infect others and that the owners have not respond in a timely fashion, and then issues an order for the patch to be applied, then it's tough for the owner. Whatever the consequences, they had their chance. I don't know if this case meets that threshold, but we should certainly consider it.
There seems to be a lot of whining about "promises" and bad behaviour. But, however morally reprehensible and against the spirit of open source Automattic's behaviour may be, I'm not sure that their marketing is legally enforceable. I hope there's something a bit more substantial in that ~140 pages; i.e actual statues that they've broken. WP Engine are, after all, a savvy company and not a powerless consumer.
Also, I'm quite surprised at the anti-Wordpress hostility here. I don't use it, so I've no dog in the race. But what I'm reading is an open source company taking vigorous action to defend the community from a vulture. If Silver Lake had their way, they would extract all the value that's been built up by the community and leave a few volunteers manning the pumps. How often have we talked about making Amazon and the like contribute back to the community? So while it's slightly worrying that Automattic has this power. Right now, they're using it to defend the community - attacking one private equity player. If I'm forced to pick a side, it's with Automattic. (But maybe I've misread things?)