There are thousands of sub 10$ case strap-attachments which make it easy to both use and not drop your phone while wearing it around your neck.
Imagine milking your phone out of this every time there is a notification... What a joke
1,485 karma · joined December 29, 2021
in: https://www.linkedin.com/in/ilya-lopukhin/
There are thousands of sub 10$ case strap-attachments which make it easy to both use and not drop your phone while wearing it around your neck.
Imagine milking your phone out of this every time there is a notification... What a joke
not the best survelliance when it's based on arbitrary input...
There are many counter-examples.
Gabe Newell (Valve co-founder) famously said:
"Piracy is almost always a service problem and not a pricing problem."
Jeff Bewkes (CEO of Time Warner) famous quote about piracy:
"Game of Thrones being the most pirated show in the world? That's better than an Emmy."
Radiohead released their In Rainbows album as "pay what you want", directly online. It generated more revenue than their previous label-backed album.
"dog": [object of class Canine]
They infer meaning from noisy, ambiguous sensory streams. The labels are not explicit, they are discovered through correlation, context, and feedback.
So although caregivers sometimes point and name things, that is a tiny fraction of linguistic input, and it is inconsistent. Children generalize far beyond that.
Real linguistic input to a child is incomplete, fragmented, error-filled, and dependens on context. It is full of interruptions, mispronunciations, and slang. The brain extracts structure from that chaos. Calling that "structured input" confuses the output - inherent structure of language - with the raw input, noisy speech and gestures.
The brain has drives: social bonding, curiosity, pattern-seeking. But it doesn't have a single optimisation target like "expand." Objectives are not hardcoded loss functions, they are emergent and changing.
You're right that lack of linguistic input prevents full language development, but that is not evidence of supervised learning. It just shows that exposure to any language stream is needed to trigger the innate capacity.
Both complexity and efficiency of the human learning is just on another level. Transformers are child's play compared to that level. They are not going to gain consciousness, and no AGI will happen in the foreseeable future, it is all just marketing crap, and it's becoming more and more obvious as the dust settles.
When photons hit the retina, the same kind of photochemical transduction happens — but the signal does not stop at measurement. It flows through a living system that integrates it with memory, emotion, context, and self-awareness. The brain does not just register and store the light, it constructs an experience of seeing, a subjective phenomenon — qualia.
Once models start continuously learning from visual subjective experience, hit me up – and I'll tell you the models "see objects" now. Until direct raw photovoltaic information stream about the world around them without any labelling can actually make model to learn anything, they are not even close to "seeing".
This is such a wildly simplified and naive claim. "Thinking with words" happens inside a brain, not inside a silicon circuit with artificial neurons bolted in place. The brain is plastic, it is never the same from one moment to the next. It does not require structured input, labeled data, or predefined objectives in order to learn "thinking with words." The brain performs continuous, unsupervised learning from chaotic sensory input to do what it does. Its complexity and efficiency are orders of magnitude beyond that of LLM inference. Current models barely scratch the surface of that level of complexity and efficiency.
> Do you have a concept of one-ness, or two-ness, beyond symbolic assignment?
Obviously we do. The human brain's idea of "one-ness" or "two-ness" is grounded in sensory experience — seeing one object, then two, and abstracting the difference. That grounding gives meaning to the symbol, something LLMs don't have.
You really consider 1 MB of JS too heavy for an application with hundreds of features? How exactly are developers supposed to fit an entire web app into that? Why does this minimalism suddenly apply only to JavaScript? Should every desktop app be under 1 MB too? Is Windows Calculator 30 MB binary also an offense to your principles?
What year is it, 2002? Even low-band 5G gives you 30–250 Mbps down. At those speeds, 20 MB of JS downloads in well under a second. So whats the math beihnd the 5–10 second figure? What about the cache? Is it turned off for you and you redownload the whole nextcloud from scratch every time?
Nextcloud is undeniably slow, but the real reasons show up in the profiler, not the network tab.
> The government should not spend money to encourage its own citizens to partake in harmful activities.
That's what goverment ever do.
So here some obscure Next.js issues magically become fundamental React architecture issues. What are these? Skill issues?
>> 'input input': 'updatePassword'
>> },
So this is no mystery?.
There is an 'events' object which has 'input input' string mapped to 'updatePassword' string. Why there is "input" written twice? Why do you have to reference functions by their name inside of a string? What if you have 100 event handlers and you make a typo in one of them? How will compiler understand there is a bug if you don't reference an actual function?
This whole "let's map string to string in this obect to make HTML element in one place fire an actual function in the third place" way of doing things must be a hell to maintain, bug-prone and frustrating. Why on earth you shouldn't do it with Element.addEventListener('input'), Element.on('input') or at least Element.oninput = ...?
What is this.$el, this.$('').html anyway?
$(() => {}) - wow this is VERY verbosely telling DOM is ready
I don't know, React really does look like a huge progress when directly compared to this hacky-looking backbone framework.
UI = fn(state), and it's beautiful. Yes, you need to understand side-effects and memoization, these are standard functional patterns, clearly described in the documentation. You need to understand the "stable identity" for the elements, because when recursing on the children of a DOM node, React just iterates over both lists of children at the same time and generates a mutation whenever there's a difference. There is an in-depth explanation for that in the documentation. There is nothing obscure or hard in React if you read the documentation once.
By the way, I'm curious what would it do if you ask it some proactive prompt like "reply to some comment in this thread"?
A billion people drink Coke every day, yes, and billions also have cavities, obesity, and diabetes.
Majorities also once thought the Earth was flat.
Some modern jobs absolutely contain elements of coercion, abuse, and exploitation that are comparable to forms of slavery.
<div hx-get="{% url 'web-step-discussion-items-special-counters' object.bill_id object.pk %}?{{ request.GET.url...who knows how many characters long it is.
It's hard to tell whether they optimised the app, deleted a ton of noise, or just merged everything into those 300-character-long megalines.