And this is why I gave a try to VueJS in the first place. It can be deployed with npm, or a simple script tag.
It still does today, making prototypes easy to write, training very simple, and yet, it plays well with the more complex ecosystem.
Now of course, VueJS has Vite, which makes all the complexity of Webpack goes away, removes the slowness of compilation and has sane defaults.
Still, npm remains. I'm now used to it, but I understand that if you come from another language, it's not attractive.
It's funny to me that most people consider JS packaging better than Python packaging.
Both are troublesome, just for different reasons. E.G: using different versions of node is much harder, espacially on windows, or for the same project, than different versions of python. And installing compiled extensions is a way better experience in Python than in any other high level language. On the other hand, node_module is easier to use than the average venv.
> And this is why I gave a try to VueJS in the first place. It can be deployed with npm, or a simple script tag.
This is exactly, what I noticed positively about VueJS and advertised as a good feature for integrating this specific "web component" framework into a project. You can add it as simply as one used to add jQuery to any project. However, others thought of including script tag as "not proper" (even though I told them, that in the end it would all be a script tag anyway ...) and it was decided to use another framework, which is way more complicated to integrate in any statically rendered / server side rendered and template based website.
Simply putting VueJS in a script tag is not a problem. One can cache it easily and one can use noscript tags at places in any page templates. All is fine.
> The article acknowledges this somewhat, but it’s an example of another confidence fallacy: The idea that nobody knows what they’re talking about.
It was the opposite for me realization for . When I was young I was assuming if somebody was saying something, they were likely knowing what they were talking about.
After a bit of a ride in life, I know now that people that does do exist, but they are a rare bread, and usually about some very specific topic.
Competent people are the exception, not the rule, degraded mode is the default for humanity, and we are pretty good at going with it. At the beginning I though: what they are doing must be complicated, since it takes so much time and effort, or since there is so much debate about it. One day, you have to do it yourself, or you are behind the curtain, and you realize in 2 years anybody seriously working at it would be better that those life timers.
But still, because of the social pressure, playing pretend is the status quo for most.
Not just about jobs, not just about science, but about pretty basic things in life as well.
In fact, we are constructing a lot of our society around myths that are emerging because of this collecting behavior. It's quite fascinating to watch unfold, but it's such a waste of potential.
In Python it's the opposite, as we good serious bootstrapping problems, and people complain for different reasons.
In C, people complain because tooling is too complex, in Haskell because 3rd party tools are unreliable, in PHP because it's riddle with security issues, in JS because it breaks compat regularly, etc.
In this era of quick outrage, thank you for doing the job of trying to figure out what is really going on, at the risk of taking the less socially acceptable side.
Interesing project, but I wish it would show me more about what doesn't work.
The bottom of the readme indicates the list of control flow instructions it supports, but it would be convenient to have in the table the ones it doesn't as well: yield, yield from, with, try/excep, match, lambda...
Does it support "else" in loops? Does it support unpacking?
Hard to know how much Python does this Python does.
> The bottom of the readme indicates the list of control flow instructions it supports, but it would be convenient to have in the table the ones it doesn't as well
Totally true. Some people would like to contribute to the project, and knowing what's lacking is a good way to make people know how to help.
Not to mention remote interviews, and with a result solely based on the company rating about perceived communication performances. This has pretty much the equivalent scientific value of a twitter poll.
I assume HN responses are based in experience, while this article shows only one thing: "companies rate communication in a certain way in remote technical interview".
The "Does communication matter in technical interviews?" is not even deserved. It's a terrible article, most likely an ad, with an artifical conclusions about a low quality biased data source composed of a one-sided, subjective star post interview star rating.
As for my experience, I've been hired to perform technical interview on behalf of companies, I hired people for my companies, and I've been interviewed many time.
And the answer is: it depends.
It depends of the person, of the job, of the context, and what you consider communication.
I have an ex that is incredibly incompetent and not very bright, but she is amazingly sexy and dresses well, and gets hired very easily. I have another one that is the best at her job, she is an angel for customers, but she is shy, doesn't explain things well, and is not as sexy. She tanks interviews regularly. Is that communication?
When I was young, I traded my contact lens for glasses and noted that, as a geek, people took me more seriously in interviews with glasses. Is that communication?
Last month, I interviewed a guy who said "I like to work at home, this allows me to be at ease when I want to code 12 hours straight". I knew he was boasting - people capable of focusing for 12 hours are very rare - and rejected him because I want to avoid BS. But he came from a trading firm, where this may be what you are supposed to say. Was it good communication?
"Communication" is not unidimensional. It's what you say, and don't say, when you say it, how and to whom. It's also what you convey by you body, your look, your voice. Being late is communicating something. Saying "I don't know" is communicating something. And the context in which you are saying it is as important as what you are saying. A good job here could be a social mistake there.
A few star rating is communicating to me that one knows nothing about the topic.
It still does today, making prototypes easy to write, training very simple, and yet, it plays well with the more complex ecosystem.
Now of course, VueJS has Vite, which makes all the complexity of Webpack goes away, removes the slowness of compilation and has sane defaults.
Still, npm remains. I'm now used to it, but I understand that if you come from another language, it's not attractive.
It's funny to me that most people consider JS packaging better than Python packaging.
Both are troublesome, just for different reasons. E.G: using different versions of node is much harder, espacially on windows, or for the same project, than different versions of python. And installing compiled extensions is a way better experience in Python than in any other high level language. On the other hand, node_module is easier to use than the average venv.