I don't think it is feasible to build one without a massive scope creeping. The grand strategies have very different focuses depending on the era.
It's not just DNS. I have this rule in my firewall:
udp dport 15600 counter drop comment "Block Samsung TV shenanigans"
So far, it has blocked 20575 packets (constituting 1304695 bytes) in 6 days and 20 hours.
Anticheats can be very invasive, they can theoretically scan all the files inside your computer (whether it is practically done, I don't know but it surely feels like it's been done), take screenshots regularly, send your hardware information, etc. So yeah, if you are someone who takes security seriously...
Growing up in a "ground floor" country, the British way feels very natural to me. Which floor do I first encounter when I climb up the stairs? The first one! I guess you can also think of the ground floor as its own thing, since it is unelevated.
If you squint your eyes just enough, insurance is like gambling... You are betting that something is going to happen to you, the insurance company is betting against that. The insurance company can improve their chances by adding conditions to that something.
For many systems out there, /bin and /lib are no longer a thing. Instead, they are just a link to /usr/bin and /usr/lib. And for some systems even /sbin has been merged with /bin (in turn linked to /usr/bin).
Not just Linux... 99% of the time you see something weird in the computing world, the reason is going to be "because history."
Gen Z's are well aware of traditional phones. Smartphones were not really that ubiquitous (up until 2010(ish)), and by that time Gen Alphas were already born.
The C developers are the ones with the ageist mindset.
The Rust developers certainly are not the ones raising the point "C has always worked, so why should we use another language?" which ignores the objective advantages of Rust and is solely leaning on C being the older language.
They very rarely have memory and threading issues
It's always the "rarely" that gets you. A program that doesn't crash is awesome, a program that crashes consistently is easy to debug (and most likely would be caught during development anyway), but a program that crashes only once a week? Wooo boy.
People vastly underestimate the value Rust brings by ensuring the same class of bugs will never happen.
Ah you got my comment wrong! I didn't mean to suggest Gecko is closed source. I just wanted another web engine that is also open source.
Servo was an experimental ground for Mozilla in some ways (like testing out a new CSS engine and porting it back to Gecko if it works). So it's quite normal for people to be unaware of it, it was not meant for the public.
But later on it was abandoned by Mozilla and stuck in a limbo, until it got picked up by the Linux Foundation. Now it's a standalone project and I wish them well. We really need a new FOSS web engine.
It really depends.
If I know I will never open the file in the terminal or batch process it in someways, I will name it using Common Case: "Cool Filename.odt".
Anything besides that, snake case. Preferably prefixed with current date: "20240901_cool_filename"
I recall reading somewhere the earlier compilers had a hard limit on the length of function names, due to memory constraints.
People back then just grossly underestimated how big computing was going to be.
The human brain is not built to predict exponential growths!
No, I am literally speaking from experience. I have seen way more door handles where both sides are connected than the opposite.
What? Plenty of door handles turn on both sides. If the handle on one side is stuck, you can't turn the other handle too.
One of the issues at hand is that X11, the predecessor of Wayland, does not have a standardized way to tell applications what scale they should use. Applications on X11 get the scale from environment variables (completely bypassing X11), or from Xft.dpi, or by providing in-application settings, or they guess it using some unorthodox means, or simply don't scale at all. It's a huge mess overall.
It is one of the more-or-less fundamentally unfixable parts of the protocol, since it wants everything to be on the same coordinate space (i.e. 1 pixel is 1 pixel everywhere, which is... quite unsuitable for modern systems.)
Wayland does operate like how you say it and applications supporting Wayland will work properly in HiDPI environments.
However a lot of people and applications are still on X11 due to various reasons.
For context: I am trying to write a Rust wrapper over a C library.
Like many C libraries, most of its functions return an int. Positive return values are meaningful (provides information) and negative values are error codes.
To give an example, think of something like int get_items_from_record(const struct record *rec, struct item *items). A positive value indicates how many items were returned. -1 could mean ErrorA, -2 ErrorB, and so on.
Since this is Rust, I want to represent this kind of integer as Result<T, E>, e.g.:
```rust enum LibError { A = -1, B = -2, // .... }
// LibResult is ideally just represented as an integer. type LibResult = Result<NonNegativeInteger, LibError>;
// Then I can pass LibResult values back to the C code as i32 trivially. ```
Is there a way/crate to do this?