2,721 karma · joined February 7, 2013
The LLM explained the core concept and features very well. But it was dull and boring to me, as I already have to read this writing style at work pretty much all day every day.
What does this mean?
Had WASM not been adopted we would have SIMD in JS ( probably via asm.js) by now. Because we didn't, JS just cannot compete with WASM in many computationally heavy workflows. We'd also have general purpose JS to Asm.js compilation, with few API restrictions, making writing it much easier.
No, it isn't. Perception is a process, and ingress only a part of the process.
Perception (from Latin perceptio 'gathering, receiving') is the organization, identification, and interpretation of sensory information, in order to represent and understand the presented information or environment.[2] All perception involves signals that go through the nervous system, which in turn result from physical or chemical stimulation of the sensory system.[3] Vision involves light striking the retina of the eye; smell is mediated by odor molecules; and hearing involves pressure waves.
Perception is not only the passive receipt of these signals, but it is also shaped by the recipient's learning, memory, expectation, and attention.[4][5] Sensory input is a process that transforms this low-level information to higher-level information (e.g., extracts shapes for object recognition).[5] The following process connects a person's concepts and expectations (or knowledge) with restorative and selective mechanisms, such as attention, that influence perception.
- https://en.wikipedia.org/wiki/Perception
> No they can't. There is no evidence at all of better color differentiation
Yes, there is. Example: "Russian blues reveal effects of language on color discrimination." https://pubmed.ncbi.nlm.nih.gov/17470790/
> Knowing the names of notes doesn't make it any easier to tell if a note is out of tune.
I didn't say that. But having a deep familiarity with tones does.
> Musicians learn.
Yes, I know. I majored in Music and have 30 years experience.
> they spend tremendous amounts of time listening to sound and being corrected
I'm confused since you seems to have just switched sides of the argument completely and entirely here. I'll give you the benefit of the doubt and assume you are thinking that _having_ knowledge (knowing the words and vocabulary) is what I meant. But that is not what I meant. I meant to speak about the _understanding_ you have when you intimately familiar and experienced.
> The difference between cyan and azure exists even if you don't have the vocabulary to communicate that difference to someone else.
Those colors are pretty different and aren't that interesting to study, from a linguistic relativity point of view. Colors much closer together, like #187af7, #1b85f5 and #187af7 are.
We know this to be obvious of sounds, musicians who can tell if a note is slightly out of tune when others who haven't learned how can't, or taste/smell: wine connoisseurs who can tell very similar wines apart that all taste the same to me.
You're not thinking in photons. Your brain is making up meaning from the stimulation your eye received from photons. The perceiving part is learned.
For those that have lost their marbles: sure, people use words incorrectly, but that does mean we all have to use those words incorrectly.
In compute vernacular, "edge" means it's distributed in a way that the compute is close to the user (the "user" here is the device, not a person); "on device" means the compute is on the device. They do not mean the same thing.
https://www.nbcnews.com/world/iran/iran-school-strike-us-mil...
In this case it seems plausible that the military would have an outdated database, and that an LLM would have "known" it wasn't a base anymore, assuming the LLM was trained on documents/maps with this up to date information.
Greenfield is easy because nothing matters yet.
No legacy data. No backwards compatibility. No users depending on uptime. If the architecture is wrong you just rewrite it, rename a few services, and move on.
Maintaining and expanding a real system means every change has consequences. You’re migrating live data, preserving behavior people rely on, and evolving the architecture while the plane is already in the air.
0→1 lets you be bold because you can break things. 1→10M is harder because you can’t.
(I'm just kidding, your dismissal just needed a dismissal to make things balanced again)