How can you cut so many budget of so many products and decide "yeah, emoji in 3d, that's what we are going to do!". I don't understand... Maybe they have some AR/VR future usage of some kind?
HN user
quentindanjou
Phone != The OS
I also really like having 12pm being the moment the sun is at the highest point. But I think the whole point of that change is to simplify and this would go the other way.
In the post the issue is performance. Are you saying that getting too attached to performance is a smell? That sounds very odd.
It's not because a model performs better in some applications (often by fine-tuning to get better scores at specific tests) that it is better across the board or that we have to believe the company releasing the model with a high number 3 > 2 so that it is commonly accepted as better.
Pushing the reasonnning further: f you need an Opus level performance then not accepting GPT 3 isn't a smell.
If there is no emergency way to contact an ambulance in network then there should be no in- or out-of-network.
Calling 911 does not give you an in-network and there no way to know in advance unless calling your insurance (in business hours, giving that you are not dying... which you probably are)
Think. Why did we start to pasteurize?
In November 2018 final payouts for members of the class were sent in the amount of $10.07.
Gosh this is ridiculous
That's lower than a good barber in NYC
It's not a plot. Everything is public in within EU strategy and the issues with the US digital products have been long discussed in the EU parliament.
There is something wrong with these graphs: they indicate nand price to be back to 2020 level but in 2020 I got nand for half the current price.
They would never say it is about the other reasons because of politics.
Also RAM is impacting other components such as SSD
The cause is the whole thing, cost of shipping (container, gas, etc), cost of components (RAM, SSD, etc), cost of tariff, cost of lobbying and lawsuits, and overall inflation cost.
bad performance review and a layoff are completely different worlds.
O1, EB5 or EB1 are visas, sure EBs are also referred to as "green cards" but they are visas. And you are also missing the E-2 category.
The US has dedicated visas for running your own company in normal circumstances. I am not sure what you mean.
It is seen constantly with a wide variety of products: the presence and visibility make the sale. You even have boxes that are much larger so that they get more visibility on shelves.
Yes. Unless you have hundreds of thousands of dollars that you can invest in the company that has not even been created, you would not be able to get a visa and your company would not be able to exist.
Unless you are a startup with large investors, that route is closed.
So it has a presence in stores.
I disagree. It's not about the culling, it has never been, and actually, it makes things worse. You spend countless hours and tons of money recruiting talented people not to lay them off because you don't want a bureaucratic org.
If the issue is inefficiency, tons of meetings, too much team alignment etc, then that's the issue that you need to tackle, and these issues can already appear in a 50-100 employee company. Sure, that's an easy problem to solve with a smaller size but unless you hired people for no reason, these people have a very specific set of problems to tackle and are often, in these companies, the best in class to tackle them, culling half of the company isn't going to make things better.
(And X rehired part of the laid-off engineers)
I don't know why I thought of Fable, the video game.
I would say if Excel instead of failing when you divide by 0 would be instead secretly changing it to a value like 0.0001
That's a very good analogy. Queues are not there to solve overload (and they never were), they are there as an *architecture tool* that allows decoupling and *can* (not always) ease the scaling of the queue process (workers).
I think the back-pressure should always be implemented from the very beginning, as it also helps with defining the requirements of what the service should be able to handle
Imagine going to a restaurant and when you pass your order "passing an order means accepting that there might be some poison in the food so double check before eating, good luck!"
I don't want my apps that have AI implemented to be able to read my messages because Europe mandates feature parity. And that's just the tip of the iceberg. For Apple it means building all the APIs that probably already exist but this time to be requested by apps, which would be a huge attack surface, even Apple's own apps suffers from security breaches (like Message before the switch to closed container execution). AI breaks the separation of concerns, which can lead to disastrous consequences.
EU has great intentions, and of course, feature parity should be offered so that competition can exist, but I don't find it crazy that it is more complicated on a product like that. As tech people things are very obvious to us but we need to remember that we are talking about a product used by everyone.
I don't think so. We have tons of apps and ideas and now AI. I honestly don't expect much from an OS on my phone or laptop and I am glad they improve what matter: OS performance and bugs. I don't mind having the "innovation" in the apps and not in the OS. Or at least for the first time and then brought in a well-thought-out ecosystem.
I also noticed the "And now" it appeared way too often in that presentation!
The printing invention didn't change the fact that we are still today celebrating painters.
It very obviously is. "The Outlier Nobody Noticed" -_-"
That might be true to some extent but what about the current product? It's nice to tell yourself that you can upgrade it in the future but the best of what the product is today isn't a great value, will the future upgrade make it better? Should we purchase a product today on what it might be tomorrow?
I think Jeff is correct when he says, "for an overall worse experience, are you willing to pay 20-40% more?". That's a tough sell. I think the only reason for me to take the Framework 12 over the Neo would be because I want to advocate for a world where upgradability and repairability are common things.
"painting is just procrastination that gets in the way of implementing your ideas."
"woodwork is just procrastination that gets in the way of implementing your ideas."
We can find plenty of others, but my main point is that industrializing a process doesn't make it "procrastinating". There are plenty of jobs that are done by machines but are still practiced by humans for multiple reasons. If we think of coding as a means to create, then we have plenty of examples of good reasons to have both the industrialized process and the 'handmade' one.
Were these from the same high-profile publishers?
What was the judgment? Seems that their domains are still active. Why is there a difference in judgment here?