Go has a heavy runtime, including both a garbage collector and a userland scheduler. Those features both make it inappropriate for some applications where you would use c, and also make calling (and especially being called from) foreign code problematic. You effectively cant implement a library in go and then call it from another language, not without considerable ffi overhead at the very least.
42 videos on his car review channel plus 13 videos on his main channel (a few might be crossposted) plus a couple tesla reviews from several years earlier than the others.
Which does not mean he's qualified to review cars.
There's been a huge trend in the last 5 or so years for corporations to go to "influencers" like Brownlee because they're ignorant and uninformed to the depth the industry press are.
This has been going on for a decade with shitty kickstarters for bicycle accessories which had to be kickstarted because the designers couldn't sell the idea to any existing companies, get funding, secure distributorship, or all of the above, because the industry knew their idea was shit.
Nowadays it's fly-by-night e-bike importers who hire a firm to do some high-end looking branding and import some shitty e-bikes with some gimmick (for a while it was lightweight single-speed ebikes, for example), last just long enough to sell a bunch, ship out replacement parts at the drop of the hat to keep early adopters happy and then evaporate as the bikes really start to break down and the brand's reputation tanks.
Brownlee knows a lot about cell phones and cameras, but his knowledge in the automotive industry is shit and everything he puts out is tepid and "safe". He regurgitates the press packet, follows the standard "nice things to say but a few subjective criticisms/opinions to make it seem impartial", and that's a wrap.
Look down his list of videos: "the Bolt EUV is the best deal in EVs!" "The Kia EV9 is surprisingly good!" Whoa whoa Keith, don't get too controversial!
> Which does not mean he's qualified to review cars.
At the age of six I knew my mom’s meatloaf sucked. For some things in life, you don’t need to be “qualified”.
You don’t need to be a Certified Gearhead to know that a backup cam that doesn’t work half the time contributes towards making a car experience crappy.
In fact it can be good to have “normie” opinions and reviews. Some things are meant to be refined tools used by the general populace.
it's maybe negligible compared to the code-size bloat of web applications, but delivering large libraries over the network with only limited caching is less than ideal
At least in English, typographic conventions have historically equated underlining with italics, and the reason the underscore key is present on your keyboard is because it was used on typewriters to format text that would have been italicized in printed text.
Surrounding text with underscores to indicate italicization is intuitive to anyone who is familiar with that convention.
Personally, I find surrounding text with forward slashes exactly wrong for italicization, because I mentally apply a skew-transform to the text to make the slashes into vertical lines, which leaves the text itself slanted in the wrong direction. Backslashes would make more sense, and also avoid looking like regular expressions. But literally no one uses that convention and we do not need a new one.
I've described what intuition is, you haven't addressed it, familiarity with convention is not intuition, it's just knowledge. And given that convention is unintuitive (_ for underlining would be, and on typewriters underscores were also used to, you know, underscore text), that's a bad convention
Also, this /convention/ already exists and used, despite its low popularity (eg orgmode or Bear note app), so you're also literally wrong here
He said the convention that doesn't exist was -backslashes-.
Also, intuition is "understanding without conscious reasoning," so remembering a convention IMO counts.
Consider e.g. parental intuition of noticing subconsciously it's too quiet and immediately going to find out what the kids have done.
For UI, consider the floppy disk icon often used for 'save' - it's considered intuitive because the vast majority of users already recognise it without having to think about it, even if they've never had a system with a 3.5" drive themselves.
"Intuition is the ability to acquire knowledge, without recourse to conscious reasoning or needing an explanation" per wiki
The convention is the precise rule that _ is italics, so no, you aquire no knowledge, you need to already possess that knowledge and remember that precise rule.
On the other hand, if you know that _ is __underline__, - is --strikethrough--, then you can acquire knowledge (guess) that / is /italics/ because the principle is the same - formatting text follows symbol's shape (though it's not a perfect mach since / transforms text, not adds new symbols unlike _ or - ). But that's still intuition (* for bold would not fit here)
The other bad analogies don't help resolve it, so best stick to the topic
From my point of view, you acquire the knowledge that this system also follows the convention by guessing that it does and trying it (though I was quoting a dictionary rather than a wiki; I usually do for word definitions).
I appreciate that you don't find the analogies convincing, but they do express how I (and many others) see the situation, and declaring it a failure to stick to the topic because it doesn't fit how -you- see things is unconstructive at best.
memory safety doesn't mean just one thing, but probably it requires either a lot of rust-like features, a tracing garbage collector, or automatic reference counting.
the language being small enough that all basics can be grasped in a day
that disqualifies taking the rust-like path.
able to use all c libraries through ffi. without loss of performance or extra fu.
that disqualifies most (all?) advanced tracing gc strategies
it must not have massive pauses or stop the world GC.
that disqualifies simpler tracing gc strategies
depending on what precisely you're looking for, it's possible it might be a pipe dream. but it's also possible you'll find what you want in one of D, Nim or Swift. Swift is probably the closest to what you want on technical merit, but obviously extremely tied to Apple. D and Nim strap you with their particular flavor of tracing gc, which may or may not be suited to your needs.
I don't care to sit through sponsor reads, nothing more to it than that. When I'm viewing on a client that doesn't support sponsorblock, I'll manually seek to the end of the segment. Supporting the creator is great; I pay for YouTube Premium, though thanks to uBlock Origin I wouldn't see the add if even if I stopped paying. To a couple creators, I send a regular donation. If I could spend another $10/mo to make up for any revenue my sponsorblock usage loses other creators, I'd do that, but I'm less enthusiastic about regularly listening to sales pitches for the same products over and over again.
Also: I'm not sure how common it is for YouTube sponsorship contracts to have payment contingent on the view count for the section of the video with the sponsored segment, and I'm not sure if the way sponsorblock skips such segments is visible to YouTube's analytics. With at least some of the most prolific sponsors of creators I watch (Audible, Brilliant, etc) the payout is based on how many viewers sign up for a trial through the affiliate link. And YouTube has no incentive to make it easy for creators to share their detailed analytics with third-party sponsors, since independent sponsorships cut YouTube out of the deal. YouTube would prefer creators replace their independent sponsor reads with mid-roll ads.
That idea of a universal/generic VM supporting many languages has been tried many times, with limited success
What wasm is doing is something different than previous efforts. The gc facilities aren't provided for the sake of interop with other languages, or for the sake of sharing development resources across language runtime implementations. Wasm is providing gc facilities so that managed-memory runtime languages can target wasm environments without suffering on account of limitations imposed by the restrictive memory model, and secondarily to reduce bundle sizes.
Wasm can potentially support more tunable gc parameters to better suit the guest language's idiosyncrasies than can other general purpose language runtimes. And unlike the runtimes we're comparing it against, language implementers don't have to option of making something bespoke.
I had a hell of a time a few months ago debugging why my child processes were dying, before learning that PDEATHSIG=9 (don't ask) kills child processes when the thread that created them in the parent process exits.
My debugging was not aided by the fact that disabling the code where I set PDEATHSIG had no effect, since someone else's code was invisibly setting it regardless.
I'm a little rusty here, but I think you are talking about the fact that the exit status of the child process has to remain available until the parent process can reap it. Until that happens the child process is in the zombie state. You indicated that the creating thread needed to exit, but that seemed a bit too specific to me, I think that any thread can reap the exit status of a child process.
Related to this is the double-fork pattern to avoid zombie processes (and a couple other issues) when initiating a daemon process.
The surprising behavior was that the child process received the configured signal not when the process that created it exited, but rather when the specific thread that called fork(2) exited.
The parent process was an event loop based python program whose main function was to manage the creation and deletion of these child processes, and the simplest way to spawn child processes without blocking the event loop is to call fork(2) on a thread pool. My thread pool was triaging the number of worker threads based on demand, so occasionally it would decide a worker was no longer needed, and all the child processes that happened to have been created on that thread would get SIGKILL'd — something you rarely want when using a thread pool!
I didn't want the child processes to die unless the parent process's business logic decided they were no longer needed, or if the parent was itself killed (this latter reason being the motivation for setting PDEATHSIG).
Once I understood why my processes were dying, the solution was simple: make sure the worker threads never exit.
No, what they're talking about is the fact that in Linux, sometimes "process" in the documentation actually means "thread", and this is particularly true if you're doing mildly funky process management APIs.
Are you quite near to where he was in 2014? He said in the article that he lived (at time of writing) in a pretty conservative area:
> I live in a Republican congressional district in a state with a Republican governor. The conservatives are definitely out there. They drive on the same roads as I do, live in the same neighborhoods. But they might as well be made of dark matter. I never meet them.
I agree with OP that it's much more likely that he did meet them, just in contexts where it doesn't come up.
I think that was because he was doing his residency in a place where he would not normally choose to live.
As typical, during that time he was probably so overworked he didn't really interact with any of the locals until his time was up and he moved back out to a self-selected community.
It might not be that these topics just "don't come up" like it's some kind of accident. When people hold these "weird beliefs" as he puts it, [I think] they generally know they are weird and would be embarrassed to bring them up.
I don't think I know any Flat Earthers, but if I actually do, they probably deliberately keep it to themselves because they know that they'd look like kooks by outing themselves. To get more extreme, maybe some of my friends are Nazis, but they sure aren't showing me their memorabilia, not because "it just doesn't come up" but because they know it's wrong and don't want to ostracize themselves.
Maybe eventually people work up the courage to probe a little, they'll use code words and innuendo, and soft dogwhistles, maintaining plausible deniability until they identify their fellow outgroup members. I think I see this behavior in a few of my friends, but they wisely don't come out with it.
Culture war topics being literally banned on /r/ssc combined with that community's imperfect ability in "keeping it together" when some conversation does sneak in leads me to believe that it would be extremely easy to be never found out if you were among them.
