p*2
2 楼
all I know is:
after learning Haskell in the evenings/weekends for a few months, reading
language feature tutorials and writing a personal project, I understand
enough about enough typeclasses / GHC extensions / etc to write somewhat
abstract Haskell code without type errors, or to read those type errors and
grok them. the abstractions increase modularity, without decreasing
readability.
after the same time/effort with Scala, I know nothing about Scala's types,
or its errors.
after learning Haskell in the evenings/weekends for a few months, reading
language feature tutorials and writing a personal project, I understand
enough about enough typeclasses / GHC extensions / etc to write somewhat
abstract Haskell code without type errors, or to read those type errors and
grok them. the abstractions increase modularity, without decreasing
readability.
after the same time/effort with Scala, I know nothing about Scala's types,
or its errors.
b*a
3 楼
not yet
e*o
4 楼
原作者不会Java吧
and
【在 p*****2 的大作中提到】
: all I know is:
: after learning Haskell in the evenings/weekends for a few months, reading
: language feature tutorials and writing a personal project, I understand
: enough about enough typeclasses / GHC extensions / etc to write somewhat
: abstract Haskell code without type errors, or to read those type errors and
: grok them. the abstractions increase modularity, without decreasing
: readability.
: after the same time/effort with Scala, I know nothing about Scala's types,
: or its errors.
and
【在 p*****2 的大作中提到】
: all I know is:
: after learning Haskell in the evenings/weekends for a few months, reading
: language feature tutorials and writing a personal project, I understand
: enough about enough typeclasses / GHC extensions / etc to write somewhat
: abstract Haskell code without type errors, or to read those type errors and
: grok them. the abstractions increase modularity, without decreasing
: readability.
: after the same time/effort with Scala, I know nothing about Scala's types,
: or its errors.
H*0
5 楼
目前有人收到吗?希望这次能收到!
f*6
7 楼
还没收到邮件
r*i
9 楼
http://new.chinesehighway.com/user/workspace/main.do
已经显示
申请获得中国驻美大使馆批准!
已经显示
申请获得中国驻美大使馆批准!
H*0
13 楼
J-1签证豁免申请状态
申请获得中国驻美大使馆批准!
愿整日辛苦等待的大家好运🍀
申请获得中国驻美大使馆批准!
愿整日辛苦等待的大家好运🍀
f*6
15 楼
同在网上看到“申请获得中国驻美大使馆批准!”
再跟各位战友确认一下,当我点击“J-1签证豁免”标题栏的时候,就显示“申请成功
,您的申请已经成功递交!审理过程中如有问题我们会通过E-mail与您联系。”没有以
前的时间状态了。
请问大家都是这样子的吗?因为大使馆的人曾告诉我要等两个月,没想到一个月就批了
O(∩_∩)O~~
再跟各位战友确认一下,当我点击“J-1签证豁免”标题栏的时候,就显示“申请成功
,您的申请已经成功递交!审理过程中如有问题我们会通过E-mail与您联系。”没有以
前的时间状态了。
请问大家都是这样子的吗?因为大使馆的人曾告诉我要等两个月,没想到一个月就批了
O(∩_∩)O~~
K*y
17 楼
和你的状态一样,点进去也是显示“申请成功
,您的申请已经成功递交!审理过程中如有问题我们会通过E-mail与您联系。”
估计很快能收到NOL发出的邮件了
: 同在网上看到“申请获得中国驻美大使馆批准!”
: 再跟各位战友确认一下,当我点击“J-1签证豁免”标题栏的时候,就显示“申
请成功
: ,您的申请已经成功递交!审理过程中如有问题我们会通过E-mail与您联系。”
没有以
: 前的时间状态了。
: 请问大家都是这样子的吗?因为大使馆的人曾告诉我要等两个月,没想到一个月
就批了
: O(∩_∩)O~~
【在 f********6 的大作中提到】
: 同在网上看到“申请获得中国驻美大使馆批准!”
: 再跟各位战友确认一下,当我点击“J-1签证豁免”标题栏的时候,就显示“申请成功
: ,您的申请已经成功递交!审理过程中如有问题我们会通过E-mail与您联系。”没有以
: 前的时间状态了。
: 请问大家都是这样子的吗?因为大使馆的人曾告诉我要等两个月,没想到一个月就批了
: O(∩_∩)O~~
,您的申请已经成功递交!审理过程中如有问题我们会通过E-mail与您联系。”
估计很快能收到NOL发出的邮件了
: 同在网上看到“申请获得中国驻美大使馆批准!”
: 再跟各位战友确认一下,当我点击“J-1签证豁免”标题栏的时候,就显示“申
请成功
: ,您的申请已经成功递交!审理过程中如有问题我们会通过E-mail与您联系。”
没有以
: 前的时间状态了。
: 请问大家都是这样子的吗?因为大使馆的人曾告诉我要等两个月,没想到一个月
就批了
: O(∩_∩)O~~
【在 f********6 的大作中提到】
: 同在网上看到“申请获得中国驻美大使馆批准!”
: 再跟各位战友确认一下,当我点击“J-1签证豁免”标题栏的时候,就显示“申请成功
: ,您的申请已经成功递交!审理过程中如有问题我们会通过E-mail与您联系。”没有以
: 前的时间状态了。
: 请问大家都是这样子的吗?因为大使馆的人曾告诉我要等两个月,没想到一个月就批了
: O(∩_∩)O~~
z*e
20 楼
其他fp语言比较纯粹,没有oop部分
除了clojure都不运行在jvm上,自然弄起来容易
但是scala强就强在它什么都有,自然弄起来就非常痛苦
花很多时间在scala上,投入成本高,见效慢
最快见效也是在面试时候加点分,但是现在说光靠scala要想弄到工作
也难,现在多数都是java程序员的一个bonus
不像swift,马上就可以写出东西来,投放到app store里面去
很快就有收益
除了clojure都不运行在jvm上,自然弄起来容易
但是scala强就强在它什么都有,自然弄起来就非常痛苦
花很多时间在scala上,投入成本高,见效慢
最快见效也是在面试时候加点分,但是现在说光靠scala要想弄到工作
也难,现在多数都是java程序员的一个bonus
不像swift,马上就可以写出东西来,投放到app store里面去
很快就有收益
z*e
22 楼
看scala代码真是生不如死,我自己写的都看不懂
不知道老头是怎么看懂的,估计它压根就没看
兼容性也做得不好,vert.x上现在代码都转回ruby和groovy了
我看公司里脚本也多数转向jruby和groovy
python,scala向后兼容做得差,导致代码生命周期偏短
保险起见,先不用了,怕以后升级出问题
不知道老头是怎么看懂的,估计它压根就没看
兼容性也做得不好,vert.x上现在代码都转回ruby和groovy了
我看公司里脚本也多数转向jruby和groovy
python,scala向后兼容做得差,导致代码生命周期偏短
保险起见,先不用了,怕以后升级出问题
u*i
23 楼
我四月初通过的初审,按理说应该也是这月初的这批,可是现在系统上还没有显示申请
成功。
成功。
r*i
25 楼
关于您申请免除回国服务两年义务的事宜,业经我处审核批准,并于2016年07月06日向
美国国务院所属的WAIVER REVIEW DIVISION 正式发出“不持异议信”。至此,关于您
申办豁免事宜的中方手续全部办理完毕。
美国国务院所属的WAIVER REVIEW DIVISION 正式发出“不持异议信”。至此,关于您
申办豁免事宜的中方手续全部办理完毕。
t*r
28 楼
看了这个帖子的回复,
结论是:
学好java 赚钱发财 娶媳妇 抱娃抱妹子才是正经事
结论是:
学好java 赚钱发财 娶媳妇 抱娃抱妹子才是正经事
p*2
30 楼
In my experience, Scala's is much more complicated. It has to be, in order
to interoperate with Java, include object-oriented programming, and
therefore use a lot of subtyping and attempt to impose principle on it.
Scala seems to be a bazaar in which concepts from Java and Haskell collide,
and there's even some Erlang thrown in (the actor model). Type-wise, these
sub-languages don't always get along well. For what it must do, Scala does a
good job. The problem is that its mandatory first-class support of Java's
type system (with, among other things, its wonky generics) imposes a ton of
complexity. Covariance and contravariance are regarded as advanced features
in Haskell and Ocaml, but in Scala you have to confront them just to
understand type signatures of basic operations.
【在 t**r 的大作中提到】
: 看了这个帖子的回复,
: 结论是:
: 学好java 赚钱发财 娶媳妇 抱娃抱妹子才是正经事
to interoperate with Java, include object-oriented programming, and
therefore use a lot of subtyping and attempt to impose principle on it.
Scala seems to be a bazaar in which concepts from Java and Haskell collide,
and there's even some Erlang thrown in (the actor model). Type-wise, these
sub-languages don't always get along well. For what it must do, Scala does a
good job. The problem is that its mandatory first-class support of Java's
type system (with, among other things, its wonky generics) imposes a ton of
complexity. Covariance and contravariance are regarded as advanced features
in Haskell and Ocaml, but in Scala you have to confront them just to
understand type signatures of basic operations.
【在 t**r 的大作中提到】
: 看了这个帖子的回复,
: 结论是:
: 学好java 赚钱发财 娶媳妇 抱娃抱妹子才是正经事
z*e
32 楼
话说class算不算是一种type?
应该算吧?
type可以包括有int, function和class这些
应该算吧?
type可以包括有int, function和class这些
p*2
33 楼
Scala's disjoint part has polymorphic sub-typing and implicit dictionaries.
Haskell's disjoint part has first-class type classes, type-level functions,
full type inference, and many other neat little tweaks. The intersection is
a higher-kinded type system with first-class functions.
Scala's part of the intersection, for a list of reasons that include JVM
type erasure, issues combining higher-kinded types with polymorphic sub-
typing, and certain implementation choices, is partially "broken" in that
its higher-kinded type support is weak enough to make its Haskell-style use
troubled because it doesn't curry types. Some detail: Disadvantages of Scala
type system versus Haskell? This necessitates ingenious workarounds like
Using scalaz.Unapply and fingers-crossed hoping that the implicits don't get
messed up.
To Michael O. Church's perfectly fair point about variance annotations,
people wrestling with Scala's type system tend to come to the conclusion
that given the higher-kinded inference limitations described above, using
variance in Scala is not worth the trouble, and you're better off just
leaving everything invariant. Paul Philips has been working on a fresh take
on Scala collections that doesn't necessitate variance: paulp/psp-std.
Written 7h ago.
【在 z****e 的大作中提到】
: 话说class算不算是一种type?
: 应该算吧?
: type可以包括有int, function和class这些
Haskell's disjoint part has first-class type classes, type-level functions,
full type inference, and many other neat little tweaks. The intersection is
a higher-kinded type system with first-class functions.
Scala's part of the intersection, for a list of reasons that include JVM
type erasure, issues combining higher-kinded types with polymorphic sub-
typing, and certain implementation choices, is partially "broken" in that
its higher-kinded type support is weak enough to make its Haskell-style use
troubled because it doesn't curry types. Some detail: Disadvantages of Scala
type system versus Haskell? This necessitates ingenious workarounds like
Using scalaz.Unapply and fingers-crossed hoping that the implicits don't get
messed up.
To Michael O. Church's perfectly fair point about variance annotations,
people wrestling with Scala's type system tend to come to the conclusion
that given the higher-kinded inference limitations described above, using
variance in Scala is not worth the trouble, and you're better off just
leaving everything invariant. Paul Philips has been working on a fresh take
on Scala collections that doesn't necessitate variance: paulp/psp-std.
Written 7h ago.
【在 z****e 的大作中提到】
: 话说class算不算是一种type?
: 应该算吧?
: type可以包括有int, function和class这些
z*e
34 楼
我看到的说法说是算high kind type
但是关键字type跟class还是分离的
可以把一个class定义成某一个type
其意思就是一个alias,我就无脑记这个了
,
is
use
Scala
【在 p*****2 的大作中提到】
: Scala's disjoint part has polymorphic sub-typing and implicit dictionaries.
: Haskell's disjoint part has first-class type classes, type-level functions,
: full type inference, and many other neat little tweaks. The intersection is
: a higher-kinded type system with first-class functions.
: Scala's part of the intersection, for a list of reasons that include JVM
: type erasure, issues combining higher-kinded types with polymorphic sub-
: typing, and certain implementation choices, is partially "broken" in that
: its higher-kinded type support is weak enough to make its Haskell-style use
: troubled because it doesn't curry types. Some detail: Disadvantages of Scala
: type system versus Haskell? This necessitates ingenious workarounds like
但是关键字type跟class还是分离的
可以把一个class定义成某一个type
其意思就是一个alias,我就无脑记这个了
,
is
use
Scala
【在 p*****2 的大作中提到】
: Scala's disjoint part has polymorphic sub-typing and implicit dictionaries.
: Haskell's disjoint part has first-class type classes, type-level functions,
: full type inference, and many other neat little tweaks. The intersection is
: a higher-kinded type system with first-class functions.
: Scala's part of the intersection, for a list of reasons that include JVM
: type erasure, issues combining higher-kinded types with polymorphic sub-
: typing, and certain implementation choices, is partially "broken" in that
: its higher-kinded type support is weak enough to make its Haskell-style use
: troubled because it doesn't curry types. Some detail: Disadvantages of Scala
: type system versus Haskell? This necessitates ingenious workarounds like
相关阅读
mit有没有版面是讨论算法之类的给nod101一个最优化的实时分配车票座位的算法动态脚本适合做glue code, 静态语言适合做heavy lifting12306是什么意思给各位frontend developer一个确切的android定位吧其实板上还有几个臭皮匠的给篇做优化的例子,普及下这里有做ServiceNow的朋友吗?Re: 维密超模竟是编程高手:开发出近10个APP (转载)说得越多,越暴露出你们有些人不懂软件工程的本质为啥一定要实时?应改采取挂号的方式,每个定单挂个号,离线处理Node.js is not suitable for generic web projects唉,看来scala已经废了不知道为什么都在骂krill,我觉得他说的是实情啊Happy New Year!go真是好东西王银水平可能确实不高,比我差些请问我如何让这2个web服务协同工作?无缝集成那大家对这高中生写个app以$30M卖给Yahoo咋看发现ramdisk不错,多个进程通信用文件就可以了,简单