Yeah they improved it on the AEW, looks far less bubonic.
10,886 karma · joined September 25, 2013
But thank you, I'll google it to know what to look for when I'm next in SF :)
On the subject of top-dressers... ...I was privileged to see a turboprop equipped Fletcher FU-24 in action a couple of weeks ago, those pilots are very darn good at flying very low in hill country. Very loud and notable engine sound.
I also imagine in the postwar WW2 antipodes, steel was a lot easier and cheaper to access, as well as work.
I'm sure if I had just started walking across the crossing it would have reacted perfectly, but I wasn't willing - based on the lack of observable "I have noticed you" cues - to test that theory.
That's why you need documentation to publish to Maven central, that's why your package needs to specify its license, GPG checksum etc.
Yep, it's a lot harder than publishing to Pypi or Cargo, but I'm now firmly of the opinion that it's good that it is. The gates between you and publishing a package are there for deliberate reasons.
> Perhaps you're alluding to the things you can do with JMX
Yep, specifically things like "set the logger org.foo.package.Bla to DEBUG while the app is running", without restarting and without having to add an internal HTTP endpoint to be able to accomplish that. It's just there for free, every JVM logging library and metrics library exposes itself via JMX for that same reason - ease of observability, without restarts, without custom code.
E.g., I can access Kafka client metrics via JMX anytime I like. JConsole will even give me pretty graphs.
If I want them in Prometheus, I run the app with a Java agent that takes those MBean metrics and exports them in Prometheus format on an HTTPS endpoint.
I understand you can accomplish much the same with some internal HTTP endpoints, but that presumes they exist.
If you need them, but that microservice hasn't deliberately exposed them, you need to change the code, and then make a new release, which slows down your ability to diagnose what's going on right now.
In Java, every observability library exposes itself via JMX, all you had to do as a sysop was ensure that the JMX port was open.
Also, the ability to easily observe the metrics of the VM itself via JMX so I can see what's going on with GC in a running app without having to explicitly expose that.
If you suspect a memory leak, or something that should be GC-able isn't, or that there's far too many object allocations occurring that's smashing the first gen portion of the heap and causing excessive GC pauses, the instrumentation to investigate it as your app runs is right there, it's baked into the JVM.
That's why I miss it - the JVM was built to be instrumented and observed by the people running it.
I really wish Golang and everyone else would emulate the Java approach to observable metrics as well as the Java approach to logging and packaging.
There's no shame in stealing the good ideas Java had, but no-one seems to, to my frustration.
Not so much the language (although modern Java is pretty slick), but the stuff surrounding it.
* No typosquatting issues because every package has a group id verified by real humans and DNS TXT records.
* JMX as a standardized mechanism of exposing ways to interact with running code / expose metrics. (Even if you have to deal with the stupid ass protocol where you have to connect using a DNS identity the JMX server recognizes)
* Logging libraries that give people running the code control over what gets logged and how, not the developers (looking at you Golang, wtf is with your logging approach where devs have to explicitly consider the fact that you might want to run logging at DEBUG and code it into your start up args?)
* The ability (via JMX) to set, at runtime, one particular logger in one class or file to a desired logging level without restarting the application.
* The performance of the JVM.
* The vast FOSS ecosystem.
* Not having to fight C build chains for that one dependency that's using CGo or a Python wrapper around a C lib that no wheel supports for your given tuple of Python version, OS, and architecture.
Honestly, as someone who is a self-taught developer who taught himself in Python, I thought I was coming home to my first love.
Turns out, I really hate the horrible things you can do in Python - looking at you Django, don't be so dynamic your brains fall out - and really dislike the experience of trying to run a Go service compared to a JVM service.
Java and its ecosystem is just good at getting shit done in a predictable manner at both the dev level and ops level.
Our butter prices in NZ are ridiculous right now (as our domestic prices are driven by export prices), so I'm wondering if making it from cream would be slightly more cost effective ( assuming my time has no value lol).
The people who did Freakonomics claimed that the drop in violent crime in the US in the 90s could be correlated to the phasing out of leaded fuel, but I'm not a statistician so can't speak to the accuracy of that correlation.
2. How would you even measure that? How would you define a better life thanks to a vehicle?
I feel like you're ice skating uphill a little given the deleterious effects of leaded fuels are well studied, but the question you're asking isn't.
And in my country there's been several ponzi schemes that targeted people through churches, because Dave is such a good Christian, he tithes every Sunday, he wouldn't at all mislead us about this exciting investment opportunity!
I learned a new word today!
Lol.
I'll believe AI is approaching human equivalence when one writes the next great American novel, or becomes superstitious - if you're going to be human level, genuine creativity ex nihilo and/or pattern recognition that overfits into religious belief would convince me.