> You don't adjust rates just because you want them to be lower, there's second order effects.
You can… in Turkey (Türkiye); from 2021:
> Erdogan is openly averse to high interest rates, claiming high rates cause inflation, which stands in opposition to mainstream economic theory.
> He has pressured the central bank to keep rates low to fuel borrowing and growth. Critics say the independence of the central bank has been severely damaged through political pressure.
> Erdogan’s decree on Saturday appoints Sahap Kavcioglu as the new central bank head. Kavcioglu is a banking professor and a columnist in a pro-government newspaper where he has argued for low interest rates.
> The first woman to lead the bank, Erkan began raising interest rates when she was appointed in June last year, launching a 180-degree pivot away from years of low rates under Erdogan that had sent inflation soaring and foreign investors fleeing.
Another appointee follows the Trump Orbit Character Arc. It's really pretty consistent, from Jeff Sessions to Mark Mikey and about 5 secretaries of defense.
Trump apparently believes appointees are there to do what Trump communicates he wants done, and to take the blame if those things don't work out.
BE isn’t technically dead buts it’s practically dead for almost all projects. You can static_assert byte order and then never think about BE ever again.
All of my custom network serialization formats use LE because there’s literally no reason to use BE for network byte order. It’s pure legacy cruft.
...Until you find yourself having to workaround legacy code to support some weird target that does still use BE. Speaking from experience (tbf usually lower level than anything actually networked, more like RS485 and friends).
18 years in my career and I’m still waiting for that BE target to rear its ugly head.
I’m more than happy to static_assert little endian. If any platform needs BE support then I’ll add support to the minimum amount of libraries necessary to do so. Super easy.
Here’s the thing. If you wrote BE compatible code today you probably dont even have a way to test it. So you’re adding a bunch of complexity and doing a bunch of work that you can’t even verify is correct! Complete and total waste of time.
Most PowerPC related stuff (e.g. Freescale MPC5xx found in a bunch of automotiver applications) can run in either big or little endian mode, as can most ARM and MIPS (routers, IP cameras) stuff. Can't think of the last time I've seen any of them configured to run in big endian mode tho.
Apart from IBM Power/AIX systems, SPARC/Solaris is another one. I wouldn't say either of these are used a lot, but there's a reasonable amount of legacy systems out there that are still being supported by IBM and Oracle.
10 years ago the fastest BE machines that were practical were then-ten year old powermacs. This hasn’t really changed. I guess they’re more expensive now.
e6500/T4240 are faster than powermacs. Not sure how rare they are nowadays, we didn't have any trouble buying some (on eBay). 12×2 cores, 48GB RAM, for BE that's essentially heaven…
This is misleading at best. The JVM only exposes multibyte values to ordinary applications in such a way that byte order doesn't matter. You can't break out a pointer and step through the bytes of a long field to see what order it's in, at least not without the unsafe memory APIs.
In practice, any real JVM implementation will simply use native byte order as much as possible. While bytecode and other data in class files is serialized in big endian order, it will be converted to native order whenever it's actually used. If you do pull out the unsafe APIs, you can see that e.g. values are little endian on x86(-64). The JVM would suffer from major performances issues if it tried to impose a byte order different from the underlying platform.
One relatively commonly used class which exposes this is ByteBuffer and its Int/Long variants, but there you can specify the endianness explicitly (or set it to match the native one).
> By that logic, we don't really need certificates, just TOFU.
It works fairly well for SSH, but that tends to be a more technical audience. But doing a "Always trust" or "Always accept" are valid options in many cases (often for internal apps).
> Yes: SSH certificates. (They're unrelated to X509 certificates and the WebPKI).
I am aware of them.
As someone in the academic sphere, with researchers SSHing into (e.g.) HPC clusters, this solves nothing for me from the perspective of clients trusting servers. Perhaps it's useful in a corporate environment where the deployment/MDM can place the CA in the appropriate place, but not with BYOD.
Issuing CAs to users, especially if they expire is another thing. From a UX perspective, we can tie password credentials to things like on-site Wifi and web site access (e.g., support wiki).
So SSH certs certainly have use-cases, and I'm happy they work for people, but TOFU is still the most useful in the waters I swim in.
I don't know what to tell you. The problem with TOFU is obvious: the FU. The FU happens more often than people think it does (every time you log in from a new or reprovisioned workstation) and you're vulnerable every time. I don't really care what you do for SSH (we use certificates) but this is not a workable model for TLS, where FUs are the norm.
> I don't really care what you do for SSH (we use certificates) but this is not a workable model for TLS, where FUs are the norm.
It was suggested by someone else: I commented TOFU works for SSH, but is probably not as useful for web-y stuff (except for maybe small in-house stuff).
Personally I'm somewhat sad that opportunistic encryption for the web never really took off: if folks connect on 80, redirect to 443 if you have certs 'properly' set up, but even if not do an "Upgrade" or something to move to HTTPS. Don't necessary indicate things are "secure" (with the little icon), but scramble the bits anyway: no false sense of security, but make it harder for tapping glass in bulk.
I really like the VS Code extension for sqliteview.app - [0]. It also offers an edit feature for a reasonable price, in my opinion. I'm curious if there are any competing editor alternatives.
> The demo on the show floor was also using eLoran to distribute time from a site in Nevada to the transmitter facility on Black Mountain outside Vegas, showing a way to be fully GPS-independent (though the current eLoran timing was sourced from GPS).
There's been a consistent call by many people that there needs to be a diversity of options for navigation and timing:
Well... and there's the electricity grid which can be used for timing needs accurate enough to a single second, and in Europe there's DCF77 [1] which can not just be used as a 2*10^-12 seconds-accurate timing standard but also a frequency standard.
You can… in Turkey (Türkiye); from 2021:
> Erdogan is openly averse to high interest rates, claiming high rates cause inflation, which stands in opposition to mainstream economic theory.
> He has pressured the central bank to keep rates low to fuel borrowing and growth. Critics say the independence of the central bank has been severely damaged through political pressure.
> Erdogan’s decree on Saturday appoints Sahap Kavcioglu as the new central bank head. Kavcioglu is a banking professor and a columnist in a pro-government newspaper where he has argued for low interest rates.
* https://www.aljazeera.com/news/2021/3/20/turkeys-erdogan-sac...
More recently in 2024:
> The first woman to lead the bank, Erkan began raising interest rates when she was appointed in June last year, launching a 180-degree pivot away from years of low rates under Erdogan that had sent inflation soaring and foreign investors fleeing.
* https://www.aljazeera.com/news/2024/2/3/turkey-appoints-fati...
In 2024 a court ruled that the President could not just fire central bank heads:
* https://www.brecorder.com/news/40306881/turkey-court-loosens...
reply