Have been working with HTML in decades and still it's quicker to write markdown for simple documents. Now if you'd have some middle ground that would be nice. And actually there are already things like Githubs Markdown which has more features, you can embed mermaid etc. Or you'd use something like MDX (which readme.com is using internally) where you mix in components when needed - those could even be based on something like bootstrap because you might like having cards and layouts. Now the only thing missing is support in the interface. Plain HTML can already be rendered, adding a more capable Markdown shouldn't be too hard.
But then at the same time you should always update because it might fix a security vulnerability. Otherwise you end up running nodejs 10 because you don't need the new stuff.
Or it might introduce one. But sure, a security fix for a known vulnerability could count as something you need in a new version. Ideally they would be backported and separated from feature updates. The constant dependency churn and single-channel update stream is kind of why a lot of vulnerabilities become problems in the first place.
You have a lot of private data. So running it locally makes you use less credits and then you also don't have your emails as training data for cloud models.
Really seems to be a government issue. I have an app on my phone where I can generate a QR code which proves my age. Nothing else is transmitted - no birthdate or name. And it's based on an open standard. You can read any verify everything yourself. You just can't fake it as you can't sign it without the private key.
> So you are saying they shouldn't have given those 30k people a job to begin with? I don't know if that's any better.
For the long term health of the company it's near a certainty that would have been better. The effects of adding ~20K then laying off 30K in such a relatively small period of time are gonna be felt for years
Yeah, I understand where you are coming from. I'm just also thinking about the human side that is discussed here so often and having a more pessimistic view on hiring might be bad for the job market. Especially in countries that are not considered a social state. So while it's not good for the company itself it might not be so bad for people overall if those billionaire companies are wasting some of their money - at least until investors start to complain.
People tend to be bad in estimating the performance of others and are almost always bad in estimating their own performance. So you end up with people asking themself why it wasn't them and if they will be next. And management can't tell you you are safe, because it might change - and if they promise they can only do that once.
Managers do know. Some of them are better at it than others. But even for the best it never is easy. And they are still humans, don't go to harsh on them with your blame.
Also the companies selling the ad platforms aren’t knowing their own technical documentation. They tell everyone you need to load JS as heavy and blocking as possible and collect as much user data as possible because they can’t read their damn documentation. That’s also why news pages always say ad only works with massive tracking, which isn’t true and not even that effective.
The fetch API is designed for browsers. It's not designed for servers. Fetch may work for a particular use case on the server, it may not. Servers have needs over and above what a browser allows the client to do.
Now I'm curious, because we have a big server side code base using fetch(). What are you using that doesn't work with fetch? Especially since axios nowadays has a fetch adapter.
reply