Well, you can already do extreme tinkering to the point that RPi can no longer guarantee it functioning properly :)
IIRC it's just that the bootcode.bin file is provided by Broadcom, and not the RPi foundation, so they can't open source it because they don't have the license to do so (this isn't the only proprietary blob in the default Pi distribution, but most of the other ones have open source alternatives/aren't that necessary/are open source now that they use the RP1 chip instead of broadcom peripherals).
There's similar, slightly more open arrangements, with the Pi Pico W, where they can't provide the firmware for the Wifi chip, but they can provide a library to interface with it, with the caveat that the license _only_ allows for that library to be used with the RP* family of microcontrollers [1]
Short answer for the type ordering and `fn`: because C/C++/Java tried that type of syntax and the result was an ambiguous grammar that is way too hard to parse, not to mention C's overly complicated pointer syntax.
This website is completely unreadable on an ultrawide monitor, it seems to make the font size dependent on the window's width, which makes it absolutely massive (I can maybe fit half a paragraph on the screen?), and the browser zoom does not seem to change the font size because of it...
> the browser zoom does not seem to change the font size because of it
This is one of the worst cases of this I have seen. It is literally unreadable for me. Normally I can use browser zoom to sort it out, but this beauty even defeats that workaround.
Yup, but while making the window smaller to write this I noticed I can make it a small window, about the size of my phone, to get text that is reasonable.
The site, giving UI advice, is written assuming your display is always ~7" ?
I thought that the site must be designed for mainly mobile, so I switched mobile mode on in the dev tools in firefox. However then there is some menu header text overlapping the main body.
It seems the design of this site is very much style over function.
One solution you could use to get around this weird design decision, is to use the reader mode in Firefox (I'm not sure what is the alternative for other browsers).
All they have to do is remove "p {max-width: 28rem;}" and the website becomes beautiful. The text fills the entire width of the screen, and the font scales with the screen size (though they should dial it back a bit, or have a different scaling ramp). It's like reading an actual document, and how the web should be. Bonus points, it's ridiculously "responsive" for small screen sizes.
Yes, I know they got it kinda "wrong", but they're arguably going in the right direction here. I'd give the author points for trying something out of the box, and also for "sticking it" to the monstrosity that Bootstrap started many years ago.
The font somehow re-scales if you zoom the web page, at least with mousewheel zoom on a desktop browser. Instant accessibility failure. I've also never seen this before and couldn't work out how it had been achieved?
I think for better or for worse it makes sense that this is delegated to a separate package. For me it always seemed like a weird tangential thing that Zig did that is not really related to Zig The Language, and more to Zig The Build System. It made more sense when they were depending on LLVM either way, but now that they're closer to getting rid of it, it does not make sense to keep the dependency just for something that always seemed more like a 'neat thing' than a core language feature.
I think it solves a different issues. This is aiming to solve a depth issue (e.g. a deeper coat rack would make a door hit it, as shown in the video) while a multi layer hanger seems to be more a "I don't have enough space for all the hangers" (but importantly, you have space for at least one!)
Yes, automations and UI can still be done using yaml (and I don't think they plan on dropping that - it's very useful to be able to put that on version control). It's mostly for configuring integrations that they've dropped the yaml (annoying if you're trying to set it up with NixOS or something, but the home assistant maintainers are unusually aggressive against distro packages anyway, especially for nix...)
I'd guess that if iMessage had a market share even remotely close to that of the US, it'd be a much bigger issue and would definitely qualify. Still, here it really isn't, no one actively uses it (if they do, it's probably because what they really wanted to do was send an SMS because they were unsure if the person had WhatsApp or something, and iMessage converted it)
Spotify arguably would have qualified if they had included an "online music service" category alongside "online video service" (where YouTube was designated). The fact that this was left out is interesting.
DT is primarily a telecom, so already subject to a lot of regulation about carriage and so on. Not sure it would do anything if they were included; it’s not like they’re saying (or could say) “yeah, you can’t phone people who use O2 with this phone”.
IMO the most surprising omission is Telegram (presumably due to the market cap thing). I would have thought they’d be quite keen to bring _that_ into the net.
Looks like Telegram is private (so harder for observers to accurately value) and likely still would be well under the size cap (support for the notion that the size cap is there to exclude EU companies).
Huh, I thought they were based in Europe, but they now say that is dated: "The Telegram team had to leave Russia due to local IT regulations and has tried a number of locations as its base, including Berlin, London and Singapore."
Not for the Digital Markets Act, but the German clothing company Zalando is iirc large enough to qualify under the stipulations of the Digital Services Act (which is more focused on digital moderation if I'm not mistaken, rather than anti-monopolist behavior).
Last I checked, Zalando sued the CJEU because they were unhappy with the designation.
Zalando objects that for everybody else users were counted, while for them it was visitors (a much looser association, they argue). The decision will sharpen DSA's profile, one way or the other.
No, it is shameful that US allows such huge monopolies in the first place. These should not exist at all and should be broken up before becoming so huge.
Interesting list. The only European companies I recognize are car companies; Volkswagen, Fiat Chrysler, and Mercedes-Benz. The rest are all energy or mining companies, with the exception of Schwarz Gruppe which is apparently a retail chain? It's also surprising how many of the American companies are healthcare-related, and how the relative ordering changes to favor tech and oil companies when you sort by profit instead of revenue.
This list actually surprised me. The European companies on the list fall into 3 categories: commodities (e.g. petroleum or mining), utilities, and automakers.
They are viable options. I dont know about regulated, but them not being used is their problem. IE6 was king and then phoenix unseated them, followed by firefox. So people have options, them not using the other option is their issue
Europe's definition of monopoly is one that actually makes sense, unlike the US's bafflingly stupid version. You do not need over 50% to be a monopoly.
More like, no other financial and investment markets are as liquid and stable as America’s, which attracts the world’s innovators and investors. The US should not replicate the failure and incompetence at the helm of the EU and other major bureaucracies.
You missed the point. It doesn't matter where competition comes from, this whole campaign is about loosening the grip a handful of companies ("gatekeepers") have over de facto monopolies.
In short, this would benefit smaller players everywhere.
If anything, YouTube is even more of a monopoly than Google, because while other search engines can index the same internet and show similar results, YouTube competitors don't have the creators behind them to create content for them, and the creators don't want to create content for these platforms since they don't have the users.
IIRC it's just that the bootcode.bin file is provided by Broadcom, and not the RPi foundation, so they can't open source it because they don't have the license to do so (this isn't the only proprietary blob in the default Pi distribution, but most of the other ones have open source alternatives/aren't that necessary/are open source now that they use the RP1 chip instead of broadcom peripherals).
There's similar, slightly more open arrangements, with the Pi Pico W, where they can't provide the firmware for the Wifi chip, but they can provide a library to interface with it, with the caveat that the license _only_ allows for that library to be used with the RP* family of microcontrollers [1]
[1]: https://github.com/georgerobotics/cyw43-driver/blob/faf36381...