Remember the X8.7 solar flare on May 14, as sunspot region 3664 was rotating away from earth?
The #CME from that flare reached Mars on May 19. Mars rover Curiosity took some nighttime images of the Martian sky hoping to catch an #aurora.
#Mars lacks a global magnetic field, hence Martian aurorae are not concentrated at the poles, but instead appear as a “global diffuse aurora” associated with Mars’ ancient, magnetized crust.
Here are some images of Martian aurora taken by Mars orbiter #MAVEN.
"Under favorable solar wind conditions, discrete auroral events occur most evenings and may last for hours. MAVEN’s observations show that discrete auroras occur at an altitude of ~130 km in the atmosphere, where energetic charged particles cause CO, CO2+, N2, and atomic oxygen to glow."
The NASA Mars Atmosphere and Volatile Evolution mission has been studying Mars' atmosphere since Sept 21, 2014.
Why is the whole #JavaScript / #TypeScript dependency management system such a mess? Cryptic warnings all over the place, non-deterministic behavior, n different module systems and dependency management tools - crazy.
With #Java and e.g. #Maven I never have any of these problems. It's also complex, sure, but in general it works really rock solid for me.
I put together productivity tips for using some of my favourite tools in this video. Which of these do you already use everyday? Did you learn something new?
After 3,5 years of working with #gradle I'm back with #maven and one thing I'm enjoying is the uniformity of how to configure Maven. With Gradle, it seems there are several ways of doing the same thing, and they don't all work when combined.
A deeper dive than anybody wanted into Semantic Versioning, how its ordering conflicts with standard practice, and how to unify spec and practice. Includes examples for SBT (Coursier and Ivy) and Maven.
This is a hill I would be willing to die on: The majority of issues in a #Maven build happen in combination with #shading. It's the worst, but sadly, sometimes inevitable.
At a job interview, I was asked why I prefer @ASFMavenProject over @Gradle and here's another example: I am facing a minor issue with https://github.com/detekt/detekt . Nothing big, in fact, fixing the issue is a matter of 10 lines of code. Nevertheless, it's a show-stopper for me, so, I can't wait for my PR to be merged. So, what do I do? I clone the repo onto our private GitLab, change the group-id and publish a patched version of detekt into our internal maven repo.
@ASFMavenProject@Gradle
Easy with #Maven, not so much with #Gradle: Because Gradle allows for so much customization, the build is very hard to understand for anyone not familiar with the project. In this case, changing the group-id (which should only be used during publishing the artifacts) also broke some tests for whatever reason. And even though I did a project-wide search and replace, I was unable to find that broken dependency.
Planning a new article on #Kotlin, #Javalin, #HTMX, #TailwindCSS, #Playwright. Probably #Gradle, although I'm more and more interested in rediscovering #Maven. Maybe #RetroFit to include some OHS/ACL (#DDD Context Mapping), but maybe this is already a lot to combine just for an exploration.
I made an almost certainly silly thing. It's a #maven plugin to support building #gradle modules in an otherwise maven project. Crazy? Maybe but it scratches an itch of mine. :)
In this post, I’d like to shed some light on my stance regarding #gradle, so I can direct people to it instead of debunking the same "reasoning" repeatedly.
Having now gone through some of the algorithms in the #JsonLD spec in a lot more detail and done more diagramming than is probably healthy, I think part of the problem I (and others) have here is that the @/context object is not (deliberately) typed.
Not as in "it doesn't represent the type," but rather "it has no type of its own to speak of."
It's series of processing directives and almost representing an internal, intermediate state in its own right for the data representation.
The (frustrating) exception to this is how it has a linear-order precedence and the ability to unset things in later contexts, but that aside
If you think of it this way, then it isn't a type and you can't really load it as one productively per se, but it may be a series of typed statements (yes, that has a type, but so does a maven build file in that sense, here have a cookie)
I stopped feeling bad about #autotools files (configure.ac Makefile.am m4/*) when I realized how much noise a new maven package throws on your disk.
The main difference is: for #maven / #npm / #cargo / #gradle / #bazel / ... these are autogenerated.
Maven Central and Gradle Plugin Portal should have never allowed to publish dependencies with not-fixed versions.
If you don't check your transitives carefully, something might sneak in. And you have non-reproducible builds. Which you only notice once something breaks.
#NASA's #MAVEN (Mars Atmosphere and Volatile EvolutioN) mission acquired stunning views of Mars in two ultraviolet images taken at different points along our neighboring planet’s orbit around the Sun.
MAVEN’s Imaging Ultraviolet Spectrograph (IUVS) instrument obtained these global views of Mars in 2022 and 2023 when the planet was near opposite ends of its elliptical orbit.
The IUVS instrument measures wavelengths between 110 and 340 nanometers.
OC Best Website documentation tool?
I am used to Java/Maven which has a command "mvn site". This lifts project information, documentation and analysis to build a website like this....