TGTGInsighttelegram intelligenceLIVE / telegram public index
← Newlearnerの自留地

TGINSIGHT SIMILAR POSTS

類似コンテンツを探す

ソースチャンネル @NewLearnerChannel · Post #14708 · 9月9日

#APPLE 🍎Apple 2025 秋季发布会看些啥?—— 自留地 の 前瞻盘点 明天凌晨,一年一度的阿果秋季春晚又要来了。老规矩,结合此前种种爆料和信息,我们一起来盘点一下今年可能的看点 📱iPhone 17 系列 - A19 系列处理器 - 推出全新 Air 系列,主打 5.5mm 超薄机身,配备「药丸」后摄模组,预计搭载 12GB RAM、Apple C1 调制解调器和 6.6 英寸显示屏 - Air 首发或暂无国行,因其大概率仅支持 eSIM,需等 eSIM 政策落地 - Pro 系列将采用半玻璃半铝的设计,其中玻璃区域用于 MagSafe 充电,后背还将采用巨大摄影头模组 - Pro 系列有望搭载 A19 Pro 处理器,以及全 48MP 后置三摄 / 最高 8 倍光学变焦 - Pro 机型将提供橙色、深蓝色、灰色、白色和黑色机型 - 数字版将迎来 6.3 英寸显示屏、A19 处理器以及「小药丸」后摄模组,有望带来 ProMotion 功能 - 将采用均热板等手段,进一步改善 iPhone 散热问题 📸 今年升级的亮点,我觉得除了推出轻薄 SKU 取代了 Plus 系列之外,依然是影像。随着国产 Android 品牌以及三星等竞品的不断发力,光学长焦等手机相机体验越来越好,Apple 这几年感受到了压力。去年使得 Pro 和 Pro Max 在影像功能上做到了对等,今年很高兴看到模组增大的同时,有新的功能和变化 像素提升、光学倍数增加,都是我们喜闻乐见的,拍演唱会等场景可以排上大用场。但是,正如我去年说的那样,我们也应该拥有一个「专业模式」来充分发挥这些硬件的实力。此外,对于日常用的中焦焦段的选择,Apple 应该有自己的思考 🧠 去年以为 Apple Intelligence 会在过去的这一年大展拳脚,但其实 Apple 还是在做底层的框架协议,至于落地一直传闻想要通过合作或者收购其他 LLM 来实现。我能理解 Apple 站到了一个十字路口,下一步选择很重要。但去全球化日益明显的今天,Apple Intelligence 在各国的落地也受到诸多法律和监管方面阻碍 从我个人的角度来看,对 Apple Intelligence 的需求也不是太强烈,日常主要还是以电脑使用为主。因此,今年也不排除会继续选择国行。最后,eSIM 或许是接下来一年每个人都要考虑的问题,如果新机真的大规模砍掉双 nano-SIM 卡,变为单卡 + eSIM 的模式,应该怎么处理自己目前的多卡问题 ⌚️Apple Watch 系列 - Apple Watch Ultra 3 将搭载全新 S11 芯片,并支持 5G 网络连接,保留卫星通信功能,略微增大屏幕尺寸 - Apple Watch Series 11 预计延续 Series 10 的设计语言 - Apple Watch SE 3 也可能获得升级,重点是升级芯片 - 目前尚不清楚是否会引入血压监测功能 🎧AirPods - AirPods Pro 3 有望在下半年发布 - 有望取消背部的传统实体配对按键,同时为充电盒正面引入触控操作区 - 耳机盒将变得更小 - 引入心率监测、体温监测等健康功能 - 实时翻译功能可能无法随硬件首发一同提供 之前通过 AC+ 更换的越南产 AirPods Pro 一代,已经快要罢工了,因此我迫切地等待第三代的发布 👀 今年的传闻大致如上所述,期待 iPad 和 Mac 更新的朋友或需要等更迟一些的发布会了。随着年龄增长,逐渐发现即便如 Apple 这样的品牌,也不能做对、做好每一件事,黄金时期的发展掩盖了很多问题,一旦停滞进入瓶颈期便暴露无遗。不管怎样,我还是很怀念那个爆料没有这么发达、发布会还是实时直播的年代 🔗 附上一些国内外媒体长文前瞻:Bloomberg | 9to5Mac | MacRumors | The Verge | sspai * 以上所有前瞻信息来自网络和爆料人,均在早晚报出现过,不一一列举来源。请以最终发布会结果为准,欢迎大家届时进群 @NewlearnerGroup 和我们一同观看 🍿️ 频道:@NewlearnerChannel

