ignaloidas

Assuming this is before taxes, no, that's not much. It takes about 1.5x-2x of what a worker gets for a company to pay them salary. I'm not familiar with French taxes, but the resulting salary is bellow what I would expect him to get for sure.

I do think that one of the prerequisites of (firm/soft)ware being good is being open source. For hardware to be good, I do believe it has to be well documented.

If we go by those two requirements, we can see how it works. We can fix things ourselves. And most importantly, anyone can create their own good firmware, without the need for the system to be designed in a holistic way.

Good firmware tells no lies. But it doesn't have to be built with a specific OS in mind to be good - on the contrary, I believe that building firmware with specific OS in mind is what got us into this whole bad firmware mess.

And yet, holistic systems can lie. They can lie horribly about their state, and you'd be none the wiser. Being "holistic", created with the intention of the whole, does not mean that the system cannot lie. If the whole is created with the intention of lying to you, than it will.

We don't need holistic systems. We need good systems. A system doesn't need to be holistic to be good, and a system doesn't need to be good to be holistic.

Not really. The list of firmware is lengthy, and most of it is loaded by the bootloader. Though some is indeed loaded by the OS.

https://github.com/AsahiLinux/docs/wiki/Introduction-to-Appl...

> This is the "Microsoft refuses to support anything" model.

It's rather "Everyone wants to boot Windows, and Microsoft can't be bothered to deal with everyone" model.

IBM Z systems are arguably the most holistic systems currently available, everything down to the silicon is designed in a coherent way. And yet, it is all incredibly proprietary.

Holistic systems don't prevent vendors from going mad with power. Competition and pressure to document their products does.

For what it's worth, a holistic system only allows the user to bring their own code only above some layer. For Unix systems of ye olden days, that would be your C source code that you compile. For Chrome OS, that's gonna be websites and extensions. For Oxide, it seems like that is going to be VM images.

But it's important to note that these days, there will always be somebody who wants to bring their code in at a lower level. And the immediate reaction of all vendors is "But why would you want to do that?". Why would you want to bring your own Unix flavor to our hardware? Why would you want to run Linux executables on Chrome OS? Why would you want to run a different hypervisor on Oxide racks?

Those people will exist. And layers like BIOS and UEFI allow system vendors to say "Eh, sure, we don't think that what you're doing is wise, but whatever, here's a standard way we'll allow you to use". Holistic systems don't have these standards. They are only usable as their creators intended. And not everyone will agree with their creators intentions. But the work required to refit them to fit another purpose, which the hardware is very fit to do, but the software fights against, is usually too high, and you'll be better off using something that is worse, but left you an avenue to customize it for your purpose easily.

My main takeaway from this talk, is that we need some standards for phase-based booting, as there is some very cool improvements that could be done with it. But I see no need for holistic systems as described in that talk, I just see a need for better, more transparent systems. And a system doesn't have to be holistic to be transparent, or good.

> You shouldn't ever be citing sources who only claim to be communicating the work of others

With the exception of secondary research, like systematic reviews. Conclusions are good to have.

It is one of the most useful airports in the world nonetheless. https://www.youtube.com/watch?v=5-QejUTDCWw

Worth noting that GN measured the power before the VRMs, while the limit is applied after the VRMs. Assuming a 90% efficiency, what GN measured would be 225.7W at the socket. Close, but still not quite.

For what it's worth, it's still way cheaper than true SRAM. And the architecture suggested is still way closer to unmanaged DRAM than to PSRAM

> What are the chances that it will charge my MacBook Pro 16 inch that does support “standard” USB C?

Most likely yes, unless it's a non-compliant cable in the first place, and possibly at a reduced speed (60W max).

>Will that “standard” USB C cable that comes with my Beats Flex headphones charge my iPhone 12 Pro Max? My Anker battery?

Ignoring that iPhones don't have USB C, yes to both at the fastest charge rate available.

Only times where you have to worry about a cable with USB-C when charging is if charging power exceeds 60W or the cable is optical. Above 60W you need marked cables, some go up to 100W, and some (will, not seen in the wild yet) go up to 240W. There are plans to deprecate the 100W tier as well.

