CHEAPWINDOWS，微信小程序的出现会让Hybrid？
原文：https://www.interaction-design.org/literature/article/native-vs-hybrid-vs-responsive-what-app-flavour-is-best-for-you
At some stage, during the design of your mobile app, you’re going to have to make a decision about how you will develop the app. Your choices include native apps, hybrid apps and responsive web sites and the decision you make will affect the final product. Learning to make the right decision requires understanding the way each type of development works and how it affects the final product.
There are three main options for creating a mobile app. You can create a native app, a hybrid app or a mobile responsive website which offers similar functionality to an app. Each option has its advantages and disadvantages and it’s important to understand these in detail before committing to a particular development path. The path you choose is likely to be informed by the resources available to you and what you’re trying to achieve.
What is a Native App?Author/Copyright holder: 3Qi Labs Inc. Copyright terms and licence: All rights reserved. Img source
A native app is designed to run on a specific mobile operating system. It won’t run on other mobile operating systems. So, for example, if you were going to develop a native app for iOS you’d do the development in Swift.
The biggest advantages to native apps are that they can normally access all the functionality of the chosen device easily and that they are more likely, if developed properly, to run without error on the device.
However, this comes with a trade-off. A native app cannot be run on a device which doesn’t utilize the same operating system. That means if you want your app to run on Windows, iOS 7, and Android – you’re going to have to develop the app 3 times, once for each operating system. This can make the development process both slower and more expensive.
Many companies will develop their app for a single operating system when they choose the native route. If the app is successful in that environment; they will then go back and recreate it for other operating systems. It’s worth noting that at this moment in time – iOS 7 apps are, generally, more profitable than apps released for other environments.
What is a Hybrid App?A hybrid app is designed to work on multiple platforms. It’s written using a single standard code language (such as C# or a combination of HTML5 and Javascript) and then compiled to be executed on each platform. Device specific interactions will normally be managed by the use of plugins for that operating system.Author/Copyright holder: Salesforce.com,inc. Copyright terms and licence: All rights reservedImg source
The biggest advantage of hybrid apps is that they enable support for multiple operating systems at a more cost effective price point than developing multiple native apps. Users, as long as the development is done well, will not normally be able to distinguish whether an app is native or hybrid. In fact users, in general, don’t care about how your app is developed – they just care if it works on their device and does what they expect it to do.
There are disadvantages to hybrid app development. It can present serious challenges if the app requires complex interaction from the device – there’s a limit to what plugins can achieve on this front. The costs of supporting a hybrid application may be higher than the costs of supporting a native application too.
What is a Responsive Website?A responsive website can deliver similar functionality to an app. In fact, with a little creativity you can keep the differences to a minimum and ensure that the home page jumps straight into a “full screen” display.
Author/Copyright holder: Serge Kij .Copyright terms and licence: CC BY-NC 2.0
Responsive websites will be developed using HTML 5 and Javascript. Typically developers will take a “mobile first” approach to development with the mobile version offering a simpler and pared down experience to the desktop version of the same site.
The biggest drawbacks to using responsive websites are firstly that the app cannot be distributed through an app store; this can be a deal breaker if you’re looking to monetize downloads of your app. Secondly, there’s the issue that the user will need constant connectivity to make use of the website. This may not be a problem in highly developed markets where mobile broadband is near ubiquitous but can be a serious issue in developing markets.
It’s worth noting that while, at this moment in time, apps appear to be the driving force behind the mobile web – there is room for serious disruption. With the average user already using up to 30 apps a month and with more than 250,000 apps being released a year; there may come a point of overload from a user’s perspective. At that point, it is possible that if there are enough well designed mobile websites – that users will move away from apps and back to browsing and individual sites to provide their online experience. Then, apps might just become “launchers” of mobile websites.
The Take AwayThe mobile web offers significant opportunity to entrepreneurs. Mobile apps are relatively cheap and easy to produce. Choosing the right development approach is critical to delivering the right experience. By understanding the differences between hybrid, native and responsive – you can make the right decision for your project.
Keywords:Responsive, Native, Hybrid, App Development
Related Concepts:UX Design, App Development, Responsive Websites
References:Learn about the differences between adaptive design and responsive design:https://www.interaction-design.org/literature/article/adaptive-vs-responsive-design
Examining the case for native apps for smartwatches -http://thenextweb.com/insider/2015/09/26/native-apps-for-watchos-2-arent-perfect-but-theyre-far-better-than-what-we-had/
A punchier comparison of native vs hybrid - http://www.netxtra.net/insights/web-apps-vs-native-apps-fight-fight-fight/
Hero Image: Author/Copyright holder: Jessica Zollman. Copyright terms and licence: CC BY-SA 3.0
文章来源： https://www.interaction-design.org/literature/article/native-vs-hybrid-vs-responsive-what-app-flavour-is-best-for-you
前端为什么有人说要关注Serverless？
Serverless 的概念或应用场景我们以前讲过很多，这里不再冗述。概括性地讲 —— Serverless 的内涵就是对全部底层资源和运维工作的封装，让开发者更专注于业务逻辑。
完备的基础性文章推荐阅读这两篇：
Serverless 基本概念入门 https://www.toutiao.com/i6794284259960947203/ Serverless 的运行原理与组件架构https://www.toutiao.com/i6794713387138810371/本回答尝试从出圈的角度，以更接地气的方式聊聊 Serverless。
先讲个故事，疫情期间在家办公，大家肯定没少做饭，自己做饭才体会到家务不易，你需要：买菜买锅、处理食材、煎炒蒸煮、最后洗碗。
听起来是不是还挺像软件开发？你需要有云服务器、后台开发、前端开发、还有运维。你想着，要是我能只翻两下铲子，然后就能吃饭那该多好。
巧了，有一些商家就提供了这种服务，帮你准备好了锅、洗干净的食材、专业的厨师指点，你只要进去翻两下铲子，就能煮一顿精美的饭食！而且不用洗碗。
对应到软件开发，开发者只需要关注业务逻辑（炒菜），而底层资源和运维工作（锅碗瓢盆、食材处理）都不用再操心。终于到了正式复工的时间，你不用再自己做饭，新买的厨具就闲置了。你回想起昨天在商圈里的美好体验，家里的厨具要是也在能用的时候付费，不用不收费多好啊。
嘿嘿，Serverless 亦如此，按水电般计费，当部署在其上的函数运行时才收费。所以回到题目中来，Serverless 本身是云计算相关技术，并非前端技术，为何前端要关注 Serverless 呢？
答案很简单 —— 解放生产力。
你的厨房里已经准备好了所有厨具和处理好的食材，你现在只需要关心火候认真炒菜，成为美食博主指日可待。也就是文首所说的 —— 开发者能更专注于业务逻辑，其他的底层资源和运维工作已经全部封装好了。
Talk is cheap, show you the code先给大家展示一个基于 Serverless 构建 docsify 文档的 demo。
这个三分钟的 demo，不仅完成了 docsify 发布代码的上传，还包括了腾讯云对象存储 COS 资源的申请和配置。要知道，demo 作者本身并非前端工程师，甚至不是开发者。
原文链接：https://www.toutiao.com/i6795809244907045379/再进一步，我们演示个 Fullstack Application。该项目借助 Serverless 社区现有的 @serverless/tencent-express 和 @serverless/tencent-website 组件来完成。
下面是一张简单的组件依赖图：
在开始所有步骤前，需执行 命令，全局安装 。1. 准备
新建项目目录 ，在该项目目录下新增 和 目录。然后新增 和 配置文件，项目目录结构如下：
├── README.md // 项目说明文档├── api // Restful api 后端服务├── dashboard // 前端页面├── .env // 腾讯云相关鉴权参数：TENCENT_APP_ID，TENCENT_SECRET_ID，TENCENT_SECRET_KEY└── serverless.yml // serverless 文件2. 后端服务开发
进入目录 `api`，新增 `app.js` 文件，编写 `express` 服务代码，这里先新增一个路由 `/`，并返回当前服务器时间：```jsconst express = require('express')const cors = require('cors')const app = express()app.use(cors())app.get('/', (req, res) => {res.send(JSON.stringfy({ message: `Server time: ${new Date().toString()}` }))})module.exports = app```3. 前端页面开发
本案例使用的是 `Vue.js` + `Parcel` 的前端模板，当然你可以使用任何前端项目脚手架，比如 Vue.js 官方推荐的 [Vue CLI](https://github.com/vuejs/vue-cli) 生成的项目。进入 `dashboard` 目录，编写入口文件 `src/index.js`:```js// 这里初始是没有 env.js 模块的，第一次部署后会自动生成require('../env')const Vue = require('vue')module.exports = new Vue({el: '#root',data: {message: 'Click me!',isVisible: true,},methods: {async queryServer() {const response = await fetch(window.env.apiUrl)const result = await response.json()this.message = result.message},},})```4. 配置
前后端代码都准备好了，再简单配置下 `serverless.yml` 文件了：```yamlname: fullstack-application-vuefrontend:component: '@serverless/tencent-website'# inputs 为 @serverless/tencent-website 组件的输入# 具体配置说明参考：https://github.com/serverless-components/tencent-website/blob/master/docs/configure.mdinputs:code:src: distroot: frontendhook: npm run buildenv:# 下面的 API服务部署后，获取对应的 api 请求路径apiUrl: ${api.url}api:component: '@serverless/tencent-express'# inputs 为 @serverless/tencent-express 组件的输入# 具体配置说明参考：https://github.com/serverless-components/tencent-express/blob/master/docs/configure.mdinputs:code: ./apifunctionName: fullstack-vue-apiapigatewayConf:protocol: https```5. 部署
部署时，只需要运行 `serverless` 命令就行，当然如果你需要查看部署中的 `DEBUG` 信息，还需要加上 `--debug` 参数，如下：```$ serverless# or$ serverless --debug```最后终端会 `balabalabala~`, 看到绿色的`done`就行了。
既然是全栈，怎么少得了数据库的读写呢？
读者可移步作者原文继续阅读：《基于 Serverless Component 的全栈解决方案》https://www.toutiao.com/i6799170151217365507/
从这两个小项目中已然得解 —— Serverless 的内涵就是对全部底层资源和运维工作的封装，让开发者更专注于业务逻辑。
写在后面题主在问题描述中的思考很有价值，其实 Serverless 的确不是一个前端的概念，甚至都不是为了解决前端的问题而出现的，它其实就是云计算发展的必经过程。
就好比，底层语言的发展趋势肯定是高级语言。而高级语言肯定也会封装起底层的硬件，让程序员无需关心硬件的状态，专注编码。
十年前编程还是比较难的高级学科，如今小学已经开展编程课程。其实就是因为程序语言的发展，让编程变得更加友好。
同样地，Serverless 的出现和完善，也是让软件开发变得更加友好。不仅前端需要关注 Serverless，它可能属于每一种类型的应用开发者。
而这会淘汰后端吗？并不会！
后端会更聚焦于业务逻辑、数据处理、算法策略等更专精的事情。
汽车的出现让马车夫成为了司机，技术在变革，工程师也将成长。
kernel一定会coding吗？
结论：用反问句作答：“不会coding，看得懂kernel吗？”
前言一张数学考卷，不是把最后一题最难的20分做出来，就算征服了整张考卷。
你会一道最难的题，真觉得剩下的80%，就是小菜一碟？
kernel不是编程天花板kernel在不断地增长，torvalds大神也投入很多时间维护内核。全世界的开发者在用智慧贡献自己的代码。看看git多么地繁忙。
代码文件目录。
内核里有许多惊为天人的巧妙设计，每个细节都值得推敲，每段注释又是一段故事。
用漫画看看内核里都有些啥？
各司其职，还有汪汪，还有文件系统的一个个抽屉，形象吧。
好了，外行看个热闹，内行看个门道。相信你一定会注意到一些精巧的小细节。下面是细节剖析。
一切的基础，要从文件存取开始。PID=421的进程在读文件。还有一个看门狗。
这一桌子上，在文件系统的上层，是一堆进程，等着上饭。左边有一个幼儿园老师一样的小企鹅，指挥者各个进程听话。
PID=1341的进程守护者80端口，这个是http服务。也就是apache http web服务器。
注意到这个半垂的21端口吗，ftp，早就不安全，而且也老旧了。
酷酷的22端口，是SSH服务监听的端口，稳定安全而又耍酷。
注意到楼梯口这个指示牌了吗，它指示这是去“文件系统File System”的入口。
房间里这个忙碌的小企鹅是cron，整个系统时间调度都是它在跑。
还有那些 pipeline 用于连接不同的功能。
还有这个喝的晕乎乎的wine，要不少需要运行windows应用，它也可以休息了。
用户面对的，是一个个终端。linux是真正的多用户系统。看，这个大屏幕多么繁忙。
还有跑偏了的zombie进程，四处游荡。
怎么样，经过漫画一看，是不是觉得linux有趣的多了？
掌握工具，创造工具都会编码了，还有什么能够阻挡你对自由的向往？
想证明你的实力吗，linus大神说了：
Talk is cheap, show me the code.甭嘚啵嘚，来段代码看看。而开源社区的打什么，也真的是在用行动，用代码践行着这个格言。所以，内核拥有者源源不断的澎湃动力。
比如觉得内核里
init
管理系统进程调度实在不便，编写出来的脚本文件很麻烦，能不能化繁从简呢？有的。Lennart Poettering为了解决这个混沌状态，开发了systemd。在centos7以后标配为系统发行版的任务调度应用。下面是systemd套件的架构功能图。
是不是看到很励志啊？有想法，有能力，有思维，大胆地给内核贡献代码吧。
全世界数以亿计的计算机运行着你写的代码，成就感能不爆棚吗？
Come on！
结语学内核而不止于内核。
王安石说：“读经则不足以知经”。
只有你博览群书，开阔眼界之后，再回来kernel看风景，相信你“坐看云起时”，别有一番领悟。
我是@程序员小助手，持续分享编程与程序员成长相关的内容，欢迎关注~~字母在英文单词中的发音规律？
26个字母在单词中的发音规律（补充读音）：
元音字母在单词中，在后面关门的情况下，还有一些常见的特殊读音：
a在ny前读“ [e] ”（短音），如：any, many, anyone, anything
a在w或wh后读“ [ɒ]”（短音，嘴形较大），如：wash, want, watch, what
a在s, ss, st前读“[ɑː] ”（长音），如：past, fast, glass, pass, class, basket
i在某些单词中读“ [iː]”（长音），如：police, machine
o在m, n, v, th前读“ [ʌ] ”（短音），如：love, son, some, mother, other
u在某些单词中读“[u:]”（长音），如：June, ruler
u在不少单词中读“[ʊ] ”（短音，想象一下公鸡的叫声，但此音与汉语拼音中对“喔”的标音并不一样，应该说是介于“哦”与“务”之间的一个音，口形比“哦”要小，但比“务”要大），如：put, pull, push, ful
元音字母后面跟着辅音字母w，也像靠着小树r一样，并不视为后面是关门的，而有其特殊的读音：
aw读“ [ɔː]”（长音，嘴形较小），如：draw, law
ew读“[uː]”（长音），如：few, new, newspaper, knew
ew也读“[uː]”（长音）, threw, drew, flew, grew
ow读“ [əʊ]”，如：slow, blow, show, snow, threw, window, yellow, borrow, tomorrow
ow也读“[aʊ]”， 如now, how, cow, down, brown
元音字母组合在单词中的读音规律：
ea 读“[iː]”（长音），如：team, clean, sea, tea, east, cheap, easy, speak, season, read
ea 读“[e]”（短音），如：head, bread, ready, weather, health
ea读“ [ɪə]”，如：idea, real, really
ea 读“ [eɪ]”，如：great, break
ee 读“[iː]”， 如：see, bee, free, sheep, feel, meet, need, green, asleep
ai 读“[eɪ] ”，如：train, rain, wait, waiter
ay读“[eɪ]”，如：today, away, stay, may, say, play
ei读“ [eɪ]”，如：eight, weight, eighteen
ey读“ [eɪ]”，如：they, hey,obey
ou 读“[aʊ]”，如：ground, round, around, out, mouse, blouse
ou 读“[ʌ]”（短音），如：young, country, touch, enough, double
ue 读“ [uː]”（长音），如：blue, true
oo 读“[uː]”（长音），如：zoo, soon, food（此单词属例外）, cool, tooth, noon, fool
oo 在字母k, d前，读“ [ʊ] ”（短音），如：cook, look, took, good, foot（此单词属例外）, wood
oa读“[əʊ] ”，如：coat, goat, soap, boat
oy 读“[ ɔi ]”（注意，此中的“哦”不是长音而是短音的“哦”，嘴形较大），如：boy, joy, toy, enjoy
oi读“[ ɔi ]”（注意，此中的“哦”不是长音而是短音的“哦”，嘴形较大），如：oil, coin, toilet,
ie 读“[ i: ]”，如：piece, thief, field
ie读“ [aɪ]”，如：lie, die, tie
au 读“ [ɔː]”（长音的“哦，嘴形小），如：autumn, daughter, August
ui 读“[uː] ”（长音），如：fruit, juice, suit
元音字母与与辅音字母组合在单词中的读音规律：
air读“[eə]”，如：chair, hair, air, pair, fair
are读“[eə]”，如：care, careful, hare
ere读“[eə]”，如：where, there
ear读“[eə]”，如：wear, pear, bear
ear读“ [ɪə]”，如：near, hear, clear, dear, nearly
ear读“[ɜː]”（长音），如：early, earth, learn, heard
al 读“ [ɔː]”（长音的“哦”，嘴形小），如：call, walk, talk, tall, small
al 读“ ['ɔːl] ”（参考前面的关于字母L读“噢”音的解释），如：also, always, already, almost
aw 读“[ɔː]”（长音的“哦”，嘴形小），如：draw, law, paw, jaw
ore读“[ɔː]”（长音的“哦”，嘴形小），如：before, more, score
oor读“[ɔː]”（长音的“哦”，嘴形小），如：door, floor
our读“[ɔː]”（长音的“哦”，嘴形小），如：four, fourth, course, pour
our读['aʊə]”，如：hour, our
ow读“ [əʊ]”，如：slow, blow, show, snow, throw, window, yellow, borrow, tomorrow
ow “ [aʊ] ”，如：now, how, cow, down, brown
ew读“ [juː]”，如：few, knew, news, newspaper
ew读“ [uː]”，如：threw, drew, flew, grew
tion读“[ˈʃən]”，如：station, action, operation, dictionary
dge 读“[dʒ]”，如：bridge, fridge, judge
igh读“ [aɪ] ”，如：light, right, night, bright, high, fight
ough读“[ɔː]”（长音的“哦”，嘴形小），如：bought, brought, thought
augh读“[ɔː]”（长音的“哦”，嘴形小），如：daughter, taught, caught
ind读“ [aɪnd]”，如：kind, find, mind, behind
old读“ [əʊld]”，如：old, cold, told, sold, hold
连衣裙的英语的复数？
连衣裙的英文为dress，其复数形式是加es，即dresses。dress可作名词和动词，作为名词时，含义为“连衣裙”、“衣服”；作为动词时，含义有“穿衣服”、“穿…的服装”。
dress的基本释义及用法介绍
1、作为名词，意为连衣裙;衣服。
例句：I'll need to iron that dress before I can wear it.
我得先把那件连衣裙烫平再穿。
I saw the dress I wanted in the window.
我在橱窗里看到了我想买的连衣裙。
She's wearing a dress like mine.
她穿的连衣裙和我的相似。
She bought a dress pattern and some material.
她买了一幅衣服纸样和一些衣料。
She was a little coy about how much her dress cost.
她对她那件衣服花了多少钱有点吞吞吐吐。
I got this dress cheap in a sale.
这件衣服是我在大减价时便宜买的。
She showered and dressed and went downstairs.
她冲了澡，穿上衣服下楼去了。
2、作为动词，意为穿衣服;给(某人)穿衣服;穿…的服装;穿正式服装。
例句：He went into his bedroom to get dressed.
他进卧室穿衣服。
The boys chatted gaily while they dressed.
男孩子们边穿衣服边兴高采烈地闲聊。
I can't go to the door ─ I'm not dressed yet.
我没法去开门——我还没穿好衣服呢。
We are going to dress the baby in new clothes and take her to the park.
我们要给小孩子穿上新衣服，带她到公园去。
The day before my father died, my mother and I had gone shopping for a prom dress.
父亲去世的前一天，我和妈妈去买参加班级舞会穿的服装。
Do they expect us to dress for dinner?
他们要求我们穿正式服装赴宴吗？
