TGTGInsighttelegram intelligenceLIVE / telegram public index
← Find Blog👁发现博客

TGINSIGHT SIMILAR POSTS

查找相似内容

Source channel @FindBlog · Post #521 · 10月9日

静态网站悖论 个人网站的两种不同实现方式:一种是复杂的内容管理系统(CMS),另一种是简单的静态 HTML 文件。文章指出,尽管大多数普通用户倾向于使用复杂的解决方案(如 WordPress),但实际上,只有少数专业软件工程师能够选择更简单的静态网站。 via HackerNews 2024 10 09 前两天刚好听朋友说 square space 已经涨到了近乎搞笑的 $25 月费,做不用来盈利的个人博客实在难以 justify。这篇文章中吐槽得很在点子上: normal users are stuck with a bunch of greedy clowns that make them pay for every little thing, all while wasting ungodly amounts of computational power to render what could have been a static website in 99% of cases. 普通用户被困在了一群屁大点功能都要收费的贪婪小丑手里,与此同时浪费着人神共愤额度的算力来渲染 99% 的情况下都可以作为静态的网站。 当然原文中说的“只有少数专业软件工程师才能选择更简单的静态网站”略微夸张并不认同,因为静态站至少是比 self-host 的动态 CMS 少太多维护了。我的 backlog 里也一直躺了篇安利新手用静态站并拉踩 WP 的文,不过网上这种文已经有无数了也还是拦不住前赴后继往各种 CMS 的坑里冲的新手,觉得写了又有什么意义呢就还搁着没写。(当然迟早会像以前反复造的无数轮子一样被废话欲战胜的 but not today) #indieblog#newletter

Results

找到 4 条相似帖子

搜索 #processes

当前筛选 #processes清除筛选
Amazing Geography 🌍

@amazingeo · Post #647 · 2026/02/25 20:31

🌍 Submarine hydrothermal vents on the ocean floor release superheated water and minerals, fueling unique ecosystems powered by chemical energy instead of sunlight. ✨ #processes⚡#ocean⚡#ecosystems⚡#geography⚡#nature⚡#earth 👉subscribe Amazing Geography 👉more Channels ​

Amazing Geography 🌍

@amazingeo · Post #39 · 2025/08/13 00:12

🌍 Earth's crust is in constant motion due to convection currents—slow, swirling movement of hot rock deep below the surface. This drives plate movement, causing earthquakes and forming new land. ✨ #processes⚡#plate⚡#tectonics⚡#geology⚡#geography⚡#nature⚡#earth 👉subscribe Amazing Geography🌍

djangoproject

@djangoproject · Post #430 · 2017/09/02 03:23

https://docs.python.org/3/library/subprocess.html The #subprocess module allows you to spawn new #processes, connect to their input/output/error pipes, and obtain their return codes. This module intends to replace several older #modules and #functions. #python

djangoproject

@djangoproject · Post #290 · 2017/04/04 21:36

https://pymotw.com/3/asyncio/executors.html Combining Coroutines with Threads and Processes A lot of existing libraries are not ready to be used with #asyncio natively. They may block, or depend on concurrency features not available through the module. It is still possible to use those libraries in an application based on asyncio by using an #executor from #concurrent.futures to run the code either in a separate thread or a separate process. #Threads The #run_in_executor() method of the event loop takes an executor instance, a regular callable to invoke, and any arguments to be passed to the callable. It returns a Future that can be used to wait for the function to finish its work and return something. If no executor is passed in, a #ThreadPoolExecutor is created. This example explicitly creates an executor to limit the number of worker threads it will have available. #Processes A ProcessPoolExecutor works in much the same way, creating a set of worker #processes instead of threads. Using separate processes requires more system resources, but for computationally-intensive operations it can make sense to run a separate task on each CPU core. #learn