Just returned from Malaga in Spain. The EasyHotel we stayed in had frosted glass cubicle for the toilet and shower. But there were huge gaps in between. Haha!
It takes an evolution for humans to adopt VR. We are not hardwired to wear an headset or glasses at all times. VR does have some nice use cases, mostly in industrial/enterprise setup, but not in day-to-day life.
It comes up all the time. But the power of capitalism is that even this idea will itself be monetized by people selling books, giving ted talks, appearing on podcasts, asking for donations for cause, etc. etc.
Okay how about we take off the blinders, stop patting each other on the back and call it "an" evil algorithm since exploitation is economic-system-agnostic?
Mostly the part that brings groups of humans to optimize for wealth, even if this directly makes the life of other humans shittier. It turns humans into automata who blindly want to make the number go up, and not worry about the consequences.
A potential mitigation could be for governments to make the bad consequences more illegal. And in order to do so they need not be influenced by the algorithm, but unfortunately they are.
Good question. Wouldn't it be convenient if this were one of the most written-about political subjects of the last 150 years?
In short: The problem with capitalism is class striation. Society is divided into a capital-owning class and a labouring class. Capitalists, as they control the productive capital in our economy, portion out economic profits as they see fit, paying labourers as little as is necessary while retaining for themselves the maximum possible amount. Labourers, owning negligible amounts of capital themselves, are dependent on capitalists for work and have little recourse.
Hence, power consolidates in the hands of capitalists. They have leverage over politicians through lobbyists, over the public through media, and over their employees through the threat of job loss. The labouring class are second-class citizens. Healthcare is inaccessible to many them. They're frequently mired in debt. If they become disabled, they could easily lose their homes and wind up on the street.
In one sense, the solution is obvious: Dissolve the boundary between these classes so that none of these class inequalities exist anymore. Now, how is that done? Who knows. The traditional answer is, "the tensions in the existing system will exacerbate until the workers all organize and force a new status quo upon society," but that doesn't seem to be happening. Then again, if we had a solution, the problem wouldn't exist anymore, would it.
on HN you can either be a moldbugian reactionary or a utopian socialist, but the important thing is that your ideology remains unimplementable and thus unfalsifiable and safe forever from the dangerous forces of empirical results
The utopian socialists were pre-Marxist, actually. Marx spent a lot of time critiquing them. They're not really around anymore.
Anyway, what does it mean to "implement" a critique? All I did was point out the problems with capitalism, for which there is plenty of empirical evidence.
If you want to know which policies I support implementing, I'm afraid they're relatively dull and incrementalist, since policy can't reorder the global economy by fiat.
Classic thought-terminating cliché. Any critique of capitalism is communism, and communism invariably entails Maoist crackdowns or what-have-you; therefore it's best to "immunize" oneself even against basic critiques of capitalism because they're just a slippery slope to the Chinese Cultural Revolution.
None of my remarks are particularly incendiary—or do you think the idea that billionaires exert control over politics through lobbyists and media corporations is controversial? And I'm pointedly not making any policy prescriptions.
I'm afraid you've immunized yourself against even reading the posts you reply to.
Let's say you are a cart pusher in a free market. After ten years of cart pushing, you land on a trading opportunity and capitalize on it. Then you hire more cart pushers.
Now you have a responsibility. Either keep the business going, or everyone loses their job.
Then others smell profit and eat up your market share. Now you have to stay afloat and the workers suffer.
As the emergent properties build up, we end up with a modern free market society with all the romanticized "class wars" worker abuse and peeing in a bottle drama all because the job market exists.
It is like an ouroboros ironically nibbling on its tail while winking.
No. Greed is inherent to humans. No social order can eliminate greed. They can, however, mitigate the harmful effects of greed on society.
In a democracy, elected leaders are not as empowered to satisfy their greed as monarchs are in monarchies. Socialism extends this logic to businesses: An elected business leader would not be able to satisfy their greed to the same extent that a capitalist business owner can.
You can get rid of money and have communism if you want and guarantee that all have what they need. But somewhere beyond need there is want, and the line is awfully fuzzy.
You can have a barter society if you want, where people trade pineapples for shoes, but you are always going to have people who want more shoes or more pineapples than what others have.
- the video watermarking will be interesting here, i wonder how ai companies and socmed companies will tolerate and punish each other on these things.
- lots of new creators on this market too, particularly those with no studio setup but better creativity and imagination. there is still cost of entry of course, need $, but it's now less.
- i wonder how each audience will react to this, from children, to teens, to adults. now that content creators are desaturated, i think it's content consumers that will be saturated.
The cost issue is similar to the bandwidth issue faced by YouTube in its early days. It took a while for countries across the world to get high speed internet. As technology advances, the cost to generate video using these models would go down significantly and perhaps the quality of the generated video would also be better than what it is today.
> React is the automatic target for a lot of newbies. They jump straight into webdev, learn some HTML/CSS and eventually work their way towards React for employability.
This has been the trend largely for last 3 to 4 years with the candidates (<5 yoe) I have interviewed. I probe them on core fundamentals of Javascript, HTML and CSS. When I get to the nuances, most of them outright call it out saying that they are React developers and do not do Javascript without realizing the fact that React is based on Javascript. And other common misconception is that they assume JSX works the same way while writing the vanilla Javascript code.
Yup. I’m hiring for a mid-level FE role right now, and the number of “React developers” that don’t know JS fundamentals is incomprehensible. I’m not talking about anything esoteric. Just the sorts of things that I as someone that’s far from a JS expert considers necessary to work in that space day to day. I’m more and more just taking it as a given now that someone won’t have much if any experience writing CSS by hand. If they do, never in an actual .css file. Always via some CSS in JS something or other. A strange new world out there.
Honestly I can’t remember half the dom manipulation stuff and at one point I did know it quite well. It’s just been 6 years since I worked on an app that wasn’t react.
It’s useless knowledge for most people now. Like knowing assembly.
I wouldn't really consider anything involving the DOM to be a JS fundamental. That's a browser fundamental, and even then, it's like, what do you want? I can use `document.write('hello world')` and replace the entire body. Or append it as a text node with `document.body.append`. Or create an element and add it. This is a pretty silly question and something people should just spend 2 seconds looking up on the rare occasion they need to do it.
I currently work with devs who've done things like create a Map and then assign properties directly instead of using .set and .get.. I'd say that shows a pretty significant lack of fundamentals
I believe Map was released in 2015 as part of ES6 so while not new, it still feels new in some code bases. Some people also confuse it with Array.prototype.map a lot.
People just assume every data structure operates like an array since it is the most commonly used without realizing the underlying object nature of the language. Like the idea of getters and setters coming from OOP paradigm is lost to fresh devs over the last 5 years using the FP paradigm as their primary means of coding in React.
So yeah some of the fundamental are missing but also most of the time this knowledge probably isn't utilized by React FP only devs in their day to day.
I would assume array methods (map, filter, reduce), callbacks, hoisting, mutability, etc.
I've interviewed a few people who don't know how some of the array methods work, and those are one of the most important parts of knowing how to write Javascript.
What does "across the board" mean? You mention that the article scores for newbie Google searches about XSS in React.
I mean, it's correct that people who ask such questions should spend a year doing web dev without React probably (and maybe learn basic programming concepts). But the people who comment to you about that post seem to be self-selected for not knowing much about JS.
People who know their ropes aren't left with any questions by your article :) and probably know about everything it contains already.
Still, feedback from me: good content, especially for beginners!
If its just the one question then sure i agree... but if it was used as a kind of fun icebreaker question, then I can kind of see where it could be used.
Especially when you deal with unsanitized data - like from a 3rd party API - you're bound to eventually have each of those cases find their way into your if statements/expressions.
Also, this question works for other languages too, as e.g. NaN can evaluate to True (Python) or have an undefined behaviour but still evaluate to true (C, C++) - it's useful to know what is true and what is false(y) in your language of choice, especially coming from another language.
But a different representation in IEEE 754 floating point. If you were building a JS interpreter it would be important to catch that 0 and -0 are different numbers in memory and to hardware operations.
Got me there, as I forgot about it, but I also don't expect anyone to always name all of them - as it's just a probe on how broad was the spectrum of errors a person encountered.
Personally I've never had an issue where that would matter, as BigInt is typically used mostly in isolation. Any avenue for errors appears only when types are mixed or used in boolean statements.
If we're being pedantic, you also forgot document.all. Which is in fact an infinite collection of values, because document.all is a different object in every frame.
about 23-24 years ago me and another senior developer were working on some important parts of the product we were building, and we had a minor task for a company that was paying a little bit, so we handed it over to a guy who was junior but should really have been better (he had the wrong kind of Laziness).
After some hours I saw him walking around with that programmers walk we get when trying to figure out a particularly hard problem. So I went over to check on him.
He informed me that his code to read in the XML file and transform it with the XSLT I had given him worked perfectly in IE but in Netscape there was some sort of problem with the ActiveX control he was using.
So - I figure assuming "JSX works the same way" is the modern day version of that.
When all the frameworks were taking off, I was at a huge company using a 15 years legacy front-end. My background was "traditional" front-end. HTML/CSS/JS and mostly jQuery at the time.
Every time I went in for an interview, the senior devs would always start with fundamental JS stuff and then go from there. I would consistently get comments about how I was the first person they interviewed who could actually talk to basic JS stuff like closures and scope chain. They said there was a huge influx of people learning React and Angular and had no idea the difference between the two or like you said, they were based on JS.
This was back around 2014/2015 and it looks as though not much has changed since then.
was at a bar and i met some guy who was like a year into his first software dev job and somebody was asking us about learning to code and i said to learn html/css first and he was like, "you don't need to know that, just learn react. i don't know anything about html."
i kept my judgement to myself and just ignored his advice. hopefully he's learned html.
I had a similar experience back in the early 2000's.
I was working with a senior developer who was having trouble moving something up on the the page when something else disappeared. He was using asp.net server controls, it was all he knew.
I suggested "just wrap the content you need to hide in a div and style it with display: none, your content will automatically float up"
He answered me with a sort of superior sneer: "I'm a .net web developer, I don't know what a div is, and I don't intend to learn it".
To be fair, that was a different time and MS was trying hard to make web development act like VB desktop development, but still...
The only challenge is a proper description. Some comments go by "Here you go: <link to pdf>" without much description of its content. But it is a good idea. I will try to figure out something.
