I’m assuming, this is what OP is using: https://docs.linuxserver.io/images/docker-firefox/
I’m assuming, this is what OP is using: https://docs.linuxserver.io/images/docker-firefox/
I’m not a lawyer, I could imagine that a copyright claim for a specific app design is viable.
But in this case, it might also just be a case of avoiding bad press and bad blood with Apple.
Huh, so Tony Hoare invented null
and then Graydon Hoare invented Rust, immediately terminating the existence of which does not have a traditional null
null
value.
I’m using Simon Tatham’s Puzzles for nonograms.
It’s basically this webpage in app form: https://www.chiark.greenend.org.uk/~sgtatham/puzzles/js/pattern.html
It doesn’t result in a pixel art picture when you solve it, if you care for that, but the solutions do have contiguous regions.
LTT is Linus Tech Tips. It’s more of an entertainment channel with technology flavor. They’re pretty terrible when it comes to actual technological understanding.
Yeah, that is my understanding, too. Otherwise you’d only want to generate them on the database host, as even with NTP there will be small differences. This would kind of defeat the purpose of UUIDs.
If you’re saying that even without NTP, just by manually setting the time, things will be fine. I mean, maybe. But I’ve seen it far too many times already that some host shows up with 1970-01-01…
For others wondering what’s wrong with UUIDv4:
UUID versions that are not time ordered, such as UUIDv4, have poor database-index locality. This means that new values created in succession are not close to each other in the index; thus, they require inserts to be performed at random locations. The resulting negative performance effects on the common structures used for this (B-tree and its variants) can be dramatic.
I guess, this means with these new UUIDs, ideally you only create UUIDs on systems that are hooked up to NTP, though I guess, it won’t really be worse than UUIDv4 either way.
We’ve been using Leptos at work, which is a similar framework (and probably shares half the stack with Dioxus).
And yeah, it’s really good. My favorite thing about using Rust for the UI is algebraic data types.
So, in Rust when you call a function which can fail, there isn’t an exception being thrown, but rather you get a Result
-type as return value.
This Result
can either contain an Ok
with the actual return value inside. Or it can contain an Err
with an error message inside.
So, in your UI code, you just hand this Result
all the way to your display code and there you either display the value or you display the error.
No more uninitialized variables, no more separate booleans to indicate that the variable is uninitialized, no more unreadable multi-line ternaries.
It just becomes so much simpler to load something from the backend and display it, which is kind of important in frontend code.
It’s not a dual-language platform, though. You write the backend and the frontend in Rust. The frontend code is compiled to WASM to serve it to the browser.
Various ant species do a similar thing where their soldiers have really big, flat heads and when their nest gets attacked, the soldiers stick their head into the entrance way, so the attackers can’t come inside.
Apparently, this kind of behaviour is referred to as phragmosis.
I mean, I doubt the Windows support is particularly solid here either. Using shell commands to formulate tasks will never be great for Windows, because the shell ecosystem is simply Linux.
Your comment is perhaps a bit confusing without a link: https://just.systems/man/en/
There’s not exactly a dichotomy there…
But that is what I mean with it needing an extension of the language.
So, I’m not saying you could just build a library that calls existing PHP functions to make it all work. Rather I’m saying there’s certain machine code instructions, which just cannot be expressed in PHP. And we need those machine code instructions for actually managing memory. So, I am talking about reading/writing to memory not being possible, unless we resort to horrible hacks.
Since we are building our own compiler anyways, we could add our own function-stubs and tell our compiler to translate them to those missing machine code instructions. But then that is a superset of PHP. It wouldn’t be possible in PHP itself.
Again, I’m not entirely sure about the above, but my web search skills couldn’t uncover any way to actually just read from a memory address in PHP.
I mean, I’m a bit out of my water there, both in terms of the featureset of PHP and what’s actually needed for a kernel, but I’m still gonna go with no.
For one, PHP uses reference counting + garbage collection for memory management. That’s normally done by the language runtime, which you won’t have when running baremetal.
Maybe you could implement a kernel, which does as few allocations as possible (generally a good idea for a kernel, but no idea, if it’s possible with PHP), and then basically just let it memory leak until everything crashes.
Then again, the kernel is responsible for making processes crash when they have a memory leak. Presumably, our PHP kernel would just start overwriting data from running processes and eventually overwrite itself in memory(?). Either way, it would be horrendous.
Maybe you could also try to implement some basic reference counting into your own PHP code, so that your own code keeps track of how often you’ve used an object in your own code. Certainly doesn’t sound like fun, though.
Well, and secondly, I imagine, you’d also still need an extension of the language, to be able to address actual memory locations and do various operations with them.
I know from Rust, that they’ve got specific functions in the stdlib for that, see for example: https://doc.rust-lang.org/stable/std/ptr/index.html#functions
Presumably, PHP does not have such functions, because its users aren’t normally concerned with that.
How? You’d need to compile it down to machine code somehow, for the processor to have any clue how to run it. And you’d need some custom library with custom compile instructions, to be able to control memory allocations, memory addresses etc…
I did a quick search and found two operating systems written in JS, both of which cop out when it comes to the kernel. Did you maybe mix it up with those?
Good thing that this isn’t actually possible…
Google isn’t exactly excited about the concept of local files. They would prefer you to keep everything in their online services.
If you need support for these, then installing a separate file manager app is your best bet.
I’m using this one:
https://f-droid.org/packages/me.zhanghai.android.files/
(No idea, though, if it supports unpacking RAR archives.)
I mean, presumably there’s a microcontroller in this radio. For programming that, your only real mainstream choices are C, C++ and Rust, since you can’t have a language runtime without a filesystem.
But yeah, it’s neither the case that Rust is overwhelmingly popular for that (C/C++ do stick around still), nor is it the only discipline where Rust shines.
No, it’s different. With you, there’s at least something that we observe that we might be hallucinating.
With worm holes, we’re taking mathematical equations that were modelled to reflect what we’ve observed of reality and then we’re pushing them to extreme cases where they’re likely to not anymore model reality correctly, and that is where we’re seeing the theoretical possibility of worm holes. No one has observed nor hallucinated worm holes.