For the past days I've been participating(albeit over Teams) in a conference relevant to my industry (intel), basically startups and established companies showcasing their products to a closed audience of EU gov. officials.
One thing I noticed right away, is that all companies were asked "Can we fully host this from within EU or our country" from the various people in audience. Every single one. Many of the startups had slides prepared for this.
Definitely a change, because it is not something I can recall being important just a couple of years ago.
After those machines, at the Pentium Pro, with look-ahead instruction decoding, it became a major lose to store into code. Superscalar x86 CPUs have the hardware to detect and handle stores into code, but it requires bringing the CPU to a clean halt, almost like an exception interrupt, discarding pipelined work that's already been done, and then restarting the pipeline, reloading the instructions ahead. All the performance gains of superscalar hardware is lost for a while.
There are RISC architectures where self-modifying code isn't supported, and code pages must be read-only. Then the CPU doesn't need the machinery for detecting and aborting look ahead on a store into code. MacOS has enforced that rule since the PowerPC era.
The Gemini app has been backported to at least Android 14 as far as I could tell (that's the oldest OS I saw it on), probably further.
Hard to say they're going to keep giving you new features, but buying a device for the future things that may be brought to it is always a massive gamble, like buying a Macbook for their failed promise of Apple Intelligence or a Windows laptop for the promised advantages of Copilot.
If the device works well enough to be worth the money, it'll keep working. If you want fancy stuff in the future, hold off on buying new hardware and wait until the stuff you want is actually available.
The mere act of scanning for vulnerability often causes outages.
I once ran a vulnerability scan at an industrial company that completely disabled their employees ability to clock in and out. I didnt believe it had anything to do with my scanner at first, but it ran on a schedule and the scanners schedule matched their outages eaxctly.
Eventually it turned out the timecard system had these IOT badge readers with a poorly written tcp stack. It would ACK every SYN, and worse the half open connections never closed, so during a port scan every port was left open until it exhausted the memory on the little buggers.
My point is... you cant know im advance what damage you'll do with this sort of testing. That's kind of the entire reason we have to actually perform the real world tests instead of assuming or emulating them.
It's also the reason that real world scanning without authorization is probably already a crime in most jurisdictions, whether it's enforced or not.
That's amazing. Are there measurements of decently large clojure applications both with the interpreter and the original clojure engine on the same machine?
Is it? I'm mostly used to (pre-)C++11 and the only unusual operators I see are ^^T (which I presume accesses the metadata info of T) and [:e:] (which I assume somehow casts the enumerator metadata 'e' to a constant value of T).
And template for but I assume that's like inline for like in zig.
You write well and you mean well but what's actually hopeless is trying to use logic with the people who post these kinds of articles and crawl out to comment on them. They're never going to view these conflicts dispassionately, seek out or absorb objective facts or explanations that challenge their preconceptions. They're motivated by an animus toward Israel they nearly all seem to lack toward any other country, they hold Israel to a standard that no other country is actively held to, and yet their worst nightmare is being called antisemites.
I think that's a very different kind of concern, and its also been very predictable and slow.
I would also say though, you have to be a bit careful about "they are discussing" because there are many people across different countries with different agendas, and a huge amount of discussion between people. Your link for example is a pretty good bit of background info, clearly saying VPNs aren't just about accessing porn
> In the corporate world, VPNs are essential for secure remote work, allowing employees to access company
systems without compromising sensitive information. For individual users, VPNs prevent tracking by
internet service providers, advertisers and potential cybercriminals. They are also used to access
educational or entertainment content that may be restricted in certain countries, including authoritarian
regimes, supporting freedom of information and digital inclusivity, as censorship becomes more difficult to
enforce through VPN use.
It links off to sites discussing possible approaches to age verification which highlights that various approaches in France didn't meet the regulators requirements because of a lack of privacy.
I think this is a different kind of concern about how your products must work compared to worrying that with little to no notice your country may be cut off due to a diplomatic spat from some specific service.
It's fine to have an unstable backup system, as long as any failures in your backups are uncorrelated with failures in your primary system. And a random datacentre burning down probably isn't correlated with anything else, unless you're foolish enough to host your primary and backup copies in the same building.
All else equal, a more stable backup is of course better, but any backup is better than no backups, so choosing the cheapest possible option is often the best strategy since that's the one that you're the most likely to keep using long-term.
Managed a fairly large matomo site in the past. Using queue plugin (https://plugins.matomo.org/QueuedTracking) with Redis Cluster really improves the situation. We actually built a custom plugin with Nginx + Lua to avoid PHP altogether for the tracking part. Scaling ingestion then wasn't the problem, draining the queue was
What was the hardest part, Range header handling or the slowloris mitigations? Both seem like they'd be a nightmare without higher-level state machines.
I've been wondering about debug-ability of code using reflection. X-Macros are quite annoying to step through in most debuggers, though possible. While the code in the first example is evaluated fully at compile-time, how would you approach debugging it?
That does not mean I cannot use the ink I want in a tool that I own.
Yes, your ink might be better. Market it that way and make it known. No problem with that. But prevent me from using my tool using DRM and firmware updates? That is customer hostile.
The little indicator stays for a while after activation to prevent apps from pinging the camera for a few milliseconds without a trace. It doesn't necessarily mean that the camera is still being used, though it could be if it stays around for longer than a second or so.
One thing I noticed right away, is that all companies were asked "Can we fully host this from within EU or our country" from the various people in audience. Every single one. Many of the startups had slides prepared for this.
Definitely a change, because it is not something I can recall being important just a couple of years ago.