Hashtags

結果

38件の類似投稿が見つかりました

検索: #asyncio

当前筛选 #asyncio清除筛选
djangoproject

@djangoproject · Post #96 · 2016/07/11 12:16

https://docs.python.org/3/library/asyncio-task.html#asyncio.run_coroutine_threadsafe #asyncio.run_coroutine_threadsafe(coro, loop) Submit a coroutine object to a given event loop. Return a concurrent.futures.Future to access the result.

Hashtags

djangoproject

@djangoproject · Post #75 · 2016/06/28 10:29

https://docs.python.org/3/library/asyncio-eventloop.html The event loop is the central execution device provided by #asyncio. It provides multiple facilities, including: Registering, executing and cancelling delayed calls (timeouts). Creating client and server transports for various kinds of communication. Launching subprocesses and the associated transports for communication with an external program. Delegating costly function calls to a pool of threads.

Hashtags

djangoproject

@djangoproject · Post #337 · 2017/05/09 08:28

http://blog.povilasb.com/posts/python-asyncio-vs-nginx-performance/ While I was playing with Python #asyncio I got interested in how well it performs serving data over TLS compared to #Nginx. So I implemented a small HTTPS server with asyncio:

djangoproject

@djangoproject · Post #152 · 2016/09/03 20:18

https://glyph.twistedmatrix.com/2014/02/unyielding.html As we know, #threads are a bad idea, (for most purposes). Threads make local reasoning difficult, and local reasoning is perhaps the most important thing in software development. With the word “threads”, I am referring to shared-state multithreading, despite the fact that there are languages, like Erlang and Haskell which refer to concurrent processes – those which do not implicitly share state, and require explicit coordination – as “threads”. #asyncio

djangoproject

@djangoproject · Post #311 · 2017/04/25 11:59

http://programtalk.com/python-examples/aiohttp.web.Application/?ipage=1 Here are the examples of the python api #aiohttp.web.Application taken from open source projects. By voting up you can indicate which examples are most useful and appropriate. #asyncio#learn

djangoproject

@djangoproject · Post #268 · 2017/02/26 05:52

https://pawelmhm.github.io/asyncio/python/aiohttp/2016/04/22/asyncio-aiohttp.html 👌Making 1 million requests with python -#aiohttp Apr 22, 2016 - by Paweł Miech - about: #asyncio, aiohttp, #python In this post I’d like to test limits of python aiohttp and check its performance in terms of requests per minute. Everyone knows that asynchronous code performs better when applied to network operations, but it’s still interesting to check this assumption and understand how exactly it is better and why it’s is better. I’m going to check it by trying to make 1 million #requests with aiohttp client. How many requests per minute will aiohttp make? What kind of exceptions and crashes can you expect when you try to make such volume of requests with very primitive scripts? What are main gotchas that you need to think about when trying to make such volume of requests?

djangoproject

@djangoproject · Post #319 · 2017/04/29 07:54

https://github.com/aio-libs/aiobotocore Async client for amazon services using #botocore and #aiohttp/#asyncio. Main purpose of this library to support amazon s3 api, but other services should work (may be with minor fixes). For now we have tested only upload/download api for s3, other users report that SQS and Dynamo services work also. More tests coming soon.

djangoproject

@djangoproject · Post #98 · 2016/07/11 12:22

https://docs.python.org/3/library/asyncio.html #asyncio #Asynchronous programming is more complex than classical “#sequential” programming: see the Develop with asyncio page which lists common traps and explains how to avoid them. Enable the debug mode during development to detect common issues.

djangoproject

@djangoproject · Post #287 · 2017/04/04 21:04

http://stackoverflow.com/questions/32054066/python-how-to-run-multiple-coroutines-concurrently-using-asyncio how to run multiple #coroutines#concurrently using #asyncio? You can use #asyncio.async() to run as many #coroutines as you want, before executing blocking call for starting event loop.

前へ1ページ / 4ページ中次へ