1,526 karma · joined August 24, 2022
>We definitely can’t open source Unreal Engine 2 or 3, because of dependencies on a large number of external closed-source middleware packages with complex licensing requirements.
>Open sourcing Unreal Engine 1 might be possible, but getting the source and dependencies into a releasable state would take a lot of cleanup effort that we just haven’t been able to find time for. I hope we can do it someday. [0]
[0] https://forums.unrealengine.com/t/unreal-engine-1/14084/6
>Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
Source for this claim?
It's a hypothetical.
>China? Really? ¯\_(ツ)_/¯
You mentioned billions of people. So your argument was clearly not limited to the US. Or you just didn't make the point well.
>which you and op are attempting to distort by cherry-picking definitions from various dictionaries, often focusing on the less common usages found at the bottom of these entries.
One of the dictionaries is an ESL dictionary. It gives words as they are used and it gives the usage I quoted as the first definition.[0] The reason that the usage in the other dictionaries have the usages I quoted at the bottom is becasue they all give the noun form of "force" first.
[0] https://www.oxfordlearnersdictionaries.com/us/definition/ame... (force_2 being the verb form as opposed to the noun.)
The first edit I mentioned is in this comment chain and the second one was in response to my post in a different chain.
>Nobody forced anyone to get vaccinated
Really? This is trivially false. For example vaccination was extensively mandated in several countries by law, for example some provinces in China.[0] In the US certain states require proof of vaccination for certain activities. For example in New York vaccination is required to go to school.[1] Perhaps you meant "not all people were forced to get vaccinated?" That is not being debated here. In any case I never even made an argument about this point until now. And in any case I don't feel too strongly about whether "force" is the right word to describe vaccine mandates. My only points were that if your boss tells you you'll lose your job if you don't have sex with him he has forced you to quit (assuming you cannot get him fired, for example if you have no proof he said that and will continue harassing you) and secondly that "forced to trust" is not complete nonsense.
>You seem to have another agenda here
You're the one that tried to say that a boss extorting sex isn't considered forcing you to quit your job in order to maintain your position. My point was actually fairly clear and not even about vaccination.
>One is rather clear and the other one is nitpicking to get an agenda across.
I would agree except you're not even nitpicking you're just claiming that whatever you decide "force" means is the one that OP must hold by as opposed to "throwing dictionaries" at the problem.
[0] https://doi.org/10.2147/RMHP.S336434
[1] https://www.health.ny.gov/prevention/immunization/schools/sc...
You edited "No, words have meanings" to "No, words have specific meanings that should accurately reflect the nuances of the situation at hand." You also edited "So?" (single word) to 'So? "Force to trust" like op wrote made absolutely no sense.'
>for me it still stands as long as you have agency over yourself nobody can force you to do anything.
It can and often does mean that though. Here's a list of 170,000 books using the phrase "forced to trust"
https://www.google.com/search?tbm=bks&q=%22forced+to+trust%2...
>to make something happen or make someone do something difficult, unpleasant, or unusual, especially by threatening or not offering the possibility of choice[0] (notice or here)
>If someone forces you to do something, they make you do it even though you do not want to, for example, by threatening you.[1]
>to make someone do something that they do not want to do
>I was forced to take a taxi because the last bus had left.[2]
[0] https://dictionary.cambridge.org/us/dictionary/english/force
[1] https://www.collinsdictionary.com/us/dictionary/english/forc...
[2] https://www.oxfordlearnersdictionaries.com/us/definition/ame...
>violence, compulsion, or constraint exerted upon or against a person or thing[0]
Compell:
>1. to drive or urge forcefully or irresistibly
>2. to cause to do or occur by overwhelming pressure[1]
>The initial version of Sheets Wasm showed calculation performance roughly two times slower than JavaScript.
>[...]
>Implementing speculative inlining and devirtualization—two very common optimizations—sped up calculation time by roughly 40% in Chrome.
So the only numbers we get are 2x slowdown and the 1.4x speedup, which makes it sound like it's still slower. I'm sure thats probably not the case but it is a strange way to write an article advertising wasm.
Also, I'm a bit confused about which language this was actually written in before the wasm switch. Was it always written in Java and transpiled to JS? It doesn't seem that way from the article:
>Removing JavaScript-specific coding patterns.
>they had a core data structure in Sheets which was blurring the lines between arrays and maps. This is efficient in JavaScript
which doesn't make sense if they were writing it in Java and transpiling to JS.
Was it transpiled to JS only once in 2013 and then developed in JS from there? In which case why go back to Java?
>Therefore, MSC-based bone regeneration is considered an optimal approach [53]. [0]
>MSC-subtypes were originally considered to contain pluripotent developmental capabilities (79,80). [1]
Both these examples give a single passing mention of the article. It makes no sense for thousands of researchers to go out and remove these citations. Realisticly you can't expect people to perform every experiment they read before they cite it. Meanwhile there has been a lot of development in this field despite the retracted paper.
[0] https://www.mdpi.com/2073-4409/8/8/886
[1] https://www.tandfonline.com/doi/full/10.3402/jev.v4.30087
What is the practical difference here? MCMC itself samples more from higher probilities than lower ones (ie. towards a local minimum). Is it just that we sample more from lower ends of the distribution? Or is it more about formalizing the previous algorithm so that it is easier to play with the different parameters? (eg. the acceptance threshold)
.
RK3588 upstreaming project: https://www.collabora.com/news-and-blog/blog/2024/02/21/almo...
Risc-V JH7110[0] upsteam status: https://rvspace.org/en/project/JH7110_Upstream_Plan
[0] used in https://www.starfivetech.com/en/site/boards
I agree but the FDA might not have the legal authority to ban chemicals that are already in use that haven't been proven to be harmful. That is the case with the EPA IIRC. Although I think there actually is a lot of evidence pointing towards phthalates being harmful especially in utero.
Maybe it should be even less descriptive.
"This message will soon no longer be available. Make sure you copy the contents of the message before you discard if you want to use them later."
Talking about the cache doesn't help the user. Really the solution is to add a button at the end of the message that says "save message contents to device." Then the message is clear and easily actionable.
>RISC-V not only isn’t that on a technical level but is fighting some serious fragmentation.
Do you have any evidence to support this? Seems like RVA23 will be the first majorly supported extension. All the "high performance CPUs" right now are just dev kits, so I don't see how there can be fragmentation in a market that does not yet even exist.
[0] https://github.com/riscv/riscv-profiles/blob/main/src/rva23-...
[1] https://opensource.googleblog.com/2023/10/android-and-risc-v... (note: the blog mentions RVA22 but this has most likely been switched to RVA23 before full Risc-V support lands in Android).
>A key subset of safety categories Carbon should address are:
>[...]
>Data race safety protects against racing memory access: when a thread accesses (read or write) a memory location concurrently with a different writing thread and without synchronizing
But then later in the doc it says
>It's possible to modify the Rust model several ways in order to reduce the burden on C++ developers:
>Don't offer safety guarantees for data races, eliminating RefCell.
>[...]
>Overall, Carbon is making a compromise around safety in order to give a path for C++ to evolve. [...]
One could read this as saying that guaranteed safety against data races is not a goal. Perhaps this doc could be reworded? Maybe something like "Carbon does not see guaranteed safety against data races as strictly necessary to achieve its security goals but we still currently aim for a model that will prevent them."
[0] https://github.com/carbon-language/carbon-lang/blob/trunk/do...
I'm not sure this is correct. As I understand it, Carbon's plan is to add a borrow checker like Rust's.
From a recent talk[0][1] by one of the lead developers:
>Best candidate for C++ is likely similar to Rust’s borrow checker
[0] slides: https://chandlerc.blog/slides/2023-cppnow-carbon-strategy/in...
[1] relevant timestamps: