> mostly nothing to do with technology or with support costs
Support costs aren't zero though. I work for a company with a lot of corporate customers and we get loads of SSO support tickets. People are always misreading the docs, (mis)configuring things against our recommendations, migrating systems, merging systems (due to acquisition etc)...
Of if you are on Air New Zealand and can't afford business class you can get a Skycouch in Economy. They're pretty great, actually, unless you're over 6ft tall or can't sleep with you knees bent a bit
Your local library probably has a copy of Nature’s Metropolis, a very well-written, information-dense book that captures much of the reason why it was Chicago rather than, say, St. Louis that became the important link in the railroad system. (In the mid 18th century France and the UK concluded a treaty that made the ‘Illinois Country’ off-limits to Europeans. It depopulated and most people moved to St. Louis. By the time Chicago was much more than an Army fort and a dozen houses, St. Louis was a 100-year old large city).
They've removed it from their pricing page now, but when they announced the discontinuation of the regular on-prem server the minimum for datacenter was like 500 licensed users or something along those lines.
In any case it was clear it's not for small shops like us.
That said, air-gapped is a hefty requirement, so perhaps those customers are predominantly large?
I still run an old version on an air gapped network and will continue to do so until we're forced to change for some reason. It's not a hefty requirement; we run it for a team of < 10 developers on a small VM and it just works.
> That said, air-gapped is a hefty requirement, so perhaps those customers are predominantly large?
There are lots of very small classified networks out there with only a few dozen users.
There are a lot more user communities course that aren’t necessarily airgapped, but where they have special compliance requirements that pretty much mandate self hosting (or at least bring-your-own cloud.)
We took a different approach with Plane's air-gapped offering. No minimum user requirements at all. We evaluate based on your use case and domain requirements, not team size.
We do the similar with our B2B product (in an entirely different niche). We have everything from single-person companies up to very large ones. Similarly we set price based on use-case and requirements.
There has historically been massive investor and shareholder pressure for companies to show "Cloud Recurring Revenue" and multiple wall street analysts will start issuing higher price points for your stock based on this, and eventually large institutional investor adjust their positions accordingly.
I like the cloud for a lot of reasons. But, making your software worse to make your stock price higher seems like a loser for everyone long term.
It might as well be for the vast majority of companies, since I believe the smallest number of users you can buy support for is 500.
To be more specific, they killed off the legacy Jira Server and now only offer these enterprise versions of Jira and the rest of the suite if you won't move to the cloud.
That exact phrase "What is 75 degrees fahrenheit in celsius, and what is 85 degrees in fahrenheit" given to ChatGPT produces the correct result (it infers that the second degrees must be Celsius) and ChatGPT gives me a nicely laid out formula for the math of the conversion.
Sleeping on the back only matters when they are very young. It’s for when they don’t have the strength to turn themselves out of a face-down / suffocating position. That’s why you practice tummy time (neck/head lifting) with an infant. Once they are older they can sleep how they like
Depends on the kid too. All 3 of my kids could lift their head up when they were born. A couple of times I forgot all babies aren't like that and picked up a friend's baby without adequate support.
For the AirGradient device I think the way to calibrate CO2 is to expose it to fresh air at some point, which has a known CO2 level. It’s supposed to auto-calibrate. But if you don’t do that regularly then the readings will drift (without anyway of telling they’re drifting). You also can’t tell when the sensor has calibrated.
IIUC VOC is way more complicated and hard to both calibrate and interpret. I’m not sure I have any faith in that value.
I do think a lot of people are going to be mislead by these monitors, the sensors and devices come with a bunch of caveats that aren’t clearly communicated.
For me what people should most care about is particulates, and at least as far as I know those sensors don’t come with the calibration issues of CO2 and VOC. That’s the sensor my AirGradient is set to alert on.
I was worried our sensors had that autocalibration mode. Our house has new concrete floors. They alternate between absorbing + outgassing CO2 (depending on room temperature), so sometimes our living room reads below 400 ppm.
From what I can tell, the sensors haven't drifted, so they're not using the "below 420 ppm => recalibrate" heuristic.
Provided they don’t get too much sun, because those dense plastic planks get much hotter than wood (I’ve measured 65C on mine). A deck is not much good if you can’t stand on it.
I think some of the Trex looks pretty good, they're definitely not all the same. If you do go this route then you will need an outdoor rug on the planks if it gets direct sun though. They're just way too hot otherwise, as you've stated. But throw a nice outdoor rug down and it's problems solved.
Which is also why it’s critical that they be installed with a gap between the boards (Kreg makes a useful set of spacers and drill jig to hide the screws). Otherwise expansion will destroy the deck.
Oh, mine have spaces and all (the very-expensive, not-optional mounting clips create the requisite spacing). They're just hot. Google "composite deck heat" etc will find lots of people complaining about it.
Not easily. There's no built-in way to access the abstract syntax tree (or equivalent) of a function at run time. The best thing you can do is to obtain the source code of a function using `.toString()` and then use a separate JS parser to process it, but that's not a very realistic option.
There is a limited form of such "expression rewriting" using tagged template strings introduced in ES2015. But it wouldn't be particularly useful for the ORM case.
That's on quicklisp, not Coalton. Honestly, quicklisp is one of the worst parts of CL nowadays (right after the lack of coroutines[1], which is by far the worst offender.) It should have been replaced a long time ago. ASDF3 provides a lot of flexibility, and quicklisp uses maybe 15% of its capabilities. There are reasons why it's still so bad, but it gets less and less excusable each year :(
[1] Does anybody know how to ping Kartik Singh about the coroutines implementation in SBCL? Apparently, he made an experimental port of the green threads implementation from CMUCL, but I can't find it anywhere online, nor any obvious way to catch anyone involved. Is the mailing list the only way?
Thank you!! I was very interested in `convert-thread-to-coroutine` - I saw it on the ELS presentation, and when I went spelunking in the CMUCL codebase, I found the prototypes for `fork` and `resume`, but (probably because CMUCL is single-threaded?) nothing that would suggest how that `convert...` should look like.
Why is there so little interest in green threads/coroutines in CL community? cl-cont really isn't something to point to when asked about C10K problem... or yield/yield*... or async/await...
There's great interest for it, not little. The challenge is who can do compiler programming, add a production ready implementation as contrib SBCL package, and maintain it?
Hm, my impression is based on the lack of posts or articles with people demanding this to be a feature. I searched, and it just doesn't seem to come up in discussions, and when it does, it's invariably about cl-cont and problems with it.
The first implementation doesn't need to be production-ready. And the maintenance burden (along with polishing the implementation and porting to other architectures) could be shared by a few people and done over time. Having a starting point in the form of CMUCL code (already adapted to SBCL!) is the perfect opportunity for everyone interested to chime in: enough voices in favor could convince someone capable to continue the work. Yet, there are literally just 3 comments under the ESL presentation video, and it's not mentioned anywhere else...
It's mentioned on X and Discord plenty, but you're right about cl-cont.
The first few steps would be building on top of this work and reaching out to the SBCL maintainers via the mailing list to see what it takes to get this merged in.
Support costs aren't zero though. I work for a company with a lot of corporate customers and we get loads of SSO support tickets. People are always misreading the docs, (mis)configuring things against our recommendations, migrating systems, merging systems (due to acquisition etc)...
reply