To me this paper confuses regulation via mitochondria from the requirement of sleep. Even if experimentally manipulating mitochondria state induces sleep, this might just be a proxy indicator control mechanism. ETC leak is only an issue for these dFBNs which are specifically complementary active to normal neuronal cells. I would say mitochondria are important for sleep regulation but this is specific to animals with brains. Other kingdoms do not "sleep". This is too much a stretch to say mitochondria dysfunction is the cause of sleep when other kingdoms also have mitochondrial stress and don't have actual analogical "sleep" processes. My raw take given my PhD work was on mitochondria.
Readit Newsbmillare commented on Sleep all comes down to the mitochondria science.org/content/blog-... · Posted by u/A_D_E_P_T
bmillare commented on Driverless semis have started running regular longhaul routes cnn.com/2025/05/01/busine... · Posted by u/harambae
I'm assuming these are electric? Because even with a driver, longhaul electric trucks are not practical at scale right now, the energy infrastructure and capacity to support them is nowhere near there.
My point being (and please correct me), this is practical but 15-20 years away from widespread adaption, best case.
If you take a look at the pictures, it appears those are Peterbilt trucks (non-electric). You can see it more clearly on their own website.
bmillare commented on Morse, an open-source interactive tool for inspecting Clojure clojure.org/news/2023/04/... · Posted by u/xmlblog
Are Clojure dev teams outside of Nubank currently using REBL excited about this?
As a small project Clojure dev (and admittedly a couple years out of daily Clojure use), these types of projects are hard for me to place in a day-to-day work context. The doc says that Morse is one tool that can "amplify the power of the programmer during interactive development".
I totally feel like Clojure REPL-based dev is better for me personally - the interactive feedback feels so natural and functional programming matches so well my preferred dev process. But it is more difficult for me to understand where this type of tooling fits in dev workflow. Is Morse an incremental improvement? Does it make more sense in significant Clojure dev shops with many programmers vs just me sitting around with an Emacs repl going?
for me, (just started using it), at least 1 good case is traversing deeply nested maps without going crazy. Even when looking at nested structures from other langs, easy enough to write a converter and then use this to inspect. Also if the datatypes are special, you can have it expand in other ways like links to browser, or other custom view types. That alone seems pretty useful. You can make GUI like behavior with just adding some metadata.
It looks like big chunks of REBL are being pulled into Clojure core:
>Fogus has been mostly focusing on some new tooling derived from REBL and we are hopefully nearing a point of release on that and some additional supporting libs soon as well.
From third paragraph here: https://clojure.org/news/2023/03/27/deref
This is important because the core Clojure license is true open source vs REBL which had a semi closed license, so it’s always been a little difficult of a choice for many people.
That's great news. It would be easier to make "ports" of REBL like to a simple cljs app with the major components available. I feel REBL might have a bunch of nav wrappers that I would have to re-implement if I had to start from scratch
Did anyone create a Clojurescript version of this like Stuart mentioned his excitement for in the talk? If not, I might put together something simple.
bmillare commented on Thoughts on Clojure UI Framework tonsky.me/blog/clojure-ui... · Posted by u/tosh
I'm curious what this would be implemented on top of. How do we get graphics acceleration playing well with java? There's a lot of details to get right. What's the scope and timeline for an mvp?
bmillare commented on Emacs is the 2D Command-line Interface hongchao.me/cli-and-emacs... · Posted by u/karlicoss
Emacs is a text UI (though it can show images too) on top of a cross OS programming platform where you can create quick UIs for any kind of task you have (interfacing with APIs, command line programs, editing tasks, etc.).
Once you learn how Emacs works and how it can be programmed, you can create interactive tools extremely quickly to make lots of tasks you encounter day to day easier. I do this all the time.
Do you have any references/tutorials/examples on how to do this?
bmillare commented on What Clojure Spec is and what you can do with it pixelated-noise.com/blog/... · Posted by u/icey
Can you elaborate with an example for s/valid? on needing to preconfrom your data. I have not had this issue.
Also note for others with regard to eagerness, this is only for maps. "When conformance is checked on a map, it does two things - checking that the required attributes are included, and checking that every registered key has a conforming value. We’ll see later where optional attributes can be useful. Also note that ALL attributes are checked via keys, not just those listed in the :req and :opt keys. Thus a bare (s/keys) is valid and will check all attributes of a map without checking which keys are required or optional."
Can you explain the point of :opt with s/keys if it will always check any registered spec in if present?
Found the answer to s/keys and :opt "The :opt keys serve as documentation and may be used by the generator."
bmillare commented on What Clojure Spec is and what you can do with it pixelated-noise.com/blog/... · Posted by u/icey
I found spec very useful and use it more and more. I'm looking forward to newer revisions, with support for optionality, it's been a big problem area in my case.
Here's a quick list of gotchas (well, they got me, so perhaps other people will find this list useful):
* `s/valid?` does not actually tell you that the data is valid
The naming of `s/valid?` suggests that you can call it on your data and find out if the data is valid according to the spec. This isn't true. What it actually tells you is if the data, when conformed, will be valid according to the spec. If you pass the data as-is to your functions (without passing it through `s/conform`), you might find that they will be surprised at what they get.
* Conformers are likely not what you think. They are not intended for coercion and have many pitfalls (for example, multi-specs dispatch on unconformed value).
* s/merge doesn't necessarily do what you wanted if you're using conformers, only the last spec passed to merge will be used for s/conform (but you're not using conformers, right?)
* specs are checked eagerly. If you think that (s/valid? ::my-spec x) will only check ::my-spec, that is not the case. It will check any key of x found in the spec registry.
I settled on a subset of spec, because of the pitfalls.
Can you elaborate with an example for s/valid? on needing to preconfrom your data. I have not had this issue.
Also note for others with regard to eagerness, this is only for maps. "When conformance is checked on a map, it does two things - checking that the required attributes are included, and checking that every registered key has a conforming value. We’ll see later where optional attributes can be useful. Also note that ALL attributes are checked via keys, not just those listed in the :req and :opt keys. Thus a bare (s/keys) is valid and will check all attributes of a map without checking which keys are required or optional."
Can you explain the point of :opt with s/keys if it will always check any registered spec in if present?
bmillare commented on CRDTs: The Hard Parts [video] martin.kleppmann.com/2020... · Posted by u/benrbray
> If you find yourself saying things like "this database is ACID compliant", "we have an SQL database with transactions, so we're fine" or "let's just add replication to Postgres and we'll be fine", you need to read this book.
can you elaborate why? are these sentences fundamentally wrong? they dont appear so.
It's simplistic. When you move into distributed systems, these claims are not sufficient to indicate "so we're fine". Even with the ACID, the "I" has multiple levels, and often they get things wrong (see Jepsen).