Whatever idea you have about how black Americans live is bizarre. And despite being ignorant of us, you attempt to silence discussions by acting like you are us.
> It had been assumed that Byfield died around 1850, but O'Keeffe's discovery of the veteran's 1851 memoir, along with additional evidence from newspapers and archives, adds new chapters to his astonishing life story.
I hate to be obnoxious, but what O'Keeffe did was happen upon a rare book in a small library the he recognized had been written by a semi-famous author. Instead of scanning it (or having it scanned) and putting it on archive.org, then writing his article, he's actively concealing these "new chapters" from the world. My assumption is that he's planning to put it into print in order to make a few bucks.
According to the Google Books entry (which I don't quite trust, because why would there be a Google Books entry?), it's 80 pages, so he'll either have to write a hefty introduction of what seems to be a story about a disabled vet talking about Jesus, or he'll combine the war narrative and the post-war narrative (both obviously long out of copyright) into a single volume and hawk that, and the article he's written will be the introduction.
I guess I advise him to self-publish and to make sure to also target Christian bookstores rather than just academic libraries? Survey a brick and mortar Christian bookstore of possible and get an idea about what covers sell?
Indeed. Don't think anything is being "concealed"! The rediscovered memoir has been transcribed and made available at the link posted above, while the full research seems to be available without a paywall here: https://www.cambridge.org/core/journals/journal-of-british-s...
This is really my priority to achieve at a job, and one of the reasons I try to be good enough to be indispensable is to be allowed to roll in in the morning whenever I get there.
I have a very tough time in the morning convincing myself to go to work, and a very tough time at work tearing myself away from something in an intermediate state. Things at work are always in an intermediate state at 5:00, unless you stopped working well before then (or got very lucky), so I always end up working late whether I come in on time or come in late.
So I'm always trying to get to the point where management lets me get there when I get there, and trusts me to be productive. It's a mental thing. I get up early and do a lot in the morning; I'm a morning person. Maybe too much so. The time between getting off work and going to bed is garbage time for me; a long annoying commute and a meal. When I leave at 5:00 I just fall asleep by 9:00.
No. As you've made clear, it's a question of being able to express things in a way that gives more information to a compiler, allowing it to create executables that run faster.
Saying that a language is about "expressability" is obvious. A language is nothing other than a form of expression; no more, no less.
Yes. But the speed is dependent on whether or not the compiler makes use of that information and the machine architecture the compiler is running it on.
Speed is a function of all three -- not just the language.
Optimizations for one architecture can lead to perverse behaviours on another (think cache misses and memory layout -- even PROGRAM layout can affect speed).
These things are out of scope of the language and as engineers I think we ought to aim to be a bit more precise. At a coarse level I can understand and even would agree with something like "Python is slower than C", but the same argument applies there as well.
But at some point objectivity ought to enter the playing field.
> ... it's a question of being able to express things in a way that gives more information to a compiler, allowing it to create executables that run faster.
There is expressing idea via code, and there is optimization of code. They are different. Writing what one may think is "fully optimized code" the first time is a mistake, every time, and usually not possible for a codebase of any significant size unless you're a one-in-a-billion savant.
Programming languages, like all languages, are expressive, but only as expressive as the author wants to be, or knows how to be. Rarely does one write code and think "if I'm not expressive enough in a way the compiler understands, my code might be slightly slower! Can't have that!"
No, people write code that they think is correct, compile it, and run it. If your goal is to make the most perfect code you possibly can, instead of the 95% solution is the robust, reliable, maintainable, and testable, you're doing it wrong.
Rust is starting to take up the same mental headspace as LLMs: they're both neat tools. That's it. I don't even mind people being excited about neat tools, because they're neat. The blinders about LLMs/Rust being silver bullets for the software industry need to go. They're just tools.
There was a long period of time during which firefox users weren't sure whether they were going to follow chrome (like they did on every single other thing.) They're still user-hostile and their values are inscrutable; I have no trust that they won't kill ad blocking next year, or the year after. Requiring add-ons to be signed was a more radically hostile leap than moving to ManifestV3 would be.
The people still complaining about firefox are its most faithful users. The reason some are vicious is because they are trapped - they'll consider cutting their use of the internet before using an non-FOSS browser. 90% of firefox's users left. People who could stand a closed browser have already decided to use one. You're in an extreme minority if you even know anything about firefox to complain about. This year the Linux desktop, of all impossible things, has become more popular than firefox.
Yet there's still this confidence and attitude about even the remaining users that comes from being spoon-fed cash by your direct competitor in return for nothing.
> There is always a pile on on Firebox for not being perfect.
Nobody has ever complained about anything not being perfect. That's just something dishonest people say when they want to avoid mentioning specific criticisms.
But the second paragraph doesn't have any of those specifics. It's just any algorithm (an actual ban on forbidden math), software, tool, technology, service, or device.
...when the primary purpose of that algorithm, software, tool, technology, service, or device is to produce an individual’s photograph, voice, or likeness
i) without the individual’s prior consent [...]
ii) with intent to cause harm [...]
you need to read it together with the two sub-clauses, which make it much more selective (and a lot more reasonable!)
reply