we have multiple former Nike missle sites here in Anchorage. in a modern day city park, you can check out a missle stabilizer on interpretive display at the former launch command center turned cross country ski chalet. there are doors in that building that are like time portals to tha past. you go through an unassuming modern commercial steel door from a room where kids gather before weekly lessons into a world of concrete hallways with enormous blast doors welded open and narrow staircases leading down to lower levels with remnants of launch and other equipment.
I would caution against assuming that anything related to commissions is actually customary, including an even split. All of this really is negotiable, and when I think about the past year, I've seen multiple occasions where different splits were offered. For example - I referred some business to an agent in Tennessee, who in order to pay my referral* convinced seller to offer a lesser split to the buyer's agent. I know of at least one agent in my market who does similar. I know of another agent who charges at least 10% on any land deal, while others are flat-fee.
* If I were a member of the public, I'd be more upset about referral fees than commissions. This is a far more grey / nebulous area of real estate compensation. We have to disclose and discuss commissions up front, but referral fees are often in the shadows and definitely can cause buyers / sellers to pay more.
yep, agreed. I know and have talked to some brokers about this in the past, and also closed a few deals as both a buyer and a seller. The commission was split evenly in my experiences but I should have said ‚typical‘ even if only as a starting point in negotiations.
One example of a framework that takes this approach is Apache Royale. It’s a reboot of the AS3 language and component library that works like Adobe/Apache Flex but compiles to JS targeting the browser runtime. This refactored Flex was rebuilt from the ground up with a Pay As You Go (PAYG) philosophy where components are composed of „beads“ on a strand that enable composition of the functionality you need rather than the kitchen sink.
I loved „Glide“ floss for years because it worked so well. Was totally dismayed when I finally put together why it did. I‘ve switched to Dr. Tung‘s now which is made of natural plant-based materials and works even better than traditional flosses.
Yes, that’s actually the thing about branching in SVN. Everyone remembers how awful it was 10+ years ago under SVN 1.4 and earlier but has improved immensely since then. Combined with modern client tooling, i.e. TortoiseSVN, problems with merging are almost non-existent for a long time.
I certainly wouldn’t call SVN modern but it’s very well maintained and has never lost code on me. Many git-like features also exist now such as being able to stash some changes in order to pivot to something else for a bit. Except for the central server being a problem for some use-cases, SVN just works.
We have various Supermicro boards in production at work with BMCs from 2018 or so. The ATEN iKVM on them works just fine with a recent OpenJDK 11 and OpenWebStart. I’ve found that all the features work including mounting ISOs and doing remote upgrades. No need to whine about installing anything ancient or spreading ridiculous Java FUD.
Sysadmin for 15 years here though, Java was always a problem. The version wasn't always the worst bit, but it was always an exercise in frustration.
Mostly security controls to blame, but I have had so many issues across so many systems that I cannot stand by and let you claim this is FUD about Java.
the .NET applets are also a problem (because who has a compatible IE version?), but they worked more consistently than the Java ones back in the day.
The HTML5 ones are the only ones that seem to work consistently; but that could be biased as HTML5 is much newer, so BMCs implementing that might be updated with more regularity. (or be more modern hardware)
With current browsers Java applets are not supported anymore. Some older HPE systems the didn't update the firmware to provide alternatives.
I've seen multiple vendors with problematic code that didn't work with newer Java versions.
This is by no means meant to bash Java. Some non-Java BMCs can be horrible as well (e.g. require many TCP ports in a firewall/tunnel unfriendly way or require SSH with old algorithms that are no longer enabled by default, or telnet..)
I‘ve really only had experience with Supermicro BMCs but I totally believe you that there are lots of crufty OOB environments in the wild which are hard to work with. While it’s true that applets don’t work anymore (probably a good thing), and therefore the experience isn‘t as integrated or seemless as it once was, it’s a practical matter to just log into the BMC and click on the console preview, using the JNLP file to launch the console via OpenWebStart as an independent application outside of the browser. One other thing is that the self signed certs from these older implementations are often expired and therefore throw an extra warning or two when you launch these interfaces, but you just click through them and carry on.
the "CH" line of waxes (CH4/6/7/8/10) are not fluorinated. The waxes that start with LF or HF (low-fluoro and high-fluoro, respectively) are the fluorinated products.
you probably don't need to worry about handling LF or HF with gloves, it's not that toxic. but if you're waxing with them you should be wearing a respirator.
Yeah ... about that. The CH wax dust isn't good respiratory-wise either. As an avid Alpine skier I used to hot wax, scrape then use the drill mounted rotary brushes pretty much every weekend until I discovered wax "dust" in my coffee! (early morning tuning!). I'd usually tune late at night I guess I never noticed the wax in my beer can/bottle! That was the last time I used them.
Now I use the Pro-Glide from SkiMD, rather than hot-waxing, scraping and brushing, you crayon the wax on cold then use it as a friction device to "melt" the wax in with some very light brushing. Much much quicker, uses far less wax and produces very little dust, highly recommended:
I never really used Fluro-based waxes because it doesn't last long and the guidance was that you needed to "get it out of your base" after racing as it supposedly did long term damage to the ski.
CH doesn't have fluoro, but the correlation between C6/C8 and LF/HF is unclear to me. Does LF use C6 and HF uses C8, or can both wax types be made with C6/C8, but in different concentrations?
