If you are CEO of a large company, and you see a huge uptick of ecommerce during covid, you could:
- Expand aggressively and compete for top talent
- Wait and possibly miss opportunity if trend continue
Most CEOs decided to expand. For example meta hired around 30k people from 2020 to 2022.
If you see end of ZIRP, slowdown and inflation and you actually overhired as CEO what you should do?
- Keep employees locked in roles that are not needed?
- Let go people that are not needed and hire for what is needed.
Meta let go most e-commerce positions and support and now is aggressively hiring AI specialists.
If you are hiring, and you see someone that cannot hold a job for more than 6 months, it is red flag. In capitalist system, employees are just to provide labor in exchange for wages. Nothing more, nothing less. Problem in US is that both retirement and healthcare is often provided by employer, creating this weird illusions of long term caring relationship.
Node.js made many decisions that have massive impact on ESM adoption. From forcing extensions and dropping index.js to loaders and complicated package.json "exports". In addition to node.js steamrolling everyone, tc39 keep making are idiotic changes to spec like `deffered import` and `with` syntax changes.
Requiring file extensions and not supporting automatic "index" imports was a requirement from Browsers where you can't just scan a file system and people would be rightfully upset if their browser modules sent 4-10 HEAD requests to find the file it was looking for.
"exports" controls in package.json was something package/library authors had been asking for for a long time even under CJS regimes. ESM gets a lot of blame for the complexity of "exports", because ESM packages were required to use it but CJS was allowed to be optional and grandfathered, but most of the complexity in the format was entirely due to CJS complexity and Node trying to support all the "exports" options already in the wild in CJS packages. Because "barrel" modules (modules full of just `export thing from './thing.js'`) are so much easier to write in ESM I've yet to see an ESM-only project with a complicated "exports". ("exports" is allowed to be as simple as the old main field, just an "index.js", which can just be an easily written "barrel" module).
> tc39 keep making are idiotic changes to spec like `deffered import` and `with` syntax changes
I'm holding judgment on deferred imports until I figure out what use cases it solves, but `with` has been a great addition to `import`. I remember the bad old days of crazy string syntaxes embedded in module names in AMD loaders and Webpack (like the bang delimited nonsense of `json!embed!some-file.json` and `postcss!style-loader!css!sass!some-file.scss`) and how hard it was to debug them at times and how much they tied you to very specific file loaders (clogging your AMD config forever, or locking you to specific versions of Webpack for fear of an upgrade breaking your loader stack). Something like `import someJson from 'some-file.json' with { type: 'json', webpackEmbed: true }` is such a huge improvement over that alone. The fact that it is also a single syntax that looks mostly like normal JS objects for other very useful metadata attribute tools like bringing integrity checks to ESM imports without an importmap is also great.
For me intermittent fasting after 6pm and small diet changes fixed my acid reflux. PPI were not helping and making things worse. I actually took Betaine HCI supplements to fix digestive issues after PPIs.
> May I know what is so "terrible" about those protocols ans what "technical debt" are you talking about?
POP is pretty archaic and lack support for multiple clients accessing the same account.
IMAP is complex, slow and lack modern email futures threading, contacts. Clients often implement it in inconsistent matter, given there are plenty of extensions.
SMTP is not a single protocol but collection of bolted on protocols (DMARC, DKIM, SPF). Lack delivery tracking, and it is very opaque when it comes to spam filtering.
All these protocols are build on top of raw TCP. It is harder to implement any things we take for granted in http like: encryption, compression, multiplexing and debugability are not there by default.
> That has nothing to do with actual email protocols. Generic email protocols are extremely reliable and resilient to any sorts of disruptions. I wish any of modern protocols exhibit similar simplicity and reliability.
People spend decades building infrastructure, but even then only hardcore graybeard will self-host email.
> POP is pretty archaic and lack support for multiple clients accessing the same account.
There are no issues with POP and multiple clients whatsoever.
> IMAP is complex, slow and lack modern email futures threading, contacts.
What's "complex" about IMAP? Extremely simple and reliable protocol. Contacts are not part of IMAP and handled by different protocols.
> SMTP is not a single protocol but collection of bolted on protocols (DMARC, DKIM, SPF).
I suggest you to educate yourself on DKIM, DMARC, SPF and SMTP before making those statements.
> Lack delivery tracking, and it is very opaque when it comes to spam filtering.
It DOES have delivery tracking. Spam filtering is not a protocol feature and it shouldn't be. I suggest you again to educate yourself.
> All these protocols are build on top of raw TCP. It is harder to implement any things we take for granted in http like: encryption, compression, multiplexing and debugability are not there by default.
Let me tell you one of most hidden secrets in the industry - EVERYTHING we have online is built on top of raw TCP. Ok, and UDP as well. Every bloody fancy JS framework or mobile app you can think about is written on top of that raw TCP. Crazy world huh?
> People spend decades building infrastructure, but even then only hardcore graybeard will self-host email
If you don't know how to build something doesn't mean it's left out to "hardcore graybeards". You got to admit you just don't know how and either learn or surrender to companies who know, offering the same for a buck. It's pretty simple.
> There are no issues with POP and multiple clients whatsoever.
POP3 in standard only have "Leave a copy on the server" but lack synchronisation mechanism.
> I suggest you to educate yourself on DKIM, DMARC, SPF and SMTP before making those statements.
You cannot use SMTP in real world without these protocols. Your messages would automatically land in spam folders of big providers. For example, if you want to send email to Gmail, you need SPF and DKIM [1]. Any half decent implementation of SMTP need to support all these protocols [2].
> It DOES have delivery tracking. Spam filtering is not a protocol feature and it shouldn't be. I suggest you again to educate yourself.
SMTP have extension for DSNs (Delivery Status Notifications) but crucially it does not provide information if/why email was classified as spam. This is a reason why many website registration form have “check spam folder”. SMTP deliverability is a hard problem both on protocol level and infrastructure on spam filtering[3].
> If you don't know how to build something doesn't mean it's left out to "hardcore graybeards". You got to admit you just don't know how and either learn or surrender to companies who know, offering the same for a buck. It's pretty simple.
I spend a significant amount of time investigating feasibility of building an email product and build some libraries for email protocols. It is not just my opinion but other HNs users including OP. Search HN for "self hosting email" for others people experience.
> POP3 in standard only have "Leave a copy on the server" but lack synchronisation mechanism.
Would you explain what do you mean under the "synchronisation mechanism"?
> You cannot use SMTP in real world without these protocols.
You absolutely can. GMail is not the only email provider out there.
> SMTP have extension for DSNs (Delivery Status Notifications) but crucially it does not provide information if/why email was classified as spam. This is a reason why many website registration form have “check spam folder”. SMTP deliverability is a hard problem both on protocol level and infrastructure on spam filtering[3].
I find it hard to even start commenting this, only can suggest you again to educate yourself. Spam related matters were never a part of transport protocol. And never will be for obvious reasons. Just because you would like them to be, it won't change anything.
> I spend a significant amount of time investigating feasibility of building an email product and build some libraries for email protocols. It is not just my opinion but other HNs users including OP. Search HN for "self hosting email" for others people experience.
Happy for you to actually explore building software, but we can't carry discussions just because some HN users carry some, possibly erroneous opinions, or can we?
Whataboutism is when you bring up something about person A, then the only argument against it is something relating to person B.
For example, when you point out the call the president made to the secretary of state in Georgia begging him to "find" 11,780 votes. Then, without a great excuse, the other person brings up Biden's mental decline.
Both true, both concerning, but the reply just being blatant and desperate misdirection.
...no it isn't? Whataboutism is when you redirect attention from issue #1 to unrelated issue #2 in an attempt to change the conversation topic: "forget that, look at this!"
OP's comment was pointing out the similarities between issue #1 and issue #2. There's no dismissal.
Whataboutism is when you are trying to show a double standard because person A did a thing that you were upset about and person B did the same thing and you don't care. Asking why you care about a person doing a thing and didn't care when a different person did something different is not whataboutism.
I agree with the GP on the definition of whataboutism, and think that you have described something with a much older term: "pointing out the hypocrisy".
They both share in common that rather than continuing to talk about just one thing, you are now talking about (at least) two.
But whataboutism is a diversion tactic that tries to shift the attention from behavior/event A to behavior/event B; pointing out the hypocrisy notes the similarities between behaviors/events A and B and contrasts the response.
Both can be deployed in similar situations, but the motivations for choosing one over the other are substantially different.
> The communication intent is often to distract from the content of a topic (red herring). The goal may also be to question the justification for criticism and the legitimacy, integrity, and fairness of the critic, which can take on the character of discrediting the criticism, which may or may not be justified. Common accusations include double standards, and hypocrisy, but it can also be used to relativize criticism of one's own viewpoints or behaviors.
Both Clintons private email server, Pete signal chats and Trump documents stash in Mar-a-lago are equally bad. Lack of consequences signal erosion of “Law and order” in the US. It seems that US is now not different from third rate countries where last minute exceptions, insider trading, open bribery, secret police(ICE) and targeted prosecution is a new norm.
We do not know. We do not know what documents Trump had in Mar-a-lago, who had access to them, and what he shared with others. Furthermore, we do not know what was in Clintons emails and who read them. If anything, Hegseth’s is less damming, since we know the content of chat and participants. In both Clintons and Trump cases, the impact could be much bigger. The problem in all cases is lack of accountability.
The dismissal is implied. And this behavior is endemic in modern reporting and political conversation.
Novel idea: what if we focus on the exact issue that was originally brought up?
'Someone else did it, or something like it, sometime, somewhere.' I'm past caring about that -- because it's used too frequently to distract from the current issue.
A. Hegseth broke the law and shared classified information on a system that wasn't approved for it.
B. Or, he unilaterally declassified operational details without informing anyone or going through a normal process.
It can only be one of the two above options, because the facts aren't in question.
Is it? I'd think that somebody who took Hillary's hidden 3rd party communications seriously would take these seriously too.
The bizarre behavior is insisting that what Clinton did was trivial, but that this is a disaster.
Also this emphasis on security is backseat driving from a bunch of people who want to attack Iran. The real problem with them using third-party communications is that they avoid FOIA.
I really want to see the people that have performance issues with Zod and what's their use case.
I mean it.
I've been parsing (not just validating) runtime values from a decade (io-ts, Zod, effect/schema, t-comb, etc) and I find the performance penalty irrelevant in virtually any project, either FE or BE.
Seriously, people will fill their website with Google tracking crap, 20000 libraries, react crap for a simple crud, and then complain about ms differences in parsing?
We use it heavily for backend code, and it is a bit of a hot path for our use cases. However the biggest issue is how big the types are by default. I had a 500 line schema file that compiled into a 800,000 line .d.ts file — occupying a huge proportion of our overall typechecking time.
Yup, maintained an e-commerce site where the products were coming from a third party api and the products often had 200+ properties and we often needed certain combinations of them to be present to display them. We created schemas for all of them and also had to transform the data quite a bit and used union types extensively, so when displaying a product list with hundreds of these products, Zod would take some time(400+ ms) for parsing through that. Valibot took about 50ms. And the editor performance was also noticeably worse with Zod, taking up to three seconds for code completion suggestions to pop up or type inference to complete - but truth be told valibot was not significantly better here at the time.
I agree though, that filling your website with tracking crap is a stupid idea as well.
I’ve used it on the backend to validate and clean up tens of thousands of documents from Elasticsearch queries, and the time spent in Zod was very much noticeable
Katt from trpc, mantine lead developer, Tanner from tanstack, Anders from typescript, Jose from elixir, antires from redis. There plenty of 10x dev examples.
In any creative industry Price's is well known phenomen. 50% of work is done by square root of people. But in reality there large number of problems that cannot be solved by average developer.
That why people that build tooling, compilers, important libraries and frameworks make often 100 times more impact. They increase productivity of everyone
This goes back to a complaint in 2022 and as mentioned in the very first sentence of the article similar rulings have already taken effect in several countries. Not everything is about Trump.
Some ruling can be blocked for years in “legal proceeding” for example Uber with plenty evidence was ignored while in the same time European Glove was fighting crinal prosecution.
I'm not taking a position on whether or not this is about Trump, but three years ago is recent enough to argue that we were already in the process of losing our dominant position.
There is an incredible amount of soft power applied in global politics and business. This why for example Google CEO have face to face meeting with prime ministers and this reported in news.
If you see end of ZIRP, slowdown and inflation and you actually overhired as CEO what you should do?
Meta let go most e-commerce positions and support and now is aggressively hiring AI specialists.If you are hiring, and you see someone that cannot hold a job for more than 6 months, it is red flag. In capitalist system, employees are just to provide labor in exchange for wages. Nothing more, nothing less. Problem in US is that both retirement and healthcare is often provided by employer, creating this weird illusions of long term caring relationship.