I've never worn a pebble, but I also have a banglejs 2 and I really love the watch for it's hackability.
I've written my own watchface and a couple of other apps and made changes to a number of existing apps, it's really simple because you can always test your code changes live on the watch while keeping it on your wrist. There's an IDE that connects to it using Bluetooth and the code can be modified during runtime
Lthere's also a great community of hackers and tinkerers that steadily improve the watch.
It might not have the same polish as the pebble had, but it makes it up in hackability. I can only recommend getting a banglejs2 (battery life is also pretty great, I get about 10 days with regular use)
Huh. I appreciate what they did with the tech there, but looking at this Bangle.js the first thing that comes to mind is I hope NuPebble(?) doesn't adopt that excessively-curvy-rectangle shape that screams Apple Watch, I've learned to recoil in disgust even seeing that shape.
It's an excellent point. In such a scenario, if you're bound to a rigid workflow system, you will probably have a hard time recreating all the intermediary steps required to get the system back into a consistent state with the external world.
Idempotency is key and the choice of the idempotency key as well ;)
Disclaimer: I don't mean to disrespect anybody by posting the title of this work. The content is not sexist or racist.
I posted this video in response to the thread about facial recognition evasion. [0]
I originally saw this at an exposition in France a few years back, and it stuck with me ever since. It's a very clever commentary about the state of AI and facial recognition software and that's long before the big AI boom. I hope you enjoy it as much as I did.
It's true that e.g. medications and alcohol can increase the risks for the child, but many people also have apnoea (often without knowing) which can also lead to sudden movements in your sleep.
The article says there's no socio-economic factors; the data says the risk is the same for all babies.
If you don't want to change your habits because of an article, that is fine, but people should be aware of the risk.
We use a co-sleeping bed next to the parents bed and the infant is just as close, but safer from harm
Yeah, it's pretty much the same story for me; after having found out how to get all the same features in KDE that I had in xfce, there was no way back. I always like to use the lightweight and less resource intensive software, but arguably not using hardware acceleration is actually very resource hungry.
> I always like to use the lightweight and less resource intensive software, but arguably not using hardware acceleration is actually very resource hungry.
What hardware are you using where KDE is considered "resource intensive", yet it also has a GPU that supports Vulkan and hardware video decoding?
I've used KDE for a long time, and can't remember a time when I noticed its resource usage (and I used to daily drive a ThinkPad X200 as late as 2016)
I notice KDE's resource utilization more or less constantly. With KDE's bling turned all the way down, Kwin constantly uses 5-10% CPU when I am literally doing nothing (with my hands off the mouse/keyboard). This causes my laptop fans to noticeably spin up and makes them a lot more prone to spinning up more forcefully while doing a small task. With XFCE, my fan never audibly spins up unless I'm actively doing something. Even if I just do something small/quick, my fans don't spin up most of the time.
I once noticed a memory leak in KDE when setting the background to a (very many image) slideshow instead of a single image. That was probably sometime around 2015.
Normally it's a bit tricky to calculate memory blame between X11, the WM, and the shell, since often their allocations are actually on behalf of an application, and killing the application will reclaim it.
KDE 6 isn't really that much heavier than a "full install" of xfce to be honest. I just prefer the simplicity (probably 1/10th the adjustability of KDE) of xfce for ease of maintenance, but KDE is fine too.
It would be awesome if there was a mode in which the pronunciation of the names is also same in the two languages.
For example, in french there is the name "Arnaud", which exists in German as "Arno". For a bilingual child it's much more important for the name to sound the same that to be written the same.
> For a bilingual child it's much more important for the name to sound the same that to be written the same.
There are downsides to the different spellings.
I have this issue within English. There are several ways to Matthew. If misspelled, it is usually Matthew. Occasionally, some spell it Mathieu.
I hate to use phones for any kind of personal info transfer for this reason, as it has caused headaches everywhere from the bank to travel agents to charitable donations to even sharing my email.
> I have this issue within English. There are several ways to Matthew. If misspelled, it is usually Matthew. Occasionally, some spell it Mathieu.
For Michael, there is only one spelling, but people nevertheless frequently misspell the name.
My favorite comment on this topic came from a Michael who, when consulted about the spelling Micheal, observed "people named Michael don't spell it that way".
> My favorite comment on this topic came from a Michael who, when consulted about the spelling Micheal, observed "people named Michael don't spell it that way".
> For a bilingual child it's much more important for the name to sound the same that to be written the same
Maybe when they're a child, but once they become an adult, having the same spelling becomes important to avoid bureaucratic headaches, especially now that KYC is becoming so strict. Are you sending money to yourself or someone else when the name is spelled differently on the two accounts?
Took me a while to understand, so to make it explicit for anyone else:
Arnaud and Arno sound the same! (in this language pair.) In Dutch, I know both an Arnaud and an Arno, and it's pronounced correctly^W like you read it (IPA: /ɑrnʌud/ and /ɑrnoː/) so that threw me off probably.
Anyway, your request is a bunch of human labeling work if there isn't already IPA conversions for every name (and if LLM can't already guess correctly 95% of the time and that's good enough for an initial comparison), but from an algorithmic standpoint shouldn't be hard: use the same comparison but on phonetic spellings of the names rather than language-specific spellings. Example: in Dutch, we pronounce "u" like IPA /y/, whereas German pronounces it as /ü/, so any name with "u" in it will automatically be incompatible pronunciation-wise.
"For a bilingual child it's much more important for the name to sound the same that to be written the same."
This feels like it will be annoying whenever someone asks for your name in order to write it down or when they are trying to read it. This happens a lot in a school context.
You're only at school in one of the countries (at a time anyway) - pick the one that corresponds there?
Of course only one of them is your 'actual' name anyway, the other is just by its existence making your name familiar and easy to pronounce. It having a different local spelling (if that's the case) doesn't have to matter or be annoying unless you decide it is. Anything where it's important obviously you make sure to get it right, as you would anyway.
I immediately have to think of the potential uses for VR: lightweight setups for Varifocal lenses are one of the missing corner pieces to create a life-like VR experince. I'm excited to see where they will go with this research!
Redundancy also adds a lot of complexity, as fail-over mechanisms aren't simple either. That added complexity then turns into additional possible error sources.
A friend of mine builds a component for a satellite system and the FDIR mechanisms need to be chosen very carefully, as adding more fail-safes can actually make the system overall more error prone.
There's an interesting blog post on from AWS about that topic [0]. Turns out adding more fallbacks and fail-safes is actually discouraged there.
I've written my own watchface and a couple of other apps and made changes to a number of existing apps, it's really simple because you can always test your code changes live on the watch while keeping it on your wrist. There's an IDE that connects to it using Bluetooth and the code can be modified during runtime
Lthere's also a great community of hackers and tinkerers that steadily improve the watch.
It might not have the same polish as the pebble had, but it makes it up in hackability. I can only recommend getting a banglejs2 (battery life is also pretty great, I get about 10 days with regular use)