if drug use is an irredeemable personal moral failure as you cast it, surely you would be similarly unconcerned about anyone who partook once it become normalized; why worry when they'll either count as a junkie to you soon enough by developing noticeable follow-on issues, or they won't, primarily by dint of not having such issues?
a model of the world in which reducing the totality of a person to "junkie" is morally neutral does not seem particularly useful to me in a real-world context, and i would urge you to reconsider ascribing to such.
im not going to stop you from discussing the sturdy nature of digging tools that have thick handles and heavy flat blades , personally im gonna call it a spade and move on , all the best
personally, i like that raku goes the other way, with exported bits of the interface explicitly tagged using `is export` (which also allows for the creation of selectably importable subsets of the module through keyed export/import with `is export(:batteries)`/`use TheModule :batteries`, e.g. for a more featureful interface with a cost not every user of the module wants to pay).
it feels more natural to me to explicitly manage what gets exported and how at a different level than the keyword used to define something. i don't dislike rust's solution per se, but if you're someone like me who still instinctually does start-of-line relative searches for definitions, suddenly `fn` and `pub fn` are separate namespaces (possibly without clear indication which has the definition i'm looking for)
Actually, a module can implement any export heuristics by supplying an EXPORT subroutine, which takes positional arguments from the `use` statement, and is expected to return a Map with the items that should be exported. For example:
sub EXPORT() { Map.new: "&frobnicate" => &sum }
would import the core's "sum" routine, but call it "frobnicate" in the imported scope.
Note that the EXPORT sub can also be a multi, if you'd like different behaviour for different arguments.
neat! i've never needed more than i could get away with by just sneaking the base stuff into the mandatory exports and keying the rest off a single arg, but that'll be handy when i do.
out of curiosity, what else would you expect the side effect profile of something mediating the effects of a potent androgen on the body to look like?
it's not estrogen where you would expect breast growth (and can't count on any particular changes to sexual function anyway), it's inhibiting conversion of testosterone to dihydrotestosterone which could have that effect, much like you could spontaneously develop gynecomastia without intentionally fiddling with your hormone balance. calling it unsolved sounds a lot like calling the very many conditions with medications that have more likely and worse side effects equally unsolved.
> what else would you expect the side effect profile of something mediating the effects of a potent androgen on the body to look like?
I'm a consumer, not a medical professional. I have no expectations based upon detailed familiarity with the underlying biology. Or is the target market for these products medical professionals?
That's what the patient information sheet is for, and why everyone's supposed to have access to a trained medical professional they can freely consult for things like this.
> it's not estrogen where you would expect breast growth
Actually, it is. Reducing DHT levels causes the body to elevate both testosterone and œstrogen levels, via homeostasis. But yeah, it's not a direct effect, and if it's a problem you can twiddle further to make it go away. (You could even do that pre-emptively, though you normally get days and days of warning before breast development actually starts, so I'd advocate the "wait and see" approach.)
A condition is typically considered solved if there are drugs or procedures that cure it and either (a) have extremely rare side effects, or (b) have side-effects that are not as big a problem as the condition they are curing. If a pill existed that cured trh common cold but had a 1% chance of giving you cancer of the throat, people wouldn't proclaim "we've cured the common cold!".
i believe the point is more that bootstrapping a higher-level programming environment up from machine code shouldn't be the sole domain of so-called genius. a forth basically writes itself once you know how the execution model works, but these days we don't focus on teaching the end to end skills required to take arbitrary hardware and target it with a new, simple language.
This; it's not rocket science. I am no university educated (maybe something compared to a community college) and yet understanding how a Forth and/or a Lisp bootstrap themselves from small cores it's something every programmer should experience at least once, even from books. If SICP for Scheme and the ones for Common Lisp are too complex, the author from https://t3x.org has two or three for scheme, one of them for almost a micro Common Lisp (less than Elisp actually), a Forth and several more. Oh, and the code runs on 8086 PC's, Unix and some of them even under CP/M 2.2. It's crazy, and eye-opening too.
With a Forth you can literally see how floats are built from 'integer' blocks in RAM. Heck, you can even see how floats are done by using integer and string related words (printing them) . And you can see the 'odd' integer based stack in a live way with once your entered a double or a float. Binary representation in the spot.
I'm familiar with SICP and t3x. Sorry if my statements made it sound like only a genius could figure this out. I think most coders I know are just trying to solve a concrete problem with the existing building blocks. Really smart (or interested) people tend to go a bit broader and deeper. I don't think HN folks are very representative of the overall coding industry - not even close.
> Case in point, just look at how Newgrounds famously had a ton of games about shooting Muslims after 9/11 and mimicking South Park’s sense of humor. If you build the old internet in 2024, it’s not going to be the same as the old internet, because the people aren’t there. Or worse, you’re not allowed to be that anymore.
rather than say anything likely unconstructive myself in direct response to this, i would very much like to see you elaborate on your understanding of mao and what value and predictive power you find in this comparison.
Maoism and Trumpism share a certain self-sabotaging ideological fetish for the virtues of rural life that expresses itself politically more in destructive resentment of urbanites and urban institutions than productive development of rural ones.
I've seen people use the USSR hammer and sickle for the O in GOP.
It's from people who think horseshoe theory has legs: that wanting to shut down prisons is the same as wanting to build concentration camps or that the people who want to say nationalize the banks are also the people who want to privatize the post office.
It's from centrists being unable to understand this difference
coming back to raku after basically any other language is a breath of fresh air. i haven't even been worrying much about when the ast stuff lands cause i can't think of anything i would even want to mess with that much, even though i seem fundamentally incapable of engaging with lisp/prolog/forth without giving in to the siren song of metaprogramming. to me that's a very strong sign of how much it gets right as a base language.
i do all my automation with one tiny 20 line raku script that manages a thousand things. hell, the entire monitoring site for our frog is basically just a pile of mixins with a neat little pipeline interface unifying everything from request profiling and html templating to reading from and filling that cache in parallel whenever it remotely pulls the sensor data off various things and gets the current webcam frame.
PA Dutch at home but they are certainly taught English in their schools, they do in fact interact with their local communities and would need to know it.
neat how you always have to dig in yourself in order to find out whether or not "sex-dependent" means chromosomal or endocrine differences. good thing those are in perfect lockstep or else we'd have to worry that we habitually gloss over such salient aspects.
reply