I think just making so that for the next year a set % of revenues that are associated with the product in question get fined would be fine.

EU publishes tons of written material, and basically all of it has to be translated. Costs for translating the proceedings are very likely less than 1% of total costs for translation.

They have given zero evidence. They haven't refuted, merely disputed.

It's yuu.choose[1]

[1] https://www.ebay.com/usr/yuu.choose

FWIW the platform must respond to DMCA requests, by law, without it's own saying in the matter. They only can check if the request satisfies the minimum requirements of DMCA. Punishment for the enforcer wouldn't fly.

You can always do a DMCA counternotice. Then the onus is onto the one who sent the notice in the first place to gather evidence and take you to court. In theory, there's fines for false notices if they can't prove anything.

Of course, you better be sure that you are in the right if you're gonna do that though.

My dad has been ordering green tea from a particular seller for maybe 10 years now, in part because they include a lovely little handwritten note for each order. It is absolutely comparable.

It slightly changes frequency randomly on every zero crossing of the input frequency, so 100Hz FSK modulation effectively. It is enough to slow down your bluetooth and wifi when the door is closed and the radiated power is fully legal (<0.1W IIRC), so the effect should be amplified a lot when the door is open. Long distance flight is already getting close to the limits of what signal integrity you can get, so even a few miliwatts at the drone might be enough to disable the communications with it.

I too would really like to know, and try it too, but getting permission for 800W transmission would be a pain.

Lazer? Sure, if you can aim it that well. Highly targeted radio? A bit doubtful, at least not without increased transmission power.

For what it's worth, this attack can be sidestepped fairly easily just by not using open frequencies, to which microwave ovens are usually tuned(for regulatory reasons). This is only useful against drones that are available to buy for individuals, as they are forced to use the same open frequencies. Anything military grade is likely using other frequencies, and you can't use cheap microwave ovens to generate ridiculous amounts of them.

A microwave hacked to work with the doors open will disable most of the commercially available drones. 800W of transmission at 2.4 GHz is tough to speak through.

Of course, this way is quite dangerous, and violates radio frequency regulations, but if it's a war, who cares.

You need to improve your micro-architecture to hit those speeds as well. You can't get there without deep pipelines.

What is something that you wanted to fit into the book but weren't able to?

Defamation is a hard thing to prove. For one, the one who publishes must know that something isn't true. Newspapers have zero risk of that when they quote somebody's statement.

I wouldn't be surprised if the fact that argon is heavier caused the failure. Argon gets into the drives, assisted by the larger pressure outside of the drive at the time of the release, and it wouldn't come out within a reasonable time even when the pressure came back to normal, since there's not much capability for venting gasses out of the hard drive. And since argon is significantly heavier, it causes larger air drag on the mechanical parts of the drive, eventually making the head driving coils too weak to operate at the needed speeds.

Considering that the data rate of the configuration specified at the scope is ~14Tbps, not really. Even the data rate that the scope is interpolating from is ~745Gbps, while 400Gbps Ethernet is still fairly rare and mostly limited to backbones.

Seems like it is focused so much on how fast it responds to queries that it forgot that it is extremely important on how good it's responses are. Lucene's main benefit is the huge library of token filters to improve the understanding of the text in index. Manticore only has an ability to plug your own single filter in. And while that doesn't make it any less possible to make search results good, it's definitely a lot harder to do. Producing good results is the main goal of search, speed is only necessary for it to not be too slow. A well working search will offset any extra infrastructure that it might need to run fast.

It's not just a custom dictionary. Stop words are usually excluded for a reason, you need to understand the nature of the query, and when to exclude what looks like stop words from being pruned. It's not really a job for a snowball stemmer, as you do need to operate over multiple tokens to gather context.

If they'd manage to convince other ISP's to drop any BGP sessions with Russia, it probably means a separation of Russian internet from the world, and that would probably make more harm than good in the bigger picture.