I would say this is true in that it's primary target originally was systems programming.
But it has seem to have taken on a lot more than that moving forwards, such as compiling to webassembly with frameworks such as leptos
Or full blown desktop applications with libraries such as egui

Most people tend to focus on the memory safety as the biggest reason, but I would say actually there are a lot of other different reasons for it gaining popularity.
1. It has a easy to use build system (cargo) it just builds on any platform including windows or linux and cross compiling is extremely easy even for embedded.
2. you can bring in libraries or external crates (build time dependencies) without magic cmake scripts / autoconf / automake / scons / Makefiles / any number of different build tools
Arguably this can lead to supply chain attacks, but the trade off is you can keep those libraries more uptodate and it's easier to add them without git submodules or other workarounds
3. No worrying about different size int's on different platforms with different custom macro's between libraries to check the size of an in at the operating system level
4. Full static typing, no ambiguity with pointers or structs
5. traits (interfaces) more of a C++ feature
6. modularity or namespaces, no having everything in a global scope such as what C does or the old pre module Javascript does where every function call has to be unique.
You can work around these in C with tools like valgrind but it's not perfect
7. Readable and helpful error messages, where it points you at the likely candidate for the fault
8. No legacy headers to worry about
9. Macro's are actually useful not magical for the most part, such as default values or serialisation

Dealing with the borrow checker or typing can be a little tricky, but I've found AI / chatgpt actually works wonders for this if you just use it for that reason only

Wait a second was this news article written by AI in response to the first news article?
Is it getting smarter and self aware

Ultimately everything that's going on at the moment is due to a new cold war between the US and China
There's been a lot of accusations of political bias when it comes to the WHO recently
So really this is just another fuck around and find out moment,

In the same way everyone keeps trying to argue about the origin of covid
People seem to be more interested in not the logic if an statement is true but the identity of the person making the statement
If something is true doesn't seem to matter as long as what its being said is on they're "side"

Today I learnt to hold my pee for 5 extra seconds while stacking boxes
Using a new form of martial arts
(cut to a training montage of someone kicking him the nuts from different angles)

> Many of them have a "dmz ip" feature which automatically forwards all ports to a specific host, its very easy to flip this on without understanding what it does.

That's a feature I've used before but you have to go out of your way to find that on most home routers its not automatically enabled and you have to specify a specific IP to forward to

> There are also thing like UPNP that can result in arbitrary ports being opened. Don't forget slipstream attacks either (google this).

IPv6 doesn’t magically prevent this it just changes what component you’re abusing.

>If you're not aware if this then you've almost certainly never used v6 or managed an environment with it active, so your knowledge on the subject is extremely questionable. This in itself is dangerous because v6 is enabled by default on most things but a lack of awareness will lead to security risks.

Historically we used Cisco ASA's, the routers they were plugged into had no IPv6 support, the default rules for zones are to automatically deny as well if you leave the acl empty
Now we're currently on AWS and that by default does not have IPv6 enabled (you can enable it but we don't)
The Asus Wireless router I'm using also has it disabled
So no it's not enabled by default on most things and even if it is your isp / router has to have it enabled in the first place

Another pain point is PCI compliance, there are additional requirements when enabling IPv6 which is another reason we currently avoid it
Regardless the point is if something is more difficult to exploit or more difficult to enable then it is a security feature even if you don't want it to be

> An incompetent firewall admin can mess up NAT just fine, and is more likely to due to the added complexity. A simple allow/deny firewall with routable addresses both sides is much easier.

With a home firewall setting up port forwarding requires additional steps outside of the rule set, setting up static nat (direct ip to ip) typically isn't supported or is very uncommon, so that's not easier and even blocks anything coming in even if you mess up the acl
With a cisco firewall setting up or messing up the access control lists is easier to do than deliberately setting up a one to one static nat
But in that scenario it's more common in a business sense to have access to external ips that can be mapped though

> You still expose the IP of the NAT gateway.
> v6 traffic by default uses random privacy addressing for outbound connections, so outbound traffic originates from random addresses

I admit the random privacy addressing feature is something I didn't know about

Even though NAT is technically not supposed to be a security mechansim it does offer some insulation against

* Competency of the person setting up the firewall
* If the firewall itself has any bugs or associated security flaws in it's firmware
* Privacy if you don't want your IP to be identified for outbound connections

If you know what your doing and the firewall is perfect and you don't care what devices are identified based on they're IP then your ok
But this is often not the case, because the person in question might be some old grandma that doesn't know anything about networking
Or if the firewall has a security issue; there's more work involved in first hacking into the firewall to setup the routing / vpn / static nat / ssh tunnelling
before you can access anything behind it, vs just enabling or adding a single rule in a list which is much easier

Then there's the other side which is anonymity or privacy if everything is being NAT'd from a single IP
for outbound connections it makes it harder to identify what's behind such as a washing machine being mixed in with UDP gaming traffic
vs everything being neatly sorted via it's own separate ip address

Moving forwards I suspect VPN's are going to become a lot more common (especially in the UK)
which in itself is just another layer of NAT
IPv6 is ideologically better, but it assumes a perfect world in so far as lack of NAT

Wasn't there a news article recently about how the WEF / Klaus Schwab altered the data to make Brexit look like a failure?
https://www.euinsider.eu/news/...

I mean I know right, when you have a political administration that manufactures intel on Russia related to they're political opponent ...
Oh wait, that actually happened.

When google's veo hits its next version we're really not going to be able to tell what's real anymore.
Especially when politicians think they can get away with crazy shit

If blue light encourages more riskier behaviour and we've now moved from yellow sodium lamps to white colored Led Lamps with more blue in
(In some cases blue or purple due to faulty led's)
I wonder if from a statistical point of view this might also impact driving safety

The recent Spanish blackouts have demonstrated that without proper storage or grid inertia renewables alone are not going to be a full solution.
While I'm all for renewables myself long term its going to take time to adapt to all the problems and costs that will impact the implementation.
There's cost factor to the end user will be the biggest one, not everyone can afford expensive power just because it's saving the planet, in which case it needs to be cheap in order to be practical.

I was on firefox for a while but they don't support new standards such as webgpu.
After moving to Opera a while back (which is chromium based) it all seems fine

I believe the Turing Test has now been surpassed by the Potato Test

https://www.reddit.com/r/Tinde...

https://www.youtube.com/shorts...

It's not the applet approach, it's more the intermediary or IL language approach.
With CSharp for example at development time you compile down to a binary that's in a language called IL.
Then at runtime you compile that IL into machine code.
The IL is fairly close to native machine code so there isn't much work do to at runtime, but at the same time it's platform independent so can be run on multiple architectures such as ARM or x86 without the need for multiple binaries.

In the case of Javascript it's already going through compile stages such as webpack or vite for a lot of sites, to work around package management or modules (ES6 modules has only just made it into the browser recently which is crazy), so compiling it into an IL such as webpack in the future makes sense, since the IL will be closer to machine code and will need less work on the browser.
The main downside is lack of access to the DOM which hopefully will get fixed.

You can already write frontend code in Rust as another example which compiles to web assembly and is a lot less painful with it's library management, one example being leptos

The replacement image will instead be of the famous actor Ricardo Milos