So, I’d argue that “frontend” and “backend” are the default modes of software engineering these days, and that embedded is a more niche field.
That said, if you’re doing encryption code, you’re doing far more advanced math than backend monitoring and alerting.
You often need to be pretty good at math. But not because you’re “doing math” to write the code.
In real world software systems, you need to handle monitoring and alerting. To properly do this, you need to understand stats, rolling averages, percentiles, probability distributions, and significance testing. At least at a basic level. Enough to know how to recognize these problems and where to look when you run into them.
For being a better coder, you need to understand mathematical logic, proofs, algebra/symbolic logic, etc in order to reason your way through tricky edge cases.
To do AI/ML, you need to know a shitton of calculus and diff eqs, plus numerical algorithms concepts like numerical stability. This is kinda a niche (but rapidly growing) engineering field.
The same thing about AI also applies to any other domain where the thing being computed is fundamentally a math or logic solution. This is somewhat common in backend engineering.
I’m not “doing math” with pen and paper at work, but I do use all of these mathematical skills all. the. time.
I am an SRE on a ML serving platform.
Big +1 for Sync.
I was paying for Sync back when it was a Reddit client, and I moved to Lemmy mostly because that is where Sync moved.
It’s an awesome app. Best app purchase I’ve ever made. (There is a free version too.)
That’s a good idea. They could probably do something similar for the audio.
They’d have to code around the rest of the animation and audio effects, but the size of that code would certainly be smaller than the rendered audio and video.
Video codecs mostly work by tracking movement, predicting which pixels will change, and striving to only encode the pixels that actually change or change dramatically. In other words, compression looks for patterns.
All of that goes out the window when you try to compress static. There are no patterns. It simply can’t be compressed. This isn’t a matter of the algorithms not being good enough. It’s a fundamental limit of information theory.
Anything fancier amounts to embedding the intro into the compressor as a well-known pattern. And at that point, you’re better off just caching a 4K version of the intro as a standalone video file directly in the app.
I think the reason Zealandia is called a “submerged continent” is because it is made of continental crust rather than oceanic crust.
But IMO the best geologic definition of continents is by tectonic plates, which mostly matches up with the cultural definitions of the continents.
For the major continents, we have these plates:
There are several smaller plates too, like the Caribbean, Indian, and Arabian plates. IMO, we should consider these independent continents.
There is also a dedicated Pacific plate. The ring of fire is the border of this plate.
New Zealand / Zealandia is on the ring of fire. Half on the Australian plate, half on the Pacific plate. You can actually see the border of the two plates when you look at the topographical map of Zealandia.
You’re using the New York Times to support the idea that the New York Times didn’t support the war.
What do you think could be an issue with using that evidence?
Nothing? It’s literally the primary source.
Did NYT support the war? Let’s look at the opinion pieces they published about the war.
I saw it at the MoMA in NYC. The thing is tiny…
Part of it is the community. I really like the OpenWRT community, but it’s harder to engage with them when you run a downstream distribution.
But also I’m a bit of a hacker (in the traditional sense). I like to experiment with custom builds of OpenWRT. (And FWIW, their build system uses the same menuconfig as Linux.)
I love my Turris Omnia!
I got the one with the WiFi 6 card. The cool thing is that you can easily open it up and replace parts.
I run the upstream OpenWRT rather than the customized version by Turris. They are good about submitting patches upstream.
+1
From an order of magnitude perspective, the max is terabytes. No “normal” users are dealing with petabytes. And if you are dealing with petabytes, you’re not using some random poster’s program from reddit.
For a concrete cap, I’d say 256 tebibytes…
I think they’re just stopping operations of the company in Brazil.
But I don’t think they’re going out of the way to prevent Brazilian IPs from connecting.
Tell me you’ve never worked on a farm without telling me that you’ve never worked on a farm.
The thumbnail photo is extreme, yes. But white farm workers still get sunburns.
TL;DR - We can now control swappiness per cgroup instead of just globally. This is something that userspace oom killers will want to use.
You don’t need to provide root access just because you used GPL code, you just have to follow the GPL.
Well, to follow version 3 of the GPL, you do actually need to provide effective root access.
Specifically, version 3 of the GPL adds language to prevent Tivoization.
It’s not enough to just provide the user with the code. The user is entitled to the freedom to modify that code and to use their modifications.
In other words, in addition to providing access to the source code, you must actually provide a mechanism to allow the user to change the code on the device.
The name “Tivoization” comes from the practice of the company TiVo, which sold set-top boxes based on GPL code, but employed DRM to prevent the user from applying custom patches. V3 of the GPL remedies this bug.
For Zulip, I’ve only used it on the web. Apparently they have iOS, Android, Desktop, and Terminal clients.
For Matrix, there are many clients on all platforms, but none have ever stood out to me. Element is the official client, and it’s… fine I guess.
I love this, especially the criticism of the FSF.
For coms, Zulip seems OK. I would really like Matrix to take off, but I honestly don’t really like any of the clients.
The meaning of version numbers can vary across projects.
One common scheme is Semantic Versioning, which divides the version number into three parts: MAJOR.MINOR.PATCH*
MAJOR is incremented when there are backwards incompatible changes.MINOR is incremented when new features are added in a backwards compatible way.PATCH is incremented for smaller big fixes.* It’s a bit more complex than this, but this is the gist.
Maybe.
Linux won because it worked. Hurd was stuck in research and development hell. They never were able to catch up.
So you’re telling me that there was a Mac super computer in '05?