570 karma · joined March 13, 2017
Can somebody here correct me if I am wrong, but my impression was that Intel did commit early to EUV, with initial plans to start high volume manufacturing in line with other fabs (initial schedule was to introduce EUV in 2017 [1], it just got postponed many times), but they just failed in their execution.
[1] https://wccftech.com/idf13-intel-ship-10nm-chips-2015-7nm-ch...
> 300-500k in upfront costs.
So before building anything just the application process will cost you up to half a million, that's an enormous hurdle.
> Fornjot is architected to be language-agnostic, and adding support for other languages should be relatively straight-forward, actually. Hopefully one day, there will be a selection of interoperable Fornjot frontends, so you can choose the best language for your model.
2022: 79%
2023: 80%
2022: 20%
2023: 14%
[1] https://www.eia.gov/electricity/data/eia860m/xls/december_ge...
If you literally look up the most upvoted HN article about FLoC [1], it specifies two main issues with FLoC in BOLD: Fingerprinting and Cross-context exposure. Which if I understand correctly the Topics API fixes. But the article implies that these are minor problems that we never really cared that much about.
Whether it is this or constant aggressive writing, it seems that the goal of this blog post is to simply inspire anger and hate, while not furthering the discussion on the topic. Which makes this article unhelpful (if not damaging) to the goal of personal data privacy.
[1] https://news.ycombinator.com/item?id=26344013 [2] https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-...
S1 does not specify the amount.
> And does that money go into the company or does it go to existing shareholders?
The money goes to the company.
Read more here: https://austinvernon.site/blog/renewablesregulatory.html
[1] https://ec.europa.eu/clima/policies/strategies/progress_en
[1] https://www.ipcc.ch/report/ar6/wg1/downloads/report/IPCC_AR6...
It does not establish clearly why carbon removal is not effective at slowing climate change, while assuming it isn't.
It critisizes as inefficient the early investing strategy to cast a wide net and give money to potentially failing ideas.
It in one place mentions that climate capture cannot "be easily scaled up" because it is "prohibitively expensive and energy intensive", while in the other part it concedes that the technology might progress in the future.
The entire article is laced with emotional contempt of technology and progress, and does little to help you understand the reasons of why you should be concerned with the problem it tries to present.
When you are a company that needs to maintain multiple clients across platforms (web, android, ios, and so on) it is very hard to be good at 3 things at the same time: application performance, development velocity and cross-platform consistency. Every solution that currently exists sacrifices some of the points to improve others. For example: If you make a web app across platforms, then you sacrifice performance on mobile; If you use native apps everywhere, you sacrifice development velocity and cross-platform consistency.
You might be wondering: isn't something like React Native or Flutter solve all those issues? Yes, on the surface it's a great fit. For only slight sacrifice in performance you get everything. That is why Airbnb have tried React Native initially, but decided to abandon it in the end due to technical and organizational issues (read mote here [1]).
This is their new attempt at getting good trade-offs here. You get full performance because you are doing everything natively. You get solid cross-platform consistency and high development velocity, because you are making changes in one place. Bravo Airbnb!
[1] https://medium.com/airbnb-engineering/sunsetting-react-nativ...